August 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1004206] New: New warning after upgrade: PyGIWarning: GnomeKeyring was imported without specifying a version first.
by bugzilla_noreply＠novell.com 19 Sep '19

19 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1004206 Bug ID: 1004206 Summary: New warning after upgrade: PyGIWarning: GnomeKeyring was imported without specifying a version first. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from 42.1 to 42.2 Beta 3 the following warning started appearing upon osc (the Build Service tool) invocation: lpechacek@fm:~> osc --version /usr/lib/python2.7/site-packages/keyring/backends/Gnome.py:6: PyGIWarning: GnomeKeyring was imported without specifying a version first. Use gi.require_version('GnomeKeyring', '1.0') before import to ensure that the right version gets loaded. from gi.repository import GnomeKeyring 0.155.0 lpechacek@fm:~> rpm -q --qf '%{disturl}\n%{name}-%{version}-%{release}\n' osc python-keyring obs://build.opensuse.org/openSUSE:Leap:42.2/standard/17c0c9649a0e2fe80b648d… osc-0.155.0-1.1 obs://build.opensuse.org/openSUSE:Leap:42.2/standard/096dcefaeead038d4cc41d… python-keyring-5.3-3.1 The machine primary desktop environment is Gnome 3.20.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1051307] New: Canon LiDE30 Scanner not working (usb2.0 and 3.0 ports)
by bugzilla_noreply＠novell.com 18 Sep '19

18 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1051307 Bug ID: 1051307 Summary: Canon LiDE30 Scanner not working (usb2.0 and 3.0 ports) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: madworm_de.novell(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: Same hardware as in: ( https://bugzilla.opensuse.org/show_bug.cgi?id=1049019 ) Scanner: Bus 001 Device 008: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Symptoms: scanimage -L detects scanner, but does absolutely nothing otherwise. xsane doesn't see a scanning device. Yast configuration is "weird" (detects scanner, but doesn't appear to store anything. same thing next run). This feels awfully similar to a sane issue I've had with 13.2 on an Acer Laptop with USB3 ports ( https://bugzilla.opensuse.org/show_bug.cgi?id=920067 ) The scanner works OUT_OF_THE_BOX with: PartedMagic 2016_12_12 (devel) Kernel: 4.8.14-pmagic64 xsane: 0.999 sane-backend: 1.0.25 Approximate list of packages: https://partedmagic.com/parted-magic-2017-01-08/ The scanner issues keep haunting me :-( Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1021293] New: Canon LiDE20 USB scanner issues with Acer laptop [intel] + USB3.0 controller (xhci)
by bugzilla_noreply＠novell.com 18 Sep '19

18 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1021293 Bug ID: 1021293 Summary: Canon LiDE20 USB scanner issues with Acer laptop [intel] + USB3.0 controller (xhci) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: madworm_de.novell(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm having the very same issues with Leap 42.2 as previously with 13.2 https://bugzilla.opensuse.org/show_bug.cgi?id=920067 I thought the fixes previously added to the scanner software would've been integrated into Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1009129] New: plasma update notifier does not update after updates have been applied manually
by bugzilla_noreply＠novell.com 12 Sep '19

12 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1009129 Bug ID: 1009129 Summary: plasma update notifier does not update after updates have been applied manually Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 701148 --> http://bugzilla.opensuse.org/attachment.cgi?id=701148&action=edit screenshot showing that zypper dup has been called in terminal but the update notifier still shows updates. ## observation when the plasma update notification icon told there are updates available I called "zypper ref && zypper dup --no-allow-vendor-change" to manually and installed updates. after that the update notification icon stilled showed available updates even though there weren't any. The update notifier only updated after a long time (still showed after many minutes. Next time I checked after at least 24h it was not showing any updates anymore. ## expected result there shouldn't be any updates shown if zypper up / dup has been called. ## further details see attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1013573] New: "dracut: Could not find FONT_MAP none!" warning while rebuilding initrd
by bugzilla_noreply＠novell.com 10 Sep '19

10 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1013573 Bug ID: 1013573 Summary: "dracut: Could not find FONT_MAP none!" warning while rebuilding initrd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: develop7(a)develop7.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Repro: 1. Install openSUSE Tumbleweed (snapshot 20161123 in my case) 2. run /sbin/mkinitrd as root (or wait for update that triggers rebuilding initrd) 3. Watch dracut output Expected: no FONT_MAP-related warnings and related issues Instead: see summary The issue is created because current TW snapshot is affected as well Additional info: > $ cat /etc/vconsole.conf > KEYMAP=us -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1046966] New: Akregator looses feed list
by bugzilla_noreply＠novell.com 08 Sep '19

08 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1046966 Bug ID: 1046966 Summary: Akregator looses feed list Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- Since I installed the 20170613 tumbleweed snapshot, Akregator looses/breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown. Explicitely exiting Akregator (by pressing Ctrl-Q) seems to avoid the breakage. After restoring feeds.opml, Akregator can be started normally and shows all my feeds. This bug was confirmed by multiple users on opensuse-factory, both with Tumbleweed and with 42.2 + KDE:Frameworks5. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 939462] New: ibus-table input methods not working
by bugzilla_noreply＠novell.com 08 Sep '19

08 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=939462 Bug ID: 939462 Summary: ibus-table input methods not working Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cycharlie(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This problem exists since openSUSE 13.2, and it continues to exist in Tumbleweed and Leap. THw whole bunch of ibus-table-* input methods can be installed and added in iBus. However, when those input methods are selected, iBus failed to utilize them, iBus stays at the input method that is currently using, instead of changing into the one that I just selected. Similar problem had occured in openSUSE 13.1, which ibus-table input methods even couldn't be added to iBus (packages installed but iBus did not list them out). There was a solution for this situation, but this time that solution does not work for what happens in openSUSE 13.2/Tumbleweed/Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1007830] New: Network Manager dispatcher script kills NFS mount when any interface went down
by bugzilla_noreply＠novell.com 05 Sep '19

05 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1007830 Bug ID: 1007830 Summary: Network Manager dispatcher script kills NFS mount when any interface went down Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: prapor(a)unixzone.org.ua QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /etc/NetworkManager/dispatcher.d/nfs does not recognizes if interface, managed by NetworkManager is VPN or any, and runs umount for NFS shares which should not be changed. How to reproduce: 1. Mount NFS from any storage in LAN, within your subnet. 2. Create any VPN session or use any virtual machine, which creates interface in host system. 3. Stop VPN/VM and get virtual interface down. 4. NFS is unmounted. Not tested, but seems to be reproduced with any type of PPP interfaces (PPPoE, PPTP, GPRS, whatever). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1022744] New: Infinite loop during boot because of USB device in kernel 4.9.6
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1022744 Bug ID: 1022744 Summary: Infinite loop during boot because of USB device in kernel 4.9.6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.jakl(a)qbicon.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Build Identifier: I have motherboard with some problematic USB device, I don't know what it is, probably something internal, but windows also show one not working device. Until kernel 4.9.4 at the beginning of boot there was some message about not working USB device, but it booted and everything worked. In kernel 4.9.5 something changed and there was a loop of messages usb usb1-port2: unable to enumerate USB device usb usb2-port1: Cannot enable. Maybe the USB cable is bad? at first for 3 minutes connected with systemd-udev-settle messages and then another another 3 minutes with lvm2, after that it started, but dmesg was flooded with these messages. I masked systemd-udev-settle and turned off lvm2 and added cron job at @reboot to do: echo '0000:00:14.0' > /sys/bus/pci/drivers/xhci_hcd/unbind echo '0000:00:14.0' > /sys/bus/pci/drivers/xhci_hcd/bind after these changes I was able to boot in reasonable time and everything worked. But 4.9.6 changed something again and during boot, there is only infinite cycle of: usb usb1-port2: unable to enumerate USB device usb usb2-port1: Cannot enable. Maybe the USB cable is bad? I've waited for 15 minutes, but nothing changed. I've also tried 4.10.rc5 and it behaved the same as 4.9.6. Reproducible: Always Actual Results: Unable to boot with kernel 4.9.6. Expected Results: To be able to boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1001971] New: greenbone-security-assistant fails to build
by bugzilla_noreply＠novell.com 30 Aug '19

30 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1001971 Bug ID: 1001971 Summary: greenbone-security-assistant fails to build Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: meissner(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- greenbone-security-assistant fails to build in Leap, please submit a fix: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:42.2/greenb… -- You are receiving this mail because: You are on the CC list for the bug.

1 9