June 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 261784] New: should not automatically move vga= from after showopts to ahead of showopts
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=261784 Summary: should not automatically move vga= from after showopts to ahead of showopts Product: openSUSE 10.3 Version: Alpha 2plus Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)ij.net QAContact: jsrain(a)novell.com When menu.lst already exists and YaST modifies it, such as when a new kernel is compiled and installed with make, it moves the vga= parameter from wherever I had it (usually at the end of the line) to ahead of the showopts parameter. It's highly annoying that I can't use menu.lst as is when YaST messes with it. vga= is the parameter I most often want to change on boot, so it needs to be readily visible and easily accessible. The only way that can happen now is if I edit it each time YaST has messed with it. YaST should leave showopts as nearly as possible in the same position it finds it instead of shuffling parameters around. -- 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 9

[Bug 260234] New: Wrong installation source picked for boot floppies creation
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=260234 Summary: Wrong installation source picked for boot floppies creation Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mbronczyk(a)novell.com QAContact: jsrain(a)novell.com I noticed on my machine, that once I tried to create boot floppy 1 in YAST->System->'Boor or Rescue Floppy' I have been asked to put CD 1 in order to proceed, I tried first DVD (as this was my installation media), also tried CD 1. None of them did work, however going to details showed me that YAST was looking for boot floppy image not on CD/DVD but on my installation source added for ATI driver. Once I disabled it boot floppy has been created (by using DVD, not CD1). -- 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 9

[Bug 258315] New: Installation system changes "splash=native" kernel option to "splash=silent"
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=258315 Summary: Installation system changes "splash=native" kernel option to "splash=silent" Product: openSUSE 10.3 Version: Alpha 2 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dbolt.abiryy(a)davjam.org QAContact: jsrain(a)novell.com When booting the installation system, I passed the following options to the kernel: linux splash=native acpi=force vga=0x317 as I like to see what's going on during the boot process, just in case of failures. After proceeding with the installation, checking the boot loader settings on the expert tab of the "Installation Settings" window shows the kernel options were going to be set to: splash=silent splash=native acpi=force However, when I clicked on "Booting", and then going to edit the "openSUSE 10.3" section to remove the additional "splash=silent" I found the kernel options had, along with the addition of a wanted "resume=" option, been changed to: splash=silent acpi=force resume=/dev/sda2 splash=silent showopts Also, this bug isn't a new one. It also exists in previous versions. -- 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 13

[Bug 253318] New: Yast destroys grub entries
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=253318 Summary: Yast destroys grub entries Product: openSUSE 10.2 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: rafpolak(a)o2.pl QAContact: jsrain(a)novell.com When I add custom kernel to grub using YaST, it deletes previous kernel entry and adds double entry with new (previously added) kernel. How to reproduce this bug (lets say we want to add our new shiny kernel): 1. Go to YaST -> System -> Boot Loader; 2. Press Add -> Clone Selected Section; 3. Make changes and save them; 4. When you enter Boot Loader Settings again you will see that default kernel entry has gone and there are two identical entries with new kernel. -- 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 17

[Bug 241121] New: autoyast fails to create reference profile on a system with cciss controller
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=241121 Summary: autoyast fails to create reference profile on a system with cciss controller Product: openSUSE 10.2 Version: Final Platform: 64bit OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: reitenbach(a)rapideye.de QAContact: qa(a)suse.de I installed an openSUSE 10.2 system on a HP DL 385. This system comes with a cciss controller for the harddisks. to install openSUSE on such a system, I exchanged the liby2storage.so.2.0.0 file in the cramfs ramdisk as explained here: https://bugzilla.novell.com/show_bug.cgi?id=228707 now, when you then log in as root and issue the command yast autoyast Then using key combination Ctrl-T to open the tools menu, and then pressing return (just activating the "Create Reference profile") menu entry. then in the next view, not selecting any additional resources, just selecting "Create" now you can wait for hours, (Have not tested that, but I at least left it running for a quarter of an hour, with no change) yast will run forever, using 100% cpu cycles. expected behaviour: autoyast of a given suse release shall always be able to create a reference profile from a system with the same suse release running. -- 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 7

[Bug 234146] New: Boot fails after installing to Dell Inspiron 5150
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=234146 Summary: Boot fails after installing to Dell Inspiron 5150 Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ammulder(a)chariotsolutions.com QAContact: jsrain(a)novell.com I installed to a Dell Inspiron 5150 laptop. On this machine, the CD-ROM is /dev/hda and the hard drive is /dev/hdc. Before the install, the drive was cleaned with "shred /dev/hdc". The installation went normally. I did not change any settings related to partitioning (I used its default suggestion) or booting (I just didn't customize anything there). When it rebooted after installing software, the boot hung on a black screen (before any Grub menu or text appeared). When the install CD was in the drive and I let its boot menu timeout, it went to a black screen, printed something like "booting from hard drive..." and then froze there with nothing else on the screen. I booted in rescue mode and manually ran "grub-install /dev/hdc" and rebooted, and then I got the expected Grub menu and things worked normally. I'm not sure if this is related to the fact that the disk was previously shredded, or that the hard drive is not /dev/hda as you might expect, or something else, but it was sure a little frightening to have it hang on boot. -- 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 11

[Bug 223857] New: yast2-bootloader UI: location uses checkboxes
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=223857 Summary: yast2-bootloader UI: location uses checkboxes Product: openSUSE 10.2 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: odabrunz(a)novell.com ReportedBy: jsuchome(a)novell.com QAContact: jsrain(a)novell.com yast2-bootloader, in part of configuration bootloader location shows checkboxes with labels where to boot from (Boot Part, MBR, Root Part, Custom). Is there any reason for using CheckBox instead of RadioButton? With CheckBoxes, it is possible to select more items or even select nothing at all, but these situations don't have sense. RadioButtons force selecting only one option. Please switch back to using RadioButtons instead of CheckBoxes after 10.2. -- 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 10

[Bug 221162] New: missing help text for "Boot Loader Location"
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=221162 Summary: missing help text for "Boot Loader Location" Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: odabrunz(a)novell.com ReportedBy: jsuchome(a)novell.com QAContact: jsrain(a)novell.com In yast2-bootloader, Expert tab has a frame with "Boot Loader Location" options. This widget is mentioned in help text only with the label ("Boot Loader Location" in bold), but without any information. -- 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 6

[Bug 208870] New: Bad grub location selected
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=208870 Summary: Bad grub location selected Product: openSUSE 10.2 Version: Alpha 4 Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hugo.costelha(a)gmail.com QAContact: jsrain(a)novell.com I had SUSE Linux 10.1 installed, and I was trying openSUSE 10.2, to help improving it by bug reporting. I had just one SATA drive installed with SUSE 10.1, so I installed an IDE hard-drive and started openSUSE 10.2 installation from the CDs. Initially openSUSE 10.2 sugested to use the SATA drive, so I changed it to use the IDE drive, and proceeded with the install. When it made the first reboot, the old (SUSE 10.1) GRUB appeared (with no reference to openSUSE 10.2) and booted the 10.1. So, the grub install location was badly selected. -- 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 35

[Bug 267832] New: kopete can't respond to GWIM chats started by the Windows Java client
by bugzilla_noreply＠novell.com 26 Jul '08

26 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=267832 Summary: kopete can't respond to GWIM chats started by the Windows Java client Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: wstephenson(a)novell.com ReportedBy: wstephenson(a)novell.com QAContact: qa(a)suse.de CC: jbeulich(a)novell.com, adrian(a)novell.com Drei Fragen: Problembeschreibung " Du chattest Adrian an, und bekommst keine Antwort, obwohl er behauptet, er hätte Dich geantwortet. " Habe ich das richtig verstanden? Wenn du ein Chat startest, und gleich keine Antwort bekommst, machst Du üblicherweise das Chatfenster zu, oder lässt du es offen, bis jemand darauf antwortet? Kommen von Adrian eingeleiteten chats bei dir an? Ich teste zuerst lokal, falls ich das Problem nicht reproduzieren kann, melde ich mich bei Dir, Jan. -- 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 19