June 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 382344] New: default to /usr/local/lib64 for self-compiled stuff
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=382344 Summary: default to /usr/local/lib64 for self-compiled stuff Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de CC: coolo(a)novell.com, schwab(a)novell.com Blocks: 369696 Found By: --- It would be nice, if autoconf based configure script will default to libdir=/usr/local/lib64 for self compiles stuff (i. e. ./configure ; make ; make install). It would prevent bi-arch clashes in packages supporting /usr/local. It's trivial to do it: Add /usr/local/share/config.site with following contents: ---- #! /bin/sh if test "$libdir" = '${exec_prefix}/lib' ; then libdir='${exec_prefix}/lib64' fi ---- It is possible to enhance it and skip the change, if it was called inside "linux32" command. -- 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 332186] New: network optimized upgrade of the system
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=332186 Summary: network optimized upgrade of the system Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- >From today experience of upgrading 10.2 to 10.3 from KDE CD I can only say it is too fragile to try it again. Too much time is wasted for displaying (when user is not looking at computer) network errors. Not mentioning it could be total network failure and then what user is supposed to do. Conclusions: user cannot work, a lot of time wasted, bad experience. It seems that only downloading full DVD would solve such problems. But not entirely. But what about such approach. One small CD installer as a kickstart disc -- user downloads it, and burns it. One install manager _program_ -- user downloads it and runs it. This IM would run in current system, user would select what kind of upgrade she/he wants, what packages to add extra, etc etc. Note that at this point system is fully running (something you cannot get with current installer) -- video card, network cards, etc. User clicks ok and downloading begins -- upgrade packages, updates, release notes, firmware, drivers, etc. NOW -- this is crucial. It is just another program in the system downloading stuff. User can still view www pages, write document in OOffice, simply put -- she/he can work! After downloading is finished, user burn DVD/CD(s) of downloaded software. And finally then she/he reboots, inserts kickstart disc, normal installer runs, but all packages are now copied from the burned disc! So there is no weak point in whole upgrade. What do you think? A bit elaborate process, but risk-free, and for upgrade (note, this not for INSTALL!) it could work like a charm. Very fast and safely. -- 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 384170] New: Translating AppAmor is a pain
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=384170 Summary: Translating AppAmor is a pain Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: michael(a)michael-skiba.de QAContact: ke(a)novell.com Found By: Localization Translating AppAmor really is a pain, extremly long texts, unsorted lists in block text form, etc. it scared all our translators.. Couldn't it be made more comfortable? The biggest pain is MID:144: <ul><li> Allow configuration of the secure attention key</li> <li> Allow administration of the random device</li> <li> Allow examination and configuration of disk quotas</li> <li> Allow configuring the kernel's syslog (printk behaviour)</li> <li> Allow setting the domain name</li> <li> Allow setting the hostname</li> <li> Allow calling bdflush()</li> <li> Allow mount() and umount(), setting up new smb connection</li> <li> Allow some autofs root ioctls</li> <li> Allow nfsservctl</li> <li> Allow VM86_REQUEST_IRQ</li> <li> Allow to read/write pci config on alpha</li> <li> Allow irix_prctl on mips (setstacksize)</li> <li> Allow flushing all cache on m68k (sys_cacheflush)</li> <li> Allow removing semaphores</li> <li> Used instead of CAP_CHOWN to \"chown\" IPC message queues, semaphores and shared memory</li> <li> Allow locking/unlocking of shared memory segment</li> <li> Allow turning swap on/off</li> <li> Allow forged pids on socket credentials passing</li> <li> Allow setting read ahead and flushing buffers on block devices</li> <li> Allow setting geometry in floppy driver</li> <li> Allow turning DMA on/off in xd driver</li> <li> Allow administration of md devices (mostly the above, but some extra ioctls)</li> <li> Allow tuning the ide driver</li> <li> Allow access to the nvram device</li> <li> Allow administration of apm_bios, serial and bttv (TV) device</li> <li> Allow manufacturer commands in isdn CAPI support driver</li> <li> Allow reading non-standardized portions of pci configuration space</li> <li> Allow DDI debug ioctl on sbpcd driver</li> <li> Allow setting up serial ports</li> <li> Allow sending raw qic-117 commands</li> <li> Allow enabling/disabling tagged queuing on SCSI controllers and sending arbitrary SCSI commands</li> <li> Allow setting encryption key on loopback filesystem </li></ul> couldn't that be displayed as <li>foo</li> <li>bar</li> <li>and</li> <li>so</li> <li>on</li> Would be far easier to read (and as long as it doesn't have a special new-line tag it shouldn't change anything in the result for the end user). Also some very long texts could be splittet in several smaller texts, it's exhausting to even find the change, it would increase translation quality and translation efficency. -- 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 404663] New: DHCP does not update DNS when configured to do so in Yast on x86_64
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=404663 Summary: DHCP does not update DNS when configured to do so in Yast on x86_64 Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: drankinatty(a)suddenlinkmail.com QAContact: qa(a)suse.de Found By: --- Devs, 11.0 doesn't update dns when using either dhcpcd or dhclient. This occurs over both wired (dhcpcd) and wireless (dhclient) connections. Yast is configured with "[x] Update DNS data via DHCP", just as it aways is by default. Both wired and wireless connect fine and receive address, gateway, wins and dns info just fine. The problem is that the client does not update DNS with its hostname to allow it to be found on the network. Example: 11.0 x86_64 laptop connecting wirelessly. Jun 25 22:08:46 acrp205d rcnetwork: Starting the NetworkManager Jun 25 22:08:50 acrp205d kernel: r8169: eth0: link down Jun 25 22:08:50 acrp205d kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jun 25 22:08:52 acrp205d avahi-daemon[2350]: Registering new address record for fe80::21b:9eff:fea9:382d on ath0.*. Jun 25 22:09:01 acrp205d kernel: ath0: no IPv6 routers present Jun 25 22:15:33 acrp205d dhclient: Internet Systems Consortium DHCP Client V3.0.6 Jun 25 22:15:33 acrp205d dhclient: Copyright 2004-2007 Internet Systems Consortium. Jun 25 22:15:33 acrp205d dhclient: All rights reserved. Jun 25 22:15:33 acrp205d dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Jun 25 22:15:33 acrp205d dhclient: Jun 25 22:15:33 acrp205d dhclient: wifi0: unknown hardware address type 801 Jun 25 22:15:33 acrp205d dhclient: wifi0: unknown hardware address type 801 Jun 25 22:15:33 acrp205d dhclient: Listening on LPF/ath0/00:1b:9e:a9:38:2d Jun 25 22:15:33 acrp205d dhclient: Sending on LPF/ath0/00:1b:9e:a9:38:2d Jun 25 22:15:33 acrp205d dhclient: Sending on Socket/fallback Jun 25 22:15:33 acrp205d dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 Jun 25 22:15:34 acrp205d dhclient: DHCPOFFER from 192.168.6.17 Jun 25 22:15:38 acrp205d dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67 Jun 25 22:15:38 acrp205d dhclient: DHCPACK from 192.168.6.17 Jun 25 22:15:38 acrp205d avahi-daemon[2350]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.6.135 . Jun 25 22:15:38 acrp205d avahi-daemon[2350]: New relevant interface ath0.IPv4 for mDNS. Jun 25 22:15:38 acrp205d avahi-daemon[2350]: Registering new address record for 192.168.6.135 on ath0.IPv4. Jun 25 22:15:38 acrp205d dhclient: bound to 192.168.6.135 -- renewal in 1408 seconds. Jun 25 22:15:39 acrp205d nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. Jun 25 22:15:39 acrp205d SuSEfirewall2: SuSEfirewall2 not active Jun 25 22:15:39 acrp205d nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_global_hooks' exited wit h error status 1. Jun 25 22:15:39 acrp205d nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2. After connect, the server DNS (bind 9.4.1 openSuSE 10.3 x86_64) is not updated with the client information. All other machines (10.3, xp, and god forbid vista) all work OK. Here is the DNS zone after connect by "acrp205d": $ORIGIN . $TTL 172800 ; 2 days 3111skyline.com IN SOA nirvana.3111skyline.com. root.nirvana.3111skyline.com. ( 2008030946 ; serial 86400 ; refresh (1 day) 7200 ; retry (2 hours) 3600000 ; expire (5 weeks 6 days 16 hours) 172800 ; minimum (2 days) ) NS nirvana.3111skyline.com. NS nemesis.3111skyline.com. MX 10 nirvana.3111skyline.com. MX 20 nemesis.3111skyline.com. $ORIGIN 3111skyline.com. $TTL 10800 ; 3 hours alchemy A 192.168.6.102 $TTL 172800 ; 2 days ftp CNAME nirvana gw A 192.168.6.13 $TTL 14400 ; 4 hours kidsdell A 192.168.6.150 TXT "31187155d49801422fdafba6e674914fe6" $TTL 172800 ; 2 days lakehouse A 192.168.6.20 localhost A 127.0.0.1 mail CNAME nirvana nemesis A 192.168.6.16 nirvana A 192.168.6.17 $TTL 10800 ; 3 hours Rankin-P35a A 192.168.6.101 $TTL 86400 ; 1 day ripper A 192.168.6.149 TXT "313c41f262462bc25dedc4fa3bb99bc318" $TTL 172800 ; 2 days trinity A 192.168.6.18 www CNAME nirvana zion A 192.168.6.19 Reverse zone is likewise not updated. This may apply equally to 11.0 i386 as well, but I haven't tested. Let me know what else I can send you and I'll be happy to do so. Not knowing more, it looks like a problem with "nm-dispatcher." -- 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 19

[Bug 388228] New: Regression: sigset didn't return expected value
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=388228 Summary: Regression: sigset didn't return expected value Product: openSUSE 11.0 Version: Beta 1 Platform: All OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: yxu(a)novell.com QAContact: kernel-maintainers(a)forge.provo.novell.com Found By: --- LTP testcase sigset_8_1 fail under openSUSE 11.0 Beta1 kernel(also fail under openSUSE 10.3 kernel), pass under SLES10,SLES10SP1,SLES10SP2 kernel. Very simple testcase. Will be attached. -- 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 10

[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 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 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