September 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 527108] New: zypper puppet provider fails when there is a new gpg key to accept
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

http://bugzilla.novell.com/show_bug.cgi?id=527108 Summary: zypper puppet provider fails when there is a new gpg key to accept Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mgiammarco(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1) Gecko/20090707 Iceweasel/3.5 (Debian-3.5-1) Puppet is used to mass install software. Suse puppet package maintainer has added a zypper provider (good thing). The zypper provider uses "-y" option to install software in non interactive mode (good too). But if I install a new repository via puppet and I install some packages from it the installation fails because zypper refuse automatically the gpg key. The option --no-gpg-checks should be added to let puppet do its work. Obviously the system administrator checks the gpg key in separate testing server so he is sure that the packages are not infected when he then does mass install with puppet. Reproducible: Always Steps to Reproduce: 1.add a new repository via puppet. 2.install a package using puppet. Actual Results: puppet refuse key and then it does not install package. BTW zypper produces a lot of logs. Because puppet tries forever the installation (due to zypper failing) it quickly fills /var/log blocking suse. Expected Results: The package is installed. /var/log is not full. -- 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

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in the NEW orREOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to default assignee of selected component" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=NEW&bug_status=REOPENED&a… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! software.opensuse.org doesn't look good in German, French, Lithuanian -> http://bugzilla.novell.com/show_bug.cgi?id=715625

1 0

[Bug 710269] Install/Update from nfs source (and probably others like smb) fails for factory (since 11.4)
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=710269 https://bugzilla.novell.com/show_bug.cgi?id=710269#c Hans-Peter Jansen <hpj(a)urpla.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[Test Case 921924] Update |Install/Update from nfs |(started from media) - |source (and probably others |SLES11-SP1 (all updates) / |like smb) fails for factory |default / smb / local |(since 11.4) |graphic / ext3 | -- 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

[Bug 711708] New: xorg crashes sometimes after resume
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=711708 https://bugzilla.novell.com/show_bug.cgi?id=711708#c0 Summary: xorg crashes sometimes after resume Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jslaby(a)novell.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=445327) --> (http://bugzilla.novell.com/attachment.cgi?id=445327) xorg.log with crash Sometimes, when I resume and it switches the console, the server crashes as below. I'm running 11.4 + tumbleweed: kernel-desktop-3.0.0-1.1.x86_64 kernel-desktop-3.0.1-1.1.x86_64 kernel-desktop-devel-3.0.0-1.1.x86_64 kernel-desktop-devel-3.0.1-1.1.x86_64 kernel-devel-3.0.0-1.1.noarch kernel-devel-3.0.1-1.1.noarch kernel-firmware-20110709-47.1.noarch nfs-kernel-server-1.2.3-27.1.x86_64 xorg-x11-7.6-43.44.1.x86_64 xorg-x11-driver-input-7.6-29.1.x86_64 xorg-x11-driver-video-7.6-53.58.1.x86_64 xorg-x11-driver-video-intel-legacy-2.9.1-8.1.x86_64 xorg-x11-driver-video-radeonhd-1.3.0_20100512_80ba041-2.1.x86_64 xorg-x11-driver-video-unichrome-20091206-9.1.x86_64 xorg-x11-fonts-7.6-10.1.noarch xorg-x11-fonts-core-7.6-10.1.noarch xorg-x11-libfontenc-7.6-6.1.x86_64 xorg-x11-libfontenc-32bit-7.6-6.1.x86_64 xorg-x11-libICE-7.6-8.1.x86_64 xorg-x11-libICE-32bit-7.6-8.1.x86_64 xorg-x11-libs-7.6-16.1.x86_64 xorg-x11-libSM-7.6-7.1.x86_64 xorg-x11-libSM-32bit-7.6-7.1.x86_64 xorg-x11-libs-32bit-7.6-16.1.x86_64 xorg-x11-libXau-7.6_1.0.6-6.1.x86_64 xorg-x11-libXau-32bit-7.6_1.0.6-6.1.x86_64 xorg-x11-libxcb-7.6_1.7-8.1.x86_64 xorg-x11-libxcb-32bit-7.6_1.7-8.1.x86_64 xorg-x11-libXdmcp-7.6-7.1.x86_64 xorg-x11-libXdmcp-32bit-7.6-7.1.x86_64 xorg-x11-libXext-7.6_1.2.0-2.1.x86_64 xorg-x11-libXext-32bit-7.6_1.2.0-2.1.x86_64 xorg-x11-libXfixes-7.6_4.0.5-6.1.x86_64 xorg-x11-libXfixes-32bit-7.6_4.0.5-6.1.x86_64 xorg-x11-libxkbfile-7.6-6.1.x86_64 xorg-x11-libxkbfile-32bit-7.6-6.1.x86_64 xorg-x11-libXmu-7.6-7.1.x86_64 xorg-x11-libXmu-32bit-7.6-7.1.x86_64 xorg-x11-libXp-7.6-2.1.x86_64 xorg-x11-libXpm-7.6-6.1.x86_64 xorg-x11-libXpm-32bit-7.6-6.1.x86_64 xorg-x11-libXprintUtil-7.6-2.1.x86_64 xorg-x11-libXprintUtil-32bit-7.6-2.1.x86_64 xorg-x11-libXp-32bit-7.6-2.1.x86_64 xorg-x11-libXrender-7.6_0.9.6-6.1.x86_64 xorg-x11-libXrender-32bit-7.6_0.9.6-6.1.x86_64 xorg-x11-libXt-7.6_1.0.9-4.1.x86_64 xorg-x11-libXt-32bit-7.6_1.0.9-4.1.x86_64 xorg-x11-libXv-7.6-6.1.x86_64 xorg-x11-libXv-32bit-7.6-6.1.x86_64 xorg-x11-libX11-7.6-10.2.x86_64 xorg-x11-libX11-32bit-7.6-10.2.x86_64 xorg-x11-server-7.6_1.9.3-15.24.2.x86_64 xorg-x11-server-debuginfo-7.6_1.9.3-15.24.2.x86_64 xorg-x11-server-extra-7.6_1.9.3-15.24.2.x86_64 xorg-x11-xauth-7.6-43.44.1.x86_64 xorg-x11-server-debuginfo is new, the trace generated is not with debuginfo, so it's incomplete... I will attach output of gdb. My card: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV515 [Radeon Mobility X1450] [1002:7186] (II) AIGLX: Resuming AIGLX clients after VT switch (II) RADEON(0): EDID vendor "CMO", prod id 5392 (II) RADEON(0): Printing DDC gathered Modelines: (II) RADEON(0): Modeline "1400x1050"x0.0 108.00 1400 1448 1560 1688 1050 1053 1057 1066 -hsync -vsync (64.0 kHz) Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x483068] 1: /usr/bin/Xorg (0x400000+0x5e6d9) [0x45e6d9] 2: /lib64/libc.so.6 (0x7f7b2fb4b000+0x32b30) [0x7f7b2fb7db30] 3: /usr/bin/Xorg (0x400000+0x14e48f) [0x54e48f] 4: /usr/bin/Xorg (0x400000+0x14cebc) [0x54cebc] 5: /usr/bin/Xorg (0x400000+0x14d134) [0x54d134] 6: /usr/bin/Xorg (xf86Wakeup+0x44d) [0x46b90d] 7: /usr/bin/Xorg (WakeupHandler+0x4b) [0x446ffb] 8: /usr/bin/Xorg (WaitForSomething+0x1ca) [0x45c02a] 9: /usr/bin/Xorg (0x400000+0x522e2) [0x4522e2] 10: /usr/bin/Xorg (0x400000+0x25ace) [0x425ace] 11: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f7b2fb69bfd] 12: /usr/bin/Xorg (0x400000+0x25679) [0x425679] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting -- 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 714631] New: libcgroup1: use of /var/lock/subsys unsupported
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=714631 https://bugzilla.novell.com/show_bug.cgi?id=714631#c0 Summary: libcgroup1: use of /var/lock/subsys unsupported Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: jslaby(a)novell.com ReportedBy: lnussel(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- libcgroup1 uses /var/lock/subsys which is unsupported on openSUSE. On openSUSE /var/lock is reserved for device lock files and must not be used for other purposes. Due to the use of tmpfs on /var/lock the subsys directory does not exist anymore either so if your package used /var/lock/subsys for any real purpose it might be silently broken already. Please fix your packge to not use /var/lock/subsys. http://en.opensuse.org/openSUSE:Packaging_checks#subsys-unsupported -- 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 656642] New: wlan does not work after upgrade to milestone 4
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=656642 https://bugzilla.novell.com/show_bug.cgi?id=656642#c0 Summary: wlan does not work after upgrade to milestone 4 Classification: openSUSE Product: openSUSE 11.4 Version: Milestone 4 of 6 Platform: 32bit OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: harmie(a)opensuse.fi QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi-FI; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-3.4 Firefox/3.6.10 After upgrading from opensuse 11.2 milestone 2 to milestone 3 & 4 my wireless stops working. It will connect after boot for short time but after a few minutes it drops the connection and keeps asking the wireless password without connecting it again. It works in milestone 2 which I have installed in separate partition. I have this in /var/log/messages Nov 30 20:53:01 compaq kernel: [ 334.579202] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 Nov 30 20:53:01 compaq kernel: [ 334.579250] b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO. Nov 30 20:53:01 compaq kernel: [ 334.579263] b43-phy0: Controller RESET (DMA error) ... Nov 30 20:53:01 compaq kernel: [ 334.579283] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 Nov 30 20:53:01 compaq kernel: [ 334.579287] b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO. Nov 30 20:53:01 compaq kernel: [ 334.579299] b43-phy0: Controller RESET (DMA error) ... Nov 30 20:53:01 compaq kernel: [ 334.822751] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) Nov 30 20:53:03 compaq kernel: [ 336.898460] b43-phy0: Controller restarted Nov 30 20:53:04 compaq kernel: [ 337.122738] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) Nov 30 20:53:06 compaq kernel: [ 339.207657] b43-phy0: Controller restarted Nov 30 20:53:17 compaq kernel: [ 350.505091] ieee80211 phy0: wlan0: No probe response from AP 00:24:01:e7:ff:1c after 500ms, disconnecting. Nov 30 20:53:17 compaq kernel: [ 350.521898] cfg80211: Calling CRDA to update world regulatory domain Nov 30 20:53:17 compaq kernel: [ 350.534410] cfg80211: World regulatory domain updated: Nov 30 20:53:17 compaq kernel: [ 350.534423] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Nov 30 20:53:17 compaq kernel: [ 350.534427] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 30 20:53:17 compaq kernel: [ 350.534439] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Nov 30 20:53:17 compaq kernel: [ 350.534442] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Nov 30 20:53:17 compaq kernel: [ 350.534454] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 30 20:53:17 compaq kernel: [ 350.534457] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 30 20:53:18 compaq kernel: [ 351.954775] wlan0: authenticate with 00:24:01:e7:ff:1c (try 1) Nov 30 20:53:19 compaq kernel: [ 352.154102] wlan0: authenticate with 00:24:01:e7:ff:1c (try 2) Nov 30 20:53:19 compaq kernel: [ 352.354071] wlan0: authenticate with 00:24:01:e7:ff:1c (try 3) Nov 30 20:53:19 compaq kernel: [ 352.554103] wlan0: authentication with 00:24:01:e7:ff:1c timed out Nov 30 20:53:33 compaq avahi-daemon[1670]: Withdrawing address record for 10.10.10.10 on wlan0. Nov 30 20:53:33 compaq avahi-daemon[1670]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.10.10.10. Nov 30 20:53:33 compaq avahi-daemon[1670]: Interface wlan0.IPv4 no longer relevant for mDNS. Here is more details about the hw 25: PCI 600.0: 0282 WLAN controller [Created at pci.318] Unique ID: y9sn.YXxFBNiV6c8 Parent ID: WL76.MLkyAiVHgf0 SysFS ID: /devices/pci0000:00/0000:00:09.0/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "Broadcom BCM4312 802.11b/g" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x4315 "BCM4312 802.11b/g" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x1508 Revision: 0x01 Driver: "b43-pci-bridge" Driver Modules: "ssb" Device File: wlan0 Features: WLAN Memory Range: 0x92000000-0x92003fff (rw,non-prefetchable) IRQ: 17 (no events) HW Address: 90:4c:e5:6e:d4:c5 Link detected: no WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000014E4d00004315sv0000103Csd00001508bc02sc80i00" Driver Info #0: Driver Status: ssb is active Driver Activation Cmd: "modprobe ssb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #5 (PCI bridge) These are the installed packages rpm -qa | grep -i network NetworkManager-0.8.1-1.7.i586 kdenetwork4-filesharing-4.5.1-1.4.i586 NetworkManager-glib-0.8.1-1.7.i586 NetworkManager-openvpn-0.8.1-1.6.i586 NetworkManager-pptp-kde4-0.9.svn1161677-1.1.i586 glib-networking-2.25.0-1.3.i586 yast2-network-2.19.38-1.2.i586 NetworkManager-vpnc-kde4-0.9.svn1161677-1.1.i586 libproxy1-networkmanager-0.4.6-2.4.i586 NetworkManager-vpnc-0.8.1-1.6.i586 NetworkManager-kde4-libs-0.9.svn1161677-1.1.i586 NetworkManager-kde4-0.9.svn1161677-1.1.i586 NetworkManager-pptp-0.8.1-1.6.i586 NetworkManager-openvpn-kde4-0.9.svn1161677-1.1.i586 Reproducible: Always Steps to Reproduce: 1.upgrade from milestone 2 to milestone 3 or 4 2.boot the upgraded opensuse 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 22

[Bug 710269] [Test Case 921924] Update (started from media) - SLES11-SP1 (all updates) / default / smb / local graphic / ext3
by bugzilla_noreply＠novell.com 18 Sep '11

18 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=710269 https://bugzilla.novell.com/show_bug.cgi?id=710269#c Hans-Peter Jansen <hpj(a)urpla.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Group|SUSE Enterprise Partner | Component|libzypp |libzypp Version|Beta3 |Factory Product|SUSE Linux Enterprise |openSUSE 12.1 |Server 11 SP2 (SLES 11 SP2) | -- 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

[Bug 708861] New: FIBMAP: Invalid argument
by bugzilla_noreply＠novell.com 17 Sep '11

17 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=708861 https://bugzilla.novell.com/show_bug.cgi?id=708861#c0 Summary: FIBMAP: Invalid argument Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/6.0 On booting I get several pages of FIBMAP: Invalid argument on console 1 (CTL+ALT+F1) Since this is a known problem, but not listed as bug (at least I could find no entry to this end) someone sould probably go ahead and fix it, as suggested at http://195.135.221.135/opensuse-factory/2011-06/msg00133.html Reproducible: Always -- 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 711006] New: error in starting amavis deamon from yast2 E-Mail Server configuration
by bugzilla_noreply＠novell.com 17 Sep '11

17 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=711006 https://bugzilla.novell.com/show_bug.cgi?id=711006#c0 Summary: error in starting amavis deamon from yast2 E-Mail Server configuration Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=444723) --> (http://bugzilla.novell.com/attachment.cgi?id=444723) yast,messages,warn User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 I´ve used yast2 to setup a E-Mail Server. During finishing there was a problem with restart services done by yast2. It is the amavis deamon with causes an error popup(no further information in this->only an o.k button). I will provide logs and a screenshot which shows in "Monitor" that amavis is started but which some heavy failures(memory,cpu usage). A try of starting amavis with yast2->runlevel (was on :yes*) results in a "...amavis start returned 7 program is not running" Reproducible: Didn't try 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 7

[Bug 715862] New: KCharSelect first letter in description is missed
by bugzilla_noreply＠novell.com 17 Sep '11

17 Sep '11

https://bugzilla.novell.com/show_bug.cgi?id=715862 https://bugzilla.novell.com/show_bug.cgi?id=715862#c0 Summary: KCharSelect first letter in description is missed Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: krachkovsky(a)mail.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=449112) --> (http://bugzilla.novell.com/attachment.cgi?id=449112) screenshot User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; uk-UA) AppleWebKit/533.3 (KHTML, like Gecko) rekonq Safari/533.3 Bug is spesific to KDE 4.7.1 from KDE Distro Factory repository. First letter of character desription is missed. Every description is corrupted - current symbol and 'see also' list. Due to https://bugs.kde.org/show_bug.cgi?id=281264#c4 openSuSE packages has new code and old data file. Reproducible: Always Steps to Reproduce: 1. Just open KCharSelect and choose any symbol -- 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