March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 482127] New: Is there any way we can decrease the time a PC takes to load all boot settings
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=482127 Summary: Is there any way we can decrease the time a PC takes to load all boot settings Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 My X_64 Quad Core Phenom running at 3.1 clicks and has 8GB of RAM takes longer to boot and load all the devices drivers and then my Athlon X_64 Dual Core running at 2.4 clicks and 2 GIG of RAM is so much quicker when both are running 11.1. Is this enhancement request as easy as creating a bigger RAM drive at Boot and loading copying all the files needed in the RAM drive or am I being so simplistic its not funny - It just ticks my off the my quad core running a much faster clock and more physical RAM taks so much longer and both PC have the same identical number of HDDs, USB devices and the Athlon has speakers where the Phenom does not. Both use the same Video Card and drivers both at default. Both use ASUS AM2 socket motherboards and both have same size, almost, SATA HDD Reproducible: Always Steps to Reproduce: 1.Turn Both PC's on from shutdown at the same time 2. 3. Actual Results: Athlon is quicker by far at boot and final display of Desktop Expected Results: Can we do something that sounds so simple as creating a larger RAM Drive and copy all required files into the RAM drive and load the files from RAM. I think this is such a poor suggestion and I must admit my knowledge of the boot loader is good but not excellent and this morning I am loaded with Espresso to the maX -- 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 462930] New: Suggest add "rccrypto" symlink to /etc/init.d/boot. crypto
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=462930 Summary: Suggest add "rccrypto" symlink to /etc/init.d/boot.crypto Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- You could add the symlink: nimrodel:~ # l /sbin/rccrypto lrwxrwxrwx 1 root root 23 Oct 20 01:41 /sbin/rccrypto -> /etc/init.d/boot.crypto* It is quite convenient. Yes, I know that gnome pops up a window to mount LUKS devices, but I don't like it, I prefer your script. -- 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 481872] New: the boot.crypto.functions doesn't understand more than 8 loop devices
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481872 Summary: the boot.crypto.functions doesn't understand more than 8 loop devices Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: 19972005(a)mail.ru QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 the boot.crypto.functions doesn't understand more than 8 loop devices, if more loop devices used it will fail w/ 'failed to find a usable loop device' . This is from this part of boot.crypto.functions code: ------------------------------------------ # if device is a regular file then it's an image if test -n "$loopdev" -o -f $device; then loopdev='' for i in 0 1 2 3 4 5 6 7; do if ! test -b "/dev/loop$i"; then continue fi unset loopsize read loopsize < /sys/block/loop$i/size if test $? -eq 0 -a "$loopsize" = '0' && /sbin/losetup $param_ro "/dev/loop$i" $device; then device="/dev/loop$i" loopdev="$device" break fi done if test -z "$loopdev"; then report 1 "$physdev: failed to find a usable loop device" failed=1 continue fi fi ------------------------------------- The related 'for i in 0 1 2 3 4 5 6 7; do' should be changed to either something counted from variable in /etc/sysconfig/boot.crypto either counted from 'ls /dev/loop*'. I could provide a patch for my own system, but unsure that will be accepted. Reproducible: Always -- 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 466405] New: mounting encrypted partition: disturbing messages
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=466405 Summary: mounting encrypted partition: disturbing messages Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- mounting encrypted partition: disturbing messages I hope it is not somethings serious, but anyway, booting up computer should be rock-solid. I have one encrypted partition, mounted at boot time, and after entering password (correct) I can see: /lib/cryptsetup/boot.crypto.functions: line 98: kill: (2041) - No such process -- 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 456664] New: make script /etc/init.d/boot. crypto show the dev_mapper_name
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=456664 Summary: make script /etc/init.d/boot.crypto show the dev_mapper_name Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- When I type "/etc/init.d/boot.crypto status" I get something like this: /dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15 [ loop0 mapped mounted running /biggy/crypta_f.mm.x [ loop1 mapped mounted ] running .. /Grande/imgs/crypta_dvd_copy unused /dev/disk/by-id/usb-Initio_ST3320620AS_0010101650000DDEW-0:0-part3 [ mrunningounted ] /dev/disk/by-id/usb-Initio_ST3320620AS_0010101650000DDEW-0:0-part4 [ mrunningounted ] I propose that instead or added to the device name (which as you see above can be pretty long and impossible to remember) show the dev_mapper_name or the mount point. After all, it is possible to mount the crypto devices specifying the dev_mapper_name, so, why not list them? See: nimrodel:~ # rccrypto start mcr_mm_nardol Please enter passphrase for /dev/disk/by-id/usb-Initio_ST3320620AS_0010101650000DDEW-0:0-part3 (mcr_mm_nardol): Please enter passphrase for /dev/disk/by-id/usb-Initio_ST3320620AS_0010101650000DDEW-0:0-part3 (mcr_mm_nardol): key slot 0 unlocked. Command successful. /dev/disk/by-id/usb-Initio_ST3320620AS_0010101650000DDEW-0:0-part3... done -- 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 471446] New: pilot-link-0.12.3-2.71: 2 * attempt to free a non-heap object
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=471446 Summary: pilot-link-0.12.3-2.71: 2 * attempt to free a non-heap object Classification: openSUSE Product: openSUSE 11.2 Version: unspecified Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just tried to compile the Suse Factory package pilot-link-0.12.3-2.71 and the compiler said 1. src/pisock_wrap.c:6347: warning: attempt to free a non-heap object 'temp1' The source code is free((char *) arg1); I agree with the compiler. This line of code is broken. Suggest remove. 2. src/pisock_wrap.c:5837: warning: attempt to free a non-heap object 'temp1' Duplicate. -- 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 481482] New: After connecting a monitor with 1680x1050 res, plasma crashes.
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481482 Summary: After connecting a monitor with 1680x1050 res, plasma crashes. Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: 64bit OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: monkey9(a)iae.nl QAContact: qa(a)suse.de Found By: Beta-Customer I connected a iiama 19" LCD monitor: Prolite E1908WSV, which is not in the sax specs. I choose the latest similar, with above res. After the sax2 reset i rebooted into kde4.2: 4.2.00 (KDE 4.2.0) "release 102" which i used with the other monitors Yusmart:1280x1024, and Videoseven 19" 1440x900. There were npws. I tried to set up the right settings via icewm in suse's system settings, but plasma still crashes. There is no useable backtrace. I write this in icewm. -- 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 13

[Bug 431508] New: seamonkey: "Could not launch Adobe Reader 8.1.2"
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=431508 User rupert.kolb(a)med.uni-tuebingen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=431508#c1 Summary: seamonkey: "Could not launch Adobe Reader 8.1.2" Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rupert.kolb(a)med.uni-tuebingen.de QAContact: qa(a)suse.de Found By: Other The acroread plugin doesn't work in seamonkey. When I click at a PDF link, I get this error message: "Could not launch Adobe Reader 8.1.2. Please make sure it exists in PATH variable in the environment. If the problem persists, please reinstall the application." I'm able to _download_ the PDFs and open it with acroread. In firefox the acrored plugin works as expected. Seamonkey: seamonkey-1.1.12-1.1 (Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.8.1.17) Gecko/20080922 SUSE/1.1.12-1.1 SeaMonkey/1.1.12) Acroread: acroread-8.1.2_SU1-0.1 Kernel: 2.6.25.16-0.1-pae #1 SMP 2008-08-21 00:34:25 +0200 i686 i686 i386 GNU/Linux -- 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 6

[Bug 482785] New: Dots in Installation Screen Look Silly
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=482785 Summary: Dots in Installation Screen Look Silly Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: visnov(a)novell.com ReportedBy: coolo(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=277620) --> (https://bugzilla.novell.com/attachment.cgi?id=277620) screenshot I don't accept the splitter for everyone everywhere when it's only a problem on 800x600 with paritioner. #yast tells me it was Stano who wanted that. -- 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 431659] New: df shows invalid filesystem informations while umount is running
by bugzilla_noreply＠novell.com 06 Mar '09

06 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=431659 Summary: df shows invalid filesystem informations while umount is running Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: schwab(a)novell.com ReportedBy: chrubis(a)novell.com QAContact: qa(a)suse.de Found By: --- When mounting for example usb flash drive, copying files there and right after that doing umount, umount stays running until caches are flushed. For this time df shows invalid filesystem informations (informations about filesystem that path belongs to thus most likely /), because it uses statfs on paths from /etc/mtab but line from mtab is deleted after mount is finished. Solution is to use /proc/mounts (on linux) or check if path in /etc/mtab is really pointing to mounted filesystem. -- 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 6