October 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 381665] New: Cannot read EXT2 formatted floppy
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=381665 Summary: Cannot read EXT2 formatted floppy Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mario_bz(a)mgtech.com QAContact: qa(a)suse.de Found By: --- Just tried beta1 which now displays a floppy icon on the system screen. However, when I put an ext/ext2 formatted floppy into the drive and click the message below appears. When I try a standard DOS floppy it works fine. I use ext2 for my grub boot and it does work fine so there is no problem with the ext2 floppies. I also tried adding: /dev/fd0 /media/floppy auto noauto,user,sync 0 0 which I found in 10.3 fstab but not in 11.0, it prevented the message below but then other errors (missing /media/floppy) occurred and not data displayed. mount: wrong fs type, bad option, bad superblock on /dev/fd0, missing codepage on helper program or other error, error in some useful info found in syslog - try dmesg | tail. mario@linux:~> dmesg | tail sd 8:0:0:0: [sdc] Mode Sense: 11 00 00 00 sd 8:0:0:0: [sdc] Cache data unavailable sd 8:0:0:0: [sdc] Assuming drive cache: write through sdc: [mac] sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8 sd 8:0:0:0: [sdc] Attached SCSI disk sd 8:0:0:0: Attached scsi generic sg3 type 0 XFS mounting filesystem sdc7 Ending clean XFS mount for filesystem: sdc7 hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. mario@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 18

[Bug 399966] New: kernel BUG at fs/reiserfs/journal.c:1036!
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=399966 User lmb(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=399966#c1 Summary: kernel BUG at fs/reiserfs/journal.c:1036! Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: jeffm(a)novell.com ReportedBy: lmb(a)novell.com QAContact: qa(a)suse.de CC: jack(a)novell.com Found By: --- My home directory is on reiserfs, on a separate logical volume. When trying to access a particular directory (my SUSE e-mail folder, of all lucky guesses), I get a kernel oops: ------------[ cut here ]------------ kernel BUG at fs/reiserfs/journal.c:1036! invalid opcode: 0000 [#1] SMP last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09 Modules linked in: authenc xfrm4_mode_tunnel deflate zlib_deflate ctr twofish_i5 Pid: 4801, comm: mutt Tainted: G N (2.6.25.5-1.1-pae #1) EIP: 0060:[<f965cedc>] EFLAGS: 00010246 CPU: 0 EIP is at flush_commit_list+0x5e/0x58d [reiserfs] EAX: f2c6b0a0 EBX: f9cf7000 ECX: f7851000 EDX: f9668ec6 ESI: f2d2f0c0 EDI: 0089e837 EBP: f2cb1f1c ESP: f2cb1edc DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Process mutt (pid: 4801, ti=f2cb0000 task=f2c6b0a0 task.ti=f2cb0000) Stack: 00000001 f7851000 0089e837 f9cf7000 f347d8c0 00000000 f700eb84 00000000 f2cb1f58 f2cb1f10 c015f623 f700eb84 00000000 f9cf7000 f7851000 0089e837 f2cb1f64 f965f966 f700ead8 f2d2f0c0 00000000 00000000 00000001 00000000 Call Trace: [<f965f966>] reiserfs_commit_for_inode+0x14f/0x17d [reiserfs] [<f964d521>] reiserfs_sync_file+0x36/0x74 [reiserfs] [<c01954e2>] do_fsync+0x48/0x75 [<c019552e>] __do_fsync+0x1f/0x2f [<c019555d>] sys_fsync+0xd/0xf [<c01059e4>] sysenter_past_esp+0x6d/0xa9 [<ffffe430>] 0xffffe430 ======================= Code: 45 c4 e8 c7 fd ff ff 83 7e 14 00 c7 45 d4 00 00 00 00 0f 85 14 05 00 00 64 EIP: [<f965cedc>] flush_commit_list+0x5e/0x58d [reiserfs] SS:ESP 0068:f2cb1edc ---[ end trace 42b3c6f590148f7c ]--- ------------[ cut here ]------------ WARNING: at kernel/exit.c:892 do_exit+0x31/0x5c6() Modules linked in: authenc xfrm4_mode_tunnel deflate zlib_deflate ctr twofish_i5 Pid: 4801, comm: mutt Tainted: G D N 2.6.25.5-1.1-pae #1 [<c01071d9>] dump_trace+0x63/0x227 [<c0107c8a>] show_trace+0x15/0x29 [<c02e84b5>] _etext+0x5b/0x65 [<c012573d>] warn_on_slowpath+0x41/0x67 [<c01287da>] do_exit+0x31/0x5c6 [<c0107702>] die+0x15e/0x166 [<c02e5279>] do_trap+0x8a/0xa3 [<c0107b25>] do_invalid_op+0x6c/0x76 [<c02e4bc2>] error_code+0x72/0x80 [<f965cedc>] flush_commit_list+0x5e/0x58d [reiserfs] [<f965f966>] reiserfs_commit_for_inode+0x14f/0x17d [reiserfs] [<f964d521>] reiserfs_sync_file+0x36/0x74 [reiserfs] [<c01954e2>] do_fsync+0x48/0x75 [<c019552e>] __do_fsync+0x1f/0x2f [<c019555d>] sys_fsync+0xd/0xf [<c01059e4>] sysenter_past_esp+0x6d/0xa9 [<ffffe430>] 0xffffe430 ======================= ---[ end trace 42b3c6f590148f7c ]--- This is reproducible. openSUSE 10.3 worked fine. It might be related to bug #389656, but I'm not seeing a hard hang. Please advise. -- 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 68

[Bug 343946] New: oprofile and libc symbols
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=343946 Summary: oprofile and libc symbols Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: peter(a)plord.co.uk QAContact: qa(a)suse.de Found By: --- I have the following packages installed :- * glib * glibc-devel * glibc-profile but when running the oprofile tool I don't get the libc symbols :- $ opreport -d .. 00000000 1 0.9615 12006 12.3130 libc-2.6.1.so (no symbols) access to the symbols are important for debugging. -- 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 439065] New: libgphoto2: Error (-8: 'Fixed limit exceeded')
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=439065 User lliu(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439065#c1 Summary: libgphoto2: Error (-8: 'Fixed limit exceeded') Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Keywords: Chinese_Traditional Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lliu(a)novell.com QAContact: qa(a)suse.de Found By: Field Engineer Created an attachment (id=248016) --> (https://bugzilla.novell.com/attachment.cgi?id=248016) The error log was from the debug mode Software env: t41p:/home/lliu/photo # cat /etc/SuSE-release openSUSE 11.0 (i586) VERSION = 11.0 t41p:/home/lliu/photo # uname -a Linux t41p 2.6.25.16-0.1-default #1 SMP 2008-08-21 00:34:25 +0200 i686 i686 i386 GNU/Linux t41p:/home/lliu/photo # rpm -qa | grep gphoto gphoto-2.4.1-24.1 libgphoto2-2.4.1.2-21.1 t41p:/home/lliu/photo # It shows error messages when executing gphoto2 command: t41p:/home/lliu/photo # env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --get-all-files *** Error (-8: 'Fixed limit exceeded') *** For debugging messages, please use the --debug option. Debugging messages may help finding a solution to your problem. If you intend to send any error or debug messages to the gphoto developer mailing list <gphoto-devel(a)lists.sourceforge.net>, please run gphoto2 as follows: env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --debug --debug-logfile=my-logfile.txt --get-all-files Please make sure there is sufficient quoting around the arguments. t41p:/home/lliu/photo # The log file 'my-logfile.txt' is now in the attachment. -- 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 373055] New: osc build --no-init does to much
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=373055 Summary: osc build --no-init does to much Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dominique.leuenberger(a)tmf-group.com QAContact: adrian(a)novell.com Found By: --- Hello, osc build no-init does to much IMO: I built an package yesterday (against Factory, i586).. it failed. So today I adjusted some things in the spec file and issued osc build --no-init and the same parameters otherwise a yesterday. Even though osc is instructed not to initialize the buildroot and actually start the build with the current one (which would be ok.. I would not need the updated rpms) it decides to download all the RPMs to their latest versions available in OBS. --no-init should be respected and the initialization should be skipped. (actually, the RPMs were only downloaded, not even installed.. so it was a pure waste of time and bandwidth) -- 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 430159] New: no Russian Language in edit my profile
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=430159 Summary: no Russian Language in edit my profile Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)novell.com ReportedBy: egd.free(a)gmail.com QAContact: adrian(a)novell.com Found By: --- Created an attachment (id=241922) --> (https://bugzilla.novell.com/attachment.cgi?id=241922) no russian language List of languages https://users.opensuse.org/my/profile/edit hasn't Russian language -- 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 404129] New: e2fsck takes extremly long on clean filesystems
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=404129 Summary: e2fsck takes extremly long on clean filesystems Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.pfaller(a)gmail.com QAContact: qa(a)suse.de Found By: --- After installing 11.0 I noticed that every boot stalled extremely long (several minutes) during the fsck phase although all filesystems were clean and a forced check (due to mount count or time limit) was not needed. Further testing showed that the 11.0 e2fsck takes much longer to check a clean file system then older versions, e.g. 11.0 fsck: [bomba ~#> time e2fsck /dev/sda7 e2fsck 1.40.8 (13-Mar-2008) data: clean, 51075/28327936 files, 43019103/56639157 blocks real 1m4.789s user 0m0.300s sys 0m0.760s Same filesystem using the 10.2 e2fsck while running 11.0: [bomba ~#> time /mnt/diavolo-root/sbin/e2fsck /dev/sda7 e2fsck 1.39 (29-May-2006) data (/dev/sda7): clean, 51075/28327936 files, 43019103/56639157 blocks real 0m0.167s user 0m0.128s sys 0m0.012s Both results are with hot caches and completely reproduceable. The complete boot takes even longer since the samples above are for one of my smaller file systems. -- 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 366762] New: cron ignores postfix environmental settings
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=366762 Summary: cron ignores postfix environmental settings Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: support(a)microtechniques.com QAContact: qa(a)suse.de Found By: Customer Security check jobs run by security-control.sh search for and prioritize which mail client that they use and use the environment variables specified in sysconfig/security (see tests around line 41) run-crons only uses the mail command, and does not export any of the mail related environmental settings (see line 224). As a result, an installation running multiple postfix instances with separate mail stores does not receive any mail from cron jobs, and you get syslog errors about a missing /var/spool/postfix/maildrop. 1)run-crons and security-control.sh should use the same means for selecting the mail system. 2)run-crons should export environment variables such as MAIL_CONFIG when specified in a crontab. -- 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 304995] New: splashy doesn't use a fullscreen image while suspending
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=304995 Summary: splashy doesn't use a fullscreen image while suspending Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: hmacht(a)novell.com ReportedBy: cstender(a)novell.com QAContact: qa(a)suse.de CC: anschneider(a)novell.com Found By: --- Splashy doesn't use a fullscreen image while suspending. I tested this on two Thinkpads (T60 and T60p) with a 1400x1050 resolution. It seems that the image is only about 1280x1024 pixels. Please let me know if you need more information or test hardware. -- 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 40

[Bug 405264] New: ext3 turned into ext2 with root on lvm on raid0
by bugzilla_noreply＠novell.com 16 Mar '09

16 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=405264 Summary: ext3 turned into ext2 with root on lvm on raid0 Product: openSUSE 11.0 Version: Final Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de Found By: --- hurtleberry, pSeries JS20 8842-21X I have installed ext3 root on lvm on raid0 over two ide disks after reboot: doing fast boot Creating device nodes with udev udevd-event[205]: node_symlink: device node '/dev/mapper/control' already exists, link to '/dev/device-mapper' will not overwrite it blogd: can not open pty/tty pair: No such file or directory mdadm: device 1 in /dev/md0 has wrong state in superblock, but /dev/sda2 seems ok mdadm: /dev/md0 has been started with 2 drives. 3 logical volume(s) in volume group "system_hurtleberry" now active 3 logical volume(s) in volume group "system_hurtleberry" now active Waiting for device /dev/system_hurtleberry/root to appear: ok fsck 1.40.8 (13-Mar-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/system_hurtleberry/root hurtleberry_root: Superblock has an invalid ext3 journal (inode 8). CLEARED. *** ext3 journal has been deleted - filesystem is now ext2 only *** hurtleberry_root: Superblock doesn't have has_journal flag, but has ext3 journal inode. CLEARED. hurtleberry_root was not cleanly unmounted, check forced. hurtleberry_root: Journal inode is not in use, but contains data. CLEARED. hurtleberry_root: Inode 449739, i_blocks is 448, should be 104. FIXED. hurtleberry_root: Inode 942059 has illegal block(s). hurtleberry_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck failed. Mounting root device read-only. Mounting root /dev/system_hurtleberry/root ext3: No journal on filesystem on dm-1 mount: wrong fs type, bad option, bad superblock on /dev/mapper/system_hurtleberry-root, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so could not mount root filesystem -- exiting to /bin/sh $ have to check if its a hardware bug or if it also happens on other disks. At least a previous similar 11.0 installation turned the ext3 also into ext2. -- 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