[Bug 816942] New: Recent update kills audio
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c0 Summary: Recent update kills audio Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai@suse.com ReportedBy: james.knott@rogers.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 There was a KDE 4 update recently, which appears to have killed audio on my computers. When I open KDE Mixer, there are no capture devices or streams. When I go into Pulse Audio I there are also no devices, though I can see the level meter on the playback tab following an audio source. This problem occurred on two different computers, one a desktop system with Asus motherboard and the other a Lenovo ThinkPad E520. Both had updates yesterday and now sound doesn't work at all on either. Reproducible: Always Steps to Reproduce: 1.Install latest updates 2. 3. Actual Results: After recent update, sound fails. Expected Results: Sound was working previously and should work now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |lmuelle@suse.com InfoProvider| |james.knott@rogers.com --- Comment #1 from Takashi Iwai <tiwai@suse.com> 2013-04-24 14:27:11 UTC --- Likely a device permission problem Lars told me recently. My wild guess is that it's a regression in KDM or whatever there... Check the device permissions of /dev/snd/* files via getfacl. getfacl /dev/snd/controlC0 In a working case, your id should be listed explicitly, for example: % getfacl /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 # owner: root # group: audio user::rw- user:tiwai:rw- group::rw- mask::rw- other::--- See user:tiwai in the above. Please check whether it's your case. If this is really the culprit, an easy workaround (but not the right solution) is to put your account to "audio" group. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c2 James Knott <james.knott@rogers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|james.knott@rogers.com | --- Comment #2 from James Knott <james.knott@rogers.com> 2013-04-24 15:07:34 UTC --- # getfacl /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 # owner: root # group: audio user::rw- group::rw- mask::rw- other::--- As you can see, there's no user listed. I just added my id to the audio group and that appears to fix the problem on both computers. What is the right solution? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c3 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |james.knott@rogers.com --- Comment #3 from Lars Müller <lmuelle@suse.com> 2013-04-24 17:29:35 CEST --- Please perform the very same getfacl check when you logged in to a text console by pressing Ctrl + Alt + 6 for example. You might keep your X11 session running. If it works for the text console works and additional ACL for your <user_name>::rw- gets added. Then we know the seat permission handling works in general. Now close the text console and your X11 session too and authenticate again against KDM. If you use a different display manager or you start the X11 session by a different means please report the way you do it back too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c4 --- Comment #4 from James Knott <james.knott@rogers.com> 2013-04-24 16:30:19 UTC --- I tried that on my notebook and I now have a user listed. However, a curious problem has now occurred on my desktop system. Ctl-Alt-Fn no longer works to switch to a text console. I tried switching to run level 3 and running and when there I saw my userid added, but it didn't stick when back in run level 5. Any idea why Ctl-Alt-Fn doesn't work any more? It was working recently, before the update. I'm running KDE4 with the KDE3 desktop on both computers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c5 James Knott <james.knott@rogers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|james.knott@rogers.com | --- Comment #5 from James Knott <james.knott@rogers.com> 2013-04-25 12:08:10 UTC --- I just checked on the desktop computer, after a reboot, and that command is now showing a user ID in a console window on the desktop. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c6 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |james.knott@rogers.com --- Comment #6 from Lars Müller <lmuelle@suse.com> 2013-04-25 14:44:04 CEST --- Please express if you tested this via a login from KDM, GDM, or any other display manager or if you performed your tests on a text console. The non working Ctl-Alt-Fn key combination issue is something else. Please track this in an independent issue if you're able to trigger the same defect again. We need to know which component causes the missing permissions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c7 Vadim Krevs <vkrevs@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |vkrevs@yahoo.com InfoProvider|james.knott@rogers.com | --- Comment #7 from Vadim Krevs <vkrevs@yahoo.com> 2013-04-25 13:11:50 UTC --- I have the same problem - user id not listed in the output of getfacl. Tried following the steps in comment 3. Ctrl-Alt-Fn does not work as mentioned above as well. Dropped to runlevel 3 via init 3, logged on as myself, and ran the getfacl command - user id was listed. Logged out, and switched back to runlevel 5 via init 5, and logged back into KDE as the same non-root user. Now getfacl lists my user id. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c8 --- Comment #8 from James Knott <james.knott@rogers.com> 2013-04-25 15:01:59 UTC --- As I mentioned above, I run KDE, so it would be KDM. The Ctl-Alt-Fn issue was resolved after rebooting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c9 --- Comment #9 from Vadim Krevs <vkrevs@yahoo.com> 2013-05-08 09:35:24 UTC --- Same problem after upgrade to KDE 4.10.3 from OBS. First login via KDM after a full reboot after installing updates - no audio, only the "Dummy output", and $ getfacl /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 # owner: root # group: audio user::rw- group::rw- other::--- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c10 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #10 from Wolfgang Bauer <wbauer@tmo.at> 2013-05-08 10:41:17 UTC --- I don't have this problem here, even after the latest KDE updates. On first login after a full reboot: wolfi@amiga:~> getfacl /dev/snd/controlC0 getfacl: Entferne führende '/' von absoluten Pfadnamen # file: dev/snd/controlC0 # owner: root # group: audio user::rw- user:wolfi:rw- group::rw- mask::rw- other::--- So I don't think this is an issue with KDE/KDM as was suggested... A guess though: Is your user session listed when you run "loginctl"? If not, that's the cause of your problem. In that case, please check if you have the line "session optional pam_systemd.so" in /etc/pam.d/common-session . (Actually /etc/pam.d/common-session should be a link to /etc/pam.d/common-session-pc, which should contain that line) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c11 --- Comment #11 from Vadim Krevs <vkrevs@yahoo.com> 2013-05-08 14:21:58 UTC --- I'll check the output of loginctl next time this happens. Could the fact that my system boots to runlevel 3 (and not 5) by default be the issue here? $ l /etc/pam.d/common-session lrwxrwxrwx 1 root root 17 Jan 12 2009 /etc/pam.d/common-session -> common-session-pc $ grep pam_systemd /etc/pam.d/common-session session optional pam_systemd.so -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c12 --- Comment #12 from Wolfgang Bauer <wbauer@tmo.at> 2013-05-08 16:00:32 UTC --- (In reply to comment #11)
Could the fact that my system boots to runlevel 3 (and not 5) by default be the issue here? Of course! And f.e. in comment#6 exactly these kind of details were asked...
You're switching to GUI mode via "startx" I suppose? Not sure if that is even supported anymore. I tried that here and after a boot to runlevel 3 and login in textmode my user has the right permissions (same as above). After running "startx" I get the following: wolfi@amiga:~> getfacl /dev/snd/controlC0 getfacl: Entferne führende '/' von absoluten Pfadnamen # file: dev/snd/controlC0 # owner: root # group: audio user::rw- group::rw- mask::rw- other::--- And btw. the graphical session is running on vt2 then instead of vt7. Maybe that has something to do with it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c13 --- Comment #13 from Vadim Krevs <vkrevs@yahoo.com> 2013-05-09 07:36:16 UTC --- No, I don't use startx. Just "init 5" to switch to GUI. I'll change /etc/systemd/system/default.target to point to "runlevel5.target" and see if that fixes the problem. W -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c14 --- Comment #14 from Lars Müller <lmuelle@suse.com> 2013-05-29 13:34:55 CEST --- I did the same on one of my test systems. As soon as the system is started in runlevel 3 and then kdm gets launched via init 5 the first login doesn't cause the extra ACL. While a second and any further do. Calling ln -fs /usr/lib/systemd/system/runlevel5.target \ /etc/systemd/system/default.target rebooting and I got the intended ACL even with the first login. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c15 --- Comment #15 from Wolfgang Bauer <wbauer@tmo.at> 2013-05-29 12:19:24 UTC --- Hm. I just tried booting to runlevel 3 and starting KDM with init 5 on both of my systems (both 12.3): On the one system with KDE 4.10.3 from the KDE:Distro:Factory repo everything worked as expected. I got ACLs on first login. But on the other system with KDE 4.10.2 from the standard update repo, it didn't work. So there does seem to be an issue somewhere. But maybe this is already fixed in the KDE 4.10.3 packages? My test in comment #12 was done after the update to 4.10.3... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c16 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |kde-maintainers@suse.de InfoProvider| |kde-maintainers@suse.de --- Comment #16 from Lars Müller <lmuelle@suse.com> 2013-05-29 16:54:15 CEST --- linux-77m7:~ # LC_ALL=POSIX rpm -qa --last \*kdm\* kdm-4.10.3-1.37.7.x86_64 Wed May 29 16:12:11 2013 kdm-branding-openSUSE-12.3-6.24.14.noarch Wed May 29 16:12:10 2013 These packages are pulled from http://download.openSUSE.org/pub/opensuse/update/12.3-test/openSUSE:Maintena... I tried the same again with the above versions and the permissions are still not granted the way they're intended. lmuelle@linux-77m7:~> LC_ALL=POSIX getfacl --tab /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 USER root rw- GROUP audio rw- other --- That above is the state after going from runlevel 3 to 5 (init 5) and login via kdm. And a second try after the KDE session got closed (but still the same KDM pid): lmuelle@linux-77m7:~> LC_ALL=POSIX getfacl --tab /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 USER root rw- user lmuelle rw- GROUP audio rw- mask rw- other --- Next test: init 3 and init 5 again and login (new KDM process). Result: the ACL gets set as intended. There must be something special when KDM gets started the first time and only in the case we're coming from runlevel 3. As soon as we start immediately with the runlevel5.target target all looks well. See comm#14. @KDE maintainers: Do you have any hints how to debug this further? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c17 --- Comment #17 from Wolfgang Bauer <wbauer@tmo.at> 2013-05-29 15:21:41 UTC --- In my test on the 4.10.2 system, it didn't even work on the second login... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c18 --- Comment #18 from Wolfgang Bauer <wbauer@tmo.at> 2013-06-03 02:46:27 UTC --- I want to confirm that it's indeed KDM's fault. (strange though that I don't have this problem on my main system... maybe some race condition?) When I switch to xdm (on the system that shows this problem), the problem does not occur. There's different output from loginctl: working: SESSION UID USER SEAT 1 0 root seat0 2 1000 armada seat0 2 sessions listed. not working: SESSION UID USER SEAT 1 0 root seat0 2 1000 armada 2 sessions listed. So in the not-working case the session isn't correctly registered with the seat. And also downgrading kdm to 4.10.0 from the Oss repo cures this, so it must be caused by some change between 4.10.0 (as of 12.3) and the 4.10.2 update... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c19 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com AssignedTo|tiwai@suse.com |kde-maintainers@suse.de --- Comment #19 from Takashi Iwai <tiwai@suse.com> 2013-06-03 02:53:35 UTC --- Reassigned to KDE guys. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c20 --- Comment #20 from Hrvoje Senjan <hrvoje.senjan@gmail.com> 2013-06-03 04:19:48 UTC --- @Wolfgang, Lars, could you test the whole 4.10.3 packages (mainly i target kdm, kde4-kgreeter-plugins and kdebase4-workspace packages) ? Asking as systemd support patch was changed for 4.10.3 with upstream version. (and also Wolfgang says in comment 15 that 4.10.3 works correctly) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c21 --- Comment #21 from Wolfgang Bauer <wbauer@tmo.at> 2013-06-03 05:12:31 UTC --- (In reply to comment #20)
@Wolfgang, Lars, could you test the whole 4.10.3 packages (mainly i target kdm, kde4-kgreeter-plugins and kdebase4-workspace packages) ? I can't test that right now, but Lars mentioned in comment#16 that he tried with kdm-4.10.3 from the Update-Test repo.
I tried to downgrade kdm to 4.10.2 from Update now on my 4.10.3 system (the one that doesn't have this problem) and still can't reproduce it there. Trying to do a full KDE downgrade now... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c22 --- Comment #22 from Hrvoje Senjan <hrvoje.senjan@gmail.com> 2013-06-03 05:52:27 UTC --- (In reply to comment #21)
(In reply to comment #20)
@Wolfgang, Lars, could you test the whole 4.10.3 packages (mainly i target kdm, kde4-kgreeter-plugins and kdebase4-workspace packages) ? I can't test that right now, but Lars mentioned in comment#16 that he tried with kdm-4.10.3 from the Update-Test repo. Yes, seen that, but it's hardly kdm (alone), as the code between 4.10.0 and 4.10.2/3 didn't change, other than translations ;-) (try to diff)
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c23 --- Comment #23 from Wolfgang Bauer <wbauer@tmo.at> 2013-06-03 07:47:55 UTC --- (In reply to comment #21)
Trying to do a full KDE downgrade now... Even after a complete downgrade to KDE 4.10.2 (by deactivating the KDE:Distro:Factory repo and running "zypper dup --from update-repo) I still cannot reproduce this issue on the first system.
I tried updating kdm to 4.10.3 from the Update-Test repo now on the second system (the one that shows the problem), the following packages got updated as well: kactivities4, kde4-filesystem, kde4-kgreeter-plugins, kdebase4-runtime, kdebase4-session, kdebase4-workspace, kdebase4-workspace-branding-openSUSE, kdebase4-workspace-ksysguardd, kdebase4-workspace-liboxygenstyle, kdebase4-workspace-plasma-calendar, kdelibs4, kdelibs4-core, kdm-branding-openSUSE, kwin, libkde4,libkdecore4, nepomuk-core. After that, the problem seemed to be fixed. Then I downgraded those packages to 4.10.2 again and the problem reappeared as expected. But then I did the update again, and now the problem persisted! So I can say, this is NOT fixed in 4.10.3. Strange enough, the problem now also shows up when I downgrade kdm (and the 9 other automatically selected packages) to 4.10.0, although that persistently fixed it before... :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c24 --- Comment #24 from Hrvoje Senjan <hrvoje.senjan@gmail.com> 2013-06-03 07:59:34 UTC --- (In reply to comment #23)
I tried updating kdm to 4.10.3 from the Update-Test repo now on the second system (the one that shows the problem)... After that, the problem seemed to be fixed.
Then I downgraded those packages to 4.10.2 again and the problem reappeared as expected.
But then I did the update again, and now the problem persisted! So I can say, this is NOT fixed in 4.10.3. this is a bit confusing?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c25 --- Comment #25 from Wolfgang Bauer <wbauer@tmo.at> 2013-06-03 08:27:50 UTC --- (In reply to comment #24)
this is a bit confusing? Sorry, I try again:
I updated kdm and dependencies to 4.10.3. After a reboot to runlevel 3 and calling "init 5" the problem did not occur, i.e. the ACLs got correctly set. Then I downgraded all the packages to 4.10.2 again. After a reboot the problem did happen, user had no permissions for the audio devices. (I did expect this since that was the original problem) Then I updated kdm and dependencies again to 4.10.3 (the same as before) and expected the problem to vanish again. But this time after a reboot, the problem happened again, the user did not get permissions. So there seems to be some random factor involved. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c26 Hrvoje Senjan <hrvoje.senjan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|kde-maintainers@suse.de | --- Comment #26 from Hrvoje Senjan <hrvoje.senjan@gmail.com> 2013-06-03 10:46:42 UTC --- (In reply to comment #25)
So there seems to be some random factor involved. Indeed. Thanks a lot for testing!
@everyone, so to summarize, and confirm, problem happens only if boot goes first into runlevel3 and then to runlevel5? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c27 --- Comment #27 from Wolfgang Bauer <wbauer@tmo.at> 2013-06-03 11:48:24 UTC --- (In reply to comment #26)
@everyone, so to summarize, and confirm, problem happens only if boot goes first into runlevel3 and then to runlevel5? For me, yes. But only on that one system. It doesn't happen on the other at all.
But I think I may have found the culprit: plymouthd! For some reason plymouthd is started when I run "init 5" and seems to cause this. If I rename /usr/sbin/plymouthd (so it can't start) the problem doesnt occur: the session gets registered correctly and the ACLs get set (and that's reliable across ~10 reboots now). Can somebody else confirm that this helps? On the other system plymouthd doesn't seem to get started, and the problem does not occur, ever. Or maybe because that system is slower it quits in time before kdm starts up? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c28 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com --- Comment #28 from Lars Müller <lmuelle@suse.com> 2013-06-03 14:41:15 CEST --- (In reply to comment #27)
But I think I may have found the culprit: plymouthd!
For some reason plymouthd is started when I run "init 5" and seems to cause this. If I rename /usr/sbin/plymouthd (so it can't start) the problem doesnt occur: the session gets registered correctly and the ACLs get set (and that's reliable across ~10 reboots now). Can somebody else confirm that this helps?
Yes. I've moved /usr/sbin/plymouthd away and then the first login gave the wanted additional ACL. Even when going from runlevel 3 to 5 and login. In a next step I've removed these plymouth packages: plymouth plymouth-branding-openSUSE plymouth-scripts Booted into runleven 3, called init 5, and got the intended ACL with the first login via kdm. One further observation I did: Before I did the quick hack/ check and renamed the plymouthd binary I mistyped by accident the password. plymouthd before but no longer afterwards. But even in the case of a no longer running plymouthd I didn't got the additional ACL set with the first login. The any later it worked. Has anyone tested the same with openSUSE Factory? I'm adding Marcus as he's marked as the bugowner for plymouth in oS 12.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c29 Lee Seymour <gtx.swift@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gtx.swift@gmail.com --- Comment #29 from Lee Seymour <gtx.swift@gmail.com> 2013-06-05 05:27:44 UTC --- ThinkPad E325 Tumblweed repos, no sound (displays dummy output only), mounting/suspend requires root privilege window dialogue instead of handling automatically, no network detected networking disabled but actually still connected. Uninstalling Plymouth seems to fix. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c30 --- Comment #30 from Wolfgang Bauer <wbauer@tmo.at> 2013-06-07 03:48:12 UTC --- Another observation which I think is related: On my other system (the one that doesn't have this problem), KDM (and KDE as a consequence) often start on VT8 instead of VT7 when booting to runlevel 5. Apparently plymouthd is also still running and claiming VT7 there when KDM starts up. (it doesn't cause the permissions issue there though) Renaming /usr/sbin/plymouthd seems to fix this problem as well. (In reply to comment #6)
The non working Ctl-Alt-Fn key combination issue is something else. Please track this in an independent issue if you're able to trigger the same defect again. This does seem to be related. I can reproduce this when the permissions issue appears most of the time (but not always). It never happens when I remove plymouthd.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c31 Carlos Robinson <carlos.e.r@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos.e.r@opensuse.org --- Comment #31 from Carlos Robinson <carlos.e.r@opensuse.org> 2013-06-09 19:38:42 UTC --- (In reply to comment #30)
Another observation which I think is related: On my other system (the one that doesn't have this problem), KDM (and KDE as a consequence) often start on VT8 instead of VT7 when booting to runlevel 5. Apparently plymouthd is also still running and claiming VT7 there when KDM starts up. (it doesn't cause the permissions issue there though) Renaming /usr/sbin/plymouthd seems to fix this problem as well.
I see this as well, 12.3, kdm and xfce. Removing plymouth-branding-openSUSE and plymouth-scripts, tabooing them, solves the problem the switch to text mode problem, but the graphical terminal goes to VT-8. I no longer have plymouthd. These remain installed: Telcontar:~ # rpm -qa | grep plym plymouth-plugin-label-0.8.8_git201211022126-4.3.1.x86_64 plymouth-plugin-script-0.8.8_git201211022126-4.3.1.x86_64 Telcontar:~ # They have to stay or suspend is also uninstalled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c32 Cristian Rodríguez <crrodriguez@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@opensuse.org --- Comment #32 from Cristian Rodríguez <crrodriguez@opensuse.org> 2013-06-09 17:07:40 CLT --- I tried to reproduce this problem in factory with no luck.. can anyone reproduce it there and provide an step by step description ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c33 Cristian Rodríguez <crrodriguez@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #33 from Cristian Rodríguez <crrodriguez@opensuse.org> 2013-06-09 22:42:52 CLT --- exactly the same bug as 811185 m plymouth bug. *** This bug has been marked as a duplicate of bug 811185 *** http://bugzilla.novell.com/show_bug.cgi?id=811185 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com