Mailinglist Archive: opensuse-bugs (7837 mails)

[bugzilla_noreply@xxxxxxxxxx]

http://bugzilla.novell.com/show_bug.cgi?id=521787

User hedgehogshiatus@xxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=521787#c15





--- Comment #15 from Hedge Hog <hedgehogshiatus@xxxxxxxxx>  2009-09-15 00:09:13 
MDT ---
Progress!  
My sound was working for two logged in users.
Overnight sound stopped working for _both_ users.... some web reports of broken
sound led me to suspect knotify:

# ps aux|grep -i knotify
root      1601  0.0  0.0   2260   684 pts/18   S+   08:47   0:00 grep -i
knotify
hedge    10897  0.0  0.5  30908 10984 ?        S    Sep10   0:00 knotify
[kdeinit]                      
hedge    31809  0.0  0.5  56820 10580 ?        S    08:16   0:00
/usr/bin/knotify4
mv       31820  0.0  0.5  56836 10628 ?        S    08:16   0:00
/usr/bin/knotify4

The "knotify [kdeinit]" process had died for one user, and sound was broken for
both.  After logging off both user's desktops I noticed that one knotify4
process (pid 31809) was orphaned.  The gdb trace is below.

After logging off both users the gui logon screen was absent vt7 was just a
blinking cursor.  
startx hung at (this startx log attached):

kdeinit4: preparing to launch /usr/bin/knotify4

Switching to vt1: init 3; init 5; did not start the login manager, the screem
just had the XWindows x cursor blinking.

Incredibly, rebooting the system did _not_ restore the sound, and the process
knotify [kdeinit] is missing.  Currently:

# ps aux|grep -i knotify
mv        7978  0.0  1.2 153744 26808 ?        Sl   13:55   0:01
/usr/bin/knotify4

So I think the first step is to try to get the KDE started such that the
knotify process is started correctly.

Any suggestions?

If you want additional data let me know what you want to see.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.