October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 911355] New: Job for spamd.service failed
by bugzilla_noreply＠novell.com 11 Nov '19

11 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=911355 Bug ID: 911355 Summary: Job for spamd.service failed Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stephan.barth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the upgrade from 12.3 I found out that spmad was not running anymore. When trying to start it manually I get: # /etc/init.d/spamd restart redirecting to systemctl restart spamd.service Job for spamd.service failed. See "systemctl status spamd.service" and "journalctl -xn" for details. Running the latter command yields: Dec 29 16:40:11 linux-wulv echo[6901]: Starting spamd: Dec 29 16:40:11 linux-wulv spamd[6903]: logger: removing stderr method Dec 29 16:40:11 linux-wulv spamd[6905]: config: no rules were found! Do you need to run 'sa-update'? Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed out without signaling production of a PID file: exit 255 at /us Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed out without signaling production of a PID file: exit 255 at /us Dec 29 16:40:12 linux-wulv systemd[1]: Failed to start Daemonized version of spamassassin. -- Subject: Unit spamd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit spamd.service has failed. -- -- The result is failed. # rpm -q perl-Mail-SpamAssassin perl-Mail-SpamAssassin-3.4.0-44.1.3.x86_64 # rpm -q spamassassin spamassassin-3.4.0-44.1.3.x86_64 Solution: Running sa-update manually makes spamd start with '/etc/init.d/spamd restart'. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 950955] New: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=950955 Bug ID: 950955 Summary: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Jan.Hebler(a)Kabeldeutschland.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rtkit-daemon produces the following Error-Messages: ... Okt 19 07:06:19 tablette rtkit-daemon[3051]: Failed to make ourselves RT: Operation not permitted ... If i understand Lennart Poettering here https://bugzilla.redhat.com/show_bug.cgi?id=1229700 correct, the Kernel-Option CONFIG_RT_GROUP_SCHED should turned off. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 941758] New: grub-once isn't called at hibernate
by bugzilla_noreply＠novell.com 22 Oct '19

22 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=941758 Bug ID: 941758 Summary: grub-once isn't called at hibernate Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the recent change of systemd, grub-once isn't called any longer, thus at thawing, the normal GRUB menu is shown instead of the direct boot to the target kernel. The regression was introduced in openSUSE:Factory/systemd changeset 215: Wed Feb 18 05:01:38 UTC 2015 - crrodriguez(a)opensuse.org .... - systemd-sleep-grub: moved to the grub2 package where it belongs as a suspend/resume hook (SR#286533) (drops prepare-suspend-to-disk.patch) However, SR#286533 was declined and it's lost since then. The fix would be either revert the change in systemd or put the hook properly into grub2 package. The latter method has a potential bug, however. systemd-sleep doesn't call hooks to restore when writing to /sys/power/state fails. That is, if we have a hook to set up grubenv, it'll left when the hibernation fails, and the next boot would go wrong. This didn't happen in the past because it invoked the grubenv setup in a different manner. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 969165] New: parted creates wrong protective mbr
by bugzilla_noreply＠novell.com 22 Oct '19

22 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=969165 Bug ID: 969165 Summary: parted creates wrong protective mbr Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: puzel(a)suse.com Reporter: snwint(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- The protective mbr parted creates has inconsistent data. The CHS value for the partition start is 0/0/1 (pointing to the MBR itself) but should be 0/0/2 (pointing to the partition). The LBA starting value of 1 is correct, however. (CHS values are 1-based.) UEFI spec also explicitly mentions the correct value 0/0/2. gptfdisk works correctly, btw. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

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