openSUSE Bugs February 2018

bugs@lists.opensuse.org

1 participants
4572 discussions

[Bug 993885] New: Kde-Live net installer does not reboot after installation

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=993885 Bug ID: 993885 Summary: Kde-Live net installer does not reboot after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: okurz(a)suse.com QA Contact: okurz(a)suse.com Found By: --- Blocker: --- ## observation Continuing through the whole installation process of the NET installer on the Kde-Live medium until the "reboot now" dialog shows up works fine but the reboot does not seem to happen ## steps to reproduce I am in the process of automating this but it can be as easy as * start Kde-Live * call installation from within plasma session * let installer run into "reboot now" action * observe that the system does not reboot ## expected result system should reboot into installed system ## workaround manual reboot of the system yields a properly setup Tumbleweed installation so the installation is ok. -- You are receiving this mail because: You are on the CC list for the bug.

1 hour, 29 minutes

[Bug 981004] New: Ensure template unit instances are deleted

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=981004 Bug ID: 981004 Summary: Ensure template unit instances are deleted Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: jengelh(a)inai.de Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a package is uninstalled, it will also be removed from the boot sequence, by means of %preun generally calling %service_del_preun foo.service, which expands to (among other things) `systemctl disable foo.service`. To disable template instances such as foo(a)bar.service and foo(a)baz.service, one can - and must, since "bar" and "baz" are not known at any time to the package management system - use `systemctl disable foo@.service`, which will disable all instances. A number of packages are lacking the corresponding %service_del_preun template@.service lines, which means template instance links like foo(a)bar.service will stick around after package uninstall. 389-ds apache2 arpwatch autossh booth chrony cups device-mapper dracut envoy freeipa govpn gpsd kmscon libteam lvm2 lvm2-clvm mariadb mdadm mgetty mysql mysql-community-server openct openvpn parkverbot rear redis rfkill syncthing system-config-printer systemd systemd-mini tomcat vpnc vsftpd wicked xf86-input-wacom -- You are receiving this mail because: You are on the CC list for the bug.

6 hours, 14 minutes

[Bug 960478] New: krunner shows inexisting VT sessions in parallel of the existing ones

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=960478 Bug ID: 960478 Summary: krunner shows inexisting VT sessions in parallel of the existing ones Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: 64bit OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 660618 --> http://bugzilla.opensuse.org/attachment.cgi?id=660618&action=edit krunner showing non existing VT sessions in parallel to existing ones Opens a new session with the applet from desktop. You will find that krunner opens as expected but that for every VT session opened there is a "ghost session" showing the very same VT as unused. When you logout from several users these ghosts persist up to a complete reboot. VT sessions once closed should be closed without residual VTs showing up. VT sessions open should not be accompanied by a VT session ghost telling unused session. I attach a screen-shot to make the thing clearer. Repeatable always. -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 6 hours

[Bug 1047218] New: trackerbug: packages do not build reproducibly from including build time

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1047218 Bug ID: 1047218 Summary: trackerbug: packages do not build reproducibly from including build time Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: SUSE Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://reproducible-builds.org/specs/source-date-epoch/ When packages include the current time of build it results in binaries that differ on every build and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 8 hours

[Bug 1074097] New: RN: "systemctl stop apparmor" intentionally broken

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1074097 Bug ID: 1074097 Summary: RN: "systemctl stop apparmor" intentionally broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- Please add this information about AppArmor to the Leap 15 release notes (copy&paste from https://blog.cboltz.de/archives/77-AppArmor-2.12-The-Grinch-is-confined!.ht… and assuming that Leap 15 will pick up AppArmor 2.12 or newer) --- One important change in the [AppArmor 2.12] packages is that I intentionally broke "systemctl stop apparmor". The reason for this is "systemctl restart apparmor" - systemd maps this to stop, followed by start. This resulted in unloading all AppArmor profiles by the "stop" part and, even if they get loaded again a second later, running processes will stay unconfined unless you restart them. The systemd developers were unwilling to implement the proposed ExecRestart= option for unit files, therefore breaking "stop" is the best thing I can do. (See boo#996520 and boo#853019 for more details.) "systemctl reload apparmor" will continue to work and is still the recommended way to reload the AppArmor profiles, but accidently typing "restart" instead of "reload" can easily happen. Therefore I chose to break "stop" - that's annoying, but more secure than accidently removing the AppArmor confinement from running processes. If you really want to unload all AppArmor profiles, you can use the new "aa-teardown" command which does what "systemctl stop apparmor" did before - but who would do that? ;-) -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 12 hours

[Bug 1050519] New: Description about kernel graphics update

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1050519 Bug ID: 1050519 Summary: Description about kernel graphics update Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: tiwai(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- Created attachment 733812 --> http://bugzilla.opensuse.org/attachment.cgi?id=733812&action=edit Patch to release-notes.xml Some information about Leap 42.3 kernel graphics update, as Ludwig suggested in opensuse-factory ML. -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 12 hours

[Bug 1048692] New: version downgrade of libgcj_bc1

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1048692 Bug ID: 1048692 Summary: version downgrade of libgcj_bc1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 42.2 vs 42.3: libgcj48: libgcj_bc1-4.8.5-24.14.x86_64 is older than libgcj_bc1-6.2.1+r239768-5.5.2.x86_64 in 42.2 libgcj_bc1 came from libgcj-gcc6 which isn't in 42.3. What is correct here? -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 12 hours

[Bug 1048660] New: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported.

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1048660 Bug ID: 1048660 Summary: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: bugrprt21882(a)online.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 13th July 2017: With the Leap 42.2 upgrade of LibreOffice from version 5.2.5 to version 5.3.3 the fact that, with version 5.3 LibreOffice has dropped support for Type 1 (Postscript) fonts was a not so pleasant surprise. Please consider placing a note indicating that, LibreOffice as of version 5.3 no longer supports Type 1 (Postscript) fonts in the Release Notes. Is also, possibly an issue for the Leap 42.3 Release Notes. --------------------------------------------------------- I haven't found anything in the LibreOffice Release Notes indicating this issue: <https://www.libreoffice.org/download/release-notes/> There's only this article in "Linux Magazine": <http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blo…> There's information in this Document Foundation Bug Report: Bug 104701 <https://bugs.documentfoundation.org/show_bug.cgi?id=104701> --------------------------------------------------------- There's possibly help for the folks (like me) with a suite of Type 1 fonts here: <https://slackbuilds.org/repository/14.2/system/afdko/> Haven't tried to build the "Adobe Font Development Kit for OpenType" yet -- will happen later today. -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 12 hours

[Bug 1048392] New: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1048392 Bug ID: 1048392 Summary: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: bugrprt21882(a)online.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 3.2 Dolphin Does Not Set Extended Permission Bits https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/#sec.gener… Unfortunately, with Leap 42.3, Konqueror is also the Plasma 5 version and, it also can not set the Extended Permissions bits . . . Therefore, the Leap 42.3, CLI only to toggle the Extended Permission bits . . . -- You are receiving this mail because: You are on the CC list for the bug.

5 days, 12 hours

[Bug 1021059] New: [s390x-port][Build0001] dependency issues when installing default with kde

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1021059 Bug ID: 1021059 Summary: [s390x-port][Build0001] dependency issues when installing default with kde Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mgriessmeier(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 710981 --> http://bugzilla.opensuse.org/attachment.cgi?id=710981&action=edit y2logs I'm trying to install Tumbleweed on s390x for the first time. Default pattern and KDE as default desktop, resulting in following dependency problems: #### YaST2 conflicts list - generated 2017-01-20 10:15:31 #### nothing provides libpfm.so.4()(64bit) needed by s390-tools-1.34.0-1.1.s390x [ ] do not install grub2-2.02~beta3-16.1.s390x [ ] break s390-tools-1.34.0-1.1.s390x by ignoring some of its dependencies nothing provides plasma5-desktop needed by patterns-openSUSE-kde_plasma-20151112-29.1.s390x [ ] do not install pattern:kde-20151112-29.1.s390x [ ] break patterns-openSUSE-kde_plasma-20151112-29.1.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install ntp-4.2.8p9-1.2.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install xinetd-2.3.15-11.4.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install kernel-default-4.9.0-2.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install pattern:base-20151112-29.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install pattern:x11-20151112-29.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies #### YaST2 conflicts list END ### see attached y2logs -- You are receiving this mail because: You are on the CC list for the bug.

1 week, 1 day

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs February 2018