August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 902067] New: Yast2 Live Installer has no icon in Gnome
by bugzilla_noreply＠novell.com 28 Aug '17

28 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902067 Bug ID: 902067 Summary: Yast2 Live Installer has no icon in Gnome Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: sjharms(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The Yast2 Live Installer shows no icon when using Gnome 3 Live CD install -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 909730] New: YaST modules have no application icon shown
by bugzilla_noreply＠novell.com 27 Aug '17

27 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=909730 Bug ID: 909730 Summary: YaST modules have no application icon shown Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: i(a)marguerite.su QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi, Currently YaST control center itself has an application icon set by setWindowIcon(QIcon), but separate YaST modules still use X icon. But in our codebase I did see such implementation eg: https://github.com/yast/yast-yast2/blob/master/library/desktop/src/modules/… Maybe I was wrong, but it would be better if common modules such as sw_single can have their own application icon (yast-sw-single) instead of X icon. Marguerite -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 730327] New: vusb-analyzer needs 'gnomecanvas'
by bugzilla_noreply＠novell.com 27 Aug '17

27 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=730327 https://bugzilla.novell.com/show_bug.cgi?id=730327#c0 Summary: vusb-analyzer needs 'gnomecanvas' Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: afaerber(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- On openSUSE 12.1 RC2, `vusb-analyzer` resulted in: Traceback (most recent call last): File "/usr/bin/vusb-analyzer", line 13, in <module> from VUsbTools import Views, Log, Diff, Decode File "/usr/lib/python2.7/site-packages/VUsbTools/Views.py", line 15, in <module> from VUsbTools import Types, Style File "/usr/lib/python2.7/site-packages/VUsbTools/Types.py", line 20, in <module> except gnomecanvas: NameError: name 'gnomecanvas' is not defined Installing python-gnome package resolved this. A suitable Depends: should be added to the vusb-analyzer 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 3

[Bug 935557] New: WARNING: CPU: 1 PID: 330 at ../fs/btrfs/qgroup.c:1414 btrfs_delayed_qgroup_accounting
by bugzilla_noreply＠novell.com 25 Aug '17

25 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=935557 Bug ID: 935557 Summary: WARNING: CPU: 1 PID: 330 at ../fs/btrfs/qgroup.c:1414 btrfs_delayed_qgroup_accounting Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: mfasheh(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dsterba(a)suse.com Found By: --- Blocker: --- On current TW. following seems to be occuring when quotas are enabled and snapper is used (and deleting snapshots). [320344.131801] ------------[ cut here ]------------ [320344.131865] WARNING: CPU: 1 PID: 330 at ../fs/btrfs/qgroup.c:1414 btrfs_delayed_qgroup_accounting+0x543/0xe40 [btrfs]() [320344.131869] Modules linked in: fuse tun sit tunnel4 ip_tunnel iscsi_ibft iscsi_boot_sysfs bluetooth af_packet msr cpufreq_stats w83627ehf hwmon_vid nls_iso8859_1 nls_cp437 vfat fat iTCO_wdt iTCO_vendor_support ppdev dm_mod arc4 rt2800pci rt2800mmio rt2800lib rt2x00pci rt2x00mmio rt2x00lib cuname -r 4.0.5-1-default oretemp mac80211 serio_raw pcspkr snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel i2c_i801 snd_hda_controller cfg80211 lpc_ich mfd_core eeprom_93cx6 crc_ccitt rfkill snd_hda_codec snd_hwdep shpchp snd_pcm snd_timer snd parport_pc tpm_infineon 8250_fintek parport tpm_tis soundcore tpm acpi_cpufreq button processor btrfs xor raid6_pq sr_mod cdrom ehci_pci uhci_hcd ehci_hcd e1000e ptp pps_core usbcore usb_common video sg efivarfs [320344.131947] CPU: 1 PID: 330 Comm: btrfs-cleaner Not tainted 4.0.5-1-default #1 [320344.131951] Hardware name: /D2500CC, BIOS CCCDT10N.86A.0040.2014.0520.1400 05/20/2014 [320344.131954] 0000000000000000 ffffffffa0251d91 ffffffff81629bec 0000000000000000 [320344.131961] ffffffff81062f21 ffff880129fec000 ffff88008263ca40 ffff880006c6d240 [320344.131966] ffff8800ce0099c8 0000000000000000 ffffffffa0235a23 ffff8800369f3cdc [320344.131972] Call Trace: [320344.131995] [<ffffffff81005635>] dump_trace+0x85/0x330 [320344.132005] [<ffffffff81005973>] show_stack_log_lvl+0x93/0x170 [320344.132014] [<ffffffff81007031>] show_stack+0x21/0x50 [320344.132024] [<ffffffff81629bec>] dump_stack+0x40/0x50 [320344.132035] [<ffffffff81062f21>] warn_slowpath_common+0x81/0xb0 [320344.132076] [<ffffffffa0235a23>] btrfs_delayed_qgroup_accounting+0x543/0xe40 [btrfs] [320344.132114] [<ffffffffa01c0957>] btrfs_run_delayed_refs.part.66+0x207/0x280 [btrfs] [320344.132150] [<ffffffffa01d08e1>] btrfs_should_end_transaction+0x41/0x70 [btrfs] [320344.132183] [<ffffffffa01beed8>] btrfs_drop_snapshot+0x458/0x860 [btrfs] [320344.132219] [<ffffffffa01d0d9c>] btrfs_clean_one_deleted_snapshot+0xac/0x100 [btrfs] [320344.132251] [<ffffffffa01c9e9c>] cleaner_kthread+0x12c/0x190 [btrfs] [320344.132263] [<ffffffff8107fce1>] kthread+0xc1/0xe0 [320344.132272] [<ffffffff8162ff98>] ret_from_fork+0x58/0x90 [320344.132280] ---[ end trace 9bacbb5026d14829 ]--- uname -r 4.0.5-1-default -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 936378] New: Yast needs to be clevered about configuring NTP after installation
by bugzilla_noreply＠novell.com 24 Aug '17

24 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=936378 Bug ID: 936378 Summary: Yast needs to be clevered about configuring NTP after installation Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The Server minimal pattern has been changed to no longer include 'ntp'. Yast does not like this too much, as it unconditionally tries to configure the NTP services, then failing for ntp.service to be missing. See https://openqa.opensuse.org/tests/69401/modules/livecdreboot/steps/14 Yast should be smarter in detecting if this service needs to be configured (only if it was installed). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 941882] New: LIRC version is really old (too old to even be supported)
by bugzilla_noreply＠novell.com 20 Aug '17

20 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=941882 Bug ID: 941882 Summary: LIRC version is really old (too old to even be supported) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: DaAwesomeP(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The LIRC version in OpenSUSE 13.2 is really, really old. The latest version is 0.9.3. The latest version also does things like automatically configure the kernel, which 0.9.0 does not do. I noticed this when I seemed o have gotten some sort of bug (or maybe just a misconfiguration) as discussed here: https://sourceforge.net/p/lirc/tickets/120/ Another problem is that it's missing the irman module, which requires libirman, but that would require a new libirman package, so I'll report that in Factory. Discussion about that here: https://forums.opensuse.org/showthread.php/508988-LIRC-missing-irman-driver -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 927681] New: USB media not accessible
by bugzilla_noreply＠novell.com 18 Aug '17

18 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=927681 Bug ID: 927681 Summary: USB media not accessible Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 Assignee: anixx(a)opensuse.org Reporter: dexter.filmore(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- attaching a usb drive it is not accessible, "unable to mount /dev/<drive>, Reason: not authorized to perform operation" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 939657] New: Apper bug after finishing updates: Failed to cache rpm database (1).
by bugzilla_noreply＠novell.com 18 Aug '17

18 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=939657 Bug ID: 939657 Summary: Apper bug after finishing updates: Failed to cache rpm database (1). Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jura.som(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After finishing updated with Apper an error occurs. It says: Failed to cache rpm database (1). "An internal system error has occurred - Apper A problem that we were not expecting has occurred. Please report this bug with the error description. Details Failed to cache rpm database (1)." The updates seem to finish normally. This error occurs always after automatic updating. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 789020] New: no more /dev/disk/by-label/LABEL symlinks for LVM devices (udev/systemd?)
by bugzilla_noreply＠novell.com 18 Aug '17

18 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=789020 https://bugzilla.novell.com/show_bug.cgi?id=789020#c0 Summary: no more /dev/disk/by-label/LABEL symlinks for LVM devices (udev/systemd?) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de Found By: Third Party Developer/Partner Blocker: --- After updating to today's FACTORY (last update was before openSUSE conf), my /space and /local partitions were no longer mounted: susi:~ # grep LABEL /etc/fstab LABEL=root-FACTORY / ext4 acl,user_xattr 1 1 # LABEL=local /local xfs noatime,logbufs=8,logbsize=262144 1 2 # LABEL=space /space xfs noatime,logbufs=8,logbsize=262144 1 2 (now commented out to get the system to boot) susi:~ # l /dev/disk/by-label/ total 0 drwxr-xr-x 2 root root 140 Nov 9 15:50 ./ drwxr-xr-x 6 root root 120 Nov 9 15:50 ../ lrwxrwxrwx 1 root root 10 Nov 9 15:50 BOOTLOADER -> ../../sda3 lrwxrwxrwx 1 root root 10 Nov 9 15:50 SYSTEM_DRV -> ../../sda1 lrwxrwxrwx 1 root root 10 Nov 9 15:50 Windows7_OS -> ../../sda2 lrwxrwxrwx 1 root root 10 Nov 9 15:50 root-FACTORY -> ../../sda6 lrwxrwxrwx 1 root root 10 Nov 9 15:50 root-stable -> ../../sda8 susi:~ # blkid /dev/sda1: LABEL="SYSTEM_DRV" UUID="7A0615220614E0C5" TYPE="ntfs" /dev/sda2: LABEL="Windows7_OS" UUID="64A42A12A429E6F0" TYPE="ntfs" /dev/sda3: LABEL="BOOTLOADER" UUID="519614e1-7c40-4866-b461-3ad4cb797538" SEC_TYPE="ext2" TYPE="ext3" /dev/sda5: UUID="fde71608-8ca9-4f2a-9a3e-501df23f8469" TYPE="swap" /dev/sda6: LABEL="root-FACTORY" UUID="71f5bfb4-3d29-4c9c-929a-3fb795cf0fd9" TYPE="ext4" /dev/sda7: UUID="3387ae99-507c-41eb-80c8-ee7b4a62353a" TYPE="crypto_LUKS" /dev/sda8: LABEL="root-stable" UUID="6983d635-99c0-48e9-b62a-74cd3b27c636" TYPE="ext4" /dev/sda9: UUID="jRlUY0-8mt0-09TE-MeAf-IqRj-TSzl-tK83Uk" TYPE="LVM2_member" /dev/mapper/main-local: LABEL="local" UUID="ac293f98-8e30-440f-8845-d067ee49d42d" TYPE="xfs" /dev/mapper/main-space: LABEL="space" UUID="17676f0d-fe6e-4b47-80bb-6d6493574569" TYPE="xfs" /dev/mapper/main-vdr: UUID="4b5b5706-84bb-4a2c-8f91-fda2784aea86" TYPE="ext4" /dev/mapper/cr_sda7: LABEL="cryptohome" UUID="98741ffb-5913-43ca-afac-500ff16d0f57" TYPE="ext3" susi:~ # blkid|grep LABEL= /dev/sda1: LABEL="SYSTEM_DRV" UUID="7A0615220614E0C5" TYPE="ntfs" /dev/sda2: LABEL="Windows7_OS" UUID="64A42A12A429E6F0" TYPE="ntfs" /dev/sda3: LABEL="BOOTLOADER" UUID="519614e1-7c40-4866-b461-3ad4cb797538" SEC_TYPE="ext2" TYPE="ext3" /dev/sda6: LABEL="root-FACTORY" UUID="71f5bfb4-3d29-4c9c-929a-3fb795cf0fd9" TYPE="ext4" /dev/sda8: LABEL="root-stable" UUID="6983d635-99c0-48e9-b62a-74cd3b27c636" TYPE="ext4" /dev/mapper/main-local: LABEL="local" UUID="ac293f98-8e30-440f-8845-d067ee49d42d" TYPE="xfs" /dev/mapper/main-space: LABEL="space" UUID="17676f0d-fe6e-4b47-80bb-6d6493574569" TYPE="xfs" /dev/mapper/cr_sda7: LABEL="cryptohome" UUID="98741ffb-5913-43ca-afac-500ff16d0f57" TYPE="ext3" As you can see, the non-LVM devices are there in /dev/disk/by-label, but the LVM devices are not. I guess this is a glitch of the new udev version. -- 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 12

[Bug 904987] New: Dracut not working as expected with full-disk encryption
by bugzilla_noreply＠novell.com 18 Aug '17

18 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Bug ID: 904987 Summary: Dracut not working as expected with full-disk encryption Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: fedev(a)gmx.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 613252 --> http://bugzilla.opensuse.org/attachment.cgi?id=613252&action=edit Screenshot - emergency console after upgrade Hi there, My laptop has full disk encryption with luks. It was working without problems until openSUSE 13.2. It seems dracut checks for encrypted partitions and volumes on crypttab however I did not have the partition listed in crypttab because all this time the luks partition information was added by grub (if not mistaken). Well, dracut seems can't recognize an unlocked luks partition/volume on its own nor from the previous used settings. Dracut was then trying to look for the volumes for home and root without trying to unlock first for the encrypted partition. There are two workarounds for this. One, use the kernel boot parameter rd.luks.uuid the other, add the disk to crypttab and then re-run dracut -M --force This however it is not obvious for those doing an upgrade. After doing an upgrade from 13.1 to 13.2, the system is no longer bootable unless you take care of the above first. Thank you. Regards, Fede -- You are receiving this mail because: You are on the CC list for the bug.

1 42