November 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 500382] New: zypper and yast2 have different opinions about what needs updating
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=500382 Summary: zypper and yast2 have different opinions about what needs updating Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)eregion.de QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.9) Gecko/2009041500 SUSE/3.0.9-0.1.1 Firefox/3.0.9 i do a "zypper -r up" as root on a commandline and i get this output: sai:~ # zypper -r lu Retrieving repository 'Packman Repository' metadata [done] Building repository 'Packman Repository' cache [done] Loading repository data... Reading installed packages... No updates found. sai:~ # to me that means "no new package versions for the stuff you have installed." Now, if i start yast2, go to "install/remove software" (yast2 sw_single), select "summary", then set the checkmark for "keep" (I see all installed packages now), then right-click somewhere in that list and choose "all in this list -> update if never version is available" i get a message telling me "plasmoid-systemloadviewer-0.6-2.36.i686 needs kdebase4-runtime >= 4.2.2 which is not available", and a list of 100 packages, all belonging to KDE 4.2.2, which should be uninstalled. The culprit is the package kde4-webkitpart-4.2.2.svn958332-2.1 from kde3::backports (which, in my opinion, should not be there at all anyways). If i select "do not install kde4-webkitpart-4.2.2.svn958332-2.1" i dont get any problems. Now, the issue in this bug is, why does yast2 think that kde4-webkitpart needs upgrading, and "zypper -r up" does not? Which of the two ways to update your installation is the one to be trusted and relied on? yast2, or zypper? Reproducible: Always Steps to Reproduce: 1. add the repositories for KDE 4.2 and KDE 3 for opensuse 11.1 2. zypper -r up 3. yast2 sw_single (see above) Actual Results: see summary Expected Results: zypper and yast2 should have the same "ideas" about which packages need updating. -- 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 21

[Bug 498556] New: Online Update will Not Install "All Patches" when selected
by bugzilla_noreply＠novell.com 21 Jan '14

21 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=498556 Summary: Online Update will Not Install "All Patches" when selected Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com 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 Online update has never been able to install anything but 'Needed Patches'. The definition of Needed Patches escapes me however, If I display 'All Patches" by filter and the select Patches in this list>Install the patches are changed to a green tick but will never be installed. Reproducible: Always Steps to Reproduce: 1.Open Online Update 2.Filter Patches by - All Patches instead on needed patches 3.Patch>In this list> Install - All Patches are marked for installation 4. Accept. 5. Result nothing is installed and suseconfig runs immediately after nothing has been installed Actual Results: Patches marked for Installation are not installed Expected Results: Patches marked for installation ARE installed. This is 100% reproducible - Please only request yast logs IF for some very strange reason it cannot be re-produced. -- 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 15

[Bug 540587] New: If Yast MUST NOT kill SQUID in middle of system update!
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=540587 Summary: If Yast MUST NOT kill SQUID in middle of system update! Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 I was doing a system update. Normally my web requests go through squid to take advantage of a large local (6GB) disk cache for various downloaded objects. However, yast also pays attention to the global vars HTTP_PROXY and friends, and uses them during its operations. Normally not a problem. However I was doing a Factory update. That just happened to include squid this time. About half way through a 500MB download/update it suddenly lost its connection -- and hung. Restarting squid didn't help. It was dead and required restart -- at which point trying to redo the factory update was futile -- it thought everything was done -- BUT the configuration of every service it updated was *wiped* and set to 'off'. I'm having to go through each service as I find which ones it killed and wiped and reconfig or at least restart them. But in a few cases, the config files have been reinitialized to non-workable values. Examples: xinetd was setup with no tcpmux builtin configure, so installed services like vnc generated errors because the standard vnc-server needs TCPMUX. The arpwatchd was no longer looking on my inside net, but on my outside and talking about bogons because it lost it's local group list. It also was no longer in its own group. named is now generating messages about not having write access to its working directory (don't know if this is a new message, or something was changed). The squid startup script was replaced and the old one wasn't saved -- I had it set to filter some common error messages (restored from an edit backup). Might be a few others -- several services were just 'stopped (chkconfiged 'off') when they had been on. Have yet to do an exhaustive search for problems, as I'm still in firefighting mode. But Yast really needs to be smart enough to check, if it is using a proxy server, AND proxy server is on same system, it needs to be "very circumspect about restarting it (if it should restart it at all, maybe it should ask user or wait for reboot?)...but if it closed all connections and was sure it would restart, then it could auto-restart it just like when log-rotation happens periodically. Marking this Critical, as it has cost a large amount of time to recover from this (still in progress).... and did lose some data (though I probably have earlier backups I could restore from, I'm taking opportunity to recheck configs. I am noticing some (1-2?) incompatible config files with the new versions that were installed. Will try to remember to file more bugs later...but filing bugs takes me away from fixing, and my email is another service that is broken right now. (was trying to fix some configuration problem and I've made things worse! --- ;^) so what else is new...but if it hadn't been broken in the first place, I probably wouldn't have been mucking w/it!...but hey, it *is* a learning experience, so I'm not "angry", more like 'annoyed'...and wanting to create this bug as a notice of the problem. Reproducible: Didn't try Steps to Reproduce: 1. have "alot" of updates (I didn't see all the updates -- it autoselected "A bunch" more than I had picked out...(as usual ;^/ )...dependency hell! 2. I was updating through a proxy server (squid) running on the machine being updated -- I didn't explicitly ask yast todo this, it just took the values from my environment vars (HTTP_PROXY & such)... 3. One of the packages updated, "apparently" was squid...right in the middle of the updates. It left my system in an inconsistent and ill-or-unconfiged state with many serviced turned off (that had been on ). Actual Results: System way messed up. Expected Results: Normal factory upgrade. -- 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 29

[Bug 555222] New: zypper dup should check if mkinitrd succeeds
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=555222 Summary: zypper dup should check if mkinitrd succeeds Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mail(a)philipp-wagner.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-7.1 Firefox/3.5 I updated from 11.1 to 11.2 using zypper dup. My /boot partition was full and mkinitd during the installation of the kernel image probably failed. I didn't see the message as I let the update run unattended and only saw the last lines of output from zypper dup, which seemed to suggest that everything went ok. When rebooting I got a "kernel panic: attempted to kill init". Fortunately I had another kernel installed and were able to boot, remove some old files from /boot and call mkinitrd again. Now the system boots fine. A full /boot partition is not that unlikely (the default partition layout suggests a rather small /boot and installing two testkernels is enough to fill it so that mkinitrd fails. Could zypper dup give a summary of errors that happened while installing all packages in the end of the upgrade process so that the user sees this error before rebooting? 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 6

[Bug 550318] New: user ids for kiwi created ltsp images wrong, taken from host
by bugzilla_noreply＠novell.com 19 Dec '13

19 Dec '13

http://bugzilla.novell.com/show_bug.cgi?id=550318 Summary: user ids for kiwi created ltsp images wrong, taken from host Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: stefan.bruens(a)rwth-aachen.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.2 (like Gecko) SUSE Kiwi creates ltsp images in two stages. The first stage is run from the host, installing packages using "zypper --root <ltsp-root>". It looks like userids for creating the files are taken from the host environment. This affects e.g. dbus and hal packages. This should be either fixed in zypper, or fixed during the the second stage, which is run in the chroot (rpm --setguids). Reproducible: Always Steps to Reproduce: 1. install kiwi-ltsp-prebuilt-unstable 2. unclicfs /srv/kiwi-ltsp/i386.img; sudo mount -o loop,ro fsdata.ext3 /mnt 3. chroot /mnt 4. ls -la /var/run/{hald,dbus} Actual Results: var/run/dbus: total 8 drwxr-xr-x 2 haldaemon privoxy 4096 2009-09-24 00:02 . drwxr-xr-x 9 root root 4096 2009-10-04 09:00 .. var/run/hald: total 16 drwxr-xr-x 4 messagebus quagga 4096 2009-10-04 08:58 . drwxr-xr-x 9 root root 4096 2009-10-04 09:00 .. drwxr-xr-x 2 messagebus quagga 4096 2009-09-24 11:50 hald-local drwxr-xr-x 2 messagebus quagga 4096 2009-09-24 11:50 hald-runner Expected Results: /var/run/dbus: insgesamt 16 drwxr-xr-x 3 messagebus messagebus 4096 27. Okt 07:53 . drwxr-xr-x 26 root root 4096 27. Okt 07:54 .. drwxr-xr-x 3 root root 4096 27. Okt 07:54 at_console -rw-r--r-- 1 root root 5 27. Okt 07:53 pid srwxrwxrwx 1 root root 0 27. Okt 07:53 system_bus_socket /var/run/hald: insgesamt 24 drwxr-xr-x 4 haldaemon haldaemon 4096 27. Okt 07:54 . drwxr-xr-x 26 root root 4096 27. Okt 07:54 .. -rw-r--r-- 1 root root 2266 27. Okt 07:54 acl-list -rw-r--r-- 1 root root 5 27. Okt 07:53 haldaemon.pid drwxr-xr-x 2 haldaemon haldaemon 4096 5. Feb 2009 hald-local drwxr-xr-x 2 haldaemon haldaemon 4096 5. Feb 2009 hald-runner -- 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 13

[Bug 557498] New: VMWare console continually grabs / releases input when mouse is moved when launched from Firefox 3.5.4 from openSUSE 11.2
by bugzilla_noreply＠novell.com 06 Dec '13

06 Dec '13

http://bugzilla.novell.com/show_bug.cgi?id=557498 http://bugzilla.novell.com/show_bug.cgi?id=557498#c0 Summary: VMWare console continually grabs / releases input when mouse is moved when launched from Firefox 3.5.4 from openSUSE 11.2 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: novell_david(a)bailey.id.au QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 Using Firefox 3.5.4 from openSUSE 11.2 final, when working with a VMWare virtual machine console, the console continually grabs / releases input as you move the mouse within the console. This makes it extremely difficult to work with the virtual machine as the mouse is quite often not focused on the machine when you need it to be. Pressing <CTRL> G to force grabbing does not change this behavior. If you persist with trying to work with the VM for a period of time, the entire desktop machine seems to loose the meta keys (ie CTRL, ALT etc). So you can't use <CTRL> D for example after closing the VMWare console. If you do this in a konsole session etc, you will see a D on the screen instead of exiting that konsole session. Restarting the DE resolves this. This is reproducable across 2 machines (x86_64 and i386 installs). It is also reproducable using both KDE and Gnome DEs. The exact versions of Firefox used are: MozillaFirefox-3.5.4-1.1.2.x86_64 MozillaFirefox-3.5.4-1.1.2.i586 VMWare version: VMware Infrastructure Web Access Version 2.0.0 Build 128374 However, under Firefox 3.5.5 from the Mozilla website, the virtual machine behavior returns to normal and grabbing releasing input works correctly. Reproducible: Always Steps to Reproduce: 1.Using Firefox 3.5.4 from openSUSE 11.2 2.Open VMWare console and attempt to work with the virtual machine 3.As mouse is moved the VM continually grabs / releases input (the status text keeps changing to confirm this) -- 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 4

[Bug 547574] New: icu: apply shared library policy
by bugzilla_noreply＠novell.com 04 Dec '13

04 Dec '13

http://bugzilla.novell.com/show_bug.cgi?id=547574 Summary: icu: apply shared library policy Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer libicu currently is not following the library policy (libicu42) but is just called libicu. This makes it impossible to install multiple versions in parallel. -- 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 514186] New: Firefox crashes when mouse wheel scrolled qtcurve is causing it
by bugzilla_noreply＠novell.com 29 Nov '13

29 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=514186 Summary: Firefox crashes when mouse wheel scrolled qtcurve is causing it Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: initialZero(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US) AppleWebKit/531.0 (KHTML, like Gecko) Chrome/3.0.187.0 Safari/531.0 Firefox has been rendered unusable due to qtcurve causing it to crash when any webpage is scrolled using the mouse wheel. I have the firefox and qtcurve debuginfo packages installed but the stack trace looks weak. Reproducible: Always Steps to Reproduce: 1. 2. 3. [New Thread 0x7fffe99e7950 (LWP 11435)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) /usr/share/themes/Sonar/gtk-2.0/gtkrc:88: error: unexpected identifier `progressbarstyle', expected character `}' (no debugging symbols found) [New Thread 0x7fffe89e4950 (LWP 11438)] (no debugging symbols found) [New Thread 0x7fffe7f0c950 (LWP 11439)] [Thread 0x7fffe7f0c950 (LWP 11439) exited] [New Thread 0x7fffe7f0c950 (LWP 11440)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread 0x7fffe70c8950 (LWP 11442)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread 0x7fffe7f0c950 (LWP 11440) exited] [New Thread 0x7fffe7f0c950 (LWP 11443)] [New Thread 0x7fffe5980950 (LWP 11444)] [Thread 0x7fffe7f0c950 (LWP 11443) exited] *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable). [New Thread 0x7fffe7f0c950 (LWP 11445)] [New Thread 0x7fffe45b9950 (LWP 11446)] [New Thread 0x7fffe3db8950 (LWP 11447)] Program received signal SIGSEGV, Segmentation fault. 0x00007fffe8dcea45 in ?? () from /usr/lib64/gtk-2.0/2.10.0/engines/libqtcurve.so -- 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

[Bug 533991] New: Adobe Reader error: suse-do-not-grab-server.so' from LD_PRELOAD cannot be preloaded
by bugzilla_noreply＠novell.com 29 Nov '13

29 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=533991 Summary: Adobe Reader error: suse-do-not-grab-server.so' from LD_PRELOAD cannot be preloaded Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: hvogel(a)novell.com ReportedBy: mvyskocil(a)novell.com QAContact: qa(a)suse.de Found By: --- Adobe reader prints a following error to stderr when I want to print something: ERROR: ld.so: object '/usr/lib/Adobe/Reader8/Reader/intellinux/lib/suse-do-not-grab-server.so' from LD_PRELOAD cannot be preloaded: ignored. -- 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 13

[Bug 508670] New: files owned by multiple RPMs cause conflicts in opensuse 11.1
by bugzilla_noreply＠novell.com 27 Nov '13

27 Nov '13

http://bugzilla.novell.com/show_bug.cgi?id=508670 Summary: files owned by multiple RPMs cause conflicts in opensuse 11.1 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: unix-support(a)ucs.cam.ac.uk QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7; en-us) AppleWebKit/525.28.3 (KHTML, like Gecko) Version/3.2.3 Safari/525.28.3 Hi, There are files in opensuse 11.1 which are owned by multiple RPMs which causes conflicts when you try to update one of the RPMs using "rpm -Uvh" (or indeed some tooms - zypper seems to work and I assume it works because it ignores the dependenices!). For example: # rpm -qf /usr/share/omf/evolution/evolution-C.omf bundle-lang-gnome-en-11.1-11.3 evolution-2.24.1.1-4.14.1 And the files are no even identical. For example running: # rpm --verify bundle-lang-gnome-en | grep evolution S.5....T /usr/share/omf/evolution/evolution-C.omf And this is not the only one. Another example: # rpm -qf /usr/share/omf/zenity/zenity-C.omf bundle-lang-gnome-en-11.1-11.3 zenity-2.24.0-1.23 This is a very bad bug as it completely breaks our package manager. )-: Multiple RPMs should never supply two files with the same path and filename! Can this please be fixed? Best regards, Anton Altaparmakov (Unix Support, University of Cambridge, UK) Reproducible: Always Steps to Reproduce: Run one of the examples from the Details to see the problem... Actual Results: See the Details. Expected Results: See the Details. - We expect never to see two RPMs owning the same path/filename. -- 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