August 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 382344] default to /usr/local/lib64 for self-compiled stuff
by bugzilla_noreply＠novell.com 03 Aug '11

03 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=382344 https://bugzilla.novell.com/show_bug.cgi?id=382344#c13 --- Comment #13 from Stephan Kulow <coolo(a)novell.com> 2011-08-03 09:35:31 CEST --- Stansislav could easily create a new one - recommended by make. Or we put this into make package. -- 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 0

[Bug 382344] default to /usr/local/lib64 for self-compiled stuff
by bugzilla_noreply＠novell.com 03 Aug '11

03 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=382344 https://bugzilla.novell.com/show_bug.cgi?id=382344#c12 --- Comment #12 from Ludwig Nussel <lnussel(a)novell.com> 2011-08-03 09:31:39 CEST --- Indeed. I suppose we don't really have some central devel package that would be a good place though. -- 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 0

[Bug 709945] New: security:apparmor:factory: Bug
by bugzilla_noreply＠novell.com 03 Aug '11

03 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=709945 https://bugzilla.novell.com/show_bug.cgi?id=709945#c0 Summary: security:apparmor:factory: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: jeffm(a)novell.com ReportedBy: avm-xandry(a)yandex.ru QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Please accept patches for package apparmor-profiles. Main bugreport and new profiles with patches on https://bugzilla.novell.com/show_bug.cgi?GoAheadAndLogIn=1&id=643387 -- 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 669797] New: KOTD: 2.6.38-rc2 kernel oops with NFSv3
by bugzilla_noreply＠novell.com 03 Aug '11

03 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=669797 https://bugzilla.novell.com/show_bug.cgi?id=669797#c0 Summary: KOTD: 2.6.38-rc2 kernel oops with NFSv3 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 I got this when moving some files from ext4 to NFS. Feb 6 07:37:08 frank kernel: [113242.846441] ------------[ cut here ]------------ Feb 6 07:37:08 frank kernel: [113242.846541] kernel BUG at /usr/src/packages/BUILD/kernel-desktop-2.6.38/linux-2.6.37/fs/nfs/nfs3xdr.c:1338! Feb 6 07:37:08 frank kernel: [113242.846702] invalid opcode: 0000 [#1] PREEMPT SMP Feb 6 07:37:08 frank kernel: [113242.846794] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map Feb 6 07:37:08 frank kernel: [113242.846922] CPU 1 Feb 6 07:37:08 frank kernel: [113242.846959] Modules linked in: via_velocity crc_ccitt atl1 nls_iso8859_1 nls_cp437 vfat fat fuse af_packet autofs4 cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 mperf snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd nfs lockd fscache nfs_acl auth_rpcgss sunrpc tcp_htcp loop snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore sr_mod cdrom edac_core floppy edac_mce_amd asus_atk0110 sg sp5100_tco snd_page_alloc k8temp pcspkr i2c_piix4 processor thermal_sys button ext4 jbd2 crc16 linear radeon ttm drm_kms_helper ata_generic drm pata_atiixp i2c_algo_bit dm_snapshot dm_mod [last unloaded: crc_ccitt] Feb 6 07:37:08 frank kernel: [113242.847203] Feb 6 07:37:08 frank kernel: [113242.847203] Pid: 31426, comm: mv Not tainted 2.6.38-rc2-1-desktop #1 M3A/System Product Name Feb 6 07:37:08 frank kernel: [113242.847203] RIP: 0010:[<ffffffffa0441ae7>] [<ffffffffa0441ae7>] nfs3_xdr_enc_setacl3args+0xb7/0xc0 [nfs] Feb 6 07:37:08 frank kernel: [113242.847203] RSP: 0018:ffff880086e39a78 EFLAGS: 00010282 Feb 6 07:37:08 frank kernel: [113242.847203] RAX: 00000000ffffffea RBX: ffff880086e39c08 RCX: 0000000000000004 Feb 6 07:37:08 frank kernel: [113242.847203] RDX: 0000000000000000 RSI: ffff880086e39958 RDI: ffff8800b7dea5a8 Feb 6 07:37:08 frank kernel: [113242.847203] RBP: ffff880086e39aa8 R08: 0000000000000001 R09: 0000000000000000 Feb 6 07:37:08 frank kernel: [113242.847203] R10: 0000000000000004 R11: 00000000000003e8 R12: 0000000000000080 Feb 6 07:37:08 frank kernel: [113242.847203] R13: ffffffffa0441a30 R14: ffff8800b64f4380 R15: ffff88006ff156c0 Feb 6 07:37:08 frank kernel: [113242.847203] FS: 00007f515a8ad7a0(0000) GS:ffff8800bfc40000(0000) knlGS:0000000000000000 Feb 6 07:37:08 frank kernel: [113242.847203] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Feb 6 07:37:08 frank kernel: [113242.847203] CR2: 00007f515a2aeac0 CR3: 00000000b60d5000 CR4: 00000000000006e0 Feb 6 07:37:08 frank kernel: [113242.847203] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Feb 6 07:37:08 frank kernel: [113242.847203] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Feb 6 07:37:08 frank kernel: [113242.847203] Process mv (pid: 31426, threadinfo ffff880086e38000, task ffff880086256180) Feb 6 07:37:08 frank kernel: [113242.847203] Stack: Feb 6 07:37:08 frank kernel: [113242.847203] ffff880086e39aa8 ffff8800b7dea5a0 ffff880043456064 ffffffffa03d5e6a Feb 6 07:37:08 frank kernel: [113242.847203] ffff8800bff9c700 ffff880086e39c08 ffff880043456088 ffff8800b7dea5a8 Feb 6 07:37:08 frank kernel: [113242.847203] ffff8800434561d8 ffff8800b7dea5a8 ffff8800b64f4380 ffff880043456028 Feb 6 07:37:08 frank kernel: [113242.847203] Call Trace: Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03d5e6a>] ? rpcauth_wrap_req+0xaa/0xe0 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03d6377>] ? unx_marshal+0x57/0xd0 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03cbe12>] ? rpc_xdr_encode+0xb2/0x110 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03cbfb8>] ? call_transmit+0x68/0x120 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03d41d0>] ? __rpc_execute+0x70/0x220 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03cd660>] ? rpc_run_task+0xf0/0x140 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa03cd7aa>] ? rpc_call_sync+0x3a/0x60 [sunrpc] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa042fc3a>] ? nfs_alloc_fattr+0x1a/0x60 [nfs] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa04438f0>] ? nfs3_proc_setacls+0x190/0x360 [nfs] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa04442f8>] ? nfs3_proc_setacl+0x68/0x120 [nfs] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff811a7a8a>] ? posix_acl_from_xattr+0x6a/0x130 Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa0444481>] ? nfs3_setxattr+0x61/0xd0 [nfs] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa0444420>] ? nfs3_setxattr+0x0/0xd0 [nfs] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff81176f7e>] ? __vfs_setxattr_noperm+0x4e/0x1b0 Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff811771a4>] ? vfs_setxattr+0xc4/0xd0 Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff81177261>] ? setxattr+0xb1/0x120 Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff8151f8e8>] ? do_page_fault+0x2d8/0x550 Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff811801b1>] ? utimes_common+0xe1/0x1d0 Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffffa01e8eef>] ? ext4_xattr_list+0x7f/0x270 [ext4] Feb 6 07:37:08 frank kernel: [113242.847203] [<ffffffff81177522>] ? sys_fsetxattr+0xd2/0xf0 Feb 6 07:37:08 frank kernel: [113242.855019] [<ffffffff81002ed2>] ? system_call_fastpath+0x16/0x1b Feb 6 07:37:08 frank kernel: [113242.855019] Code: 1f 44 00 00 48 8b 4b 18 eb d0 66 2e 0f 1f 84 00 00 00 00 00 48 8b 4b 20 48 8b 73 30 31 d2 48 89 ef e8 4e cc f9 ff e9 7a ff ff ff <0f> 0b 0f 0b 0f 1f 44 00 00 48 83 ec 18 48 89 5c 24 08 48 89 f3 Feb 6 07:37:08 frank kernel: [113242.855019] RIP [<ffffffffa0441ae7>] nfs3_xdr_enc_setacl3args+0xb7/0xc0 [nfs] Feb 6 07:37:08 frank kernel: [113242.855019] RSP <ffff880086e39a78> Feb 6 07:37:08 frank kernel: [113242.883219] ---[ end trace 7a020017e81dde71 ]--- Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. -- 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 638745] New: really poor flush performance on unmount
by bugzilla_noreply＠novell.com 03 Aug '11

03 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=638745 https://bugzilla.novell.com/show_bug.cgi?id=638745#c0 Summary: really poor flush performance on unmount Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 I have a system where, periodically, filesystems undergo a bunch of mounting, copying, and then unmounting. I noticed a change with openSUSE 11.3, and it was not for the better. I believe I've narrowed down a test case: 1. format a new filesystem (xfs, ext4, btrfs, etc...) 2. copy a bunch of stuff (not large files, preferably) to the filesystem (cp, rsync, cpio, whatever) (even a few 10's of MB should be sufficient, but I don't know for sure) 3. *don't issue sync* 4. umount the filesystem 5. watch I/O grind to a halt and the cached buffers take a _very_ long time to get to disk. Expecting to see flush I/O in the neighborhood of 30-60 MB/s, I saw mere hundred's of KB per second. Repeat again, but this time in step 3 issue a sync. I don't recall seeing the horrible flush-on-umount performance with openSUSE 11.2 When I first encountered this, I thought the system was hung. The disk light was steadily lit, but the umount call went on for minutes and minutes. Please note that I haven't had 100% success in replicating this, but more often than not, the test works. I *am* using LVM, but I've seen the behavior where the LVM is on a software raid device and where it is on raw disk and also where it is on a luks-formatted encrypted volume. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 618867] New: atombios stuck in loop while booting with KMS enabled
by bugzilla_noreply＠novell.com 02 Aug '11

02 Aug '11

http://bugzilla.novell.com/show_bug.cgi?id=618867 http://bugzilla.novell.com/show_bug.cgi?id=618867#c0 Summary: atombios stuck in loop while booting with KMS enabled Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jeffm(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- Created an attachment (id=372987) --> (http://bugzilla.novell.com/attachment.cgi?id=372987) dmesg While booting a freshly installed 11.3 RC1 system with the following graphics hardware, I end up with black screens and the displays are in low power mode. ATI Technologies Inc M56GL [Mobility FireGL V5250] If I boot with radeon.modeset=0, the problem clears up. The issue occurs with both the radeon driver and the radeonhd driver. It also occurs with the current 11.3 Factory kernel as well as the 2.6.35-rc3 master kernel. Nothing in libdrm versions newer than 2.4.20 looks relevant. I'll attach hwinfo, dmesg, and Xorg.0.log from the system while booted in KMS mode. -- Configure bugmail: http://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 538795] 11.2 M7 - resume from hibernation problem w/ root on reiserfs
by bugzilla_noreply＠novell.com 02 Aug '11

02 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=538795 https://bugzilla.novell.com/show_bug.cgi?id=538795#c32 Jeff Mahoney <jeffm(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel AssignedTo|jeffm(a)novell.com |kernel-maintainers(a)forge.pr | |ovo.novell.com Product|openSUSE 11.2 |openSUSE 12.1 --- Comment #32 from Jeff Mahoney <jeffm(a)novell.com> 2011-08-02 23:42:51 UTC --- Rafael, does this issue still exist in Factory? I'd assume yes. -- 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 0

[Bug 660373] New: Apparmour Offers little if no Functionality - Its Logic is Unclear and Help pages are of Little User Value
by bugzilla_noreply＠novell.com 02 Aug '11

02 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=660373 https://bugzilla.novell.com/show_bug.cgi?id=660373#c0 Summary: Apparmour Offers little if no Functionality - Its Logic is Unclear and Help pages are of Little User Value Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: AppArmor AssignedTo: jeffm(a)novell.com ReportedBy: scott(a)aphofis.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=405476) --> (http://bugzilla.novell.com/attachment.cgi?id=405476) PROGRESSIVE IMAGES User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 Apparmour found back in 10.3, was at best unclear and offered the user no real way of receiving email alerts - Now, with the addition of the 'Update Profile Wizard' everything about Apparmour has changed dramatically and I still cannot test that Apparmour actually performs some type of function despite it having new functions within Yast and given new Apparmour GUI Tools. The way a user needs to start to use Apparmour is confusing at best and there is not much Logic in having a Control Panel in Apparmours many GUIs I'll demonstrate in both the text procedure as well as images below - Reproducible: Always Steps to Reproduce: 1.To be able to set a notification email address and other important functions, we need to start with the Update Profile Wizard First and Foremost. After opening the Wizard the user needs to create a user login as well as initiate a Repository. 2.The wizard is a bit confusing as we need to start by registering the user details. Within this procedure, a user password details are required in 2 different panels. The newly registered user has a unique user name and some how user login details are created and a repository added from who knows where! 3.Once you have a user login you can now go back to the control panel and enter the email address you chose when you registered as a New User. The capacity to enable alerts via a local host email address and locally held 'system type' notification; will be accepted, but an external email address will be accepted in the notification fields, once a user has created a user login and 'added a repository'?? I think the concept of creating a user login is suppose to enable the downloading of profiles that Novell or other have created and want to share?? I could continue to type text after text after text with little value as I have provided images. The worst thing about the Apparmour Profile Wizard is, once you have register a user login and offered all the reliant details and finished; The very same Wizard offer not 1 piece of functionality - Its just dumps the user after clicking on the Wizard GUI. My Opinion would be to totally scrap ALL Apparmour GUIs and put some logic and functionality back. I would also rewrite the ALL GUI Help texts and to provide Apparmour Profiles that I think are suppose to be downloaded and shared to everyone. As it stands all Apparmour GIs should be classified as 'ALPHA' and far far away from even BETA -- 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 33

[Bug 668515] New: xdg-screensaver: it depends on KDE3stuff (dcop, specifically) but doesn't RPM require it
by bugzilla_noreply＠novell.com 02 Aug '11

02 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=668515 https://bugzilla.novell.com/show_bug.cgi?id=668515#c0 Summary: xdg-screensaver: it depends on KDE3stuff (dcop, specifically) but doesn't RPM require it Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 You can easily see this here: [~] xdg-screensaver status /usr/bin/xdg-screensaver: line 569: dcop: command not found ERROR: kdesktop KScreensaverIface isEnabled returned '' [~] It should probably be modified to use qdbus which comes wit libqt4: qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock and qdbus org.freedesktop.ScreenSaver /ScreenSaver GetActive and qdbus org.freedesktop.ScreenSaver /ScreenSaver Inhibit firefox because 11489 and qdbus org.freedesktop.ScreenSaver /ScreenSaver UnInhibit 11489 and so on. NOTE: this is /probably/ a problem for openSUSE 11.4 as well. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 701659] New: AutoFS: stat -L triggering mounts
by bugzilla_noreply＠novell.com 02 Aug '11

02 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=701659 https://bugzilla.novell.com/show_bug.cgi?id=701659#c0 Summary: AutoFS: stat -L triggering mounts Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: SuSE Other Status: ASSIGNED Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: lchiquitto(a)novell.com ReportedBy: lchiquitto(a)novell.com QAContact: qa(a)suse.de CC: pth(a)novell.com, mszeredi(a)novell.com Found By: Community User Blocker: --- Opening bug to track the inclusion of patches in openSUSE Factory. Problem originally reported upstream at: http://linux.kernel.org/pipermail/autofs/2011-March/006540.html Copying here for reference: After the update to 2.6.38, I noticed that AutoFS started to mount volumes at times it normally wouldn't. More specifically, "ls -la" inside an AutoFS mount point will trigger the mount of all available maps. This can be reproduced with a simple indirect mount setup: # cat /etc/auto.master /data /etc/auto.data # cat /etc/auto.data isos -fstype=nfs4,ro,rsize=8192,wsize=8192,intr,nolock,nosuid libre:/isos # egrep '(autofs|nfs4)' /proc/mounts /etc/auto.data /data autofs rw,relatime,fd=7,pgrp=4300,timeout=600,\ minproto=5,maxproto=5,indirect 0 0 # stat -L /data/isos > /dev/null # egrep '(autofs|nfs4)' /proc/mounts /etc/auto.data /data autofs rw,relatime,fd=7,pgrp=4300,timeout=600,\ minproto=5,maxproto=5,indirect 0 0 libre:/isos /data/isos nfs4 ro,nosuid,relatime,vers=4,(.. more mount\ options ..) 0 0 Bisecting the changes between 2.6.37 and 2.6.38, I found that 2.6.38-rc1 exhibits the new behavior already. I went as near 2.6.37 as I could and verified that commit b650c858c2 (autofs4: Merge the remaining dentry ops tables) also shows the new behavior. I tried to bisect the remaining ~18 commits but everything I tested/built ended up unbootable. I also tested mainline and verified that the problem is still there. According to David Howells in [1], the problem will be fixed upstream by patching acl and coreutils. [1] http://linux.kernel.org/pipermail/autofs/2011-April/006548.html -- 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