February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1012648] New: readline: /etc/inputrc: line 19: term: unknown variable name
by bugzilla_noreply＠novell.com 16 Oct '19

16 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1012648 Bug ID: 1012648 Summary: readline: /etc/inputrc: line 19: term: unknown variable name Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: JeanLasVEGAs(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- > uname -a Linux jano 4.8.10-1-default #1 SMP PREEMPT Mon Nov 21 13:50:28 UTC 2016 (d1ec066) x86_64 x86_64 x86_64 GNU/Linux > cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20161125" ID=opensuse ID_LIKE="suse" VERSION_ID="20161125" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20161125" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" When opening a new terminal session, I get a message: readline: /etc/inputrc: line 19: term: unknown variable name -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 992519] New: obsolete font package requirements
by bugzilla_noreply＠novell.com 15 Oct '19

15 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=992519 Bug ID: 992519 Summary: obsolete font package requirements Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: coolo(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: simonf.lees(a)suse.com Found By: --- Blocker: --- Quote from factory mailing list: https://lists.opensuse.org/opensuse-factory/2016-08/msg00133.html > # rpm -qR release-notes-openSUSE > dejavu-fonts > google-opensans-fonts > rpmlib... > I find hard requires of any particular font package just to have release > notes locally available onerous and unnecessary, especially since > neither requires (AFAICT) are used as system fonts in any of the DEs. > I'd be surprised to find other distros have corresponding font deps. > Release notes work fine with google-opensans-fonts tabooed out, falling > back to the monospace, sans-serif and serif defaults. Its probably a historical thing more then anything else especially now that the default fonts have changed, if you would be so kind as to open a bug ticket for me i'll remember to look into it when I next get to doing a clean up of the patterns. Or for that matter the same can be done for any other legacy pattern issue. -- Simon Lees (Simotek) -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 984976] New: XF86MonBrightnessDown and XF86MonBrightnessUp don't work in TW-20160422
by bugzilla_noreply＠novell.com 03 Oct '19

03 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=984976 Bug ID: 984976 Summary: XF86MonBrightnessDown and XF86MonBrightnessUp don't work in TW-20160422 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: h.m.brand(a)xs4all.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- XF86MonBrightnessDown and XF86MonBrightnessUp do not work for a while now in TumbleWeed patterns-openSUSE-kde_plasma-20151112-15.1.x86_64 plasma5-desktop-5.6.4-2.1.x86_64 Linux 4.6.2-1-default [openSUSE Tumbleweed (20160422) (x86_64)] HP EliteBook 8560p Core(TM) i7-2620M CPU @ 2.70GHz/1901(4) x86_64 7932 Mb xev still recognizes the keys: KeyPress event, serial 37, synthetic NO, window 0x8c00001, root 0x49e, subw 0x0, time 2298889, (-656,74), root:(630,500), state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x8c00001, root 0x49e, subw 0x0, time 2298959, (-656,74), root:(630,500), state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x8c00001, root 0x49e, subw 0x0, time 2673178, (115,109), root:(1401,535), state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False The weird thing I see here is that Fn-F9 (Down) is detected as both Press and Release and that FnF100 (Up) is only seen as Release -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 939153] New: Thunderbird 38: Integrated Lightning calendar is not properly localized
by bugzilla_noreply＠novell.com 27 Sep '19

27 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=939153 Bug ID: 939153 Summary: Thunderbird 38: Integrated Lightning calendar is not properly localized Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: lashkevi(a)landau.ac.ru QA Contact: ke(a)suse.com Found By: --- Blocker: --- Created attachment 641749 --> http://bugzilla.opensuse.org/attachment.cgi?id=641749&action=edit Snapshot for a fresh profile. Integrated Lightning in the Thundebird 38.1.0 from the last official update is not localized. Its whole UI is in English. Versions: MozillaThunderbird-38.1.0-70.57.1.x86_64 MozillaThunderbird-translations-common-38.1.0-70.57.1.x86_64 Steps to reproduce: 1. Update TB to 38.1. It removes the Lightning add-on substituting it by its integrated version as well as I understand. 2. Start TB in Russian (LANG=ru_RU.UTF-8 LANGUAGE=ru) locale. Actual results: Calendar (Lightning) menu items, config options and the whole UI is in English. Expected results: Calendar (Lightning) menu items, config options and UI should be in Russian. The issue is corrected after installing Lightning from a file (lightning-4.0.1-sm+tb-linux.xpi). But such workaround must make thundebird use more memory. The vanilla Russian version <https://download.mozilla.org/?product=thunderbird-38.1.0&os=linux64&lang=ru> does not show this issue, so that it is a problem of the OpenSUSE build. -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 921221] New: Unable to install with UEFI Secure Boot if Windows is present
by bugzilla_noreply＠novell.com 26 Sep '19

26 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=921221 Bug ID: 921221 Summary: Unable to install with UEFI Secure Boot if Windows is present Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: rbrown(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hardware: ASUS UX303LA with Windows 8.1, i7 5500U, 12GB RAM Steps to Reproduce: 1. Factory/Plain installation of Windows 8.1 2. Burn a Tumbleweed (or 13.2) USB stick - Tried with a NET, DVD, or Live ISO 3. Boot to it - Blue ncurses screen asking if you trust the SUSE Keys pops up 4. Click Yes 5. End up at a Grub2 command prompt, system refuses to boot into YaST - lots of different attempts to get it booted by setting linuxefi and initrdefi don't work 6. Clearing KEK, etc, in the Bios doesn't help 7. Trying different USB sticks doesn't help 8. The 'do you want to trust SUSEs Keys' ncurses window never appears again 9. Switching the BIOS to boot into Legacy mode, booting to a liveUSB in Legacy, wiping the hard drive and starting the process fresh works..but obviously, you have no opportunity to dual boot with Windows 8 Looks to me like there is something wrong with how we're currently trying to insert keys/shim/whatever into the EFI configuration present on a fresh Windows 8.1 install. This is a pretty serious problem if people want to easily install openSUSE on freshly purchased hardware. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

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