February 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 435351] New: Audio delayed with USB headset
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=435351 Summary: Audio delayed with USB headset Product: openSUSE 11.0 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: donrhummy(a)yahoo.com QAContact: qa(a)suse.de Found By: --- When I play a flash video, the audio is delayed by 5 seconds behind the video. When the video is stopped, the audio continues to play out. (I am able to temporarily fix the problem, but upon restart of the computer, the problem returns) See below for notes and steps: NOTES --------- * I have a USB headset, no sound card * Previously when I was using OpenSUSE 11.0 Beta, I had sound for the operating system (opening windows for example) but no sound in Flash. * Since installing OpenSUSE 11.0 I have no sound for the OS, but now get (delayed) sound for flash videos after following the steps below. STEPS --------- 1. I updated Alsa (and Flash with sound support) using: - Flash Player:Additional Interface Support for Linux - Adobe Labs ( http://labs.adobe.com/wiki/index.php/Flash_Player:Additional_Interface_Supp… ) - Alsa-update - openSUSE ( http://en.opensuse.org/Alsa-update#openSUSE-11.0 ) After doing that, the flash video would play and for 3 seconds have no sound, then all of a sudden the sound would play but delayed 3-seconds behind the video. If I pause the video, the audio keeps playing until it completes up to the point the video was paused at. So it's always delayed. 2. Created the file "/home/yourusername/.asoundrc" with the data: [code] usb.default # usb.default begins ### pcm.!default { type hw card 1 } ctl.!default { type hw card 1 } # usb.default ends ### [/code] 3. Restarted Alsa with command: "rcalsasound restart" 4. Removed my USB headset and plugged it back in NOTE: This made it so there was NO sound. 5. Deleted the file "/home/yourusername/.asoundrc" 6. Restarted Alsa again 7. Removed my USB headset and plugged it back in NOTE: At this point, the audio and video are working CORRECTLY. 8. Restarted the computer NOTE: Now, the audio is delayed again! 9. Repeat steps 2-7 and it works properly again, however, restarting the computer brings the problem back. -- 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.

1 8

[Bug 421996] New: USB-Audio don't work
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=421996 Summary: USB-Audio don't work Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: opensuse(a)wolotec.de QAContact: qa(a)suse.de Found By: --- I have a Sennheiser USB-Audio_Headset. Yast and alsaconf don't found the Headset, but in lsusb the device is found with: Bus 001 Device 004: ID 1395:3556 Sennheiser Communications USB Headset Manually add a "generic USB-Audio"-Device in yast don't help. -- 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.

1 6

[Bug 471476] New: KDE4.2 search items in the "Application Launcher" are shown twice.
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=471476 Summary: KDE4.2 search items in the "Application Launcher" are shown twice. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: joop_boonen(a)web.de QAContact: qa(a)suse.de Found By: --- Created an attachment (id=269221) --> (https://bugzilla.novell.com/attachment.cgi?id=269221) KDE4.2 search items in the "Application Launcher" are shown twice. User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 KDE4.2 search items in the "Application Launcher" are shown twice. I've installed KDE4.2 via: http://news.opensuse.org/2009/01/29/kde-42-in-opensuse/ Reproducible: Always Steps to Reproduce: 1. 2. 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.

1 2

[Bug 421880] New: Can't connect if wireless SSID not broadcast
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=421880 Summary: Can't connect if wireless SSID not broadcast Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nick.battle(a)uk.fujitsu.com QAContact: qa(a)suse.de Found By: Community User Configuring a WPA wireless client to connect to an AP that doesn't broadcast its SSID used to work perfectly in openSUSE 10.3, but 11.0 fails to add "WIRELESS_AP_SCANMODE='2'" to the ifcfg file, which causes the WPA supplicant to fail to form an association. Details: ipw2200 device, configured for WPA_PSK security, AP's BSSID (and SSID) set via Yast. Subsequently adding WIRELESS_AP_SCANMODE='2' to the ifcfg file and stop/starting the interface cures the problem. The Yast in 10.3 appears to add the scan mode line, which then works first time. More information at http://forums.opensuse.org/network-internet/wireless/393838-ipw2200-failed-… -- 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.

1 23

[Bug 463493] New: Disturbing log entries from pam_winbind after joining Windows (ADS) Domain
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=463493 Summary: Disturbing log entries from pam_winbind after joining Windows (ADS) Domain Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: msa(a)gaugusch.at QAContact: samba-maintainers(a)SuSE.de Found By: Customer After joining a fresh installed Machine to a Windows Domain (net rpc join), and activating the following options in YAST, at least cron and sshd write an error message to syslog: Yast Settings: [x] Also Use SMB Information for Linux Authentication [x] Create Home Directory on Login [x] Offline Authentication [x] Single Sign-On for SSH Error message: sshd[18501]: pam_winbind(sshd:session): pam_putenv: delete non-existent entry; KRB5CCNAME This occurs for every task that is spawned by cron and every SSH session. -- 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.

1 5

[Bug 405868] New: [iwl3945] Can't activate intel 3945AGB with softkey; only over yast or by reloading the module
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=405868 Summary: [iwl3945] Can't activate intel 3945AGB with softkey; only over yast or by reloading the module Product: openSUSE 11.0 Version: Final Platform: IA64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marko.obert(a)googlemail.com QAContact: qa(a)suse.de Found By: Customer Hi Novell-Team, I have a BenQ R55 G21 notebook with an intel 3945 AGB wireless network card on OpenSuse 11 (Gnome). Thats how it was before with the ipw3945 module: Press the wireless softkey an wait a few seconds, then I saw all available networks listed in the gnome-network-manager. Thats how it's right now: Press the bottom an nothing happens ..... Two ways to get it work: Over Yast2: Yast2 -> Network preferences -> PRO/Wireless 3945AGB Network Connection -> Edit -> Continue -> Continue -> Close Then the available networks get listed, but I have to do it after each reboot. Reload module: 1.) Press the softkey 2.) modprobe -r iwl3945 3.) modprobe iwl3945 If it doesn't work, start with 2.) again. Conclusion: Thats not how it should be. It would be greate, if you could solve that problem. 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.

1 16

[Bug 471465] New: KDE4 updateapplet does not show available upgrades
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=471465 Summary: KDE4 updateapplet does not show available upgrades Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: graham.anderson(a)gmail.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=269214) --> (https://bugzilla.novell.com/attachment.cgi?id=269214) update applet configured to show upgrades, no upgrades shown even if available User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 FirePHP/0.2.1 With the packageKit plugin for KDE4 update applet, only patches and security updates from the current version update repository are shown or notified. Upgrades available from additional repositories do not get displayed or notified. Reproducible: Always Steps to Reproduce: 1. 2. 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.

1 1

[Bug 425485] New: gnome-keyring-daemon does not exit when session exits
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=425485 Summary: gnome-keyring-daemon does not exit when session exits Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- I use KDE 3.5 as it comes with opensuse 11.0 I also use a program which makes use of the gnome-keyring-daemon. Since using that program, I have noticed that: 1. logging out takes much longer. 2. shutting the machine down *always* results in it being unable to unmount /home 3. gnome-keyring-daemon *DOES NOT EXIT* when the session exits 4. this prevents the unmounting of NFS-based filesystems, 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.

1 3

[Bug 439199] New: occasional problem with gnome session manager during boot
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=439199 Summary: occasional problem with gnome session manager during boot Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: bobharvey(a)europe.com QAContact: qa(a)suse.de Found By: Community User Hi. I use a pretty-much default system with a gnome desktop and a single user apart from root. The system is set to auto-login that user at bootup. Around one time in ten or so, Before the Gnome 'panel' appears, I get an error dialogue (with a stop sign) which says "The GNOME session manager cannot start properly. Please report this as a GNOME bug. Please include this ICE failure message in the bug report 'Cannot establish any listening sockets'. meanwhile you could try logging in using the failsafe session." If I acknowledge this box I get the normal GDM username box, and if I log in after that (without using the failsafe session) it all appears normal but nothing works. I once tried the failsafe session and that was just as broken, so I have never bothered again. I have noticed that when this happens, if I ctrl-alt-1 without acknowleding the error dialogue that booting has not completed. Sometimes the first console is sitting at the line about NTPd . there is no login prompt. Nor is there one on the other consoles either. Today when I went ctrl-alt-1 the green bootup screen with it's faint little progress bar re-appeared, and the progress bar started moving left from about 3/4 across. When it finished I got the normal login prompt, and was indeed able to login in as root. I have had a similar session manager dialogue box sometimes, complaining about the ownership of my .ICEauthority file. I had a quick look at that and it was dated at the moment I last performed a shutdown from the panel at the bottom of the screen (libssui-tool --shutdown) . I then rebooted and the sequence was normal. I have searched bugzilla for the strings from the message, and not finding them I am making the bug report as requested. Are there any logs you want me to save next time this happens? -- 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.

1 6

[Bug 104590] ISDN start script is always running
by bugzilla_noreply＠novell.com 02 Feb '09

02 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=104590 User swamp(a)suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=104590#c9 Swamp Script User <swamp(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.1:22238 --- Comment #9 from Swamp Script User <swamp(a)suse.com> 2009-02-02 04:10:52 MST --- Update released for: yast2-network, yast2-network-devel-doc Products: openSUSE 11.1 (i586, ppc, x86_64) -- 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.

1 0