June 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 579797] New: ooffice startup menu click-able region
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=579797 http://bugzilla.novell.com/show_bug.cgi?id=579797#c0 Summary: ooffice startup menu click-able region Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: m.munnix(a)redcross.be QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.7) Gecko/20091222 SUSE/3.5.7-1.1.1 Firefox/3.5.7 when starting ooffice from the command line, I am offered a menu "welcome to open openoffice.org". The click-able region should be extended to the written text Reproducible: Always Steps to Reproduce: 1.I click on "Text Document" 2. 3. Actual Results: nothing happens Expected Results: ooffice writer should start Am I the only user trying to clink on the sentence instead of clicking on the logo or entering the underlined letter on the keyboard ? The meaning of the text sentence is better understood than the logo, so every time I click on the text. If the click-able region comprised both the logo and the text, I'd be happy -- 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 609954] New: yast2 bootloader needs a long time to display the vga-mode and additional parameters
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=609954 http://bugzilla.novell.com/show_bug.cgi?id=609954#c0 Summary: yast2 bootloader needs a long time to display the vga-mode and additional parameters Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ctrippe(a)gmx.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=365579) --> (http://bugzilla.novell.com/attachment.cgi?id=365579) yast-logs User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.80 (like Gecko) SUSE yast2 bootloader needs a long time to display the vga-mode and additional parameters Reproducible: Always Steps to Reproduce: 1.launch yast2 bootloader 2.select one entry of your grub menu and choose configure 3.Wait a long time until the vga-mode and additional parameters are displayed -- 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 610554] New: easy way to leave chroot
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=610554 http://bugzilla.novell.com/show_bug.cgi?id=610554#c0 Summary: easy way to leave chroot Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: HP OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: alavrentiev(a)yandex.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 there is a simple way to leave chrooted environment. just mount /proc filesystem and reference to pid/cwd, for example. Reproducible: Always Steps to Reproduce: vz15:/ # uname -a Linux vz15 2.6.31.12-0.2-default #1 SMP 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux vz15:/ # cat /etc/SuSE-release openSUSE 11.2 (x86_64) VERSION = 11.2 vz15:/ # ls -al /ve/private/ total 20 drwxr-xr-x 5 root root 4096 2010-03-30 14:47 . drwxr-xr-x 11 root root 4096 2010-03-30 14:41 .. drwxr-xr-x 19 root root 4096 2009-10-08 16:55 400 drwxr-xr-x 19 root root 4096 2009-11-16 14:54 401 drwxr-xr-x 21 root root 4096 2010-06-01 13:24 suse-11.2 vz15:/ # cd /ve/private/suse-11.2/ vz15:/ve/private/suse-11.2 # chroot . vz15:/> ls -al /ve/private/ /bin/ls: cannot access /ve/private/: No such file or directory vz15:/> mount -t proc none /proc vz15:/> ls -ald /proc/1/cwd lrwxrwxrwx 1 root root 0 2010-05-12 09:40 /proc/1/cwd -> / vz15:/> ls -ald /proc/1/cwd/ve/private/ drwxr-xr-x 5 root root 4096 2010-03-30 10:47 /proc/1/cwd/ve/private/ vz15:/> ls -al /proc/1/cwd/ve/private/ total 20 drwxr-xr-x 5 root root 4096 2010-03-30 10:47 . drwxr-xr-x 11 root root 4096 2010-03-30 10:41 .. drwxr-xr-x 19 root root 4096 2009-10-08 12:55 400 drwxr-xr-x 19 root root 4096 2009-11-16 11:54 401 drwxr-xr-x 21 root root 4096 2010-06-01 09:24 suse-11.2 Actual Results: filesystem above chrooted directory is available. Expected Results: filesystem above chrooted directory is prohibited. -- 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 1

[Bug 551116] New: GDM pops up for a while although is used autologin
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=551116 User rastislav.krupansky(a)gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=551116#c540482 Summary: GDM pops up for a while although is used autologin Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: All OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: rastislav.krupansky(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 Before loading Gnome, GDM pops up for a while, although i use autologin. Here you are link of captured movie, what i exactly mean. http://img687.imageshack.us/i/suselinuxmovie.mp4/ Tested on real hardware and in VMware. output rpm -q gdm: gdm-2.28.0-2.3.2.i586 output rpm -q --changelog gdm: * Tue Oct 20 2009 vuntz(a)opensuse.org - Add gdm-look-at-runlevel.patch to work around issue where gdm blocks the restart/shutdown process because of a race there. Should fix bnc#540482. - Version the Provides/Obsoletes to fix a rpmlint warning. - Reorder packageand() arguments for the branding supplements to fix rpmlint warning. * Fri Oct 02 2009 vuntz(a)opensuse.org - Add gdm-devkit-power.patch: gdm was using a dbus API which doesn't exist anymore, and the right way to handle this is to use DeviceKit-power. - Add DeviceKit-power-devel BuildRequires for the patch. - Add gdm-polkit-gnome-path.patch to use the correct path for the polkit agent. - Rebase gdm-greeter-greater-ui.patch. Fix bnc#533597. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 608263] New: zypper assumes /var/tmp & /var/cache on same fs; WRONG assumption
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=608263 http://bugzilla.novell.com/show_bug.cgi?id=608263#c0 Summary: zypper assumes /var/tmp & /var/cache on same fs; WRONG assumption Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 FireDownload/2.0.1 Firefox/3.6.3 FireTorrent/2.0.1 Mnenhy/0.8.2 Trying to do command 'zypper si iotop'. Relevant info: /, /var[/tmp] and /var/cache are all on separate file systems. zypper seems to be assuming it can hardlink between /var/tmp and /var/cache. Should assume it can hard link between any two directories. I.e. if hard link fails, should automatically follow up with a real "cp -al" of the affected files/directories. Perhaps not ideal in terms of file space, but if this is what is required, it's better than throwing out an error message that indicates a dsyfunctional operation, namely: zypper si iotop Reading installed packages... Loading repository data... Resolving package dependencies... The following source package is going to be installed: iotop 0 new packages to install. Overall download size: 341.0 KiB. After the operation, additional 338.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving: iotop-0.2.1-34.1.src.rpm [done (13.4 KiB/s)] Retrieving: content [done (0 B/s)] Problem retrieving the package file from the repository: Can't provide ./suse/src/iotop-0.2.1-34.1.src.rpm : Can't hardlink/copy /var/tmp/AP_0x00000001/suse/src/iotop-0.2.1-34.1.src.rpm to /var/cache/zypp/packages/repo-source Repository 'repo-source' is out of date. Running 'zypper refresh' might help. -------------- NOTE: Of additional note is that the "might help" note at the end is a "red-herring" -- it does nothing to "help". ----- ADDITIONAL NOTE (possible fix/workaround ): In trying to find where the RPM might be, I eventually WIPED "/var/tmp/ contents. Rerunning the zypper si iotop then WORKED! (* WHY? *) (output:) zypper si iotop Reading installed packages... Loading repository data... Building repository 'Compiz & Fusion' cache [done] Building repository 'Mozilla Latest & 64bit' cache [done] Building repository 'Open Build Service' cache [done] Building repository 'network:samba:MAINTAINED:SLE_11' cache [done] Building repository 'network_samba_STABLE' cache [done] Building repository 'openSUSE 11.2-0' cache [done] Building repository 'openSUSE-11.2-Oss' cache [done] Building repository 'openSUSE-11.2-Source' cache [done] Building repository 'openSUSE-11.2-Update' cache [done] Building repository 'openSUSE-11.2-Non-Oss' cache [done] Resolving package dependencies... The following source package is going to be installed: iotop 0 new packages to install. Overall download size: 341.0 KiB. After the operation, additional 338.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving: iotop-0.2.1-34.1.src.rpm [done (31.3 KiB/s)] ----------------- While this solve my basic /immediate problem, someone might wish to look at why wiping "/var/tmp" would prevent this cross link problem, as it wouldn't solve the issue of "/var/tmp" and "/var/cache" being on two separate file systems. Weird. Reproducible: Always Steps to Reproduce: 1. <see details> 2. 3. Actual Results: <cross file-system> link error message.... Expected Results: operation to be completed w/o problems. details show addition steps that got rid of problem...but reason why it got rid of problem isn't clear. -- 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 604043] New: Automatic configuration with non-ACPI BIOS causes installation to halt with errors at 1st reboot
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=604043 http://bugzilla.novell.com/show_bug.cgi?id=604043#c0 Summary: Automatic configuration with non-ACPI BIOS causes installation to halt with errors at 1st reboot Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: terence.silk(a)tesco.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 During clean install from a fully validated DVD (created from a fully validated iso image), if automatic configuration was left selected, then a non-ACPI BIOS was not identified as such and on 1st reboot, the OS/installer reported that it could not find the ACPI information in RAM that it expected to find and the configuration came to a halt. Reproducible: Always Steps to Reproduce: 1.Clean install openSUSE 11.2 x86-64 on any non-ACPI BIOS PC. 2.Do not attempt to facilitate the installation using the acpi=off option or equivalent (please note that this stipulation makes sense when you read the preferred solution to this problem in the Additional Information section). 3.Proceed to the 1st reboot point and observe the error messages which clearly indicate that the installer has failed to the BIOS type properly in automatic configuration mode. Actual Results: On screen error messages about missing ACPI information appeared and the computer froze. Expected Results: The installation should have proceeded to a configuration screen. The problem was solved with all 3 of my non-ACPI BIOS machines by clearing the "use Automatic Configuration" option box on the "Installation Mode" screen during the installation. I did not have to resort to using the acpi-off option which would undesirably disable PowerNow! processor control. After installation by this method completed, the PowerNow! functions were clearly in good health. Whilst I accept that Automatic Configuration is a "nice to have" it is extremely puzzling why the behaviour reported here occurs in an automatic configuration and yet does not occur when automatic is deselected. It must be very off-putting for Linux newcomers. -- 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 5

[Bug 600471] New: zypper's package resolving gives strange errors
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=600471 http://bugzilla.novell.com/show_bug.cgi?id=600471#c0 Summary: zypper's package resolving gives strange errors Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- + /usr/bin/zypper --non-interactive --no-gpg-checks --reposd-dir /var/cache/kiwi/zypper --cache-dir /var/cache/kiwi/zypper --raw-cache-dir /var/cache/kiwi/zypper --root /usr/src/packages/KIWIROOT-oem install --auto-agree-with-licenses --no-recommends bundle-lang-common-en filesystem openSUSE-release openSUSE-release-usb-x11 zypper + SPID=3382 + wait 3382 Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Loading repository data... Reading installed packages... 'openSUSE-release = usb-x11' not found in package names. Trying capabilities. No provider of 'openSUSE-release = usb-x11' found. I didn't ask for such a provider but for openSUSE-release-usb-x11 -- 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 5

[Bug 442291] New project: Padre
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=442291 http://bugzilla.novell.com/show_bug.cgi?id=442291#c4 Marcus Rückert <mrueckert(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|kaare(a)jasonic.dk | Resolution| |WONTFIX --- Comment #4 from Marcus Rückert <mrueckert(a)novell.com> 2010-06-01 15:49:35 UTC --- ok then please reopen the bug when you created packages and need a project for it. -- 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 0

[Bug 610635] New: mkinitrd calls /bin/on_ac_power
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=610635 http://bugzilla.novell.com/show_bug.cgi?id=610635#c0 Summary: mkinitrd calls /bin/on_ac_power Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- While the binary is in /usr/bin/ on my Factory system. This leads to an error message at the end of the installation while the initrd gets created. -- 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 1

[Bug 598972] New: "zypper dup" from 11.1 to 11.3 hangs in xorg-x11-fonts-core-7.5-1.2
by bugzilla_noreply＠novell.com 01 Jun '10

01 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=598972 http://bugzilla.novell.com/show_bug.cgi?id=598972#c0 Summary: "zypper dup" from 11.1 to 11.3 hangs in xorg-x11-fonts-core-7.5-1.2 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- I'm trying to update a 11.1 copy in chroot to 11.3 factory via "zypper dup" which right now hangs here: ... Retrieving package xorg-x11-fonts-core-7.5-1.2.noarch (956/1796), 9.0 M (10.4 M unpacked) Retrieving: xorg-x11-fonts-core-7.5-1.2.noarch.rpm [........done (1.1 M/s)] Installing: xorg-x11-fonts-core-7.5-1.2 [......... with the following process trace: # ps uaxwwOT .. root 19067 0.2 0.1 36844 5632 pts/6 S+ 19:33 0:01 rpm --root / --dbpath /var/lib/rpm -U --percent --force --nodeps -- /var/cache/zypp/packages/oss/suse/noarch/xorg-x11-fonts-core-7.5-1.2.noarch.rpm root 19068 0.0 0.0 11268 1384 pts/6 S+ 19:33 0:00 /bin/sh /var/tmp/rpm-tmp.hMDXku 2 root 19069 0.0 0.0 11272 1532 pts/6 S+ 19:33 0:00 /bin/sh /sbin/SuSEconfig --module fonts root 19076 0.0 0.0 11268 1380 pts/6 S+ 19:33 0:00 bash /sbin/conf.d/SuSEconfig.fonts root 19077 0.0 0.1 20452 5456 pts/6 S+ 19:33 0:00 /usr/bin/perl -w # -*- perl -*- /usr/sbin/fonts-config --verbose root 19078 0.0 0.1 23532 5828 pts/6 S+ 19:33 0:00 /usr/bin/xfs root 19124 0.0 0.0 4840 1012 pts/13 R+ 19:41 0:00 ps uaxwwOT zypper.log: 2010-04-22 19:33:22 <1> os4(7912) [zypp] RpmDb.cc(doInstallPackage):1976 RpmDb::installPackage(/var/cache/zypp/packages/oss/suse/noarch/xorg-x11-fonts-core-7.5-1.2.noarch.rpm,0x0000000c) 2010-04-22 19:33:22 <1> os4(7912) [zypp++] ExternalProgram.cc(start_program):210 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--force' '--nodeps' '--' '/var/cache/zypp/packages/oss/suse/noarch/xorg-x11-fonts-core-7.5-1.2.noarch.rpm' 2010-04-22 19:33:22 <1> os4(7912) [zypp++] ExternalProgram.cc(start_program):355 pid 19067 launched running "/usr/sbin/fonts-config --verbose:" seems to works fine (doesn't hang) btu gives this output: /root/# /usr/sbin/fonts-config --verbose /usr/bin/xfs error: CONFIG: unknown parameter "cache-hi-mark" /usr/bin/xfs error: CONFIG: unknown parameter "cache-low-mark" /usr/bin/xfs error: CONFIG: unknown parameter "cache-balance" _FontTransSocketUNIXCreateListener: ...SocketCreateListener() failed _FontTransMakeAllCOTSServerListeners: server already running /usr/bin/xfs fatal error: cannot establish any listening sockets Creating fonts.{scale,dir} files .......... writing /etc/fonts/suse-font-dirs.conf /etc/fonts/suse-hinting.conf unchanged /etc/fonts/suse-bitmaps.conf unchanged Creating cache files for fontconfig ............................... Creating 32bit cache files for fontconfig ............................... generating java font setup Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. Warning: cannot find a serif Japanese font. Japanese in Java might not work. Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Java might not work. Warning: cannot find a sans serif Korean font. Korean in Java might not work. Warning: cannot find a serif Korean font. Korean in Java might not work. writing /usr/lib64/jvm/java-1.5.0-sun-1.5.0/jre/lib/fontconfig.SuSE.properties Generating CJK setup for xpdf ... /usr/bin/xfs error: CONFIG: unknown parameter "cache-hi-mark" /usr/bin/xfs error: CONFIG: unknown parameter "cache-low-mark" /usr/bin/xfs error: CONFIG: unknown parameter "cache-balance" _FontTransSocketUNIXCreateListener: ...SocketCreateListener() failed _FontTransMakeAllCOTSServerListeners: server already running /usr/bin/xfs fatal error: cannot establish any listening sockets after killing xfs 4 times, update now continues ... -- 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 14