March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 468835] New: Repeated failures to add or update software repositories
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=468835 Summary: Repeated failures to add or update software repositories Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: raffo(a)cdi.com QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=267225) --> (https://bugzilla.novell.com/attachment.cgi?id=267225) Yast2 logs User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 When the software installer starts updating the list of repositories or updating my configured repositories, I randomly get errors about being unable to download certain files. There is also a problem with the NVIDIA repository. At other times all the repositories update without a problem. Please look at the attached yast2 logs to see specific errors. I tried to add the GNOME community repositories and one of them failed to be added. When I immediately tried to add it again, it succeeded. Another issue with the "installation sources" GUI, when a repository fails to be added, a check mark is drawn next to its name as its done with the successfully added repositories. Shouldn't a red "x" be drawn instead? Reproducible: Sometimes 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 4

[Bug 482853] New: LILO throws fatal error when installing openSUSE 11.1
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=482853 Summary: LILO throws fatal error when installing openSUSE 11.1 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ashaduri(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=277718) --> (https://bugzilla.novell.com/attachment.cgi?id=277718) y2logs User-Agent: Opera/9.63 (X11; Linux i686; U; en) Presto/2.1.1 During installation of openSUSE 11.1, if LILO is chosen, it throws the following fatal error: Fatal: /boot/message is too big (> 65535 bytes) The message is indeed about 440KB, but there was no such problem in previous openSUSE versions - LILO happily accepted message files over 64KB. This effectively makes the lilo option useless, unless one knows how to comment out the message entry in /etc/lilo.conf . While I do understand that GRUB is the default boot loader, I've had problems with it being unable to boot on some machines in the past. The filesystem access part may also be discouraging in some recovery situations. Reproducible: Always Steps to Reproduce: 1. Start installing openSUSE 11.1. 2. Switch bootloader to LILO, choosing the "Propose new configuration" option. 3. See the installation fail with a "cannot install bootloader" message. Actual Results: LILO must be installable. Expected Results: Installation failed. -- 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 483939] New: xfs label of the root filesystem does not appear in /dev/disk/by-label/ and is not addressable by "root=LABEL=root"
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=483939 Summary: xfs label of the root filesystem does not appear in /dev/disk/by-label/ and is not addressable by "root=LABEL=root" Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bcihelp(a)merck.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081213 SUSE/1.1.14-1.1 SeaMonkey/1.1.14 After giving the root partition (better said - its XFS filesystem) a new label with xfs_admin -f -L root /dev/sda3 and specifying "root=LABEL=root" in /boot/grub/menu.lst and rebooting, the kernel acts as if the root device were not there: Waiting for /dev/root to appear.................................... Would you like me to fail back to /dev/sda3 [Y/n]? Being dropped into /bin/bash, there is in fact no label entry for /dev/sda3: lrwxrwxrwx 1 root root 10 2009-03-10 15:39 boot -> ../../sda1 lrwxrwxrwx 1 root root 10 2009-03-10 15:39 data -> ../../sdb1 lrwxrwxrwx 1 root root 10 2009-03-10 15:39 swap -> ../../sda2 lrwxrwxrwx 1 root root 10 2009-03-10 15:39 unused -> ../../sda4 The label in fact is there: # xfs_admin -l /dev/root or # xfs_admin -l /dev/sda3 warning: AG 1 label differs warning: AG 2 label differs warning: AG 3 label differs label = "root" Even after booting into runlevel 5 with "root=/dev/sda3", the root filesystem's label is again not recognized - the listing above lacks "root -> ../../sda3", despite the label still really being set in the superblock. It is NOT - I repeat - NOT a problem with XFS in itself! The second disk's /dev/sdb1 is as well XFS and has got a label of "data" - this in fact shows up in /dev/disk/by-label/ (as shown above)! Reproducible: Always Steps to Reproduce: 1. chose XFS filesystem on root device 2. give it a label: xfs_admin [-f] -L root /dev/sda3 3. reboot (or restart udev) Actual Results: The XFS label is not shown in /dev/disk/by-label/, though another XFS's label does show up (/dev/sdb1 with LABEL=data is also XFS in the listing above). Expected Results: The label should appear in /dev/disk/by-label/ Kernel: 2.6.27.19-3.2-pae xfsprogs-2.10.1-1.26 -- 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 474650] New: YAST2 ncurses - sysconfig editor will not accept parameters
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=474650 Summary: YAST2 ncurses - sysconfig editor will not accept parameters Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: drankinatty(a)suddenlinkmail.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 FirePHP/0.2.1 Devs, With Bugs 457093 & 461868 marked FIXED I tried using the ncurses sysconfig editor again, this time attempting to set network -> www -> apache2 -> APACHE_MODULES to add the deflate module. There is no way to add anything or even get to the text entry line just exactly like the two bugs above. I have installed all updates. Am I doing something wrong or is the ncurses sysconfig editor still broken? I presumed that the operation of the sysconfig editor was fixed when the two bugs above were marked FIXED or did nobody check the sysconfig editor's operation beyond the DAILY_TIME variable? Please check and confirm that I'm really not the one doing something stupid here (yes I'm running it as root, not sudo) Reproducible: Always Steps to Reproduce: 1. go to konsole 2. open yast2 ncurses sysconfig-editor 3. try to add a module in network/www/apache2 Actual Results: can't enter squat Expected Results: to be able to add a module to the list like in every release through 11.0 -- 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 4

[Bug 409143] New: frame widget to narrow in qt
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=409143 Summary: frame widget to narrow in qt Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: sh(a)novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development The frame widget can be to narrow in qt so that the frame title is truncated. See Frame1.ycp example. -- 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 9

[Bug 482838] New: RandR in Xserver 1.6.0 doesn't reactivate re-cloned outputs
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=482838 Summary: RandR in Xserver 1.6.0 doesn't reactivate re-cloned outputs Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: ASSIGNED Severity: Major Priority: P5 - None Component: X.Org AssignedTo: mhopf(a)novell.com ReportedBy: mhopf(a)novell.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com CC: sndirsch(a)novell.com Found By: --- xrandr --verbose --output a --left-of b -> a uses CRTC0, b uses CRTC 1 xrandr --verbose --output b --crtc 0 -> both a,b use CRTC0 xrandr --verbose shows that X has the view that both outputs are active and using the same CRTC. Using the radeonhd driver and -logverbose 7 shows that the driver doesn't get an rhdRROutputDpms() activation of the re-cloned output: (II) RADEONHD(0): State at POST-CrtcDpms: RRCrtc #0 [rhd CRTC 1]: active 1 [1] mode unnamed (1680x1050) +0+0 RRCrtc #1 [rhd CRTC 2]: active 0 [0] mode unnamed (0x0) +1680+0 RROut DVI-I_1/analog [Out DAC A Conn DVI-I 1] Crtc null [null] [inactive] disconnected RROut DVI-I_1/digital [Out TMDS A Conn DVI-I 1] Crtc CRTC 1 [CRTC 1] [active] connected RROut TV_SVIDEO [Out DAC B Conn TV SVIDEO] Crtc null [null] [inactive] disconnected RROut DVI-I_2/analog [Out DAC B Conn DVI-I 2] Crtc null [null] [inactive] disconnected RROut DVI-I_2/digital [Out TMDS B Conn DVI-I 2] Crtc CRTC 1 [CRTC 2] [inactive] connected This clearly indicates a bug in the RandR implementation in the Xserver. -- 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 7

[Bug 461595] New: Check handling of installation sources during distribution update
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=461595 Summary: Check handling of installation sources during distribution update Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)novell.com Found By: --- I adjusted the paths for the installation sources in my openSUSE 11.0 system on Saturday evening as a preparation for the recent software release. http://en.opensuse.org/Package_Repositories I tried the update from the openSUSE 11.1 DVD on Sunday morning. http://download.opensuse.org/distribution/11.1/iso/openSUSE-11.1-DVD-x86_64… I checked the corresponding details again after this update was "successfully" performed. I was annoyed that most of my adjustments were lost. A couple of installation source entries refer only to the 10.3 package repositories now. I would prefer that more settings like titles, paths and priorities should be kept by the distribution update process. I could live better with a management change if existings settings can be easily reactivated later on. I do not like the noticed data loss. -- 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 483211] New: some unknown error in yast2 after grub/bootloader installation - system seems only partly installed
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=483211 Summary: some unknown error in yast2 after grub/bootloader installation - system seems only partly installed Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: abittner(a)stud.fh-heilbronn.de QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=277866) --> (https://bugzilla.novell.com/attachment.cgi?id=277866) opensuse 11.2alpha0 factory netiso cleaninstall logs - messed up system User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-2.14 Firefox/3.0.6 i have ran opensuse 11.2 x86 from netinst iso image http://download.opensuse.org/factory/iso/openSUSE-Factory-NET-i586-Build002… and tried a clean install 11.2. at the end of the whole install process there are some quick error messages and as im too tired by now i dont really recall the error, only something like some yast2 module ycp or something failed or crashed, bad parameters or something, some $ signs and variables and whatever, but i dont seem to be able to find it in the yast2log folder as the logdetails and volume is too high for me as a non-developer. an effect of this partly installed system is that i have no properly configured keyboard local (keyboard english only) and my user that i created and given a password during early install stage has also not been created, but the username (testuser) is being mentioned in /var/log/YaST2/macro_inst_initial.ycp: UI::ChangeWidget( `id (`username), `Value, "testuser" ); // YInputField "Username" ------------- nevertheless the user is not in /etc/passwd, and also didnt show up on the left side on the kde4 logon screen, so i had to manually log in as root as testuser didnt work (cos it never got created, as i later found out and i am reporting it here...) so something went wrong with parts of the factory install. will attach logs, and please feel free renaming this bug to something more meaningful once you discovered the real reason and where this bugreport fits best. thanks 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 12

[Bug 475961] New: software repositories: after editing the repo the sort order in the repo table is reseted
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=475961 Summary: software repositories: after editing the repo the sort order in the repo table is reseted Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- software repositories: after editing the repo the sort order in the repo table is reseted Steps to reproduce: * run SR * sort by repo name * edit any repo, accept * observe the table is now sorted by priority -- 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 483845] New: Cannot resize XFS on LVM2 while beeing mounted
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=483845 User rfno(a)fietze-home.de added comment https://bugzilla.novell.com/show_bug.cgi?id=483845#c473717 Summary: Cannot resize XFS on LVM2 while beeing mounted Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rfno(a)fietze-home.de QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE Besides the bug mentioned in #473717 I cannot resize a mounted XFS LV. This worked and works in openSUSE 11.0. Esp. the manual page of xfs_growfs says: "expands an existing XFS filesystem .. The filesystem must be mounted to be grown ..." The relevant part of y2log is: [YCP] Storage.ycp:672 GetPartitionLst tmp:[$["disk":"/dev/vgsys", "nr":"lvusr"]] [YCP] FileSystems.ycp:1189 IsResizable fsys:`unknown ret:$["extend":false, "mount_extend":false, "mount_shrink":false, "shrink":false] [YCP] FileSystems.ycp:1189 IsResizable fsys:`xfs ret:$["extend":true, "mount_extend":true, "mount_shrink":false, "shrink":false] [YCP] Storage.ycp:4625 IsResizable part:$["detected_fs":`xfs, "device":"/dev/vgsys/lvusr", "fstopt":"defaults", "fstype":"LV", "mount":"/usr", "mountby":`device, "name":"lvusr", "size_k":8388608, "stripes":1, "type":`lvm, "used_fs":`xfs, "uuid":"d518a6a9-9207-4439-bcea-8865f6f79ebc"] ret:$["extend":true, "mount_extend":true, "mount_shrink":false, "shrink":false] [YCP] FileSystems.ycp:1140 MinFsSizeK fsys:`xfs ret:40960 [libstorage] Storage.cc(getFreeInfo):5399 device:/dev/vgsys/lvusr use_cache:0 [libstorage] Storage.cc(getFreeInfo):5453 blocks:2094592 free:290079 bsize:4096 [libstorage] Storage.cc(getFreeInfo):5454 free:1160316 used:7218052 [libstorage] Storage.cc(setFreeInfo):5529 device:/dev/vgsys/lvusr df_free:1160316 resize_free:1160316 used:7218052 win:0 efi:0 [libstorage] Storage.cc(getFreeInfo):5518 resize_free:1160316 df_free:1160316 used:7218052 [libstorage] Storage.cc(getFreeInfo):5519 ret:1 win:0 [YCP] Storage.ycp:911 GetFreeSpace resize_free 1188163584 add_free 0 [YCP] Storage.ycp:977 GetFreeSpace /dev/vgsys/lvusr ret $["df_free":1188163584, "efi":false, "free":1188163584, "linux_size":873590784, "max_win_size":8055160832, "new_size":7705858048, "ntfs":false, "ok":true, "used":7391285248, "win_disk":false] [YCP] partitioning/ep-dialogs.ycp:676 used_k:7218052 size_k:8388608 [YCP] partitioning/ep-dialogs.ycp:677 min_size_k:7228292 max_size_k:21729280 [ui] YPushButton.cc(setFunctionKey):160 Guessing button role YHelpButton for YPushButton "Help" at 0x10ff688 from function key F1 [ui] YPushButton.cc(setFunctionKey):160 Guessing button role YCancelButton for YPushButton "Cancel" at 0x1119448 from function key F9 [ui] YPushButton.cc(setFunctionKey):160 Guessing button role YOKButton for YPushButton "OK" at 0x1119fd8 from function key F10 [ui-shortcuts] YShortcutManager.cc(checkShortcuts):127 No valid shortcut for YSlider "New Logical Volume Size (in GB)" at 0x1124ae8 [YCP] FileSystems.ycp:1189 IsResizable fsys:`xfs ret:$["extend":true, "mount_extend":true, "mount_shrink":false, "shrink":false] [YCP] partitioning/custom_part_lib.ycp:1184 CheckResizePossible resize 2097152 ask false lvm false fsys `xfs mount /usr [ui] YPushButton.cc(setFunctionKey):160 Guessing button role YOKButton for YPushButton "OK" at 0x10a4ea8 from function key F10 I get the pop up "The file system is currently mounted under /usr. It is not possible to resize the file system while it is mounted ...". Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: As in openSUSE <= 11.0. -- 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