July 2015 - 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 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 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 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 934055] New: yast2-network: Do not use .site as default TLD
by bugzilla_noreply＠novell.com 23 Aug '19

23 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=934055 Bug ID: 934055 Summary: yast2-network: Do not use .site as default TLD Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: mfilka(a)suse.com Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Blocks: 923990 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #923990 +++ YaST should not set any domain at all anymore in /etc/hostname. The domain name entry box (eg https://openqa.opensuse.org/tests/67247/modules/yast2_lan/steps/3) should be removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 840485] New: Firefox 24.0/17.0.9esr security release
by bugzilla_noreply＠novell.com 16 Aug '19

16 Aug '19

https://bugzilla.novell.com/show_bug.cgi?id=840485 https://bugzilla.novell.com/show_bug.cgi?id=840485#c0 Summary: Firefox 24.0/17.0.9esr security release Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- 2013-09-17 is the announced release date for the following Mozilla applications which contain security fixes (as always) (https://wiki.mozilla.org/Releases) Firefox 24.0 Firefox 17.0.9esr xulrunner 17.0.9esr Seamonkey 2.21 Thunderbird 17.0.9esr Thunderbird 24.0 (minimum NSPR 4.10 and NSS 3.15.1 requirements I think already met with last update round) I'll provide updates for openSUSE distributions as usual with one exception where I'd like to get some feedback: Thunderbird will do a big version update to 24.0 for non-esr versions. Since esr and non esr versions were 99,9% identical in the 17.0 series we have the choice to update to 17.0.9esr or 24.0 for released distributions which will only move the major upgrade around 12 weeks so I'm in favor to follow the big update now already. -- 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 46

[Bug 935339] New: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz
by bugzilla_noreply＠novell.com 05 Jul '19

05 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=935339 Bug ID: 935339 Summary: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Uninstalling gpgme, I get the following: 1 package to remove. After the operation, 355.3 KiB will be freed. Continue? [y/n/? shows all options] (y): y (1/1) Removing gpgme-1.5.5-1.1 .........................................................................................................[done] Additional rpm output: install-info: No such file or directory for /usr/share/info/gpgme.info.gz warning: %postun(gpgme-1.5.5-1.1.x86_64) scriptlet failed, exit status 1 # rpm -ql gpgme | grep info /usr/share/info/gpgme.info-1.gz /usr/share/info/gpgme.info-2.gz /usr/share/info/gpgme.info.gz This looks similar to bug #929415 and may have the same fix? -- You are receiving this mail because: You are on the CC list for the bug.

1 5