Fedora 37 hangs after graphical login
by Karlderletzte
Hello, since yesterday i do have a big problem.
After some updates and a succesfull reboot, i first could not login
anymore. Alsways a wrong password.
I solved this with resetting root password and my two user passwords.
Now i could login.
Root account works,
one user account (the empty one) also.
But my usually working account freezes, after i login.
If i login via terminal Ctrl-Alt-F3 it works.
So i think that something is crashed during the load after graphical
login.
How could i See, what is going on after graphical login? The different
steps and programs i mean. Any logfiles?
I know that one of the first thing is loading gdm? Or am i wrong?
Btw: i use wayland and GNOME. An update via dnf brings nothing.
Hope someone does have an idea.
Thanks
Jens
1 year, 3 months
FYI - Issues with kernel-6.0.17-200.fc36.x86_64 and KDE
by Go Canes
I had issues after updating to kernel-6.0.17-200.fc36.x86_64 this past
Sunday. Two dissimilar systems (a Dell XPS 15 laptop and a
scratch-built media PC) both locked-up hard when booting - never got
as far as the login screen. I thought I had some older systems that
were OK, but today I ran into issues with them - one had the login
screen, but locked-up with the black-and-white KDE/Plasma "splash"
screen (not sure what else to call it), and a 2nd locked-up before it
got that far. In both cases it was the first time trying to login
since the kernel update.
Reverting to 6.0.15-200.fc36.x86_64 made everything OK again.
FYI....
1 year, 3 months
koji
by Bill Cunningham
I will post this here since the test list is low traffic; I don't
believe it is OT. Is koji only used for the testers? I know fedpkg is
for development and there is a build system too called "Copr". I am only
interested in looking into testing. So to begin this would an interested
person look into koji? I posted something like this to a list before and
it wasn't answered so I assumed there was no interest or others were busy.
Is the only place to go to here concerning testing
docs.fedoraproject.org? Does anyone here do testing?
B
1 year, 3 months
F37/Xfce no Firefox window
by Robert Moskowitz
Brand new F37/Xfce install.
Used Everything/Netinst CD and selected Xfce desktop.
I start Firefox and task manager shows it running, but there is no
Firefox window for me to use.
I did a few tweaks that I have on my F35 system, but can't see how that
would impact this...
What should I look for?
1 year, 3 months
coreutils explosion?
by Geoffrey Leach
rkhunter notices this, among other members of coreutils
File: /usr/bin/uniq
Current inode: 524313 Stored inode: 4033
Is there an explanation?
1 year, 3 months
Nautilus/Files 'lost' date field/info
by lejeczek
Hi guys
Since f37 (upgrade from f36) I do not get 'dates' in/from
Nautilus - you know, in 'Preferences -> Grid View Captions'
one can tell Nautilus what 'date' to show in Second and/or
Third.
Anybody else could please confirm this?
Mine shows only names & sizes.
If you think that it is a bug, as I do, then please chip in
here: https://bugzilla.redhat.com/show_bug.cgi?id=2150033
I filed it while ago but does not look like devel gave much
toss - if it is a bug indeed - and your help might... help.
many thanks, L.
1 year, 3 months
Launching Nautilus makes F37 'hard crash'
by Frederic Muller
Hi!
This is happening with the latest 2 kernel versions (just updated and
the same is happening). I thought I wouldn't be the only one and the bug
would magically disappear... well it seems not.
Has anyone experience this?
On my side it's happening 100% of the time, starting with previous
kernel (well.. previous previous now) 'fixes' the problem.
Where should I report this?
Thank you.
Fred
1 year, 3 months
kernel bug? listening on same port with IPv4 and IPv6
by Sjoerd Mullender
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically: create
new socket for IPv6, set option IPV6_V6ONLY to off, bind, listen; then
create a new socket for IPv4, and also bind and listen. The first bind
is either to a specific port, or to port 0 to let the system assign a
port. The second bind uses the port that the first one used (i.e. what
the system assigned).
With the latest kernel, this still works if listening to localhost
([::1]/127.0.0.1) only, but not when listening to [::]/0.0.0.0. In that
case, the second bind gets a different port number assigned to it.
Moreover, the second bind system call returns 1, which it is not
supposed to do according to the manual. Bind is supposed to return 0 on
success and -1 on error.
What is going on? Is this a kernel bug, or is this the future?
Kernel is 6.0.16-300.fc37.x86_64, i.e. the latest Fedora 37 kernel.
--
Sjoerd Mullender
1 year, 3 months
grubby --set-default LOLs at me
by Sam Varshavchik
Can anyone try using grubby --set-default to change the default boot kernel
to something other than the most recently-installed kernel, successfully?
It tells me that it obeys my request, and grubby --info=DEFAULT shows that
the default boot kernel is what I specified.
But at boot the grub menu still highlights the most recently installed
kernel, and that's what boots by default.
1 year, 3 months
