November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 693039] New: skype symbol lookup error in libQtGui
by bugzilla_noreply＠novell.com 23 Sep '13

23 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=693039 https://bugzilla.novell.com/show_bug.cgi?id=693039#c0 Summary: skype symbol lookup error in libQtGui Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: th.plaga(a)fz-juelich.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Various skype versions (2.1.0.81 / 2.2.0.25) could not start!! skype: symbol lookup error: /usr/lib/libQtGui.so.4: undefined symbol: _ZN24QAbstractDeclarativeData9destroyedE libqt4-x11-32bit-4.7.1-8.2.x86_64 openSuSE 11.3 - x86_64 Reproducible: Always Steps to Reproduce: 1. just starting skype 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 643176] New: qcatool2 hangs trying to access gnupg plugin.
by bugzilla_noreply＠novell.com 23 Sep '13

23 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=643176 https://bugzilla.novell.com/show_bug.cgi?id=643176#c0 Summary: qcatool2 hangs trying to access gnupg plugin. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: dnascimento(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10 Trying to list the supported keystores using: qcatool2 keystore list-stores the command hangs. Reproducible: Always Steps to Reproduce: 1. Run: qcatool2 keystore list-stores Actual Results: Command doesn't return. Expected Results: Command should list the available keystores. To fix this problem is necessary to install the package libgpgme-devel. It should be a dependency of the libqca2 or libqca-gnupg.so should be placed in a different package which depends of libgpgme-devel. -- 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 625404] New: FreeNX uses authorized_keys2 as default key file, while sshd uses authorized_keys.
by bugzilla_noreply＠novell.com 23 Sep '13

23 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=625404 http://bugzilla.novell.com/show_bug.cgi?id=625404#c0 Summary: FreeNX uses authorized_keys2 as default key file, while sshd uses authorized_keys. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: muhlemmer(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 Enhangement: Change /var/lib/nxserver/home/.ssh/authorized_keys2 to /var/lib/nxserver/home/.ssh/authorized_keys when running nxsetup --install. Motivation: When running "nxsetup --install" the file /var/lib/nxserver/home/.ssh/authorized_keys2 is created to store the authorized private keys. As nx uses the ssh for tunneling the connection, sshd needs to be pointed to the authorized key file for authentication to work. Under openSUSE (at least version 11.1+ for sure) the default keyfile for sshd is %h/.ssh/authorized_keys. Where %h points to the user's home directory. Now there are to ways to get the connection working: either you set the AuthorizedKeyFile option in sshd_config to %h/.ssh/authorized_keys2, which involves changing all the names of the file for all your users + when you use ssh-copy-id, the new keys go by default to authorized_keys, so not out newly set file. Or (this is a simpler solution) change in ...nxserver/home/ the authorized_keys2 file to authorized_keys. Either way, the default nxserver does not comply with the default sshd, while it maybe working with people who are using the same sshd_config file for the past years and the default settings has been changed throughout the years, but not for them since they un-commented the option. Downside: Maybe to many people are already used to this workaround. Improving this will enforce them to undo there workaround. So we have to decide: be loyal to the old users or make it work right out of the box for new users (which would be my #1 option) Maybe we can run the setup to check the setting of sshd's AuthorizedKeyFile option, this would be a winner for both sides. Reproducible: Always Steps to Reproduce: 1. Install a clean version of openSSH (move to other location: /etc/ssh/ and manualy update package in yast) 2. Run nxsetup --install Actual Results: 1. cat /etc/ssh/sshd_config | grep AuthorizedKeysFile Output: AuthorizedKeysFile .ssh/authorized_keys 2. Or submit a new key to sshd using ssh-copy-id and ls ~/.ssh Output: authorized_keys 3. ls /var/lib/home/.ssh Output: authorized_keys2 Expected Results: nxsetup should create /var/lib/home/.ssh/authorized_keys -- 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 624653] New: Network installation fails under VirtualBox
by bugzilla_noreply＠novell.com 23 Sep '13

23 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=624653 http://bugzilla.novell.com/show_bug.cgi?id=624653#c0 Summary: Network installation fails under VirtualBox Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fremenzone(a)poczta.onet.pl QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=377730) --> (http://bugzilla.novell.com/attachment.cgi?id=377730) Screenshot of error messages User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.2.4) Gecko/20100611 SUSE/3.6.4-6.1 Firefox/3.6.4 Network installation doesn't work under VirtualBox. When network installation CD is booted and the "Installation" is selected from the menu, the kernel loads, booting gets to a point when it displays " Integrating /parts/00_lib" message and then the computer freezes. It's not a kernel panic and it's not actually frozen, it just hangs for a minute, displays information about CPU soft lockup and does the same thing again -> see attached screenshots. The error log (Call trace, etc.) is always the same. Host configuration: - Suse 11.1 x86_64 - kernel: 2.6.27.45-0.1-default - VirtualBox: 3.1.6 Guest: - Suse 11.3 i586, network installation Reproducible: Always -- 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 675411] New: Second network card not identified / depicted correctly
by bugzilla_noreply＠novell.com 23 Sep '13

23 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=675411 https://bugzilla.novell.com/show_bug.cgi?id=675411#c0 Summary: Second network card not identified / depicted correctly Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dieter.jurzitza(a)t-online.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=416417) --> (http://bugzilla.novell.com/attachment.cgi?id=416417) This looks like I'd expect it to - both NICS have the same name User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 When starting yast2 from the RC1-CD of openSUSE11.4, the second network card on my mainboard (Tyan Thunder) is not shown correctly. In contrast, this works ok for openSUSE 11.3, so something must have gone wrong here. Please take a look onto the pictures attached, one from openSUSE 11.3, one from openSUSE 11.4, both on the same computer - the NICs are identical! Reproducible: Always Steps to Reproduce: 1. Boot openSUSE 11.4 2. configure network 3. the NICS are depicted different Actual Results: Two names for two identical NICS Expected Results: Similar names for two identical NICS This is the result when configuring the NICs on my PC from within openSUSE 11.3. Both network cards are identified identically as they are identical (and use the same driver) -- 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 690178] New: gnome3: once gtkimageview3 lands, re-enable support in evo
by bugzilla_noreply＠novell.com 22 Sep '13

22 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=690178 https://bugzilla.novell.com/show_bug.cgi?id=690178#c0 Summary: gnome3: once gtkimageview3 lands, re-enable support in evo Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Evolution needs a gtk3-powered gtkimageview for the inline-image plugin. There's no tarball for that yet, but it's work in progress, see: http://trac.bjourne.webfactional.com/ticket/41 http://trac.bjourne.webfactional.com/timeline?from=04%2F27%2F11&daysback=30… -- 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 667806] New: Insufficient escaping in .pc file
by bugzilla_noreply＠novell.com 22 Sep '13

22 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=667806 https://bugzilla.novell.com/show_bug.cgi?id=667806#c0 Summary: Insufficient escaping in .pc file Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs(a)forge.provo.novell.com ReportedBy: christoph(a)maxiom.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.41 (like Gecko) "pkg-config --cflags mobile-broadband-provider-info" output: -DMOBILE_BROADBAND_PROVIDER_INFO=\"/usr/share/mobile-broadband-provider-info/serviceproviders.xml\" According to a KDE developer, the backslash needs to be escaped as well, "which is necessary when adding variables to Makefiles". According to him, after investigation of a build failure on openSUSE, the output should be: -DMOBILE_BROADBAND_PROVIDER_INFO=\\\"/usr/share/mobile-broadband-provider-info/serviceproviders.xml\\\" 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 725934] New: GNOME crashed upon login
by bugzilla_noreply＠novell.com 21 Sep '13

21 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725934 https://bugzilla.novell.com/show_bug.cgi?id=725934#c0 Summary: GNOME crashed upon login Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jrswagswegie1996(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 When I log into GNOME (same problem happens when I use a Live CD, boot an updated system, boot a New Installation system, using GDM, XDM or KDM) I see the Desktop Background then I get a error that reports something has gone wrong and I am usually (not always) prompted to log out. Reproducible: Always Steps to Reproduce: 1.Log in 2.It happens. 3. Actual Results: GNOME crashes and gives an error message "Something has gone wrong! Contact your system administrator" then usually prompts me to log out. Expected Results: GNOME Shell loads I can get around by logging into a window manger like FVWM and typing in xterm GNOME. I have a 2005 Dell Dimension B110 with an Intel 865G graphics card, 1.2 GB of RAM, and a 2.53 GHz Intel Celeron 32-bit processor. This error was not prevalent in Milestone 5, in fact it ran gnome-shell in the non-fallback mode and ran fine. This issue popped up in the Beta and stuck around to the RC1. I am willing to submit xsesion or other logs (just tell me where they are) -- 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 728336] New: gnome-color-manager (part of GNOME 3) doesn't work in openSUSE
by bugzilla_noreply＠novell.com 20 Sep '13

20 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728336 https://bugzilla.novell.com/show_bug.cgi?id=728336#c0 Summary: gnome-color-manager (part of GNOME 3) doesn't work in openSUSE Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: glesage(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- gnome-color-manager is a standard part of GNOME 3… and doesn't work in openSUSE. There are a few reasons why it doesn't work: 1) argyllcms isn't installed by default (and it's a dependency for gnome-color-manager to work) 2) argyllcms isn't even packaged in the main repository (it's in multimedia:photo) 3) gnome-color-manager even knows that argyll must be installed, however, it silently fails when trying to install the package (due to #2) 4) monitor awareness and default profiles are not set up by default (and are missing from the session) unless one toggles the color setting in dconf under org > gnome > settings-daemon > plugins > color > active (this can be accomplished using dconf-editor) 5) when the color plugin is activated, it prompts the user several times for the administrator password; there's some issue with authentication where it isn't given the correct privileges a single time 6) similar to #5, an admin password is needed a couple times each time the profile is changed Issue #3 (and basically #1 & #2) are related to a longstanding bug: https://bugzilla.novell.com/show_bug.cgi?id=619915 Issues #5 & #6 also affect the GNOME 3 desktop in other ways, but aren't as painful as in the color management settings. It appears to be related to this bug: https://bugzilla.novell.com/show_bug.cgi?id=706908 All together, these bugs make it impossible to calibrate one's screen with openSUSE 12.1 and keep using the generated profiles (as one must manually toggle the dconf key each time, and then enter their root password several times after that for *every* time a session is started). A user may even see these password prompts for calibration even if they do not have a device, too. I saw this after installing openSUSE 12.1 RC2 on my mom's and nephew's computer as well as my netbook and workstation @ work. (I did try to calibrate my netbook and my workstation @ work, but the issues above prevented me from using it, even after adding the photo repo for the argyllcms package, installing argyll, making a profile for each monitor, etc.) -- 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 631994] New: Xvnc crash
by bugzilla_noreply＠novell.com 16 Sep '13

16 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=631994 https://bugzilla.novell.com/show_bug.cgi?id=631994#c0 Summary: Xvnc crash Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major 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: --- Blocker: --- rpm -qf /usr/bin/Xvnc xorg-x11-Xvnc-7.5_1.8.0-9.4.x86_64 we found two "ways" to crash Xvnc with very different call traces and situations: 1) the easy (and nasty) one: gnome-session kills Xvnc in strlen(): try: xinit /usr/bin/gnome-session -- /usr/bin/Xvnc :3 gdb backtrace: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff63c96a2 in strlen () from /lib64/libc.so.6 (gdb) where #0 0x00007ffff63c96a2 in strlen () from /lib64/libc.so.6 #1 0x000000000051eecd in ?? () #2 0x000000000051f5d0 in ?? () #3 0x000000000046c74c in ?? () #4 0x000000000045baca in ?? () #5 0x00007ffff636bb7d in __libc_start_main () from /lib64/libc.so.6 #6 0x000000000041ad29 in _start () Backtrace: 0: /usr/bin/Xvnc (xorg_backtrace+0x28) [0x5552a8] 1: /usr/bin/Xvnc (0x400000+0x158a49) [0x558a49] 2: /lib64/libc.so.6 (0x7ffff634d000+0x32a60) [0x7ffff637fa60] 3: /lib64/libc.so.6 (strlen+0x12) [0x7ffff63c96a2] 4: /usr/bin/Xvnc (0x400000+0x11eecd) [0x51eecd] 5: /usr/bin/Xvnc (0x400000+0x11f5d0) [0x51f5d0] 6: /usr/bin/Xvnc (0x400000+0x6c74c) [0x46c74c] 7: /usr/bin/Xvnc (0x400000+0x5baca) [0x45baca] 8: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7ffff636bb7d] 9: /usr/bin/Xvnc (0x400000+0x1ad29) [0x41ad29] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting =============================================================================== 2) a bit more weird: vncviewer-reconnect after server re-initialisation Xvnc crashes with the following sequence: Xvnc :3 & DISPLAY=:3 xterm & vncviewer :3 & exit in xterm vncviewer :3 & the reconnect of the 2nd vncviewer kills Xvnc. backtrace in gdb: Program received signal SIGSEGV, Segmentation fault. 0x000000000050f2c0 in ?? () (gdb) where #0 0x000000000050f2c0 in ?? () #1 0x0000000000473e43 in ?? () #2 0x00000000004b6eba in mieqProcessDeviceEvent () #3 0x00000000004b6feb in mieqProcessInputEvents () #4 0x000000000046c583 in ?? () #5 0x000000000045baca in ?? () #6 0x00007ffff636bb7d in __libc_start_main () from /lib64/libc.so.6 #7 0x000000000041ad29 in _start () backtrace output from Xvnc itself (not running in gdb): 17/08/2010 20:04:03 17/08/2010 20:04:03 Got VNC connection from client 127.0.0.1 Backtrace: 0: Xvnc (xorg_backtrace+0x28) [0x5552a8] 1: Xvnc (0x400000+0x158a49) [0x558a49] 2: /lib64/libc.so.6 (0x7f0b1d727000+0x32a60) [0x7f0b1d759a60] 3: Xvnc (0x400000+0x10f2c0) [0x50f2c0] 4: Xvnc (0x400000+0x73e43) [0x473e43] 5: Xvnc (mieqProcessDeviceEvent+0x19a) [0x4b6eba] 6: Xvnc (mieqProcessInputEvents+0xcb) [0x4b6feb] 7: Xvnc (0x400000+0x6c583) [0x46c583] 8: Xvnc (0x400000+0x5baca) [0x45baca] 9: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f0b1d745b7d] 10: Xvnc (0x400000+0x1ad29) [0x41ad29] 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 20