April 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 497576] New: colemak layout broken in KDE4.2, working in GNOME
by bugzilla_noreply＠novell.com 07 Oct '09

07 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=497576 Summary: colemak layout broken in KDE4.2, working in GNOME Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: curiousjan(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 Selecting the colemak layout requires changing the behavior of Caps lock to delete. This works just fine in GNOME, but KDE still uses Caps lock in the Colemak layout Reproducible: Always Steps to Reproduce: 1.Change desktop to KDE 2.Change layout to Colemak(US) 3.login and type Actual Results: Find that the caps lock key still changes capitalization, although colemak does not have a caps lock. Expected Results: pressing caps lock should produce a backspace -- 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.

1 1

[Bug 499113] New: Sound is super quiet even though volume is up.
by bugzilla_noreply＠novell.com 06 Oct '09

06 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=499113 Summary: Sound is super quiet even though volume is up. Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: au4dp(a)yahoo.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 When I turn on my computer the sound does not work correctly. There is sound but it is so faint I cannot hear it unless I put my ear to the speakers and even then I can barely hear it. My volume is up on both the mixer and the speakers. Reproducible: Always Steps to Reproduce: 1.Turn on computer 2.log on to openSUSE Actual Results: Super Faint Sound Expected Results: the sound should have been loud enough to hear. My info as gathered by ALSA Information Script v 0.4.56 http://www.alsa-project.org/db/?f=0ac02e878ac8fd4f797e3e4dd15e4e1e9273695b -- 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.

1 8

[Bug 494189] New: Faulty kernel module for sound card Opti 82c933
by bugzilla_noreply＠novell.com 06 Oct '09

06 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=494189 Summary: Faulty kernel module for sound card Opti 82c933 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rcoo(a)free.fr QAContact: qa(a)suse.de Found By: --- Created an attachment (id=285295) --> (http://bugzilla.novell.com/attachment.cgi?id=285295) bootlog User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1 Firefox/3.0.8 I own an old PC, running OpenSuSE 11.1 (works perfect). The installed ISA (not PCI) sound card is based upon an OPTi 82c933 chip. At boot I obtain error messages Reproducible: Always Steps to Reproduce: 1. Install OPTI 933 sound card 2. Start 3. Read bootlog Actual Results: No sound can be produced. Intending a YasT configuration provokes a system freeze. Expected Results: Sound, of course. This sound card worked almost normally under opneSuSE 10.3 (autoconfig worked) -- 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.

1 5

[Bug 496281] New: no options for this module => CMI8788 [Oxygen HD Audio]
by bugzilla_noreply＠novell.com 06 Oct '09

06 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=496281 Summary: no options for this module => CMI8788 [Oxygen HD Audio] Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: pearson44j(a)wanadoo.fr QAContact: qa(a)suse.de Found By: --- Created an attachment (id=286643) --> (http://bugzilla.novell.com/attachment.cgi?id=286643) YaST details and pics User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.9 (like Gecko) SUSE I have no sound Primary sound card is Xonar Essence STX 03:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] Subsystem: ASUSTeK Computer Inc. Virtuoso 100 (Xonar Essence STX) Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at a000 [size=256] Capabilities: [c0] Power Management version 2 There are no options for this module => CMI8788 [Oxygen HD Audio] Reproducible: Always Steps to Reproduce: 1. install Xonar Essence STX sound card => no sound 2. 3. Actual Results: YaST shows CMI8788 [Oxygen HD Audio] When I select Edit, YaST says There are no options for this module => CMI8788 [Oxygen HD Audio] EP45:/proc # lsmod | grep snd snd_pcm_oss 42452 0 snd_mixer_oss 14468 1 snd_pcm_oss snd_seq 53468 0 snd_seq_device 7308 1 snd_seq snd_hda_codec_atihdmi 3304 1 snd_hda_intel 26152 3 snd_hda_codec 70628 2 snd_hda_codec_atihdmi,snd_hda_intel snd_hwdep 7164 1 snd_hda_codec snd_pcm 78900 4 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 21316 2 snd_seq,snd_pcm snd 60984 14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 7068 1 snd snd_page_alloc 8888 2 snd_hda_intel,snd_pcm Expected Results: Seeing the price of this card and the manufacturer (ASUSTeK Computer Inc. Virtuoso 100 (Xonar Essence STX) - and the fact that it will soon be very popular it would be nice if it would work under your next release see attachments -- 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.

1 28

[Bug 498018] New: MSI PR200: brightness keys go haywire when defined as a hal quirk
by bugzilla_noreply＠novell.com 05 Oct '09

05 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=498018 Summary: MSI PR200: brightness keys go haywire when defined as a hal quirk Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jmatejek(a)novell.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.3 Firefox/3.0.8 so. there is no hal quirk configuration for my notebook - but all keys do what they're supposed to do, except that they also spam syslog with "unknown keycode" messages. i tried to fix that, using the guide from http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html i added the following to the default 30-keymap-misc.fdi file : <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" contains="MSI Notebook PR200"> <append key="input.keymap.data" type="strlist">e064:f22</append>  <append key="input.keymap.data" type="strlist">e077:brightnessdown</append>  <append key="input.keymap.data" type="strlist">e078:brightnessup</append>   <append key="input.keymap.data" type="strlist">e079:prog1</append>  <append key="input.keymap.data" type="strlist">e06e:camera</append>  <append key="input.keymap.data" type="strlist">e076:wlan</append>  <append key="input.keymap.data" type="strlist">e062:bluetooth</append>  </match> when the changes took effect, everything still worked and syslog was no longer spammed. however, after playing a bit with brightness keys, the backlight started blinking randomly, X's cpu usage went through the roof and X was no longer usable. also, a whole new keycode appeared in syslog, many times over: atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. i didn't press any keys and i don't know what this might be. when i restarted X via double-ctrl-alt-bksp, another keycode appeared, but only once: atkbd.c: Unknown key released (translated set 2, code 0x5b on isa0060/serio0). atkbd.c: Use 'setkeycodes 5b <keycode>' to make it known. (i'm not sure i can reproduce this one, though) after some restarting hal and X processes from a remote session, the system was usable again. Reproducible: Always if you close this as invalid with "don't modify quirk confs", i'm just going to submit a new bug called "quirk conf missing for PR200", provide info and let somebody else hit the same bug again :P also, it would be nice, once this is resolved, to merge the quirk conf and send it upstream then again ... the system is usable without a quirk conf, all keys do what they're supposed to. it just makes reporting other bugs that much harder, because one has to filter out the keycode spam from syslogs first -- 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.

1 8

[Bug 493878] New: KIWI: recovery stops working after firstboot
by bugzilla_noreply＠novell.com 05 Oct '09

05 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=493878 Summary: KIWI: recovery stops working after firstboot Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: i586 OS/Version: SLED 11 Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)novell.com ReportedBy: jsung(a)novell.com QAContact: adrian(a)novell.com CC: aliao(a)novell.com, machen(a)novell.com Found By: --- Created an attachment (id=285192) --> (http://bugzilla.novell.com/attachment.cgi?id=285192) patch for kiwi Hi, After finishing firstboot, the recovery stops working. It fails to mount imageRecoveryDevice since the variable is not set. The attached patch should fix this issue. -- 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.

1 3

[Bug 491834] New: Desktop freezing repeatedly
by bugzilla_noreply＠novell.com 05 Oct '09

05 Oct '09

http://bugzilla.novell.com/show_bug.cgi?id=491834 Summary: Desktop freezing repeatedly Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chuller(a)novell.com QAContact: qa(a)suse.de Found By: Component Test Description: On my workstation the desktop freezes after some days of usage. This behavior repeats about every second to third week. The mouse is still moving and the X applications still redraw their content, however it is not possible anymore to click anywhere as the mouse clicks seem not to reach the application windows anymore. Dmesg shows some output that I have not seen before, it might be a pointer to what is happening. Howto repeat: Install OpenSUSE 11.1 and use it for a longer time without reboot or logout. The output from dmesg: ------------------------snip---------------------------- CPU0 attaching NULL sched-domain. CPU1 attaching NULL sched-domain. CPU0 attaching sched-domain: domain 0: span 0-1 level MC groups: 0 1 domain 1: span 0-1 level NODE groups: 0-1 CPU1 attaching sched-domain: domain 0: span 0-1 level MC groups: 1 0 domain 1: span 0-1 level NODE groups: 0-1 heci: schedule work the heci_bh_handler failed error=0 heci: schedule work the heci_bh_handler failed error=0 heci: schedule work the heci_bh_handler failed error=0 heci: schedule work the heci_bh_handler failed error=0 heci: schedule work the heci_bh_handler failed error=0 heci: schedule work the heci_bh_handler failed error=0 CPU0 attaching NULL sched-domain. CPU1 attaching NULL sched-domain. CPU0 attaching sched-domain: domain 0: span 0-1 level MC groups: 0 1 domain 1: span 0-1 level NODE groups: 0-1 CPU1 attaching sched-domain: domain 0: span 0-1 level MC groups: 1 0 domain 1: span 0-1 level NODE groups: 0-1 ------------------------snip---------------------------- -- 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.

1 10

[Bug 497971] New: upgrade KDE4 using stable repos has an internal conflict and can lead to breaking an installation
by bugzilla_noreply＠novell.com 30 Sep '09

30 Sep '09

http://bugzilla.novell.com/show_bug.cgi?id=497971 User mvdv(a)spamcop.net added comment http://bugzilla.novell.com/show_bug.cgi?id=497971#c16 Summary: upgrade KDE4 using stable repos has an internal conflict and can lead to breaking an installation Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mvdv(a)spamcop.net QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=288045) --> (http://bugzilla.novell.com/attachment.cgi?id=288045) YaST2 conflicts screenshot 1 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1 Firefox/3.0.6, Ant.com Toolbar 1.3 This bug reproduces the steps and effects reported in Comment #16 of Bug #494160 Note if you abort while downloading a package you can have a mangled installation and you can even have YaST2 refuse to update from the same repo, so the update /must/ run without error and without given any scares. Reproducible: Always Steps to Reproduce: 1. Download openSUSE 11.0 VirtualBox archive and extract vdi.: http://downloads.sourceforge.net/virtualboximage/opensuse-11.0-kde4-x86.7z 2. Setup VB guest machine (see attached machine description file (xml). 3. Start openSUSE 11.0 guest. 4. Take a snapshot of the guest openSUSE-11.0. 6. (right)CTRL+F1 7. login as root: init 3 zypper mr --keep-packages --remote zypper refresh zypper mr --all --no-refresh zypper dup --dry-run zypper dup zypper clean zypper mr --all --refresh init 5 8. Repeat Comment #16 Bug #494160 steps: Under the section "STABLE KDE Project (KDE 4.1.3)" on the page: http://en.opensuse.org/KDE4 Select the basic desktop for 11.0: http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS… Accept the repos and software the one-click installer proposes to add: http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSU… (KDE:KDE4:STABLE:Desktop)- http://download.opensuse.org/repositories/devel:/tools:/building/openSUSE_1… (devel:tools:building) http://download.opensuse.org/update/11.0/ (openSUSE:11.0:Update)Running Software to be installed: kde4-dolphin kde4-kdepasswd kde4-kdialog kde4-keditbookmarks kde4-kfind kde4-kio_sysinfo-branding-openSUSE kde4-kmix kde4-konqueror kde4-konsole kde4-kwin kde4-kwrite kdebase4 kdebase4-openSUSE kdebase4-session kdebase4-workspace kdebase4-workspace-branding-openSUSE kdebase4-workspace-plasmoids Select Next, then yes, login as root. Warning about workspace plasmoids appears (screenshot yast2-1-005.png). *** Yast@ wants to, not install, deinstall or downgrade to to KDE 4.0.4, a total of 65 packages!!! *** The 11.0 update repo seems to be the source of this error. The one click install clearly indicates 4.1.3 is going to be installed, but instead it looks like you can easily be downgraded to 4.0.4 **** The 11.0 updates repo and workspace plasmoids package are _both_ added by the oneclick installer **** Specifically, kdebase4-workspace-plasmoids package was not installed previously. So the choices are: a) Abort and moveon.org b) Accept the first choice (deinstall, not install, downgrade) c) Don't install/update kdebase4-workspace-plasmoids, d) Ignore dependencies e) Abort, disable the 11.0 updates repo, try again, in which case you'll go around in circles.... This is a bug? if so in.... - update repo? - STABLE:KDE4 repo? - one click installer? - elsewhere? Likewise: I elected to deinstall compiz-kde4-0.7.4-31.2.i586 (screenshot yast2-1-006.png) Which is the recommended solution? After this the install proceeds without error. # systemsettings --version Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) "release 76.4" System Settings: 4.1.3 (KDE 4.1.3) "release 76.4" Actual Results: If you accepted the first course of action to resolve the workspace-plasma and compiz conflicts you'd have a mixed bag of KDE 4.0.4 and KDE 4.1.3 installed. Expected Results: No conflict on upgrading to KDE4 after having run: `zypper dup` -- 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.

1 8

[Bug 494160] New: A default user's polkit-auth settings are empty by default
by bugzilla_noreply＠novell.com 30 Sep '09

30 Sep '09

http://bugzilla.novell.com/show_bug.cgi?id=494160 Summary: A default user's polkit-auth settings are empty by default Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: mvdv(a)spamcop.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1 Firefox/3.0.6, Ant.com Toolbar 1.3 Default user accounts are not permitted to mount or eject removable media. There are many bug reports, forum posts and blog posts advising people to edit xml files or otherwise wrestling with USB/DVD/CDROM drive behavior, e.g. http://sathyasays.com/2008/08/20/how-to-enable-auto-mounting-of-external-dr… Instead openSUSE hal settings should just work. There is a suggested fix for removable media, but what else should be properly set.....? Please can we have a patch for all openSUSE systems, not just 11.2 that sets the 'correct policies' for a user to have a fully functional installation? Reproducible: Always Steps to Reproduce: 1. As an ordinary user run: # polkit-auth 2. 3. Actual Results: empty Expected Results: AT LEAST: org.freedesktop.hal.storage.mount-removable org.freedesktop.hal.storage.eject Suggested fix: # sudo polkit-auth --grant org.freedesktop.hal.storage.mount-removable --user <user_name> # sudo polkit-auth --grant org.freedesktop.hal.storage.eject --user <user_name> -- 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.

1 19

[Bug 497120] New: bridge-creation ignores MTU setting in /etc/sysconfig/network; OK manually with ifconfig
by bugzilla_noreply＠novell.com 26 Sep '09

26 Sep '09

http://bugzilla.novell.com/show_bug.cgi?id=497120 Summary: bridge-creation ignores MTU setting in /etc/sysconfig/network; OK manually with ifconfig Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pgnet.trash(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 on openSUSE 11.1, uname -ri 2.6.27.21-29-xen x86_64 i've defined a bridge, rm /etc/sysconfig/network/ifcfg-eth0 cat /etc/sysconfig/network/ifcfg-brTEST NAME='test' LLADDR='xx:xx:xx:xx:xx:xx' BRIDGE='yes' BRIDGE_PORTS='eth0' BOOTPROTO='static' STARTMODE='auto' BRIDGE_FORWARDDELAY='0' BRIDGE_STP='off' ETHTOOL_OPTIONS='' IPADDR='10.10.10.2/24' BROADCAST='10.10.10.255' NETWORK='10.10.10.0' PREFIXLEN='24' GATEWAY='10.10.10.1' MTU='9000' USERCONTROL='no' NM_CONTROLLED='no' after startup, i've, brTEST Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx inet addr:10.10.10.2 Bcast:10.10.10.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:904 errors:0 dropped:0 overruns:0 frame:0 TX packets:590 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:70580 (68.9 Kb) TX bytes:75995 (74.2 Kb) eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:904 errors:0 dropped:0 overruns:0 frame:0 TX packets:590 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:70580 (68.9 Kb) TX bytes:75995 (74.2 Kb) Interrupt:19 note that the MTU setting is @ '1500'. changing manually, ifconfig eth0 mtu 9000 i get, as expected, ifconfig eth0 | grep -i mtu UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 & ifconfig brTEST | grep -i mtu UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 but am unable to get those MTU values to init/stick @ boot. the eventual goal here is to get JumboFrame transport working between Xen DomUs, and setup automatically on boot. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.

1 2