April 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 594199] New: Kiwi Not Producing Bootable USB Stick Images
by bugzilla_noreply＠novell.com 08 Apr '10

08 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=594199 http://bugzilla.novell.com/show_bug.cgi?id=594199#c0 Summary: Kiwi Not Producing Bootable USB Stick Images Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Major Priority: P5 - None Component: System Imaging AssignedTo: ms(a)novell.com ReportedBy: delder(a)novacoast.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- Created an attachment (id=352725) --> (http://bugzilla.novell.com/attachment.cgi?id=352725) Build logs from new (kiwi) and old (kiwi.old) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I recently upgrade my kiwi installation but I unfortunately don't know what version I had previously from the Virtualization:Appliances repo (http://download.opensuse.org/repositories/Virtualization:/Appliances/SLE_11/) For safety sake, I bumped the version number (0.7.0->0.7.1) in my config.xml and changed the name and after performing a new build I'm getting an image that won't boot from USB. The kiwi build process completes successfully but when loaded onto a USB stick results in GRUB giving an Error 21. If I reload the old image on the USB stick it loads fine and the system can boot again. It looks like the build process has changed from using fdisk to parted and I'm guessing other pieces have changed as well. When I compare the old image (built within the last 60 days) to the new one with the file command I see: zenboot.x86_64-0.7.0.raw: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, stage2 address 0x2000, stage2 segment 0x200, GRUB version 0.97; partition 1: ID=0x83, active, starthead 1, startsector 63, 1654632 sectors zenboot.x86_64-0.7.1.raw: x86 boot sector; partition 1: ID=0x83, active, starthead 1, startsector 63, 1654632 sectors I currently have the following kiwi packages installed although I unfortunately don't have the older (< 2 month old) version numbers. kiwi-desc-isoboot-4.26-91.1 kiwi-desc-xenboot-4.26-91.1 kiwi-4.26-91.1 kiwi-tools-4.26-91.1 kiwi-desc-oemboot-4.26-91.1 kiwi-desc-usbboot-4.26-91.1 kiwi-templates-4.26-91.1 kiwi-desc-vmxboot-4.26-91.1 kiwi-pxeboot-4.26-91.1 kiwi-desc-netboot-4.26-91.1 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 21

[Bug 531958] New: s2disk produces segmentation fault
by bugzilla_noreply＠novell.com 08 Apr '10

08 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=531958 User syseng(a)adnovum.ch added comment http://bugzilla.novell.com/show_bug.cgi?id=531958#c1 Summary: s2disk produces segmentation fault Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i386 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: syseng(a)adnovum.ch QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 OpenSUSE 11.0 with latest applied patches on a Dell Precision T5400. System is installed with Autoyast and swap sizing set to "auto" in the Autoyast XML. Autoyast set the swap partition to 2GB although system has 4GB RAM. adnws007:~ # echo "disk" >/sys/power/state -bash: echo: write error: Cannot allocate memory adnws007:~ # s2disk Segmentation fault adnws007:~ # tail /var/log/messages Aug 18 07:21:15 adnws007 kernel: PM: Syncing filesystems ... done. Aug 18 07:22:37 adnws007 kernel: Freezing user space processes ... (elapsed 0.00 seconds) done. Aug 18 07:22:37 adnws007 kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. Aug 18 07:22:37 adnws007 kernel: PM: Shrinking memory... /Restarting tasks ... done. Aug 18 07:26:28 adnws007 kernel: PM: Syncing filesystems ... done. Aug 18 07:26:31 adnws007 kernel: Freezing user space processes ... (elapsed 0.00 seconds) done. Aug 18 07:26:31 adnws007 kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. Aug 18 07:26:31 adnws007 kernel: PM: Shrinking memory... |Restarting tasks ... done. Aug 18 07:27:54 adnws007 kernel: s2disk[23364]: segfault at 0 ip b7f66efd sp bfba9a18 error 4 in libc-2.8.so[b7e86000+13d000] adnws007:~ # uname -a Linux adnws007 2.6.25.20-0.4-pae #1 SMP 2009-06-01 09:57:12 +0200 i686 i686 i386 GNU/Linux The suspend to RAM seems to work only with the --force option: adnws007:~ # s2ram Machine is unknown. This machine can be identified by: sys_vendor = "Dell Inc." sys_product = "Precision WorkStation T5400 " sys_version = "" bios_version = "A04" See http://en.opensuse.org/S2ram for details. If you report a problem, please include the complete output above. If you report success, please make sure you tested it from both X and the text console and preferably without proprietary drivers. adnws007:~ # s2ram --force Switching from vt7 to vt1 fbcon fb0 state 1 fbcon fb0 state 0 switching back to vt7 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 10

[Bug 585742] New: fsck reports errors when run with -n on mounted ext4 fs, but no errors when remounted readonly
by bugzilla_noreply＠novell.com 08 Apr '10

08 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=585742 http://bugzilla.novell.com/show_bug.cgi?id=585742#c0 Summary: fsck reports errors when run with -n on mounted ext4 fs, but no errors when remounted readonly Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: HP OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ramon.casha(a)linux.org.mt QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I ran the command "fsck -n" on the mounted root filesystem and got a list of errors. I rebooted to single-user mode, remounted the filesystem readonly and ran "fsck -f" but this gave no errors. I remounted it read-write and ran fsck and got the same errors again. Reproducible: Always Steps to Reproduce: fsck -n -f mount -o remount,ro /dev/sda1 / fsck -f Actual Results: First fsck: fsck from util-linux-ng 2.16 e2fsck 1.41.9 (22-Aug-2009) Warning! /dev/sda1 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/sda1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found. Fix? no Inode 1239 was part of the orphaned inode list. IGNORED. Inode 1354 was part of the orphaned inode list. IGNORED. Inode 917831 was part of the orphaned inode list. IGNORED. Inode 917836 was part of the orphaned inode list. IGNORED. Inode 917839 was part of the orphaned inode list. IGNORED. Inode 917840 was part of the orphaned inode list. IGNORED. Deleted inode 917848 has zero dtime. Fix? no Inode 917849 was part of the orphaned inode list. IGNORED. Inode 917857 was part of the orphaned inode list. IGNORED. Inode 917860 was part of the orphaned inode list. IGNORED. Inode 917862 was part of the orphaned inode list. IGNORED. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +(15136855--15136864) -(15136865--15136868) -(15182336--15182341) -15499414 -(15505408--15505418) -(15509530--15509544) -(15515648--15515726) Fix? no Free blocks count wrong for group #461 (18066, counted=18072). Fix? no Free blocks count wrong for group #463 (22515, counted=22509). Fix? no Free blocks count wrong for group #473 (27175, counted=27159). Fix? no Free blocks count wrong (8076210, counted=8074199). Fix? no Inode bitmap differences: -1239 -1354 -917831 -917836 -(917839--917840) -(917848--917849) -917857 -917860 -917862 Fix? no Free inodes count wrong (7911248, counted=7911111). Fix? no /dev/sda1: ********** WARNING: Filesystem still has errors ********** /dev/sda1: 1599664/9510912 files (0.3% non-contiguous), 29947629/38023839 blocks ===================================================== Second fsck produced no errors at all I don't know yet whether this is a problem with fsck reporting inexistent errors on mounted filesystems, or whether there really are errors which are not being reported when the fs is mounted readonly - so I have marked this as critical in case it is the latter. On one occasion I ran "fsck -n" and got a number of files that contained errors, but on running the same command immediately after, these were no longer among the errors. -- 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 593872] New: bootloader GRUB does not start after installation
by bugzilla_noreply＠novell.com 08 Apr '10

08 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=593872 http://bugzilla.novell.com/show_bug.cgi?id=593872#c0 Summary: bootloader GRUB does not start after installation Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: jastgasi(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-2.1 Firefox/3.6 After installation of Milestone 4 Grub could not load reporting error 23. installation medium was checked and md5sum was correct. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. afterwards i "updated" the system with the same DVD and it worked. remark: the rescue system was not loadable! -- 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 594434] update-ca-certificates should be called in %post?
by bugzilla_noreply＠novell.com 08 Apr '10

08 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=594434 http://bugzilla.novell.com/show_bug.cgi?id=594434#c3 Ludwig Nussel <lnussel(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|vuntz(a)novell.com | --- Comment #3 from Ludwig Nussel <lnussel(a)novell.com> 2010-04-08 09:41:24 CEST --- I see the problem. ca-certificates-mozilla and openssl-certs have most certificates in common. ca-certificates-mozilla obsoletes openssl-certs but at the time %post is running the files from openssl-certs are still present. So the new links from ca-certificates-mozilla cannot be installed. So I'll have to make ca-certificates obsolete openssl-certs too so the package is fully gone already when ca-certificates-mozilla gets installed. -- 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 594434] update-ca-certificates should be called in %post?
by bugzilla_noreply＠novell.com 08 Apr '10

08 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=594434 http://bugzilla.novell.com/show_bug.cgi?id=594434#c2 Ludwig Nussel <lnussel(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |vuntz(a)novell.com --- Comment #2 from Ludwig Nussel <lnussel(a)novell.com> 2010-04-08 09:12:24 CEST --- ca-certificates itself doesn't contain any certificates, just the scripts so ca-certificates-mozilla pre requires ca-certificates and calls update-ca-certificates in %post instead. Any error messages in /var/log/zypp/history? -- 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 588157] New: artefacts without compositing (KDE 4.3.5)
by bugzilla_noreply＠novell.com 07 Apr '10

07 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=588157 http://bugzilla.novell.com/show_bug.cgi?id=588157#c0 Summary: artefacts without compositing (KDE 4.3.5) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jc(a)phocean.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=348310) --> (http://bugzilla.novell.com/attachment.cgi?id=348310) KDE artefact User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I have frequently a lot of artefacts in KDE 4.3.5 (I switched to it straight from Gnome). It happens most of time when I put the mouse cursor over the task bar to display the info bubble, or over the clock. The artefact displays the background inside a shape equal to the info bubble, but misplaced. Please look at the screenshots for better understanding. I didn't notice any issues neither while using compositing (but I don't want to use it because of the ressources drain) nor using the Gnome environment, so I think it is more a KDE issue than an Nvidia one (I am using the proprietary driver from the nvidia repo). Is it a known problem? Shall I report the issue upstream? 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 11

[Bug 548328] New: installer screen turns blank after reboot - unable to finish installation - Dell Optiplex 330
by bugzilla_noreply＠novell.com 07 Apr '10

07 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=548328 Summary: installer screen turns blank after reboot - unable to finish installation - Dell Optiplex 330 Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ah(a)idra.pl QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) The first part of installation goes on smoothly - both in automatic and "manaul" modes however after the reboot installer is suppose to continue but when it enters the graphical mode the screen justs blank. IT appears that there is some problem with screen setup the machine is Dell Optiplex 330 with build-in graphics card, the monitor is XHD3000 by Gateway (PC is functioning e.g can switch to terminal and the installer processes seem to running) I attach some logs: Reproducible: Always Steps to Reproduce: 1. start installation 2. let installer reboot the PC 3.wait for the 2'nd graphical part -- 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 50

[Bug 561870] New: After Upgrade to 11.2 xrandr stops with "screen cannot be larger than 2048x2048"
by bugzilla_noreply＠novell.com 07 Apr '10

07 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=561870 http://bugzilla.novell.com/show_bug.cgi?id=561870#c0 Summary: After Upgrade to 11.2 xrandr stops with "screen cannot be larger than 2048x2048" Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: R.Escher(a)osram.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=331745) --> (http://bugzilla.novell.com/attachment.cgi?id=331745) My xorg.conf User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 Until OpenSuse 11.1 I had a working Xinerama configuration (same hardware as described in bug http://bugzilla.novel.com/show_bug.cgi?id=341241) In short: intel 915G chipset, 17" lcd on the VGA output, 22" lcd on the hdmi output. In my xorg.conf I use the driver "Intel" and set Virtual 3000 1200 I use these command to enable xinerama: xrandr --output VGA --right-of TMDS-1 xrandr --newmode "sxga" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 xrandr --addmode VGA sxga xrandr --output VGA --mode sxga Before I got a warning in the xorg.log that no DRI support is possible, but xinerama worked. After the upgrade xrandr tells: "xrandr: screen cannot be larger than 2048x2048 (desired size 2880x1200)" I tried to disable DRI support manually in xorg.conf, but without success 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 25

[Bug 570600] New: radeon: The Xserver crashed after resuming from s2ram
by bugzilla_noreply＠novell.com 07 Apr '10

07 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=570600 http://bugzilla.novell.com/show_bug.cgi?id=570600#c0 Summary: radeon: The Xserver crashed after resuming from s2ram Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: christiandehne(a)web.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=336540) --> (http://bugzilla.novell.com/attachment.cgi?id=336540) xorg.conf User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.90 (like Gecko) SUSE After a resume from s2ram I found myself in front of the login manager instead of my usual desktop. When this happened I had two Xsessions where running. This happend only once and I use openSUSE 11.2 since the release candidate and s2ram usually several times a day. So rarely reproducible, if at all. My card is radeon mobility 9600 /usr/sbin/hwinfo --gfxcard 20: PCI 100.0: 0300 VGA compatible controller (VGA) [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_1002_4e50 Unique ID: VCu0.qPhhfLi5vp3 Parent ID: vSkL.VPA5WRkwsF4 SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0 SysFS BusID: 0000:01:00.0 Hardware Class: graphics card Model: "Samsung Electronics P35 notebook" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x4e50 "RV350 NP" SubVendor: pci 0x144d "Samsung Electronics Co Ltd" SubDevice: pci 0xc00c "P35 notebook" Driver: "radeonfb" Driver Modules: "radeonfb" Memory Range: 0xd8000000-0xdfffffff (rw,prefetchable) I/O Ports: 0x3000-0x3fff (rw) Memory Range: 0xd0100000-0xd010ffff (rw,non-prefetchable) Memory Range: 0xd0120000-0xd013ffff (ro,prefetchable,disabled) IRQ: 11 (5584892 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00001002d00004E50sv0000144Dsd0000C00Cbc03sc00i00" Driver Info #0: XFree86 v4 Server Module: radeon Driver Info #1: XFree86 v4 Server Module: radeon 3D Support: yes Extensions: dri Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (PCI bridge) Primary display adapter: #20 Reproducible: Couldn't Reproduce xorg.conf is needed to have the correct display size on my Samsung P35 -- 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