December 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 734629] New: kde system settings - crashed, cannot restart
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=734629 https://bugzilla.novell.com/show_bug.cgi?id=734629#c0 Summary: kde system settings - crashed, cannot restart Classification: openSUSE Product: openSUSE 12.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: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 system settings crashed (the following message is all I saw in ~/.Xsession-errors): *** glibc detected *** /usr/bin/systemsettings: corrupted double-linked list: 0x0000000000c62ed0 *** Once it crashed, it could not be restarted. At all. Systemd problem? dbus problem? The following is a partial strace: 48}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 262 [pid 3318] recvmsg(3, 0x7ffffd7a6420, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) [pid 3318] sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\33\0\0\0\2\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/fre"..., 144}, {"\26\0\0\0org.kde.systemsettings\0", 27}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 171 [pid 3318] poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) [pid 3318] recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1\4\0\0\0\3\0\0\0=\0\0\0\6\1s\0\6\0\0\0:1.470\0\0"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 84 [pid 3318] recvmsg(3, 0x7ffffd7a6090, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) [pid 3318] sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\35\0\0\0\3\0\0\0\212\0\0\0\1\1o\0\20\0\0\0/MainApp"..., 160}, {"\0\0\0\0\25\0\0\0\0\0\0\r/home/jnelson\0\0\0\0", 29}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 189 [pid 3318] poll([{fd=3, events=POLLIN}], 1, -1 <unfinished ...> [pid 3319] exit_group(0) = ? Process 3319 detached <... poll resumed> ) = ? ERESTART_RESTARTBLOCK (To be restarted) --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3319, si_status=0, si_utime=0, si_stime=0} (Child exited) --- restart_syscall(<... resuming interrupted call ...> and there it sits. No feedback, nothing. If you check the process table, there are multiple 'Zombie' systemsettings processes. Something is not reaping them properly. Killing them off allows one to start systemsettings again. 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 3

[Bug 735262] New: home:crevetor:llvmpipe/llvm: Bug
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=735262 https://bugzilla.novell.com/show_bug.cgi?id=735262#c0 Summary: home:crevetor:llvmpipe/llvm: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: testmrs.evo(a)gmail.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- Hi, I am trying to test llvm of armv7hl package on arm-cortexA-9 based target. I installed below package from your armv7hl repo. llvm,llvm-devel,mesa-gallium-driver-llvmpipe,mesa-gallium-driver-llvmpipe-devel,x11vnc package. My OSS & NonOss pacakge is base on below repo. http://repo.meego.com/MeeGo/builds/trunk/1.2.90.0.0.20110824.2/repos/oss/ar… http://repo.meego.com/MeeGo/builds/trunk/1.2.90.0.0.20110824.2/repos/non-os… Now i tried to build clutter 1.6 or above version to test the graphic performance,but while testing test i found below error. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- /test-actors Running ./test-interactive test-actors NOTE: For debugging purposes, you can run this single test as follows: $ libtool --mode=execute \ gdb --eval-command="b test_actors_main" \ --args ./test-interactive test-actors X Error of failed request: BadValue (integer parameter out of range for operat) Major opcode of failed request: 140 (MIT-SHM) Minor opcode of failed request: 3 (X_ShmPutImage) Value in failed request: 0xffd2 Serial number of failed request: 145 Current serial number in output stream: 146 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Can you please let me know how to get successfull test running. 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 1

[Bug 690038] New: Packages loose their marking as "do not change"
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=690038 https://bugzilla.novell.com/show_bug.cgi?id=690038#c0 Summary: Packages loose their marking as "do not change" Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major 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: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0 I repetitively stumble across the fact that Yast is loosing the attributes of "don't change" files either due to package kit or due to a timeout. The current mgetty / sendfax distribution is buggy (bug report exists) Hence I installed a fixed version - somewhat older than the recend one and marked it as "do not change". This always ensured that the packages were kept as long as I did not intentionally change the attribute. However, since openSUSE 11.4 the attribute "don't change" (Geschützt - nicht verändern) get's lost -the heck knows why this happens. So I cannot tell an unexperienced user to upgrade - because the upgrade potentionally destroys a running system. Reproducible: Always Steps to Reproduce: 1. Mark a package as "Geschützt - nicht verändern") 2. wait (a day, a week, don't know how long 3. Marking is gone!!!!! Actual Results: Well, the mark as "Geschützt" is vanishing into the haze after some time - don't know what causes this behaviour! Expected Results: Guess what :-) If I intentionally mark software as _dont_change_this_ I would expect the updater to respect my decision. I have my reasons!!!! -- 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 32

[Bug 689002] New: kpackagekit clears yast protected flag
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

1 4

[Bug 698250] colord: new dbus and polkit rules
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=698250 https://bugzilla.novell.com/show_bug.cgi?id=698250#c39 --- Comment #39 from Vincent Untz <vuntz(a)suse.com> 2011-12-07 10:00:50 UTC --- (In reply to comment #37) > It might make sense to have create-device imply create-profile and > modify-device, if we change the policy to KEEP. I can patch colord for that if > you agree it's the right way forward. Actually, this will still be a horrible user experience as you'll still have on popup on each login :/ (the device is re-created on each login) -- 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 555907] New: libapr1 doesn't work on a vserver with old kernel (alloc_listener: failed to get a socket for (null)
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

http://bugzilla.novell.com/show_bug.cgi?id=555907 Summary: libapr1 doesn't work on a vserver with old kernel (alloc_listener: failed to get a socket for (null) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: novell(a)gmuer.org QAContact: qa(a)suse.de Found By: --- Blocker: --- --- Comment #0 from Marcel Gmür <novell(a)gmuer.org> 2009-11-16 20:05:40 UTC --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-6.1 Firefox/3.5.4 after a zypper dup to 11.2, apache didn't start anymore: alloc_listener: failed to get a socket for (null) I found a related Fedora report with same issue: http://rackerhacker.com/2009/08/14/fedora-11-httpd-alloc_listener-failed-to… I was able to build libapr1 so it works again on my vserver: changes to the libapr1 spec from standard repo: before %configure export apr_cv_epoll_create1=no export apr_cv_dup3=no export apr_cv_accept4=no export apr_cv_sock_cloexec=no (https://build.opensuse.org/package/show?package=libapr1&project=home%3Aamml…) Greets Ammler Reproducible: Always Steps to Reproduce: 1. upgrade a vserver with suse 10.3 to 11.1 uname: Linux localhost 2.6.9-023stab048.5-smp #1 SMP Wed Aug 20 18:58:38 MSD 2008 x86_64 x86_64 x86_64 GNU/Linux 2. rcapache2 restart Actual Results: alloc_listener: failed to get a socket for (null) Expected Results: running apache ;-) -- 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 696793] New: NetworkManager - WiFi system connection does not start automatically
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c0 Summary: NetworkManager - WiFi system connection does not start automatically Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hrach2(a)post.sk QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=431984) --> (http://bugzilla.novell.com/attachment.cgi?id=431984) NetworkManager log - network connection on eth0 starts succesfully at boot time User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Using plasmoid-networkmanagement-0.9.1git20110503-8.1.x86_64. In system connections (/etc/NetworkManager/system-connections) I have two connections: 1. One for eth0 2. Second for wlan0 Both have setting for automatic start at boot time. WiFi connections are enabled. When only eth0 is presented (cable plugged in, WiFi net not available), connection on eth0 starts automatically as expected at boot time. When only wlan0 is presented (cable not plugged in, WiFi net available), connection on wlan0 does not start automatically at boot time. Later it can be manually started, when logged in. Reproducible: Always Steps to Reproduce: 1. Two system connections, one for eth0, one for wlan0, both with option start automatically. 2. Make WiFi net available, does not plug ethernet cable 3. Start computer and wait OS is completely booted Actual Results: Network connection is not automatically established at boot time. (wlan0 interface) Expected Results: Network connection is automatically established at boot time. (wlan0 interface) -- 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 15

[Bug 729777] New: The connection is closed
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=729777 https://bugzilla.novell.com/show_bug.cgi?id=729777#c0 Summary: The connection is closed Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: 32bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: idulk(a)kendari.linux.or.id QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I can not open YaST2 through the terminal, and found an error message like this: The connection is closed. As for the steps that I do # su # YaST2 The same thing happens when I open gedit through terminal applications and appear this error: (gedit: 8382): WARNING **: Could not connect to session bus but both the above problems can be solved when I use the command # su - to root access # su - Reproducible: Always Steps to Reproduce: 1.open Terminal 2.#su 3.#yast2 -- 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 698250] colord: new dbus and polkit rules
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=698250 https://bugzilla.novell.com/show_bug.cgi?id=698250#c38 Vincent Untz <vuntz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |casualprogrammer(a)opensuse.o | |rg --- Comment #38 from Vincent Untz <vuntz(a)suse.com> 2011-12-07 08:22:59 UTC --- *** Bug 706908 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=706908 -- 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 706908] New: Authentication for color device required before login
by bugzilla_noreply＠novell.com 07 Dec '11

07 Dec '11

https://bugzilla.novell.com/show_bug.cgi?id=706908 https://bugzilla.novell.com/show_bug.cgi?id=706908#c0 Summary: Authentication for color device required before login Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(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:5.0) Gecko/20100101 Firefox/5.0 For some time now I get three prompts for root authorization before I can log in. #cat /var/log/messages | grep color Jul 13 07:02:25 workstation6l polkitd(authority=local): Operator of unix-session:/org/freedesktop/ConsoleKit/Session2 successfully authenticated as unix-user:root to gain ONE-SHOT authorization for action org.freedesktop.color-manager.create-device for system-bus-name::1.12 [/usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon] (owned by unix-user:gdm) Jul 13 07:02:49 workstation6l polkitd(authority=local): Operator of unix-session:/org/freedesktop/ConsoleKit/Session2 successfully authenticated as unix-user:root to gain ONE-SHOT authorization for action org.freedesktop.color-manager.create-profile for system-bus-name::1.12 [/usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon] (owned by unix-user:gdm) Jul 13 07:02:56 workstation6l polkitd(authority=local): Operator of unix-session:/org/freedesktop/ConsoleKit/Session2 successfully authenticated as unix-user:root to gain ONE-SHOT authorization for action org.freedesktop.color-manager.modify-device for system-bus-name::1.12 [/usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon] (owned by unix-user:gdm) #cat /etc/SuSE-release openSUSE 12.1 Milestone 3 (i586) VERSION = 12.1 CODENAME = Asparagus 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 13