[Bug 406998] New: Login and Shutdown sounds work for "root" but not for regular user,
https://bugzilla.novell.com/show_bug.cgi?id=406998 Summary: Login and Shutdown sounds work for "root" but not for regular user, Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai@novell.com ReportedBy: jimomura@pathcom.com QAContact: qa@suse.de Found By: Customer Compaq Presario V2570ca. I changed the settings in "Application Browser" -> "Sound" from "Autodetect" to "ALSA Mixer" and the login and shutdown sounds work reliably in "root". I tried the same thing as a regular user and it did not help. When logged in as a regular user, the sound "test" buttons for the various sounds (like the "Login" and "Shutdown" and "Alert" sounds) are not doing anything. However, as a "regular user", sound out of the "Flash-Player" is working properly through "nspluginwrapper". I have not tried the "Real Player 10" sound yet. I checked the permissions of the .wav files in "/usr/share/sounds" and they are all set to "read", so that does not seem to be a problem. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c1 --- Comment #1 from Jim Omura <jimomura@pathcom.com> 2008-07-08 19:42:35 MDT --- "Real Player 10" is also working. -- 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=406998 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c2 Takashi Iwai <tiwai@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jimomura@pathcom.com --- Comment #2 from Takashi Iwai <tiwai@novell.com> 2008-07-09 10:10:34 MDT --- So you are trying to run GNOME system without pulseaudio, right? What else exactly did you change from the system default? -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c3 Jim Omura <jimomura@pathcom.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jimomura@pathcom.com | --- Comment #3 from Jim Omura <jimomura@pathcom.com> 2008-07-09 15:36:22 MDT --- Re: PulseAudio This is an "all default" installation of 10.3, so as far as I know, there is no PulseAudio, but there is some "gstreamer" stuff in it. I am not sure if that was added by the updates or whether that was in the initial installation. Actually, yesterday something went wrong with the installation. I think I accidentally moved a file (the touchpad mouse controller is hard for me to use) and the system would not boot X, so I re-installed. This is interesting: My first installation used 1 distro CD and I enabled downloading files during installation, but when it came time to setup the update repositories, I decided to do it later. On that installation, when I was logged on as "root" the "startup" and "shutdown" sounds were working before I updated. After I updated, then they were not working until I changed the "sounds" settings from "autodetect" to "ALSA Mixer" (as I mentioned above). On my 2nd installation, I used both distro CDs but did NOT enable downloading during installation, so the whole installation was done locally. Then later I updated everything. Now, as "root" the "startup" and "shutdown" sounds are working even with the "autodetect" settings, so I have not changed those setting under "root". However, when I log in as a regular user, there was no improvement. Again, the "startup" and "shutdown" sounds do not work, and the "test" buttons for those sounds also do not work. So, for some reason, things are a bit better this time. It does look like this is all to do with the installing, the starting up of X and (maybe) the shutting down of X. Actually, the shutting down of X might not have any real error but it might be failing because of an error in starting 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c4 --- Comment #4 from Jim Omura <jimomura@pathcom.com> 2008-07-10 06:20:40 MDT --- I think the "regular user" problem has changed since I re-installed. I am now seeing that the only problem is that the "Volume" control is not retaining its settings between reboots. So this is looking more like the problem I ran into in 11.0, but this time only for regular users. The "Volume" control has all mutes set and the sliders fully down. When I redo the setup, the "test" buttons in the "sound" utility work and "shutdown" sound works. AND If I make these corrections and "logout" and "login" again as a regular user, the "login" sound plays properly and the volume control retains its settings. AND If I "login" as "root", from a cold boot, nothing is wrong (as I said above), AND if I then "logout" and "login" as a regular user, then nothing is wrong. So, for this installation, the only problem is retaining the "volume" settings across a full power shutdown and reboot. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c5 --- Comment #5 from Jim Omura <jimomura@pathcom.com> 2008-07-11 07:05:12 MDT --- This morning on my first login as a regular user it reverted back to the earlier bug functioning: The volume control is NOT muted and all the settings are correct, but there was no "startup" sound. Going into the "Sound" utility, the first tab tests work (for ALSA), but the 2nd tab playing of the specific event sounds did nothing. I ran Firefox and tried YouTube (for Flash video sound) and it is working perfectly. I am attaching my ".xsession-errors" file. The thing that looks significant to me is the top: "/etc/X11/xim: Checking whether an input method should be started. /etc/X11/xim: user environment variable LANG=en_US.UTF-8 sourcing /etc/sysconfig/language to get the value of INPUT_METHOD INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale en_US.UTF-8 ... There is no default input method for the current locale. SESSION_MANAGER=local/CPV25L:/tmp/.ICE-unix/3352 ** (gnome-session:3352): WARNING **: Failed to start sound. Window manager warning: Failed to read saved session file /home/User01/.metacity/sessions/default0.ms: Failed to open file '/home/User01/.metacity/sessions/default0.ms': No such file or directory Failed to get the list of printers from cupsd MSG: /org/freedesktop/DBus org.freedesktop.DBus NameAcquired" Anyway, that is all I have right 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c6 --- Comment #6 from Jim Omura <jimomura@pathcom.com> 2008-07-11 07:11:00 MDT --- Created an attachment (id=227294) --> (https://bugzilla.novell.com/attachment.cgi?id=227294) ".xsession-errors" As mentioned, this failure did not show the "volume applet" muted, but the "Sound" utility does not play the event sounds. During actual use though, the sound system seems to be working properly. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c7 --- Comment #7 from Jim Omura <jimomura@pathcom.com> 2008-07-11 07:14:18 MDT --- One more comment: So far, the only packages I have loaded beyond the "defaults" are "Chromium" and "kmahjongg" both of which I loaded before yesterday, so those do not seem to have had any effect. I will be installing "gsynaptics" shortly, because I am finding the touchpad is causing me more usage trouble than I can put up with. If that leads to changes in this sound problem I will note them. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c8 --- Comment #8 from Jim Omura <jimomura@pathcom.com> 2008-07-11 21:21:07 MDT --- Other Efforts: Today I did more testing. 1. I tried loading "alsa-firmware". That actually made things a bit worse. Both "root" and "User01" eventually settled down to having the 2nd style problem where the volume control came up muted and all sliders were down. When adjusted, the sound worked properly. I deemed this to be worse and removed "alsa-firmware". 2. I tried changing the options in the "Sound" utility away from ALSA, selected the "AC97" options with the Conexant OSS mixer. This was no better than "ALSA" options, so I have returned the settings to "ALSA", though for some reason the sound is now a bit louder under ALSA. 3. I tried adding the regular user account to the "audio" group. This made no difference, but for now, I am leaving that setting, since it makes sense anyway. If someone could tell me where the "Failed to start sound" message in the above log file quote came from, I think that is something that would be worth checking. -- 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=406998 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c9 Takashi Iwai <tiwai@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tiwai@novell.com |bnc-team-gnome@forge.provo.novell.com --- Comment #9 from Takashi Iwai <tiwai@novell.com> 2008-07-12 02:46:13 MDT --- Thanks for your efforts and reports. Some notes on your issues mentioned above: - The alsa-firmware must have nothing to do with your device. It's for special devices that require external firmwares. So, this must be a coincidence. - The OSS mixer can't be better than ALSA one simply because OSS maps only the subset of ALSA mixer elements - The "audio" group is helpful only when you *always* get the permission error. Usually the permission is set up additionally via hal-resmgr using ACL. I think this is rather GNOME-related issue than the generic sound problem. Reassigned to GNOME maintainers who may have a better clue. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c10 --- Comment #10 from Jim Omura <jimomura@pathcom.com> 2008-07-12 14:39:21 MDT --- First, More Reports: I decided to check the ".xsession-errors" report information. I booted to run level 3 and looked around. Regarding the "SESSION_MANAGER=local/CPV25L:/tmp/.ICE-unix/3352" I checked "/tmp/.ICE-unix" and the folder is empty at run level 3. So I guess this is file created at the session. Regarding "Window manager Warning: Failed to read saved session file /home/User01/.metacity/sessions/default0.ms: Failed to open file" .. "No such file or directory" I checked ".metacity/sessions/" and there are a number of files there, but there is definitely no file named "default0.ms" However, I looked at the ".xsession-errors" file for "root", which is working, and the same reports are there as well. The only difference in that area is that there is no "... Failed to start sound." warning. Regard your message above: I expect that this might be a "timing" issue. The main difference between logging in as "root" and as a regular user is that at some point in the startup for "root" there is a little window that stops and warns you that you might not want to log in as "root" because then you can break stuff. It waits for an input, and then the startup continues. So maybe if you throw in a small delay at that point, it will allow a timing issue to be corrected. I think the "alsa-firmware" probably just changed the timing of some events a bit. On the one hand, I think that it is possible to correct that issue with a temporary delay patch in a startup script somewhere. However, I think there are better ways to correct that, and other bugs, on a one-by-one basis. However, looking ahead to "Pulse Audio". I think someone (or group more likely) should sit down and think whether the whole sound system could be better designed, both bottom - to - top and top - to - bottom. From what I saw, it looks like a "whole world of pain" for debugging. Really, that is the reason I am bothering to get this "little" bug corrected here. I think to even start into "Pulse Audio" you need as pristine a sound system as you can get. One Hopefully Unrelated Issue: When I was alerted to the lack of previous session files in the xsession-errors file, I started watching the shutdown sequence visually. It is very quick. Maybe it is a bit too quick. Sometimes the last disc access light flash come on right before the power shuts off. That can be very bad. I think that it is possible that the write buffer is not being completely written before power is shut off. Anyway, for now, that is just a thought. As for passing it to the GNOME team, that sounds good for now. Though I am getting the impression that they are eyebrow deep already. . . . -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c11 --- Comment #11 from Jim Omura <jimomura@pathcom.com> 2008-07-14 14:38:01 MDT --- And Sometimes Things Get Accidentally Fixed: Yesterday I decided to try and get Wi-Fi and Dial-Up connections working. That failed. However: 1. First I tried to get Wi-Fi working. So I disconnected the LAN and booted the computer, and logged in as "root". The speaker showed up "muted" and the sound problem was as stated above. This is not a huge surprise. I wasted the better part of my day trying to get Wi-Fi to connect, but failed. As far as I can tell, the driver is working, but I suspect that the WEP Hex key is not being passed along. When I plugged the LAN in again, sound again worked for "root" and failed for the regular user account. No change. 2. Next I decided to try to get Dial-up working First, "smpppd" was loaded. Also, in order to allow the regular user account to work as well, the "Modem" utility loaded "KInternet" which in turn loaded a bunch of KDE3 packages and stuff. In the end, I failed to get the dial-up connection working as well, however, being curious, I tried shutting down and logging in as a regular user, and, yes, the sound is now working properly. I do not know if it will be working consistently yet. I will confirm it later if I am convinced. However, it has survived 2 reboots so far. Is This Just Another Timing Effect? This might actually be an indication of a possible "real" fix. That is to say, buried in the binary, there might actually be something that helps to start up the sound system as a bi-product of its action. This is possible because the sound and modem are both related circuits on the same chip. In order to fix the sound system, there might be a bit of code that you could swipe from the modem binary. On the other hand, it might just be an effect of the modem circuit being turned on long before the sound system is being started up. So that the only real fix needed would be to add a delay in the startup of the sound system. I will not be closing this bug at this time because even if it proves to be "reliable", the sound system is not supposed to rely on the presence of the dial-up code. I have no need to remove the dial-up related packages at this time, so I will be leaving it alone for now, but if someone wants me to remove it to see what happens, I can give it a try later. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c12 --- Comment #12 from Jim Omura <jimomura@pathcom.com> 2008-07-14 16:08:59 MDT --- False Hope: I decided to try again to fix the "dial-up", this time by manually editing the ".conf" file. It did not work. But regarding sound: 1. With the LAN disconnected a. As "root" the "volume applet" came up muted and all sliders down. Same characteristics as usual for that situation. b. As a regular user, the "volume applet" was not muted but no login or shutdown sounds, and all the same characteristics for that situation. 2. With the LAN re-connected: a. As "root" everything worked ok. b. As a regular user, on the first reboot the "volume applet" came up muted, and the usual characteristics returned, but on the next re-boot, the sound came up properly, just as it does under "root". So adding the modem stuff has probably only readjusted some timing issue again -- not a reliable fix at all. -- 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=406998 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c13 Vincent Untz <vuntz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vuntz@novell.com Priority|P5 - None |P4 - Low --- Comment #13 from Vincent Untz <vuntz@novell.com> 2008-07-24 04:14:28 MDT --- Hrm, this is 10.3. It's a bit surprising that it doesn't work for you since it works for most people, I guess :/ Also not sure if we'll have enough time to fix the issue un 10.3. Assigning to Rodrigo since he might know how things were handled before PA world order. I'm sure he can reassign to somebody else :-) -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c14 --- Comment #14 from Jim Omura <jimomura@pathcom.com> 2008-07-24 16:06:20 MDT --- Leave It Till When? I do not understand the logic. You have a bug at 10.3 level without Pulse Audio. It is a "flakey" bug, so that it shows up sometimes but not in all cases, which makes it difficult bug to fix. So you are going to leave it till when? Till you find it again in 11.0 with Pulse Audio's potential bugs, so it will be even harder to debug? Well . . . Actually this bug does show up in 11.0, along with a lot of other bugs. I reported it in "bug#402447" (which was a bug report opened in regard to a different bug, and later expanded) and later separated it out as "bug#405088". The reason I replaced 11.0 with 10.3 was to run a less buggy platform overall, and in particular, hopefully avoid this bug. Unfortunately, although 10.3 is better overall, it seems that this bug probably started in 10.3 and because it was never fixed, it found its way into 11.0. I have seen reports posted by people using computers almost identical to this one with 10.2, and there is no mention of a problem like this, so I expect that 10.3 probably where it started. Furthermore: It appears this bug may have been found before as bug#399114 in 11.0 (RC1) however, that bug was left without enough documentation. The original reporter of the bug stopped responding. Possibly he gave up on 11.0. We do not know. Since the situation with that bug was never clarified, I did not consider my report a duplicate. Also, "bug#360606" sounds very much like this bug. However, because it did not have completely identical characteristics, I felt that I should leave the two bug reports separate. This is especially important because 360606 is regarding the i586 version, and I believe that my bug might be x86_64 specific. But do not be surprised if fixing one of these two bugs turns out to fix the other as well. But the bottom line is, that I really do believe that 10.3 is a better place to start debugging the sound systems than in 11.0. :-) -- 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=406998 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c15 --- Comment #15 from Vincent Untz <vuntz@novell.com> 2008-07-25 06:24:07 MDT --- Jim: I'm not saying we should wait. But it's rather low priority compared to some other bugs, even when you only look at sound-related bugs. And it's hard to know if PA changes things about this in 11.0, but Rodrigo should know. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c16 --- Comment #16 from Jim Omura <jimomura@pathcom.com> 2008-07-27 15:54:58 MDT --- (In reply to comment #15 from Vincent Untz)
Jim: I'm not saying we should wait. But it's rather low priority compared to some other bugs, even when you only look at sound-related bugs.
Understood. I was half joking. Everything I said was true, but having looked at what there is currently I know that you guys have plenty to do. . . .
And it's hard to know if PA changes things about this in 11.0, but Rodrigo should know.
I do not have time to look at the sources myself, but I have a feeling this is not a binary problem so much as structural -- more the fault of the "startup" scripts and daemons. But without spending days, which I do not have, I can only guess. But if this is true, then there might be some "leverage" to this bug. That is to say, solving it might help solve other bugs. Then again, that hope often turns out empty 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=406998 User rodrigo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c17 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodrigo@novell.com --- Comment #17 from Rodrigo Moya <rodrigo@novell.com> 2008-07-29 08:05:13 MDT --- Takashi, any idea what the problem might be? -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c18 --- Comment #18 from Jim Omura <jimomura@pathcom.com> 2008-07-31 09:25:13 MDT --- I am looking at: "/root/gnome2/session" and it has a line "6,RestartCommand=ggreeter --once" Where and what is "ggreater". Is that a script that runs the startup sound? -- 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=406998 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c19 --- Comment #19 from Vincent Untz <vuntz@novell.com> 2008-07-31 09:37:38 MDT --- (In reply to comment #18 from Jim Omura)
I am looking at:
"/root/gnome2/session"
and it has a line
"6,RestartCommand=ggreeter --once"
Where and what is "ggreater". Is that a script that runs the startup sound?
ggreeter is the application that shows a window the first time you log in. It has nothing to do with sound. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c20 --- Comment #20 from Jim Omura <jimomura@pathcom.com> 2008-08-29 20:22:20 MDT --- As of today, the "startup" and "shutdown" sounds seem to be working. Do not get your hopes up yet because this has happened before. However, I have rebooted 3 times and done light work with some programs and there has not been a change yet. The real test will be if I reconfigure the system a couple of times and it is still working. The system changes that I have recorded since the last time I tested the sounds were: Aug. 5, Update "inst-sources-utils" Aug. 7 "gsynaptics 0.9.9" only the source code -- no binaries Aug. 13 Update "gnome-screensaver" Aug. 14 Update "postfix 2.4.5-20.4" Aug. 15 Update "python-2.5.1-39.6" Aug. 22 Update "perl 5.8.8-76.4" Aug. 29 Update "java 1_5_0-sun" I will not be closing this report quite yet. However, if I do not post anything more after 1 month, then assume it can be close. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c21 --- Comment #21 from Jim Omura <jimomura@pathcom.com> 2008-08-31 13:45:56 MDT --- It is not fixed, though it might be a bit better than before: I loaded "gsynaptics" to see if that was working. On reboot to the limited account the volume applet came up un-muted but the startup sound did not play. In the "sound" application the "test" buttons did not play the sounds. I checked the ".xsession-errors" and the "sound" reported a failure to start up, (and later in the boot "gsynaptics" also gave an error, which is a different problem which I have reported elsewhere). Later, after various other tests, I removed "gsynaptics" and rebooted to the limited account and the "volume applet" came up muted. I un-muted the "volume applet" and rebooted the system back to the limited account. This time, the sound is working at startup. But I would say that this is probably still a somewhat "random" effect, depending on exactly what configuration I am using. In other words, for today, it seems like I have a fully working sound system, but I can cause it to fail by simply changing the configuration by loading or removing another program, and it probably does not really matter exactly which program I load or remove. -- 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=406998 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406998#c22 --- Comment #22 from Jim Omura <jimomura@pathcom.com> 2008-10-07 19:53:15 MDT --- This problem is also on my MSI K9A Platinum system. It has been evident since I loaded 10.3 on it a while ago. I did not bother to report it at the time because this report is already open. However, the K9A Platinum is a later chipset and uses different sound chips, and thus different drivers. So it somewhat confirms that the problem is probably not driver specific. I am currently considering removing 10.3 from the Compaq Presario V2570CA, but since the problem exists on the K9A Platinum, I will leave the bug open and provide further information on request based on the K9A Platinum. If the driver is not the specific problem, then presumably whatever fixes it on the K9A Platinum will fix it on the Compaq as well. -- 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