August 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 939248] New: gnome-shell not having correct SSH_AUTH_SOCK variable
by bugzilla_noreply＠novell.com 20 Oct '19

20 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=939248 Bug ID: 939248 Summary: gnome-shell not having correct SSH_AUTH_SOCK variable Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: vuntz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Any process that I start through gnome-shell seems to have a SSH_AUTH_SOCK matching a ssh-agent process (probably started through the X11 session scripts). However, if I start a process through gnome-settings-daemon (like a terminal, through the shortcurt for that), it has SSH_AUTH_SOCK set to the path for gnome-keyring. The result is that any app I start through gnome-shell actually has, by default, not access to my ssh keys :/ (also, I thought I had fixed a long time ago the bit starting ssh-agent on gnome sessions -- this shouldn't happen because of the keyring) -- 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 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 987720] New: Egypt (Africa/Cairo) DST cancelled, 2016f timezone release
by bugzilla_noreply＠novell.com 28 Aug '19

28 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=987720 Bug ID: 987720 Summary: Egypt (Africa/Cairo) DST cancelled, 2016f timezone release Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: astieger(a)suse.com Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de CC: alnovak(a)suse.com, andreas.taschner(a)suse.com, astieger(a)suse.com, brent.griggs(a)suse.com, jake.norris(a)suse.com, jeff.ray(a)suse.com, ntsbugsiebint-bugs(a)forge.provo.novell.com, roger.whittaker(a)suse.com, rosuna(a)suse.com, wpreston(a)suse.com Blocks: 982833 Found By: --- Blocker: --- http://mm.icann.org/pipermail/tz-announce/2016-July/000040.html Customers should avoid installing the PTF or the update already released for SLE 12: http://mm.icann.org/pipermail/tz-announce/2016-July/000040.html > The 2016f release of the tz code and data is available. It reflects the > following changes, which were either circulated on the tz mailing list > or are relatively minor technical or administrative changes: > > Changes affecting future time stamps > > The Egyptian government changed its mind on short notice, and > Africa/Cairo will not introduce DST starting 2016-07-07 after all. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 930173] New: VUL-0: CVE-2015-0847: nbd: incorrect signal handling DoD
by bugzilla_noreply＠novell.com 28 Aug '19

28 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=930173 Bug ID: 930173 Summary: VUL-0: CVE-2015-0847: nbd: incorrect signal handling DoD Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- http://seclists.org/oss-sec/2015/q2/388 CVE-2015-0847 in nbd-server From: Florian Weimer <fw () deneb enyo de> Date: Thu, 07 May 2015 22:45:33 +0200 nbd-server uses signal handlers incorrectly, which leads to a denial of service vulnerability. We have assigned CVE-2015-0847 to this vulnerability. This was first reported to the Debian security team by Tuomas Räsänen, but we did not think this warranted an embargo. More details are available upstream: <http://sourceforge.net/p/nbd/mailman/message/34091218/> -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 902779] New: [Factory] Long boot delay "a start job is running for..."
by bugzilla_noreply＠novell.com 27 Aug '19

27 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=902779 Bug ID: 902779 Summary: [Factory] Long boot delay "a start job is running for..." Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, My openSUSE Factory installation was taking at least 60 seconds longer than normal to boot. The delay always occurred on every boot. The delay occured before initializing the display manager with a message: "A start job is running for", and it would alternate between four different services: X display manager, Avahi, NetworkManager, and Modem Manager. I tried disabling the Modem Manager service, but it still kept hanging on Avahi and NetworkManager. I eventually tried disabling and later re-enabling the NetworkManager services, and it now boots quickly without hanging. I don't really know why this happened or what I did to fix it. Please let me know what additional information you need to prevent this bug from happening. Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 996551] New: Make libldap library to be a symlink to libldap_r library
by bugzilla_noreply＠novell.com 23 Aug '19

23 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=996551 Bug ID: 996551 Summary: Make libldap library to be a symlink to libldap_r library Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: hguo(a)suse.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When an application uses libraries that cause both libldap or libldap_r to end up in the process image, the libraries sometimes happen to use a different function than expected. The fix is to make /usr/lib64/libldap-2.4.so.2 a symlink to libldap_r-2.4.so.2. More detail: https://bugzilla.redhat.com/show_bug.cgi?id=1370065 This bug is for tracking the same issue in openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 3