November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 725062] New: zypper ignores download.max_download_speed property
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725062 https://bugzilla.novell.com/show_bug.cgi?id=725062#c0 Summary: zypper ignores download.max_download_speed property Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: pavel(a)argo-tours.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 It downloads packages on the full maximum available speed instead of limiting speed to the proper /etc/zypp/zypp.conf parameter Reproducible: Always Steps to Reproduce: 1. Add the parameter download.max_download_speed to the file /etc/zypp/zypp.conf. Set it to 100000 (assuming you have internet connection faster then 100 KBytes/s) 2. Start some update (I've used zypper -n update -l) Actual Results: I see in my KDE network monitor, that download is being processed at the full (in my case 200-300 KBytes/s) speed. Expected Results: Download should proceed with the limited (100 KBytes/s) speed -- 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 725872] New: zypper: reduce duplicated messages
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725872 https://bugzilla.novell.com/show_bug.cgi?id=725872#c0 Summary: zypper: reduce duplicated messages Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Printing the "No package matching 'xxx*'" multiple times is redundant, it would suffice if it did this once, or completely omit it, since there is not going to be a package called "lib*". # zypper up --no-r 'lib*' 'bundle*' Loading repository data... Reading installed packages... No package matching 'bundle*' are installed. [message repeated 69 more times...] No package matching 'lib*' are installed. [message repeated 409 more times...] [...] Resolving package dependencies... [...] -- 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 668593] New: windows:mingw:win32/mingw32-pdcurses: Bug
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=668593 https://bugzilla.novell.com/show_bug.cgi?id=668593#c0 Summary: windows:mingw:win32/mingw32-pdcurses: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Windows Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: fstrba(a)novell.com ReportedBy: roger(a)opq.se QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: tlillqvist(a)novell.com, fridrich.strba(a)bluewin.ch, abharath(a)novell.com Found By: Community User Blocker: No PD Curses, like it's ncurses counterpart, supports wide characters and UTF-8. However, these versions of the library are not contained in the build. It would be really useful if they were also built. -- 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 637215] New: Yast will not start from Gnome System menu
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=637215 https://bugzilla.novell.com/show_bug.cgi?id=637215#c0 Summary: Yast will not start from Gnome System menu Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: support(a)microtechniques.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=387641) --> (http://bugzilla.novell.com/attachment.cgi?id=387641) console messages User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729) Although Yast is listed on the Gnome System menu, it will not start when selected. It will start when called as yast2 from a text-mode command line. There are several errors in the logs which are attached. Reproducible: Always Steps to Reproduce: 1.startx 2.Select Computer 3.Select YaST from System menu Actual Results: Absolutely nothing Expected Results: Yast system startup -- 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 25

[Bug 541674] New: mkinitrd: include-all-libata-drivers not always working
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=541674 Summary: mkinitrd: include-all-libata-drivers not always working Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de CC: hare(a)novell.com Found By: Beta-Customer This is about commit 87d86855cf54ff125ab6e059ddc4a66987e1b533 in mkinitrd. First of all I noticed that the commit message mentions "This default is improper as it increases the bootup time for machines that have multiple controllers". However, the code (still) causes all libata modules to be pulled in. So if I have multiple ATA controllers, it would be increasing the bootup time. Second, in recent versions of the kernel, CONFIG_ATA may have been changed from =m to =y[1], so that the test for "-L /sys/module/libata/holders/$procname" in setup-block.sh does not fire anymore, because holders will not be tracked when a piece of code is =y. [1] http://lists.opensuse.org/opensuse-kernel/2009-09/msg00001.html -- 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 4

[Bug 679092] New: kernel-desktop debuginfo missing - unable to debug kernel crash
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=679092 https://bugzilla.novell.com/show_bug.cgi?id=679092#c0 Summary: kernel-desktop debuginfo missing - unable to debug kernel crash Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical 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; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 My openSUSE 11.4 install (kernel-desktop) oopses (almost) every time I unplug my USB audio headset. I made a kernel crash, but 'crash' claims that the debuginfo can't be found: worklaptop:/var/crash # crash 2011-03-11-19\:29/System.map-2.6.37.1-1.2-desktop 2011-03-11-19\:29/vmlinux-2.6.37.1-1.2-desktop 2011-03-11-19\:29/vmcore .. crash: 2011-03-11-19:29/vmlinux-2.6.37.1-1.2-desktop: no debugging data available worklaptop:/var/crash # rpm -qa | grep kernel-desktop kernel-desktop-2.6.37.1-1.2.2.x86_64 kernel-desktop-devel-2.6.37.1-1.2.2.x86_64 kernel-desktop-devel-debuginfo-2.6.37.1-1.2.2.x86_64 kernel-desktop-debuginfo-2.6.37.1-1.2.2.x86_64 kernel-desktop-base-2.6.37.1-1.2.2.x86_64 kernel-desktop-base-debuginfo-2.6.37.1-1.2.2.x86_64 worklaptop:/var/crash # What's more, boot.kdump is *not* in /etc/init.d/boot.d and trying to enable it results in this: worklaptop:/var/crash # chkconfig --add boot.kdump insserv: FATAL: service network is missed in the runlevels 4 to use service SuSEfirewall2_setup insserv: exiting now! /sbin/insserv failed, exit code 1 boot.kdump 0:off 1:off 2:off 3:off 4:off 5:off 6:off worklaptop:/var/crash # finally, 'openSUSE 11.4' is missing from the Operating System dropdown in bugzilla. 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 14

[Bug 732904] New: Cannot boot: "bind failed: Address already in use" and "error binding udev control socket"
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=732904 https://bugzilla.novell.com/show_bug.cgi?id=732904#c0 Summary: Cannot boot: "bind failed: Address already in use" and "error binding udev control socket" Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cymerio(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=464198) --> (http://bugzilla.novell.com/attachment.cgi?id=464198) dmesg output User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Sometimes when booting the system it stops at the recovery console prompt. When inspecting the last errors you see 4 or 5 messages like this: bind failed: Address already in use error binding udev control socket The workaround is to log in with the root password and write "exit" afterwards. The system continues booting normally. Reproducible: Sometimes Steps to Reproduce: 1. Boot the system normally (with systemd) Actual Results: The booting process is taking longer than usual. Then the nice splash logo is gone and you are in text mode and the system is asking you the root password to log in the recovery console. Expected Results: The system should boot without issues, like it normally does. Maybe related to bug #728315 ? But this one doesn't happen always, only sometimes. -- 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 656536] New: booting on some sw-RAID setups does not assemble root device in initrd
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=656536 https://bugzilla.novell.com/show_bug.cgi?id=656536#c0 Summary: booting on some sw-RAID setups does not assemble root device in initrd Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: bwiedemann(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- my automated testing scripts for openSUSE can setup and boot software RAID which works for LiveCD installs such as http://www3.zq1.de/opensuse/video/openSUSE-KDE-LiveCD-x86_64-Build0681-RAID… and http://openqa.opensuse.org/opensuse/video/openSUSE-KDE-LiveCD-x86_64-Build0… but failed for 11.3-DVD and current Factory DVD/NET installs in http://openqa.opensuse.org/opensuse/video/openSUSE-DVD-x86_64-Build0909-RAI… at 01:11 you can see the intended RAID setup with / being /dev/md0 with /dev/vd[abcd]2 as underlying block-devices but at 02:14 you can see that in initrd only a /dev/md0 is assembled from /dev/vd[abcd]3 which then can not be used to boot the system, because it is the swap. -- 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 15

[Bug 702360] New: some symbols are only in kernel-*base
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=702360 https://bugzilla.novell.com/show_bug.cgi?id=702360#c0 Summary: some symbols are only in kernel-*base Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: mmarek(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- I blocked -base and -devel from LiveCDs, normally kernel-default should be enough, but some symbols are not provided by it. preload-kmp-default-1.2_k2.6.39.0_2-11.7.i586 requires ksym(default:yield) = 760a0f4f, but this requirement cannot be provided >!> uninstallable providers: kernel-default-base-2.6.39-2.3.i586[tmp] kernel-default-devel-2.6.39-2.3.i586[tmp] -- 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 732881] New: XFS module not built into initrd at install
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=732881 https://bugzilla.novell.com/show_bug.cgi?id=732881#c0 Summary: XFS module not built into initrd at install Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: suse-20050616(a)bgcomp.co.uk QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en-GB) Presto/2.9.168 Version/11.52 I upgraded from 11.4 to 12.1. All file systems are running as mirrored XFS. When initrd is recreated during upgrade, XFS is not added to the kernel module list meaning that when the system is rebooted it is unable to mount any disks including root. Provided there is an old kernel to boot from, adding xfs to INITRD_MODULES list in the file /etc/sysconfig/kernel and then rebuild the default kernel will correct the problem. Reproducible: Always Steps to Reproduce: 1. Upgrade 2. Reboot Expected Results: Boot into system -- 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 624654] New: mkinitrd should not use sysfs for module names
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=624654 http://bugzilla.novell.com/show_bug.cgi?id=624654#c0 Summary: mkinitrd should not use sysfs for module names Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: msvec(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- In case the currently running kernel differs a lot from the one which is installed (for example a case of distro upgrade), mkinitrd might not get the module names correct as sysfs contains the old info. It should only use modalias and look up the names somewhere in the new (installed) kernel. -- 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 2

[Bug 556953] New: can not boot with / on RAID10
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=556953 http://bugzilla.novell.com/show_bug.cgi?id=556953#c0 Summary: can not boot with / on RAID10 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: novellbmw(a)lsmod.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.23) Gecko/20090912 SUSE/1.1.18-1.2 SeaMonkey/1.1.18 Because of https://features.opensuse.org/305343 it is now possible to install openSUSE on RAID6 and RAID10, but a system with / on RAID10 will not boot after installation. Reproducible: Always Steps to Reproduce: 1. boot openSUSE-11.2-DVD-i586.iso 2. create 4 partitions with type FD=Linux RAID autodetect (2 partitions might suffice) 3. create RAID10 mounted on root (/) partition 4. use a non-raid or RAID1 for /boot 5. finish install Actual Results: on first boot, system stops in initrd: http://www.zq1.de/bernhard/temp/raid10-boot-fail.png Expected Results: should boot up as an equivalent RAID6 setup does Probable cause is that raid10.ko is missing from initrd. -- 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 5

[Bug 598077] New: mkinitrd: domain search list not used
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=598077 http://bugzilla.novell.com/show_bug.cgi?id=598077#c0 Summary: mkinitrd: domain search list not used Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- When boot-network.sh runs from an initramfs, /etc/resolv.conf is only populated with nameservers, but not the domain search list. This however, would be very welcome. -- 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 4

[Bug 642235] New: multiple copies/versions of /lib/firmware/2.6.34-*/radeon in initrd
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=642235 https://bugzilla.novell.com/show_bug.cgi?id=642235#c0 Summary: multiple copies/versions of /lib/firmware/2.6.34-*/radeon in initrd 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: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- Blocker: --- running mkinitrd-2.6.0-2.3.x86_64 on my xen dom0 server after the 1st kernel update generates an initrd with all available copies of /lib/firmware/2.6.34*/radeon/ : $ zcat /boot/initrd-2.6.34.7-0.3-default | cpio -itv | grep R100_cp.bin -rw-r--r-- 1 root2 root 2048 Jun 29 20:05 lib/firmware/2.6.34-12-xen/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Sep 16 01:14 lib/firmware/2.6.34.7-0.2-default/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Sep 21 01:56 lib/firmware/2.6.34.7-0.3-xen/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Jul 6 17:37 lib/firmware/2.6.34.1-0.0.6.82d7a13-xen/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Sep 21 01:45 lib/firmware/2.6.34.7-0.3-default/radeon/R100_cp.bin 54780 blocks $ zcat /boot/initrd-2.6.34.7-0.3-default | cpio -it | grep /radeon/ | sed 's,[^/]*$,,' | uniq -c 54780 blocks 2 lib/firmware/radeon/ 27 lib/firmware/2.6.34-12-xen/radeon/ 27 lib/firmware/2.6.34.7-0.2-default/radeon/ 27 lib/firmware/2.6.34.7-0.3-xen/radeon/ 27 lib/firmware/2.6.34.1-0.0.6.82d7a13-xen/radeon/ 27 lib/firmware/2.6.34.7-0.3-default/radeon/ 1 lib/modules/2.6.34.7-0.3-default/kernel/drivers/gpu/drm/radeon/ reason for the multiple kernel versions is this $ grep ^multiversion /etc/zypp/zypp.conf multiversion = provides:multiversion(kernel) but in initrd-2.6.34.7-0.3-default there should be only /lib/firmware/2.6.34.7-0.3-default/* , isn't it?! $ rpm -qf /sbin/mkinitrd mkinitrd-2.6.0-2.3.x86_64 -- 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 7

[Bug 623268] New: LVM support was lost for booting of updated system.
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=623268 http://bugzilla.novell.com/show_bug.cgi?id=623268#c0 Summary: LVM support was lost for booting of updated system. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- I updated a couple of software components from current packages on Friday. Yesterday I was surprised that all Linux kernels I could select from the GRUB menu could not find the root file system which is contained in a logical volume. I reactivated an old kernel with the corresponding initial RAM disk to get a working openSUSE back. I am curious which update "dropped" the LVM2 support to boot as expected from /dev/mapper/system-root"". Which ways would be recommended to repair the contents of the other RAM disks? -- 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 18

[Bug 723406] New: encrypted /var is not accessed by initrd
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=723406 https://bugzilla.novell.com/show_bug.cgi?id=723406#c0 Summary: encrypted /var is not accessed by initrd Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: yoshi314(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I've installed opensuse 11.4 on a following layout root is on ssd. it's a GPT partition layout /var is on hdd, as a lvm volume which is inside of encrypted PV. 11.4 installer opens encrypted device and discovers lvm volumes. Setup goes without issues. Generated initrd does not include luks support (i've filed a bug about that), and after rebuilding with mkinitrd -A fails to open the luks device - it claims that aes-cbc-essiv is not supported by kernel, even though the installer kernel had no issues opening it. I've tried updating to tumbleweed kernel. Regenerated the initrd (mkinitrd -A as before). Hit similar issue as before. Either mkinitrd -A does not include crypto modules, or there is something wrong with stock kernel configuration. Using a dracut generated initrd from custom built vanilla kernel works with this installation. Reproducible: Always Steps to Reproduce: 1. Install system in aforementioned partition setup 2. Rebuild initrd 3. enter luks password at boot, no lvm volumes are found 4. manual attempts to use luksOpen from recovery shell fail due to errors suggesting lacking crypto features 5. Try again with tumbleweed kernel and -A generated kernel 6. no lvm volumes are found; will check for more info booted with parameters luks=box luks_box=/dev/sda1 Actual Results: system waits for /var lvm volume and times out. eventual recovery shell or botched boot. Expected Results: normal system boot luks volume info : LUKS header information for /dev/sda1 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec: sha1 Payload offset: 4096 (....) -- 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 727352] New: df displays wrong device names
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=727352 https://bugzilla.novell.com/show_bug.cgi?id=727352#c0 Summary: df displays wrong device names Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rhg(a)marxmeier.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23 This is a server system using a MD/LVM layout. MD is RAID1: /dev/md0 -> /boot (EXT2) /dev/md1 -> swap /dev/md2 -> LVM Logical volumes: /dev/vg00/root -> / /dev/vg00/usr -> /usr /dev/vg00/opt -> /opt /dev/vg00/var -> /var Below is the df -h output. Note the /dev/dm-2 device name, should be: /dev/mapper/vg00-usr # df -h Filesystem Size Used Avail Use% Mounted on rootfs 1014M 192M 823M 19% / devtmpfs 2,0G 44K 2,0G 1% /dev tmpfs 2,0G 0 2,0G 0% /dev/shm tmpfs 2,0G 288K 2,0G 1% /run /dev/mapper/vg00-root 1014M 192M 823M 19% / /dev/dm-2 3,0G 1,4G 1,6G 47% /usr tmpfs 2,0G 0 2,0G 0% /sys/fs/cgroup tmpfs 2,0G 0 2,0G 0% /media /dev/mapper/vg00-opt 1014M 33M 982M 4% /opt /dev/mapper/vg00-var 2,0G 103M 1,9G 6% /var tmpfs 2,0G 288K 2,0G 1% /var/lock tmpfs 2,0G 288K 2,0G 1% /var/run /dev/md0 250M 27M 211M 12% /boot 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 8

[Bug 618442] New: Minimal X install comes up in twm rather than IceWM Lite
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=618442 http://bugzilla.novell.com/show_bug.cgi?id=618442#c0 Summary: Minimal X install comes up in twm rather than IceWM Lite Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: znmeb(a)borasky-research.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 I installed a VirtualBox guest from the i586 openSUSE 11.3 RC1 DVD. For desktop I selected "Minimal X". I was expecting it to come up in IceWM. I checked the packages to be installed before the install and "IceWM Lite" was indeed installed. But when I logged in after the install, the system came up in "twm", not "IceWM". I'm still searching the web for how to configure the system so it comes up in IceWM, but I was assuming that it would come up that way automatically - that's the way an appliance built with SUSE Studio with the "Minimal X" pattern works. This isn't by any stretch of the imagination a show-stopper, but it would be nice if a minimal X install came up in IceWM. Reproducible: Always Steps to Reproduce: 1. Install a system with the "Minimal X" desktop option 2. Boot it up 3. Log in Actual Results: System came up in "twm" Expected Results: It should have come up in IceWM -- 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 3

[Bug 725684] New: booting with pxe and root on nfs fails due to no dhcp interface found
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725684 https://bugzilla.novell.com/show_bug.cgi?id=725684#c0 Summary: booting with pxe and root on nfs fails due to no dhcp interface found Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)opensuse.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 I'm booting a Factory system over PXE and with root on NFS. This stops very quickly with the following: running dhcpcd on interface err, no interface specified I've investigated it a bit further, and determined that the variable 'dhcp_macaddresses' is not set when run_all.sh is called. It therefore ends up defaulting to a MAC-address of the system where the initrd was built which means boot/12-network.sh cannot identify the interface, hence "err, no interface specified" It is quite possible that this is a direct effect of bug#724775, but for the moment there is no obvious connection. 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 9

[Bug 724775] New: initramfs and ifup-sysctl
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=724775 https://bugzilla.novell.com/show_bug.cgi?id=724775#c0 Summary: initramfs and ifup-sysctl Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aj(a)suse.com QAContact: qa(a)suse.de CC: mmarek(a)suse.com, fcrozat(a)suse.com Found By: Product Management Blocker: --- Created an attachment (id=457191) --> (http://bugzilla.novell.com/attachment.cgi?id=457191) screenshot of initial boot with error message I was able to catch the appended screenshot: udevd[202]: failed to execute /etc/sysconfig/network/scripts/ifup-sysctl... This is done from initial ramdisk. This is with current openSUSE factory as of 2011-10-18 under kvm (but noticed the same problem on real 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 35

[Bug 536470] New: mkintrd cp_bin does not create directories
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=536470 Summary: mkintrd cp_bin does not create directories Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mvancura(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de CC: hare(a)novell.com, mmarek(a)novell.com Found By: --- scripts/setup-progs.sh uses cp_bin to copy dependent programs of initrd scripts to the image. It does not create directories though so programs in 'unusual' locations such as /lib/cryptsetup/scripts are not copied. -- 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 4

[Bug 672172] New: initrd can not mount nfsroot
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=672172 https://bugzilla.novell.com/show_bug.cgi?id=672172#c0 Summary: initrd can not mount nfsroot Classification: openSUSE Product: openSUSE 11.4 Version: RC 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ohering(a)novell.com QAContact: jsrain(a)novell.com Found By: Outsourced Testing Blocker: --- Created an attachment (id=414201) --> (http://bugzilla.novell.com/attachment.cgi?id=414201) nfsroot.initrd.txt to workaround bug #672118 I did an installation of 11.4rc1 to nfsroot. All went fine until the initrd tried to mount the nfsroot. Appearently some protocol is not supported, but its not clear which one it is. The mount -v output from inst-sys vs. initrd looks identical to me. .. preping 82-resume.kernel.sh running 82-resume.kernel.sh preping 83-mount.sh running 83-mount.sh device node not found Mounting root 192.168.2.100:/opt/cross/sys-root/oss/11.4/rc1 mount -o rw,nolock -t nfs 192.168.2.100:/opt/cross/sys-root/oss/11.4/rc1 /root mount.nfs: timeout set for Tue Feb 15 17:54:18 2011 mount.nfs: trying text-based options 'nolock,vers=4,addr=192.168.2.100,clientaddr=192.168.2.81' [ 25.760586] eth0: no IPv6 routers present mount.nfs: mount(2): No such file or directory mount.nfs: trying text-based options 'nolock,addr=192.168.2.100' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.2.100 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.2.100 prog 100005 vers 3 prot UDP port 47022 mount.nfs: Protocol not supported could not mount root filesystem -- exiting to /bin/sh sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell $ cat /proc/modules nfs 361495 0 - Live 0xffffffffa028f000 lockd 82143 1 nfs, Live 0xffffffffa0278000 fscache 55451 1 nfs, Live 0xffffffffa0268000 nfs_acl 3107 1 nfs, Live 0xffffffffa000d000 auth_rpcgss 49071 1 nfs, Live 0xffffffffa025a000 sunrpc 250613 6 nfs,lockd,nfs_acl,auth_rpcgss, Live 0xffffffffa0205000 af_packet 23463 0 - Live 0xffffffffa0075000 radeon 983145 1 - Live 0xffffffffa00f4000 ttm 74341 1 radeon, Live 0xffffffffa00d6000 drm_kms_helper 36694 1 radeon, Live 0xffffffffa00cb000 e1000e 208062 0 - Live 0xffffffffa0089000 drm 232019 3 radeon,ttm,drm_kms_helper, Live 0xffffffffa003a000 i2c_algo_bit 6246 1 radeon, Live 0xffffffffa0033000 fan 3215 0 - Live 0xffffffffa002d000 processor 39701 0 - Live 0xffffffffa001b000 thermal 14914 0 - Live 0xffffffffa0011000 thermal_sys 17462 3 fan,processor,thermal, Live 0xffffffffa0006000 ata_generic 3995 0 - Live 0xffffffffa0000000 $ -- 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 719360] New: gmixer 1.3 misses the options tab so it is not possible to set channel and input source
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=719360 https://bugzilla.novell.com/show_bug.cgi?id=719360#c0 Summary: gmixer 1.3 misses the options tab so it is not possible to set channel and input source Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: mpapis(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 gmixer 1.3 misses the options tab so it is not possible to set channel and input source Reproducible: Always Steps to Reproduce: 1. open gmixer 2. go to edit->preferences 3. unselect all except channell/input source (those are options on my laptop), alternatively try selecting every single track - and some are just not visible. I was able to see the channel/input source using alsamixer and xfce4-mixer Actual Results: it is not possible to change channel and input source options Expected Results: it should be possible to change options (terminology from xfce4-panel) because of that I was not able to set my external microphone to work, and internal has really poor quality, I found it only because I was heaving same microphone problems earlier with KDE ... solved then with the switches - but could not set it now with gmixer (default volume control in XFCE) -- 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 11

[Bug 686831] New: /sbin/conf.d/SuSEconfig.glib2 fails when .desktop files contain () in their filenames
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=686831 https://bugzilla.novell.com/show_bug.cgi?id=686831#c0 Summary: /sbin/conf.d/SuSEconfig.glib2 fails when .desktop files contain () in their filenames Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: holger.lehmann(a)catworkx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.16) Gecko/20110319 SUSE/3.6.16-0.2.1 Firefox/3.6.16 ZarafaCheck/1.1.1.20080624.110 When SuSEconfig -module glib2 is called an one has the ianywhere (Sybase) installed it fails to register the following files correctly: /usr/share/applications/ianywhere-11-Network Server (32-bit)-GNOME.desktop /usr/share/applications/ianywhere-11-Network Server (32-bit)-KDE.desktop /usr/share/applications/ianywhere-11-Network Server (64-bit)-GNOME.desktop /usr/share/applications/ianywhere-11-Network Server (64-bit)-KDE.desktop /usr/share/applications/ianywhere-11-Personal Server (32-bit)-GNOME.desktop /usr/share/applications/ianywhere-11-Personal Server (32-bit)-KDE.desktop /usr/share/applications/ianywhere-11-Personal Server (64-bit)-GNOME.desktop /usr/share/applications/ianywhere-11-Personal Server (64-bit)-KDE.desktop Giving these errors: /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(32_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(32_Mbit)_MKDE_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(64_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(64_Mbit)_MKDE_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(32_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(32_Mbit)_MKDE_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(64_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(64_Mbit)_MKDE_Ddesktop' I would suggest changing the lines: eval "if test \"\$DEFDESKTOP_$DESKTOPS\" ; then IS_DEFAULT_DESKTOP=true DEFTYPE=\$DEFDESKTOP_$DESKTOPS fi" into some code that looks a bit like this: cat > /tmp/eval-file.$$ <<EOF if test '$DEFDESKTOP_$DESKTOPS# ; then IS_DEFAULT_DESKTOP=true DEFTYPE='\$DEFDESKTOP_$DESKTOPS' fi EOF /tmp/eval-file.$$ rm /tmp/eval-file.$$ this should do the trick (code is untestet :-) ) Regards, Holger Reproducible: Always Steps to Reproduce: 1. Install Sybase SQL Anywhere Client, any other application that creates () in the desktop links will do 2. run SuSEconfig -module glib2 Actual Results: /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(32_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(32_Mbit)_MKDE_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(64_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MNetwork_SServer_S(64_Mbit)_MKDE_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(32_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(32_Mbit)_MKDE_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(64_Mbit)_MGNOME_Ddesktop' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: syntax error near unexpected token `(' /sbin/conf.d/SuSEconfig.glib2: eval: line 81: ` DEFTYPE=$DEFDESKTOP_ianywhere_M11_MPersonal_SServer_S(64_Mbit)_MKDE_Ddesktop' Expected Results: No error messages -- 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 598116] New: PackageKit zypp-backend log rotates too fast
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=598116 http://bugzilla.novell.com/show_bug.cgi?id=598116#c0 Summary: PackageKit zypp-backend log rotates too fast Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ma(a)novell.com QAContact: qa(a)suse.de Found By: Community User Blocker: --- See https://bugzilla.novell.com/show_bug.cgi?id=581089#c3 Maybe the zypp-backend can be changed to keep more then one old log, or consider to use logrotate. -- 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 4

[Bug 692441] New: gnome-power-manager causes backlight flicker on MSI PR200 and other laptops
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=692441 https://bugzilla.novell.com/show_bug.cgi?id=692441#c0 Summary: gnome-power-manager causes backlight flicker on MSI PR200 and other laptops Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jmatejek(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- when changing brightness (regardless of whether by keyboard or from some GUI control), the backlight will flicker wildly between the proposed and lowest setting. This also happens on gnome startup, because g-p-m is trying to set brightness to a predefined level and this also triggers the problem. The flicker usually stops after a second or two, but occassionally it goes on for more than five seconds. During that, the system doesn't seem to process keyboard events. Killing gnome-power-manager solves the problem. Redefining XF86MonBrightnessUp and XF86MonBrightnessDown events to no-ops (via xkb or xmodmap) and restarting g-p-m also fixes the problem. The backlight then can be changed through keyboard. (A minor drawback of both solutions is that g-p-m doesn't know about the brightness events and therefore doesn't display its brightness GUI. I can live with that, as opposed to killing my backlight ;) ) this is apparently fallout from a kernel change in 11.4 - i didn't try this, but reportedly downgrading the kernel solves the issue. Other distros (Ubuntu Natty, Fedora 15, Arch) have the same problem. Interestingly, OpenSUSE's behavior is slightly different, and best of the three: the flicker settles really quickly, whereas on the other distros it often continues for more than 15 seconds. here is a bugreport from ubuntu about the issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/756509 a related issue might be bug 498018 investigating with evtest discovers that every change to brightness triggers a keyboard "Brightness up" (or Down) event, even in cases where the change was made in software (e.g. echo 5 > /sys/class/backlight/acpi_video0/brightness). This leads me to believe that the problem is a race between g-p-m and kernel about changing the brightness level, and the underlying bug might be in the kernel. (i assigned this to gnome, though, because without g-p-m the problem doesn't exist) the severity is Major, because this behavior could in theory cause damage to the backlight -- 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 728105] New: Gnome: can not change system language
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728105 https://bugzilla.novell.com/show_bug.cgi?id=728105#c0 Summary: Gnome: can not change system language Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: puzel(a)suse.com QAContact: qa(a)suse.de Found By: L3 Blocker: --- After live migration from 11.4 to 12.1 RC1, it does not seem to be possible to change the language settings in GNOME. Currently, the selected language is English. If I go to 'Region and Language settings' dialog, the 'English' entry is highlighted. (There's also British English, Chinese (simplified), Spanish'. I want to add 'Czech' -> click on the '+' button, select 'Czech'. It is now present and highlighted. So far so good. After opening the 'Region and Language settings' dialog again, the 'Czech' entry disappeared and 'English' is highlighted again. Obviously nothing changed in the interface, not even after logout/login. bundle-lang-gnome-cs is installed: $ rpm -q bundle-lang-gnome-cs bundle-lang-gnome-cs-12.1-41.5.1.noarch -- 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 729343] New: mini_commander_applet doesn't display in panel - 12.1RC2 on VMplayer.
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=729343 https://bugzilla.novell.com/show_bug.cgi?id=729343#c0 Summary: mini_commander_applet doesn't display in panel - 12.1RC2 on VMplayer. Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: VMWare OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- mini_commander_applet doesn't display in panel - 12.1RC2 on VMplayer. Host: 11.4 Guest: 12.1 RC2 Environ: VMWare player. Running gnome fallback desktop. I add the minicomander applet to the top panel, but it does not display. Using ps afx | grep commander I can find that it is running. It is not Bug 695113 Ii classify as major because this application doesn't work, not because it would be a major distribution fault. -- 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 730627] New: gnome panel calendar not showing all evolution calendars
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=730627 https://bugzilla.novell.com/show_bug.cgi?id=730627#c0 Summary: gnome panel calendar not showing all evolution calendars Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: 64bit OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: brainstormtrooper(a)free.fr QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I have a couple of google calendars and a yahoo calendar in evolution. non-default google calendars show up in the panel sometimes, but events from the yahoo calendar don't show up in the calendar applet of gnome3. Reproducible: Always Steps to Reproduce: 1.click on the calendar applet... 2. 3. Actual Results: google and local events show up Expected Results: all evolution calendar events show up in 11.4 with gnome3 I had the opposite problem, google calendars would display in the applet but not in evolution and yahoo calendars worked in both... -- 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 707377] New: Selecting "Other" at login screen triggers failure
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=707377 https://bugzilla.novell.com/show_bug.cgi?id=707377#c0 Summary: Selecting "Other" at login screen triggers failure Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- XFCE appears to use gdm, thus this may alos be a problem with GNOME installs. When selecting "Other" in the login screen no "Username" and "Password" fields are displayed. The display is stuck at "Other", thus it is not possible to log in as a configured user either unless the system is restarted. To reproduce: 1.) Install M3 selecting XFCE as the desktop 2.) Configure a user during install 3.) When install is complete and the login screen is displayed select "Other" Behavior observed on Dell mini 10 -- 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 7

[Bug 728646] New: GNOME Shell crashed with fglrx driver (GNOME 3.2 / openSUSE 12.1 RC2 / AMD Catalyst Beta 11.11)
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728646 https://bugzilla.novell.com/show_bug.cgi?id=728646#c0 Summary: GNOME Shell crashed with fglrx driver (GNOME 3.2 / openSUSE 12.1 RC2 / AMD Catalyst Beta 11.11) Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: freespacer(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Ubuntu/10.04 Chromium/15.0.874.106 Chrome/15.0.874.106 Safari/535.2 Hi, I test the beta of AMD Catalyst 11.11 (fglrx) with GNOME 3.2 (openSUSE 12.1 RC2). I am the officially packaging script maintainer for AMD installer and beta tester. I am in constant contact with AMD. AMD (and me) have tested this driver with GNOME 3.2 and openSUSE 12.1 RC1. It works. But now with openSUSE 12.1 RC2, it does not work anymore and that is really annoying. The gnome shell crashed immediately after booting. AMD assumed that a regression patch was trigger the error. The GNOME maintainer should check this. # gnome-shell --sync --replace (gnome-shell:2383): Gdk-WARNING **: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadRenderRequest'. (Details: serial 181 error_code 153 request_code 137 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) There is no further information in /var/log/Xorg.0.log. I try to debug this with gdb. But I get also no information. That is really crazy. How we can fix this in GNOME 3.2 (openSUSE 12.1 RC2) asap? Reproducible: Always Steps to Reproduce: 1. Install openSUSE 12.1 RC2 with GNOME 3.2 2. Install fglrx driver 3. Reboot the computer Actual Results: GNOME Shell crashed Expected Results: GNOME Shell should run -- 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 28

[Bug 731451] New: After update, touchpad don't works
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=731451 https://bugzilla.novell.com/show_bug.cgi?id=731451#c0 Summary: After update, touchpad don't works Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: rauhmaru(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I updated my notebook cp -rfv /etc/zypp/repos.d /etc/zypp/repos.d.old sed -i 's/11.4/12.1/g' /etc/zypp/repos.d/* zypper ref && zypper dup But, after the update, my touchpad don't works. Reproducible: Always Steps to Reproduce: 1. sed -i 's/11.4/12.1/g' /etc/zypp/repos.d/* 2. zypper ref && zypper dup 3. And touchpad fails Actual Results: Touchpad don't work Expected Results: Touchpad works -- 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 730135] New: at boot time the wallpaper is a distorted picture, instaed of normal Wallpaper
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=730135 https://bugzilla.novell.com/show_bug.cgi?id=730135#c0 Summary: at boot time the wallpaper is a distorted picture, instaed of normal Wallpaper Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: pierre.5933(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1 at boot time the wallpaper is a distorted picture. This image comes in part from a previous assignment with an operating system. This O S may be the one which I use in routine work, for exemple suse 11.4 annd a windows of libre office , Chrome or someting else! I am obliged to go to systemsetting >>>Background>>>>walpaper and select my wall paper Some times it is a distorded picture and I cannot recognize from where it is comming I used the same swap for all my Operating systems Reproducible: Sometimes Steps to Reproduce: 1.stop en OS 2.restart 3.the first wall paper is generaly a strange picture Expected Results: to get immediatly the correct wall paper -- 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 728530] New: Wi-Fi Drops Out Periodically in openSUSE 12.1 RC 2 (Gnome)
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728530 https://bugzilla.novell.com/show_bug.cgi?id=728530#c0 Summary: Wi-Fi Drops Out Periodically in openSUSE 12.1 RC 2 (Gnome) Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: PC OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: matty.fong(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 After a while of general use, wi-fi seems to stop transferring data between computer and router. Thought it could have been an ISP issue but even access to the router's IP was cut off. Connectivity seems to resolve itself but then cuts out again. Turning off the computer's wi-fi and turning it on again seems to resolve it also temporarily. Reproducible: Didn't try Steps to Reproduce: 1.Just seems to happen randomly 2.In fact, it just happened as I tried to submit this 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 13

[Bug 731559] New: metacity login makes controlls unusable - trap with autologin and access to last session
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=731559 https://bugzilla.novell.com/show_bug.cgi?id=731559#c0 Summary: metacity login makes controlls unusable - trap with autologin and access to last session Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I know that Mutter is the actual windowmanager for GNOME, but I have the option on login screen to access metacity. I´ve done this and it is a trap when you have autologin enabled. The login work, but in metacity I have no mouse no keyboard and also no access to shell. -> bad think. A newstart of the system bring me again to metacity(last desktop is accessed by default), because I had automatic login enabled(again without controlls=. It was necessary to start the system again and in shell mode to edit DISPLAYMANAGER_AUTOLOGON in etc/sysconfig to get the system back to another desktop(KDE with controls). Reproducible: Always Steps to Reproduce: 1.Install openSUSE12.1 with autologin 2.switch from a kde session to a metacity session -> see that you have no keyboard or mouse 3.make a hard reboot of the system 4.see that you access metacity automatically(because of autologin and last session access) again without keyboard and mouse. Expected Results: What I expect is to bring metacity in a state in which you have mouse and keyboard or to dismiss the metacity option at the login screen. What it is in the moment is to dangerous. When you not know how to get out of the trap I described you a near by to make a new install or try with rescue. I was surprised to see metacity in the options of the login screen. I thought that metacity was the window manager of GNOME2 and not a stand alone thing. -- 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 728598] New: gnome-shell-extension-dock broken in factory and RC 2, SOLUTION/FIX!
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728598 https://bugzilla.novell.com/show_bug.cgi?id=728598#c0 Summary: gnome-shell-extension-dock broken in factory and RC 2, SOLUTION/FIX! Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: smartdumbguy22(a)yahoo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.106 Safari/535.2 package gnome-shell-extension-dock GNOME shell extension: Dock is broken in openSUSE:Factory & RC 1, RC 2,+. Shell Extension: Dock, Fails to load due to incompatibility with current GNOME Version. (Fails with any gnome-shell > 3.2.0) gnome-shell version = 3.2.1 SOLUTION/FIX: There is a typo in the file in /usr/share/gnome-shell/extensions/dock(a)gnome-shell.extensions.gnome.org/metadata.json - "shell-version": [ "3.2.0" ], + "shell-version": [ "3.2.0", "3.2" ], The above change adding "3.2", changes the metadata.json for the Dock extension to the same configuration as other working extensions. All other extensions are already configured this way. Reproducible: Always Steps to Reproduce: 1. zypper install gnome-shell-extension-dock 2. enable extension with "Advanced Settings" 3. Alt+F2 (in GNOME); lg [enter]; view Errors tab Actual Results: 1. zypper install gnome-shell-extension-dock 2. enable extension with "Advanced Settings" 3. Alt+F2 (in GNOME); lg [enter]; view Errors tab Extension fails to load due to incompatibility with current GNOME-Shell version. Expected Results: Extension should have loaded fine. SOLUTION/FIX: Correct version string in gnome-shell-extension-dock installed file /usr/share/gnome-shell/extensions/dock(a)gnome-shell.extensions.gnome.org/metadata.json - "shell-version": [ "3.2.0" ], + "shell-version": [ "3.2.0", "3.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.

1 18

[Bug 634578] New: Secure file permissions prevent shutdown due to overheating
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=634578 https://bugzilla.novell.com/show_bug.cgi?id=634578#c0 Summary: Secure file permissions prevent shutdown due to overheating Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: martin(a)etainable.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4) Gecko/20100817 SUSE/4.0b-13.1 Firefox/4.0b4 Changed file permissions from "easy" to "secure" on a Lenovo W500 laptop. This makes power management commands privileged. In gnome when you start it asks for root to enable drive power-down. Key issue is if you walk away and machine is running in high CPU state and can start to overheat. Machine will not shut down on a APCI temperature event as it is awaiting input. (I am working "why is it overheating" separately.) For system safety, system should be able to shut itself down to maintain integrity. Would like to know what to fix so system can shutdown for safety to resolve this. Reproducible: Always Steps to Reproduce: 1.enable secure file permissions 2.let "tracker" run for a few hours in a new gnome user (or any other behavior that causes system to stay in high CPU state in powertop) 3.system will get hot 4. Gnome dialog will state waiting on user input before shutting down... Actual Results: system gets hot and will wait until it fails before shutting down. Expected Results: Would like it to shutdown for safety. -- 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 623732] New: "Automatic Download Printer Driver" not works when plug the printers usb cable.
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=623732 http://bugzilla.novell.com/show_bug.cgi?id=623732#c0 Summary: "Automatic Download Printer Driver" not works when plug the printers usb cable. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: kota.seki(a)avasys.jp QAContact: jsmeix(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB6.5; NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E) * I reported same bug information at https://bugzilla.redhat.com/show_bug.cgi?id=616281 The system-config-printer supported "Automatic Download Printer Driver". (When Printer USB cable plugs to the PC, then printer driver is downloaded from internet and installed it) But when I try the above, printer driver was not downloaded. (I use GNOME desktop) Reproducible: Always Steps to Reproduce: 1. Edit the yum repository setting file. # vi /etc/yum.repos.d/lsb.repo [lsb-drivers] baseurl=http://linux.avasys.jp/drivers/lsb/Epson-inkjet/stable/RPMS enabled=1 gpgchecnk=1 2. Get and register the gpg key. # wget https://linux.avasys.jp/drivers/lsb/epson-inkjet/key/pubkey.asc # rpm --import pubkey.asc 3. Turn on the Printer and Plugs the Printer's USB cable to the PC. Actual Results: Printer Driver was not downloaded and installed. Expected Results: When printer is plugged, it should be download the driver. Then it will install. I tried to see system-config-printer's log. # system-config-printer --setup-printer='file:/tmp/printout' --devid='MFG:Epson;MDL:Stylus Photo TX800FW' --debug When I type this, then I found logs about "jockey". ... Asking Jockey to install drivers Got Jockey error: org.freedesktop.DBUS.Error.ServiceUnknown: The name com.ubuntu.DeviceDriver was not provided by any .service files ... -- 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 5

[Bug 661991] New: FreeBSD (0xA5) partitions appearing in nautilus and other applications open/save dialogs
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=661991 https://bugzilla.novell.com/show_bug.cgi?id=661991#c0 Summary: FreeBSD (0xA5) partitions appearing in nautilus and other applications open/save dialogs Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: hippolyte(a)shaw.ca 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 FreeBSD primary partitions are seen by udev as being from type "ufs" and usage "filesystem". As a consequence these partitions show up in nautilus filemanager and other applications' file dialogs under Linux. User defined udev rules intended to hide them either with ENV{ID_FS_TYPE}=="ufs",ENV{UDISKS_PRESENTATION_HIDE}="1" or ENV{UDISKS_PARTITION_TYPE}=="0xa5",ENV{UDISKS_PRESENTATION_HIDE}="1" have no effect. Neither does adding type 0xa5 to the list of partition types which desktops should not display in /lib/udev/rules.d/80-udisk.rules. Reproducible: Always Steps to Reproduce: start nautilus file browser or open/save file dialog of applications (such as the Gimp) under Gnome, Kde or Lxde on any sytem containing one or more FreeBSD primary partitions. Actual Results: The primary 0xA5 partition shows up as a filesystem. Expected Results: Since these partitons are containers for Unix slices and do not include a filesystem themselves, they are not mountables (just like the Linux extended partition) and should never appear anywhere in filemanagers or on the desktop or applications file dialogs. It doesn't occur while using XFCE or Icewn as window manager (!) It concerns all Linux distros with Gnome, KDE, LXDE. It can been easily solved by adding entries for FreeBSD partitions in /etc/fstab using the mountpoint "none" and the filesystem type "ignore". However this hack should not be necessary as such partitions should be ignored by default. -- 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 629961] New: no visual feedback of umount
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=629961 http://bugzilla.novell.com/show_bug.cgi?id=629961#c0 Summary: no visual feedback of umount Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- In openSUSE 11.2 there was a visual feedback of umount progress. If it tool more than about a second, a pop-up appeared that informed me about umounting progress. In openSUSE 11.3 this feedback disappeared. How to reproduce: 1. Attach an USB flash disc 2. Write thousands of files into a large directory. 3. Disconnect the medium in Nautilus Actual behavior: - Icon disappears and nothing indicated write in progress. - Write continues in next few minutes. (sync hangs and LED on the device flashes, if there is one) Expected behavior: - Visual feedback: "Writing data to the device." Marking the bug as Critical: It causes data losses and medium corruption for LED-less flash dongles and SD/CF cards. -- 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 1