July 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 343670] New: Bootloader -- Cannot be reset to propose a new configuration or reset doesn 't work
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=343670 Summary: Bootloader -- Cannot be reset to propose a new configuration or reset doesn't work Product: openSUSE 10.3 Version: Final Platform: Macintosh OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: dfiser(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com CC: anicka(a)novell.com Found By: --- Created an attachment (id=184422) --> (https://bugzilla.novell.com/attachment.cgi?id=184422) logs, etc. I've been installing openSUSE 10.3 PPC on Mac mini. It had the MacOS_whatever already installed and it occupied the whole disk. Partitioner didn't find any solution and wrote this in the proposal: No automatic proposal possible. Specify mount points manually in the 'Partitioner' dialog. Bootloader wrote this: Configure a valid boot loader location before continuing. In case that no selection can be made it may be necessary to create a PReP Boot partition. (PPC bootloader needs PReP Boot partition to be installed there). Even if I either created a valid partitioning or let partitioner use the whole disk, Bootloader didn't use that "new" partitioning. So I tried "Propose New Configuration" (bootloader) and also "Start from Scratch". Nothing worked. In my opinion, Bootloader proposal should be be updated when partitioning changes, especially when no valid configuration was possible before. See the attachment * /var/log/YaST2/ (all logs) * /root/yast2-screen-shots (screenshots of the problem) * pdisk--list.txt (list of the current partitioning) -- 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 227513] New: Missing username/password in $http_proxy and friends
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=227513 Summary: Missing username/password in $http_proxy and friends Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mludvig(a)logix.net.nz QAContact: qa(a)suse.de I need to supply username and password for my webproxy. Once set in Yast Proxy module it's supposed to be exported to http_proxy (and https_proxy, ftp_proxy) environment variables. Although the proxy hostname and port are exported as expected the username and password part is missing. I.e. instead of http_proxy=http://user:password@proxyhost:3128 I get only http_proxy=http://proxyhost:3128 which is of not much use for programs like wget. Indeed I set it up manually in .bashrc but I believe it should be done by Yast for me. -- 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, or are watching someone who is.

1 23

[Bug 350956] New: rt2500usb module/interface fails to load correctly
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=350956 Summary: rt2500usb module/interface fails to load correctly Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: james(a)usr-local-bin.org QAContact: qa(a)suse.de Found By: Beta-Customer Created an attachment (id=188911) --> (https://bugzilla.novell.com/attachment.cgi?id=188911) dmesg lines I've filed this under Kernel but since it's a network adapter, someone may want to reallocate it... Just got a USB dongle that uses an RAlink chipset for my wife's laptop - this should be supported by the rt2x00-kmp-* package. It appears to be detected and the module is loaded but the interface goes down when it's handed over to NetworkManager. Attaching three files - relevant dmesg lines; /var/log/messages from it being plugged in; /var/log/NetworkManager from it being plugged in. -- 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 22

[Bug 365649] New: zypper doesn't run SuSEconfig after installing packages
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=365649 Summary: zypper doesn't run SuSEconfig after installing packages Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: dmacvicar(a)novell.com ReportedBy: wberrier(a)novell.com QAContact: dmacvicar(a)novell.com CC: twiest(a)novell.com Found By: --- I have an rpm that installs new icons in /usr/share/icons/hicolor. When I install it with zypper, the icons don't show up in the gnome main menu because the icon cache hasn't been updated. Installing from yast runs SuSEconfig, and the icon cache gets updated, and icons are loaded as expected. -- 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 44

[Bug 411587] New: Very slow to switch desktops
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=411587 Summary: Very slow to switch desktops Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: cschum(a)novell.com QAContact: qa(a)suse.de Found By: --- Under some circumstances it's very slow to switch virtual desktops. I'm not sure what the exact conditions are, but here is one way to reproduce it: 1) Open five nedit (www.nedit.org) windows. 2) Switch to another virtual desktop 3) Switch back to the desktop where the nedit windows are 4) Experience a big delay. You can watch the window decorations being painted for something like two seconds before the desktop becomes responsive again. -- 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 17

[Bug 407168] New: docbook-to-man fails with 'illegal input sequence' from / usr/bin/iconv
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=407168 Summary: docbook-to-man fails with 'illegal input sequence' from /usr/bin/iconv Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: teastep(a)shorewall.net QAContact: qa(a)suse.de Found By: Customer Created an attachment (id=226501) --> (https://bugzilla.novell.com/attachment.cgi?id=226501) Sample XML document that produces the failure XML->man translation of a number of my manpages fails on OpenSuSE 11.0 as shown here: teastep@opensuse11:~/shorewallBuild/4.2/shorewall-common-4.2.0-Beta3/manpages> docbook-to-man -C /usr/share/docbook2X/xslt/catalog.xml --utf8trans-map /usr/share/docbook2X/charmaps/roff.charmap shorewall-accounting.xml /usr/bin/iconv: illegal input sequence at position 673 /usr/bin/db2x_manxml: program in pipeline exited with an error teastep@opensuse11:~/shorewallBuild/4.2/shorewall-common-4.2.0-Beta3/manpages> By contrast, under OpenSuSE 10.3: teastep@ursa:~/shorewallBuild/4.2/shorewall-common-4.2.0-Beta3/manpages$ docbook-to-man -C /usr/share/docbook2X/xslt/catalog.xml --utf8trans-map /usr/share/docbook2X/charmaps/roff.charmap shorewall-accounting.xml teastep@ursa:~/shorewallBuild/4.2/shorewall-common-4.2.0-Beta3/manpages$ I will attach a sample xml document that produces the failure. -- 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 8

[Bug 337665] New: Printer out of paper disables printer, needs admin to fix
by bugzilla_noreply＠novell.com 09 Feb '09

09 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=337665 Summary: Printer out of paper disables printer, needs admin to fix Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: com.opensuse(a)bucksch.org QAContact: jsmeix(a)novell.com Found By: Customer Reproduction: (typical day-to-day end-user scenario) 1. Put only 2 sheets of paper in your printer, or no paper at all 2. Print a document with 3 pages 3. When printer complains, refill paper 4. Press print again and again and again Actual result: When the printer is out of paper, CUPS automatically disables the printer. You can only reactivate it by going to the CUPS admin console, entering the admin (typically root) password, and enable the printer. Expected result: - When the printer has paper again, the printing of the current job resumes and new jobs are carries out as well. - Or, worse, but far better than now: Only cancel current job, but keep printer active. Importance: This is an extremely common end user scenario. Clueless newbies being out of paper happens all the time. I just had to remote assist my father because of that, and felt embarrassed for Linux. Of course he felt no need to tell me that he once was out of paper, because that's a completely normal and unproblematic situation for him - put paper in and all is well. And he's right: It's a complete non-issue on all other systems I used in the last decade. The first time that happened, it took me *hours* to figure out what happened. I did not imagine that such a simple, temporary problem would permanently disable a printer. You need an admin to recover from "out of paper". It may make sense for a big facility where the printer has its own admin (and that admin can reconfigure CUPS all he wants), but makes no sense at all in the normal desktop situation where you have an average users who doesn't know what "print jobs" are, much less the admin interfaces or root password. The average users are the majority and rely on the default settings, so the default needs to change. -- 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 14

[Bug 329668] New: When i choose NFS as installation source i cant set a network proxy or an fixed ip address at the startup screen
by bugzilla_noreply＠novell.com 08 Feb '09

08 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=329668 Summary: When i choose NFS as installation source i cant set a network proxy or an fixed ip address at the startup screen Product: openSUSE 10.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joop_boonen(a)web.de QAContact: jsrain(a)novell.com Found By: --- When i choose NFS as installation source i cant set a network proxy or an fixed ip address at the startup screen -- 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 381024] New: [multiscreen] Wrong resolution displayed for the external monitor
by bugzilla_noreply＠novell.com 08 Feb '09

08 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=381024 Summary: [multiscreen] Wrong resolution displayed for the external monitor Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Blocks: 374148 Found By: --- 1. Run gnome-display-properties 2. Click detect 3. See that you have a second monitor in the canvas. The size looks good 4. Look at the proposed resolutions for this monitor: they're not good. More specifically, it should list 1440x900 for me. And it lists 1400x1050 (which is the resolution of my main monitor) -- 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 408733] New: Check the process for boot loader restoration
by bugzilla_noreply＠novell.com 08 Feb '09

08 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=408733 User Markus.Elfring(a)web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408733#c357290 Summary: Check the process for boot loader restoration Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)novell.com Found By: --- I installed the current software "GParted 0.3.8" yesterday. http://packman.links2linux.de/package/gparted/66366 Today I have dared to resize my boot partition with this tool. Unfortunately, I have got the display "GRUB " after reboot. It seems that the boot loader does not like the adjusted disk layout. I wonder why it has got problems to find its configuration file "menu.lst" after the space adjustment. I booted from a DVD then. http://download.opensuse.org/distribution/11.0/iso/dvd/openSUSE-11.0-DVD-x8… 1. I have chosen to start an update. I was pointed to the rescue system as an alternative a step later which I chose. I have selected minimum options. It was reported that an error occurred during boot loader installation. (The message did not tell any more details!) 2. I have selected the option "Repair installed system" from the main boot menu where I have started the action "Restore GRUB" from the expert tools section. It was reported that the boot loader could not be installed because the root directory could not be found. (Do you support a "/" here that is contained in a LVM2 setup?) 3. I have chosen to perform a (complete) update. I was presented the same questionable error message as in 1. at the end after I went all through the hassle of long waiting for dependency and conflict resolution. I booted from another DVD. ftp://ftp.uni-kl.de/pub/linux/knoppix/DVD/KNOPPIX_V5.3.1DVD-2008-03-26-DE.iso root@Knoppix:~# e2fsck /dev/sda2 e2fsck 1.40.8 (13-Mar-2008) /dev/sda2: clean, 103/28224 files, 96561/112452 blocks root@Knoppix:~# mount /dev/sda2 /mnt/B root@Knoppix:~# e2fsck /mnt/B e2fsck 1.40.8 (13-Mar-2008) e2fsck: Is a directory while trying to open /mnt/B The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> It seems that an other approach for a GRUB restore will be needed like it is described in the article "http://grub.enbug.org/grub-install" or the issue "'yast2 bootloader' module rewrites grub generic code when leaving with no changes, which may corrupt grub" (bug #357290). The protocol files became too big (> 10 MB) to append them for this bug report in an attachment. root@Knoppix:~# cd /mnt/H/elfring/Projekte/YaST/ && tar -cjf broken_GRUB.tbz /mnt/V/log/YaST2 && du -h broken_GRUB.tbz 31M broken_GRUB.tbz -- 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 42