March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 488987] New: kde4-smb4k: undefined symbol
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=488987 Summary: kde4-smb4k: undefined symbol Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: kailed(a)kailed.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.1 (like Gecko) SUSE smb4k for kde4 is broken (maybe a building issue): smb4k: symbol lookup error: smb4k: undefined symbol: _ZN16Smb4KMountDialog16staticMetaObjectE kde4-smb4k-0.10.2.99svn20090324-1.2 from buildserver with kde-4.2.1 Reproducible: Always Steps to Reproduce: 1. install and call smb4k 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 3

[Bug 490519] New: Sax2 does not have Cherry B.Unlimited keyboard setting
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490519 Summary: Sax2 does not have Cherry B.Unlimited keyboard setting Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jeffmeld(a)shaw.ca QAContact: sax2-maintainer-bugs(a)forge.provo.novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1 Firefox/3.0.8 Sax2 does not detect the Cherry model B.Unlimited wireless keyboard properly and is detected as a Microsoft Natural. The regular keys do function with that setting but not the 4 special keys. The Cherry model B.Unlimited keyboard is not available when manually searched in the list of models. Several other Cherry models are listed. The special keys are as follows: xev# Icon on Key 1) 161 NoSymbol Calculator 2) 236 NoSymbol Email 3) 178 NoSymbol Home 4) 115 Super_L Lock Also, the Cherry B.Unlimited wireless keyboard does not have any LEDS, if possible it would be nice to have a desktop display for the cap, number and scroll lock status. Reproducible: Always Steps to Reproduce: Run Sax2, the keyboard is detected as a Microsoft Natural keyboard. Actual Results: I manually go threw the keyboards and pick the Generic 104PC Keyboard. The regular keys function without issue but do not have function of the calculator, email, home and lock keys. Expected Results: The keyboard is a business model and one would expect the model to be detected and available. -- 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 4

[Bug 486267] New: Latest update of NetworkManager breaks wireless networking
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=486267 Summary: Latest update of NetworkManager breaks wireless networking 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: Larry.Finger(a)lwfinger.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 Since the update to NetworkManager 0.7.0.r4359-15.1.1-x86_64, I could only connect using a wire. Wireless failed. I fixed by downgrading NetworkManager, NetworkManager-glib, NetworkManager-kde and NetworkManager-gnome. The NetworkManager log shows the following: Mar 17 16:06:01 larrylap NetworkManager: <info> Activation (wlan2/wireless): access point 'lwfdjf_rad' has security, but s ecrets are required. Mar 17 16:06:01 larrylap NetworkManager: <info> (wlan2): device state change: 5 -> 6 Mar 17 16:06:01 larrylap NetworkManager: <info> Activation (wlan2) Stage 2 of 5 (Device Configure) complete. Mar 17 16:06:01 larrylap NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: A security policy in pl ace prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.NetworkManagerSettings.Connection.Secrets" member "GetSecrets" error name "(unset)" destinat ion "org.freedesktop.NetworkManagerUserSettings"). I am not using SELinux and I do not know why this violation of security policy shows up. 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 64

[Bug 487401] New: zapping Xserver and switching to text-vc does not work
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=487401 Summary: zapping Xserver and switching to text-vc does not work Classification: openSUSE Product: openSUSE 11.1 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: koenig(a)linux.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- after updating workPC to 11.1 CTRL-ALT-BACKSPACE and CTRL-ALT-F1 to -F6 did not work anymore (initially no ServerFlags section in xorg.conf). I tried to add explicit server flags with no success: Section "ServerFlags" Option "DontVTSwitch" "false" Option "DontZap" "false" EndSection comparing the keyboard section of my working (== zapping/vc-switchign) notebook xorg.conf showed that it's a problem in the keyboard section: Section "InputDevice" Identifier "venus_keyboard" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "pc104" Option "XkbRules" "xfree86" Option "AutoRepeat" "500 30" Option "LeftAlt" "Meta" Option "RightAlt" "ModeShift" # Option "XkbKeymap" "xfree86(us)" # Option "XkbVariant" "nodeadkeys" EndSection if I use one of the last two options ("XkbKeymap"/"XkbVariant") then zapping/switching does not work anymore! bug or known feature ? using option "XkbKeymap" the Xserver log shows the following messages which I wouldn't consider significant for or related to the zapping/vc-switching problem: (**) venus_keyboard: XkbKeymap: "xfree86(us)" (**) venus_keyboard: XkbKeymap overrides all other XKB settings (EE) XKB: No components provided for device venus_keyboard (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap only adding option "XkbVariant" does not issue any server warnings/errors 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.

1 6

[Bug 479341] New: /etc/init.d/ntp ntptimeset wait time is not long enough
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=479341 Summary: /etc/init.d/ntp ntptimeset wait time is not long enough Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dave.hansen.lange(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.1b2) Gecko/20081208 SUSE/3.1b2-3.7 Firefox/3.1b2 If I run /etc/init.d/ntp ntptimeset it waits for 10 seconds before deciding that a server could not be reached. However it usually takes my system 10-15 seconds to complete the process. My solution is simply to increase the time in the script. Line 219 becomes: for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do Reproducible: Always Steps to Reproduce: 1./etc/init.d/ntp ntptimeset Actual Results: . . . . . . . . . no server reached Expected Results: . . . . . . . . . . ntpd: time set -6.292356s To aid in further debugging, the following is what I get if I run the same command with some extra debugging output: linux-6d2n:~ # ntpd -g -u ntp:ntp -c /etc/ntp.conf -qd ntpd 4.2.4p5(a)1.1541-o Mon Jan 19 15:17:30 UTC 2009 (1) addto_syslog: precision = 1.000 usec addto_syslog: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 addto_syslog: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled addto_syslog: Listening on interface #1 wildcard, ::#123 Disabled addto_syslog: Listening on interface #2 lo, ::1#123 Enabled addto_syslog: Listening on interface #3 eth0, fe80::216:17ff:fe1c:47d6#123 Enabled addto_syslog: Listening on interface #4 lo, 127.0.0.1#123 Enabled addto_syslog: Listening on interface #5 lo, 127.0.0.2#123 Enabled addto_syslog: Listening on interface #6 eth0, 192.168.0.198#123 Enabled local_clock: time 0 offset 0.000000 freq 0.000 state 0 addto_syslog: kernel time sync status 0040 peer_crypto_clear: at 0 next 0 assoc ID 57445 key_expire: at 0 peer_clear: at 0 next 1 assoc ID 57445 refid INIT newpeer: 127.0.0.1->127.127.1.0 mode 3 vers 4 poll 6 10 flags 0x1221 0x1 ttl 0 key 00000000 addto_syslog: frequency initialized -50.951 PPM from /var/lib/ntp/drift/ntp.drift peer_crypto_clear: at 0 next 0 assoc ID 57446 key_expire: at 0 peer_clear: at 0 next 2 assoc ID 57446 refid INIT newpeer: 192.168.0.198->202.130.120.114 mode 3 vers 4 poll 6 10 flags 0x201 0x1 ttl 0 key 00000000 peer_crypto_clear: at 0 next 0 assoc ID 57447 key_expire: at 0 peer_clear: at 0 next 3 assoc ID 57447 refid INIT newpeer: 192.168.0.198->219.117.196.43 mode 3 vers 4 poll 6 10 flags 0x201 0x1 ttl 0 key 00000000 local_clock: time 0 offset 0.000000 freq -50.951 state 1 report_event: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) refclock_transmit: at 1 127.127.1.0 refclock_receive: at 1 127.127.1.0 peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000001 clock_filter: n 1 off 0.000000 del 0.000000 dsp 7.937500 jit 0.000001, age 0 auth_agekeys: at 1 keys 1 expired 0 timer: refresh ts 0 timer: interface update transmit: at 2 192.168.0.198->202.130.120.114 mode 3 receive: at 2 192.168.0.198<-202.130.120.114 mode 4 code 1 auth 0 peer 202.130.120.114 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) clock_filter: n 1 off -0.000456 del 0.022638 dsp 7.937501 jit 0.000001, age 0 transmit: at 3 192.168.0.198->219.117.196.43 mode 3 receive: at 3 192.168.0.198<-219.117.196.43 mode 4 code 1 auth 0 peer 219.117.196.43 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) clock_filter: n 1 off 0.003655 del 0.090269 dsp 7.937503 jit 0.000001, age 0 transmit: at 4 192.168.0.198->202.130.120.114 mode 3 receive: at 4 192.168.0.198<-202.130.120.114 mode 4 code 1 auth 0 clock_filter: n 2 off -0.000701 del 0.022794 dsp 3.937509 jit 0.000244, age 0 transmit: at 5 192.168.0.198->219.117.196.43 mode 3 receive: at 5 192.168.0.198<-219.117.196.43 mode 4 code 1 auth 0 clock_filter: n 2 off 0.003829 del 0.091821 dsp 3.937512 jit 0.000174, age 0 transmit: at 6 192.168.0.198->202.130.120.114 mode 3 receive: at 6 192.168.0.198<-202.130.120.114 mode 4 code 1 auth 0 clock_filter: n 3 off -0.001069 del 0.022379 dsp 1.937517 jit 0.000506, age 0 transmit: at 7 192.168.0.198->219.117.196.43 mode 3 receive: at 7 192.168.0.198<-219.117.196.43 mode 4 code 1 auth 0 clock_filter: n 3 off 0.004149 del 0.091690 dsp 1.937520 jit 0.000417, age 0 transmit: at 8 192.168.0.198->202.130.120.114 mode 3 receive: at 8 192.168.0.198<-202.130.120.114 mode 4 code 1 auth 0 clock_filter: n 4 off -0.001107 del 0.022036 dsp 0.937523 jit 0.000444, age 0 transmit: at 9 192.168.0.198->219.117.196.43 mode 3 receive: at 9 192.168.0.198<-219.117.196.43 mode 4 code 1 auth 0 clock_filter: n 4 off 0.003945 del 0.091277 dsp 0.937526 jit 0.000215, age 0 transmit: at 10 192.168.0.198->202.130.120.114 mode 3 receive: at 10 192.168.0.198<-202.130.120.114 mode 4 code 1 auth 0 clock_filter: n 5 off -0.000099 del 0.023618 dsp 0.437527 jit 0.000782, age 0 report_event: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_ntp, 2 events, event_restart' (0xc621) addto_syslog: synchronized to 202.130.120.114, stratum 2 clock_update: at 10 assoc 3 local_clock: assocID 57446 offset -0.000099132 freq -50.951 state 1 addto_syslog: time slew -0.000099 s ntpd: time slew -0.000099s linux-6d2n:~ # -- 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 487590] New: Typos in /etc/sysconfig/mail SKIP_ASK description
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=487590 Summary: Typos in /etc/sysconfig/mail SKIP_ASK description Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: varkoly(a)novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer I just found this text in /etc/sysconfig/mail for SKIP_ASK: # Set this to "yes" if the yast2 mail module must not # start with the with the vizard for asking the ^^^^^^^^^^^^^^^^^ ^^^^^^ One "with the" would be enough. And it's "_w_izard", not vizard. Please correct these typos. -- 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 490037] New: "pccardctl eject" hangs in state D
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490037 Summary: "pccardctl eject" hangs in state D Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: Other Status: NEEDINFO Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jslaby(a)novell.com QAContact: qa(a)suse.de CC: gp(a)novell.com, seife(a)novell.com Blocks: 370872 Found By: --- The logs are at: https://bugzilla.novell.com/attachment.cgi?id=267094 Relevant part: pccardctl D 00000000 0 5359 5358 d2ef5efc 00000082 c0523c0c 00000000 c0585670 c0588300 c0588300 c0588300 cf922d80 cf922ff4 c1d90300 00000000 c1d90300 71d844b0 0000444d de2372c0 cf922ff4 c0523c00 f7929560 f7929564 cf922d80 f7929568 c0344b65 f7929568 Call Trace: [<c0344b65>] __mutex_lock_slowpath+0x60/0x9e [<c0344add>] mutex_lock+0xa/0xb [<f91fe642>] pcmcia_eject_card+0x1a/0x67 [pcmcia_core] [<f9200d53>] pccard_store_eject+0x1b/0x23 [pcmcia_core] [<c029e7b9>] dev_attr_store+0x24/0x29 [<c01d0c00>] sysfs_write_file+0xaf/0xdb [<c018fa60>] vfs_write+0x8b/0x13d [<c018fbb4>] sys_write+0x41/0x67 [<c0104c9b>] sysenter_do_call+0x12/0x2f [<ffffe430>] 0xffffe430 Gerald, please provide sysrq-d info from the kernel available at: http://labs.suse.cz/jslaby/bug-370872/ -- 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 480818] New: pinentry-qt dialog does not handle dead keys correctly
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=480818 Summary: pinentry-qt dialog does not handle dead keys correctly Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mmtsales(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-1.4 Firefox/3.0.6 When using gpg, kgpg or kleopatra do decrypt a file, they use pinentry-qt to ask the user for the passphrase. It is impossible to enter the passphrase correctly if it has accented characters in it, because pinentry-qt dialogs do not handle dead keys correctly. For example, if I type "á", it gets "'a" (two asterisks are shown instead of just one). The same problem occurs when I try to change the password (pinentry-qt is used here too). As a result, I can't decrypt my files because of the accented characters in my private key's passphrase and I can't change the passphrase either. The files were encrypted using Kgpg in Fedora, this problem did not exist there. Reproducible: Always Steps to Reproduce: 1. Open Kgpg 2. Try to change the passphrase of a private key of yours by another with accented characters in it Actual Results: Asterisks are shown immediately after a dead key is pressed. Expected Results: An asterisk should be shown only when the next key is pressed after the dead key. -- 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 9

[Bug 490593] New: kmps have requires on symbols
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490593 Summary: kmps have requires on symbols Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: mmarek(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de CC: jeffm(a)novell.com, agruen(a)novell.com, dmueller(a)novell.com Found By: --- I checked preload-kmp-default and kvm-kmp-default and both are empty in requires on kernel-default. There must be a bug in the way these requires are calculated by rpm. -- 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 490170] New: /etc/init.d/boot.crypto forgets to remove a loop device on some circumstances.
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490170 Summary: /etc/init.d/boot.crypto forgets to remove a loop device on some circumstances. Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1 Firefox/3.0.7 Setup: /etc/crypttab: cr_mm_dvd.l /dev/dvd.l none noauto,loop cr_mm_dvd /dev/dvd none noauto,loop \ cipher=twofish-cbc-plain,size=256,hash=sha512 fstab: /dev/mapper/cr_mm_dvd.l /mnt/dvd.crypta.l auto \ ro,noauto,user,noatime,nodiratime 0 0 nimrodel:~ # l /dev/dvd.l lrwxrwxrwx 1 root root 8 Mar 25 04:30 /dev/dvd.l -> /dev/dvd The dev/dvd.l has to be a symlink because: /dev/dvd.l for LUKS encrypted dvds. /dev/dvd for old style encrypted dvds (previous to LUKS in SuSE) /dev/dvd is used in fstab for normal dvds What happens? When I put a LUKS encrypted DVD, after a while the gnome desktops asks for a password, which I refuse. Then I mount it manually: :~ # rccrypto start cr_mm_dvd.l and checking with "losetup -a" gives the expected output: /dev/loop2: [000f]:5034 (/dev/hdc) But after I umount the dvd: :~ # rccrypto stop cr_mm_dvd.l the loop device is not freed: /dev/loop2: [000f]:5034 (/dev/hdc) If I mount the dvd again (:~ # rccrypto start cr_mm_dvd.l) I get two loop devices: /dev/loop2: [000f]:5034 (/dev/hdc) /dev/loop5: [000f]:5034 (/dev/hdc) and three if I repeat the process: /dev/loop2: [000f]:5034 (/dev/hdc) /dev/loop5: [000f]:5034 (/dev/hdc) /dev/loop6: [000f]:5034 (/dev/hdc) Till a moment when the system is out of loop devices. They have to be removed manually. This problem does not occur with the other entries in crypttab, but this is the only one with symlinks to devices. Reproducible: Always Clasified as "security" as encryption is a security feature, but perhaps it should be "basesystem". I'm unsure. -- 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