May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1131754] New: sssd fails to start due to a ldb module version mismatch (after installing updates on 2019-04-05)
by bugzilla_noreply＠novell.com 14 May '22

14 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1131754 Bug ID: 1131754 Summary: sssd fails to start due to a ldb module version mismatch (after installing updates on 2019-04-05) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: mhupfer(a)franken-online.de QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: # rcsssd status * sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2019-04-06 11:23:34 CEST; 17min ago Process: 4985 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=4) Main PID: 4985 (code=exited, status=4) Apr 06 11:23:34 pcito20.leistritz.de systemd[1]: Starting System Security Services Daemon... Apr 06 11:23:34 pcito20.leistritz.de sssd[4985]: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.4 module_version=1.2.3 Apr 06 11:23:34 pcito20.leistritz.de sssd[4985]: ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable Apr 06 11:23:34 pcito20.leistritz.de sssd[4985]: ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable Apr 06 11:23:34 pcito20.leistritz.de sssd[4985]: SSSD couldn't load the configuration database [5]: Input/output error. Apr 06 11:23:34 pcito20.leistritz.de systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION Apr 06 11:23:34 pcito20.leistritz.de systemd[1]: Failed to start System Security Services Daemon. Apr 06 11:23:34 pcito20.leistritz.de systemd[1]: sssd.service: Unit entered failed state. Apr 06 11:23:34 pcito20.leistritz.de systemd[1]: sssd.service: Failed with result 'exit-code'. Reproducible: Always Steps to Reproduce: 1. zypper up 2. reboot 3. verify sssd status Actual Results: sssd fails to start, domain users cannot log on! Expected Results: sssd starts successfully as it did before the update on Friday, April 5. Previous "zypper up" run was roughly one week before. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 960478] New: krunner shows inexisting VT sessions in parallel of the existing ones
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

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.

2 10

[Bug 1086063] New: RPM bad GROUP type/error/duplicate
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1086063 Bug ID: 1086063 Summary: RPM bad GROUP type/error/duplicate Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: fbourdonnec(a)chez.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 764285 --> http://bugzilla.opensuse.org/attachment.cgi?id=764285&action=edit some screenshot of obvious errors Hello, Each RPM have at least a hierarchical group membership. Supposedly, Yast2 can show them under useful grouping. But nobody cares and the thing is slowly becoming a mess. Just some examples (images in zip files) Developement/Languages/Python/python-castellan Development/Languages/Python/ all other python stuff is here System/Filesystem/f2fs-tools-compat System/Filesystems/all others and so on many Group with on RPM because of typo/duplicate name Games/Arcade/Logic Games/Logic Really RPG & Action ? System/Libraries/KDE/kdiagram-devel !!!! You have also some -devel files disseminated System/I18n/Chineese|Jap/ Strange Java or Office toplevel Groups. Should be something else Communication/Connectivity Adaptation -ofono Really ? Two level for a single tool lib ? System Environment Systems Management Tools Unspecified Utilities are just another name for an existing group Please at least fix obvious errors that are spotted just by looking yast2 rpm packages manager. Thank you -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1129362] New: openSUSE:Leap:15.1/erlang-rebar-testsuite failed
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129362 Bug ID: 1129362 Summary: openSUSE:Leap:15.1/erlang-rebar-testsuite failed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://build.opensuse.org/package/live_build_log/open SUSE:Leap:15.1/erlang-rebar-testsuite/standard/x86_64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: nkrinner(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Leap:15.1/erlang-rebar-testsuite failed to build. Please see build log: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1/erlang… -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1126496] New: [doc] Syntax about packages modifying /var or /srv
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1126496 Bug ID: 1126496 Summary: [doc] Syntax about packages modifying /var or /srv Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: santiago.zarate(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 1.1 Using Atomic Updates With the System Role <span class="emphasis"><em>Transactional Server</em></span> https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.1/#sec.insta… Message reads: > Note: Incompatible Packages > >Some packages modify the contents of /var or /srv in their RPM %post scripts. > These packages are incompatible. If you happen upon such package, file a bug report. However "If you happen upon such package" seems a bit odd, I suggest that part being changed to: "If you happen to find packages doing this..." or something similar. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1125819] New: YaST2 fonts - Internal error
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1125819 Bug ID: 1125819 Summary: YaST2 fonts - Internal error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 797090 --> http://bugzilla.opensuse.org/attachment.cgi?id=797090&action=edit y2log openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-yast2_gui@aarch64 fails in [yast2_control_center](https://openqa.opensuse.org/tests/857564/modules/yast… y2log attached. Relevant part is probably: YCP_UI.cc(SetApplicationTitle):1722 Setting application title to '"YaST2 - fonts @ susetest"' 2019-02-18 09:25:25 <1> susetest(16018) [Interpreter] bin/y2start:62 Calling YaST client fonts 2019-02-18 09:25:25 <1> susetest(16018) [Ruby] yast/wfm.rb:308 Call client /usr/share/YaST2/clients/fonts.rb 2019-02-18 09:25:25 <2> susetest(16018) [Ruby] yast/builtins.rb:586 tostring builtin called on wrong type Class 2019-02-18 09:25:25 <3> susetest(16018) [Ruby] yast/wfm.rb:253 Client /usr/share/YaST2/clients/fonts.rb failed with 'cannot load such file -- yast/fontconfig_setting' (LoadError). Backtrace: /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' /usr/share/YaST2/lib/fonts/fpl-add-dialog.rb:4:in `<top (required)>' /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' /usr/share/YaST2/lib/fonts/fonts-dialog.rb:10:in `<top (required)>' /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' /usr/share/YaST2/clients/fonts.rb:4:in `<top (required)>' /usr/lib64/ruby/vendor_ruby/2.6.0/yast/wfm.rb:313:in `eval' /usr/lib64/ruby/vendor_ruby/2.6.0/yast/wfm.rb:313:in `run_client' /usr/lib64/ruby/vendor_ruby/2.6.0/yast/wfm.rb:206:in `call_builtin' /usr/lib64/ruby/vendor_ruby/2.6.0/yast/wfm.rb:206:in `call_builtin_wrapper' /usr/lib64/ruby/vendor_ruby/2.6.0/yast/wfm.rb:195:in `CallFunction' /usr/lib/YaST2/bin/y2start:62:in `<main>' 2019-02-18 09:25:25 <3> susetest(16018) [Ruby] yast/wfm.rb:276 Internal error. Please report a bug report with logs -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1116922] New: [rn] amanda - amanda user (and group) should be considered privileged user
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1116922 Bug ID: 1116922 Summary: [rn] amanda - amanda user (and group) should be considered privileged user Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: kstreitova(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- I would like to add a section to openSUSE:Leap:15.1 release notes about amanda. Draft ----- We currently limit the execution of the binaries in this package to the group amanda. Some of the binaries are setuid root. As the implementation of these binaries is partially problematic, the user amanda and members of the group amanda should be considered privileged users with equivalent permissions to the root user. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1100005] New: add note about dropped git-annex
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1100005 Bug ID: 1100005 Summary: add note about dropped git-annex 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: lnussel(a)suse.com QA Contact: lnussel(a)suse.com CC: peter.simons(a)suse.com Found By: --- Blocker: --- git-annex is no longer maintained and was requested to be dropped: https://build.opensuse.org/request/show/619548 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1100003] New: use %_with_betatest
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1100003 Bug ID: 1100003 Summary: use %_with_betatest 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: lnussel(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- LIFECYCLE=beta in the spec file needs to be changed to use %_with_betatest otherwise we will forget about this -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1092056] New: [doc] SuSEfirewall2 is mentioned where only firewalld should be the supported version
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1092056 Bug ID: 1092056 Summary: [doc] SuSEfirewall2 is mentioned where only firewalld should be the supported version 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: okurz(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 1.1 Minimal System Installation https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/#sec.insta… -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1091866] New: RN: PostfixAdmin - changed directory layout
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091866 Bug ID: 1091866 Summary: RN: PostfixAdmin - changed directory layout Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: openSUSE 42.3 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: Beta-Customer Blocker: --- The PostfixAdmin package in Leap 15.0 (and also Tumbleweed) comes with a changed directory layout, which also brings a backwards-incompatible change (PostfixAdmin will no longer read the config files at the old location). This especially means users will have to move their config.local.php to /etc/postfixadmin and (if they did changes to config.inc.php) migrate these changes, ideally to /etc/postfixadmin/config.local.php. Users will also need to enable or add the /postfixadmin alias in the apache config. Can you please add [something like] the following text to the "Upgrade" section of the release notes? ------------------------------------------------------------------------- PostfixAdmin: Changed directory layout PostfixAdmin 3.2 comes with a changed directory layout. Instead of having everything in /srv/www/htdocs/postfixadmin/, - the config files (config.inc.php and config.local.php) are now in /etc/postfixadmin/. (It's recommended to keep config.inc.php unmodified, and to add config changes to config.local.php.) - the PHP code moved to /usr/share/postfixadmin/ - the smarty cache moved to /var/cache/postfixadmin/ Note that /srv/www/htdocs/postfixadmin/config.*.php will _not_ be moved to /etc/postfixadmin/ automatically on upgrades, so you'll have to migrate your config changes manually. Also note that the /postfixadmin alias is _not_ enabled in Apache by default. To enable the /postfixadmin alias, run a2enflag POSTFIXADMIN && rcapache2 restart This will make /postfixadmin available on all virtual hosts. If you want to have the /postfixadmin alias only on a specific virtual host, add the alias to the config of that vhost. ------------------------------------------------------------------------- For the Apache config, you can replace the text starting at "To enable..." with a reference to the comments in /etc/apache2/conf.d/postfixadmin if you think the text is too long. Also, feel free to drop the "(It's recommended ...)" sentence if you think it makes the text too long. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1091021] New: Yast /etc/sysconfig removal of default DM option
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091021 Bug ID: 1091021 Summary: Yast /etc/sysconfig removal of default DM option Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: SUSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: maninredd(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 768371 --> http://bugzilla.opensuse.org/attachment.cgi?id=768371&action=edit screenshot of yast In pretty much every Opensuse and SLE that i have used there was the ability to in yast under the /etc/sysconfig module in SYSTEM to change the default Windows Manager and Desktop Environment. Somehow this has disappeared between Leap 42.3 and Leap 15. Attached is a comparison of Leap 42.3 and Leap 15 (as of late April 2018) You can see in the 42.3 on the right there is the option to change the Display Manager and that is omitted in the Leap 15 screen on the left. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1090382] New: KDE wayland not supported with the nvidia binary driver
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1090382 Bug ID: 1090382 Summary: KDE wayland not supported with the nvidia binary driver 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: lnussel(a)suse.com QA Contact: lnussel(a)suse.com CC: fvogt(a)suse.com Found By: --- Blocker: --- the KDE plasma wayland session is not supported with the Nvidia proprietary driver. it is recommended to stay with X when using KDE and the nvidia proprietary driver. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1090358] New: [doc] we now default to firewalld
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1090358 Bug ID: 1090358 Summary: [doc] we now default to firewalld 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: aj(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 1.1 Minimal System Installation https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/#sec.insta… contains "Note that the minimal installation has no firewall by default. If you need one, install SuSEfirewall2". AFAIK it should be firewalld. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1090240] New: document Qt/sddm hidpy options
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1090240 Bug ID: 1090240 Summary: document Qt/sddm hidpy options 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: lnussel(a)suse.com QA Contact: lnussel(a)suse.com CC: fvogt(a)suse.com Found By: --- Blocker: --- The options Fabian listed in https://bugzilla.opensuse.org/show_bug.cgi?id=1083873#c5 need to be documented in the release notes. QT_AUTO_SCREEN_SCALE_FACTOR=1 can be passed on the bootloader command line of the installation. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1085372] New: RN: add notes about font rendering change
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1085372 Bug ID: 1085372 Summary: RN: add notes about font rendering change Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: jengelh(a)inai.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- Created attachment 763734 --> http://bugzilla.opensuse.org/attachment.cgi?id=763734&action=edit Original behavior aka interpreter v35 Please add this information to the release notes: In wanting to mimic the contemporary Microsoft Windows font rendering more closely, freetype 2.6.4 has changed the way it hints font glyphs. To restore the previous FreeType behavior, set the following environment variable at any level (system-wide, user-specific, or program-specific) of your choice. FREETYPE_PROPERTIES="truetype:interpreter-version=35" [2 screenshots for comparison] -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1074097] New: RN: "systemctl stop apparmor" intentionally broken
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

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.

2 2

[Bug 1050519] New: Description about kernel graphics update
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

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.

2 5

[Bug 1048692] New: version downgrade of libgcj_bc1
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

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.

2 2

[Bug 1048660] New: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported.
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

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.

2 7

[Bug 1048392] New: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

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.

2 3

[Bug 1111572] New: patch segfaults if it can't write *.orig
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1111572 Bug ID: 1111572 Summary: patch segfaults if it can't write *.orig Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: jdelvare(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 785784 --> http://bugzilla.opensuse.org/attachment.cgi?id=785784&action=edit reproducer (tar.gz) Tumbleweed 20181009, patch-2.7.6-3.5.x86_64 I tried to apply a (non-matching) patch, and when patch tried to create the *.orig file, it printed a long list of error messages: # patch cleanprofile.py < changes.diff patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied [...] patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.orig : Permission denied patch: **** Can't create file cleanprofile.py.origSegmentation fault (core dumped) I'd expect _one_ "Permission denied" message, and no segfault. Reproducer: - unpack the attached tarball (as user) - chown root cleanprofile.py.orig (obviously as root) - run patch cleanprofile.py < changes.diff as user Note: This seems to be related to the files in the attached tarball. If I try with a simple one-line file and a boring patch, patch doesn't segfault. The reproducer files must have something special that send patch into an endless loop. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1103239] New: valgrind doesn't understand -z separate-code linked objects
by bugzilla_noreply＠novell.com 10 May '22

10 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1103239 Bug ID: 1103239 Summary: valgrind doesn't understand -z separate-code linked objects Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When linking with -z separate-code (which is the default on x86_64 starting with binutils 2.31 currently in staging) valgrind doesn't seem to find debuginfo anymore. Reproduce like > echo 'int main() { return 0; }' | gcc -g -Wl,-z,separate-code -x c - > valgrind --tool=callgrind ./a.out > grep main callgrind.out.* fn=(220) (below main) fn=(14) dl_main while the correct one looks like cfn=(220) (below main) fn=(246) main fn=(14) dl_main -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1131299] New: fontconfig creates an enormous number of files in /var/cache/fontconfig that are never cleaned up
by bugzilla_noreply＠novell.com 10 May '22

10 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1131299 Bug ID: 1131299 Summary: fontconfig creates an enormous number of files in /var/cache/fontconfig that are never cleaned up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: shundhammer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Earlier today I discovered that I had over 350,000 files in /var/cache/fontconfig that had accumulated in the 4 years that I have been using Tumbleweed. This not only consumed a lot of disk space, it also brought the system to a screeching halt every once in a while: All those files were in that single directory without any subdirectory. Even modern filesystems like XFS (which is what I use on that filesystem) break down completely in terms of performance when so many files are dumped into a single directory. It took more than 20 minutes (!) to remove the files (which needed "ls | xargs rm" because the argument list was much too long). So this directory needs to be cleaned up automatically every once in a while. Better yet, don't create so many files there in the first place. And even better, if so many files are needed, do it like the browsers (for their cache directories) and use an intermediate subdirectory (maybe on multiple levels) for better performance. [shundhammer @ morgul] ~ % cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190318" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190318" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190318" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" [shundhammer @ morgul] ~ % rpm -q fontconfig fontconfig-2.13.1-2.1.x86_64 After the cleanup, some files were recreated: [shundhammer @ morgul] ~ % ls -1 /var/cache/fontconfig 4bc6e738-4f14-4bb3-b1c1-113e1440c1c9-x86_64.cache-7 62a2cfd2-5b41-4739-9b75-5f646215de71-x86_64.cache-7 66f92a5c-8bae-4b9c-ba14-cf0cecec77a2-x86_64.cache-7 6f5661a4-b4de-4837-a6cb-77408b27d222-x86_64.cache-7 81ea5785-41f1-4169-a014-a9180af45296-x86_64.cache-7 8bfbb25c-ea26-45ef-9fa8-8bc1cd23e6c8-x86_64.cache-7 a74dc887-85ed-4c63-a0b3-3520f4be1244-x86_64.cache-7 b77b3349-5612-4eeb-95e2-a017bef0b7b7-x86_64.cache-7 be89a7c6-246d-476f-9e7e-e63a135fcfea-x86_64.cache-7 c210a518-33c5-48da-a1b9-55b4a4895c28-x86_64.cache-7 cbe681e7-c178-45ed-a1dd-523a6515af68-x86_64.cache-7 e0f28a10-064e-443c-9da1-1ad111a20ab1-x86_64.cache-7 e50cc437-bedf-4c0d-a1fb-f06def71d136-x86_64.cache-7 f5d4db0f-7acc-412e-b184-266c457f1a79-x86_64.cache-7 f6c4cbb4-f12c-4f74-8d69-264c5d8bbf56-x86_64.cache-7 That is a reasonable number. 350,000+ is not. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1114741] New: Spectacle fail to take screenshot on multi-monitor
by bugzilla_noreply＠novell.com 09 May '22

09 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1114741 Bug ID: 1114741 Summary: Spectacle fail to take screenshot on multi-monitor Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lubomirov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Half of the time or more Spectacle fails to take screenshot from either screen - initial overlay is created, no selection box can be created, and Esc/Enter doesnt work, so its just stuck on the overlay. When overlay is created at start, content from right screen is moved to the left one and right screen remains all white. Following command is applied manually after user login and may or may not be related to the issue: xrandr --output DisplayPort-0 --auto --output HDMI-0 --auto --panning 3840x2160+3840+0 --scale 2x2 --right-of DisplayPort-0 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112518] New: KDE3 + KDE Plasma doubled taskbar
by bugzilla_noreply＠novell.com 09 May '22

09 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1112518 Bug ID: 1112518 Summary: KDE3 + KDE Plasma doubled taskbar Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: anatoly.a.shipov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 786501 --> http://bugzilla.opensuse.org/attachment.cgi?id=786501&action=edit KDE3 + KDE Plasma doubled taskbar OpenSUSE 15.0 with KDE Plasma. If KDE3 is installed, it will be running 'inside' KDE Plasma. No such behavior if KDE3 is installed on top of MATE (no KDE plasma at all). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1021059] New: [s390x-port][Build0001] dependency issues when installing default with kde
by bugzilla_noreply＠novell.com 08 May '22

08 May '22

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.

2 5

[Bug 1102408] New: trackerbug: packages do not build reproducibly from race conditions
by bugzilla_noreply＠novell.com 05 May '22

05 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1102408 Bug ID: 1102408 Summary: trackerbug: packages do not build reproducibly from race conditions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory 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 Depends on: 1021335, 1021353 Blocks: 1081754 Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/race When packages build with make -j$N (N>1), it sometimes results in binaries that differ between builds and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. Build results can also be incorrect due to races. Often it is possible to fix races by adding proper dependencies between build targets (e.g. https://bugzilla.sudo.ws/show_bug.cgi?id=842 ) or fixing involved racy tools -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1116053] New: Please convert SysV init scripts by xfs into native systemd services
by bugzilla_noreply＠novell.com 25 Apr '22

25 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1116053 Bug ID: 1116053 Summary: Please convert SysV init scripts by xfs into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1135733] New: vorta package should be updated
by bugzilla_noreply＠novell.com 25 Apr '22

25 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1135733 Bug ID: 1135733 Summary: vorta package should be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sekhemty(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "vorta" package should be updated https://build.opensuse.org/package/show/openSUSE%3AFactory/vorta currently the repo has version 0.6.10, while upstream has v0.6.20, which includes several fixes and performance improvements -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1081947] New: PAM module pam_keyinit is still not included in the PAM stack
by bugzilla_noreply＠novell.com 20 Apr '22

20 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1081947 Bug ID: 1081947 Summary: PAM module pam_keyinit is still not included in the PAM stack 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Bug #1045886 revealed the lack of the integration of the PAM module "pam_keyinit". The pam_keyinit PAM module ensures that the invoking process has a session keyring other than the user default session keyring. The created session keyring will be linked to the user keyring. Even if it currently works without the integration of "pam_keyinit", in this case the user session keyring is used as fallback, it's strongly recommended to use a session-keyring instead especially for root user, see man user-session-keyring(7). That would also has the benefit to re-enable the keyring support in systemd where each system service gets its own session keyring automatically not linked with the user-keyring (the root one). pam-config gained support for the configuration of pam_keyinit recently [1] but it's still not used and therefore pam_keyinit is still not integrated in the PAM stack. [1] https://build.opensuse.org/request/show/565816 -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 1128846] New: chrony-dnssrv@.service has wrong path to helper script
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1128846 Bug ID: 1128846 Summary: chrony-dnssrv@.service has wrong path to helper script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.blume(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190307" # grep helper /usr/lib/systemd/system/chrony-dnssrv@.service ExecStart=/usr/share/chrony-helper update-dnssrv-servers %I ^^^^^^^^^^^^^^^^^^^^^^^^ rpm -ql chrony | grep helper /usr/lib/chrony/helper ^^^^^^^^^^^^^^^^^^^^^^ Please correct the path in ExecStart to point correctly to the helper script. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1105075] New: grub2-once does not parse /etc/sysconfig/bootloader properly
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1105075 Bug ID: 1105075 Summary: grub2-once does not parse /etc/sysconfig/bootloader properly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jack(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 779931 --> http://bugzilla.suse.com/attachment.cgi?id=779931&action=edit Patch to make grub2-once sysconf parsing more permissive grub2-once parses /etc/sysconfig/bootloader to determine value of LOADER_TYPE variable. However the regular expression there assumes that loader type has to have quotes around the value which is not always the case (generally assignments are treated the same way as in shell). This causes failure of grub2-once when used on openstack instances. I suggest the regexp should be more permissive to allow but not require quotes. Something like attached patch. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1045886] New: ecryptfs problems with recent Tumbleweed
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1045886 Bug ID: 1045886 Summary: ecryptfs problems with recent Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ecryptfs and the ecryptfs tools have stopped working correctly on recent versions of Tumbleweed. I noticed this because an existing ecryptfs Private directory could only be seen after a local login. ecryptfs-mount-private over ssh stopped working. On investigation, it is no longer possible to do ecryptfs-setup-private for a new user. $ ecryptfs-setup-private Enter your login passphrase [roger]: Enter your mount passphrase [leave blank to generate one]: ************************************************************************ YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION. ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME. ************************************************************************ Done configuring. Testing mount/write/umount/read... Inserted auth tok with sig [83ecc1d632221288] into the user session keyring Inserted auth tok with sig [90e42628446d371b] into the user session keyring mount: No such file or directory ERROR: Could not mount private ecryptfs directory In the system logs we see: 2017-06-25T07:04:39.396038+01:00 [localhost] kernel: [140502.266628] Could not find key with description: [90e42628446d371b] 2017-06-25T07:04:39.396052+01:00 [localhost] kernel: [140502.266630] process_request_key_err: No key 2017-06-25T07:04:39.396054+01:00 [localhost] kernel: [140502.266631] Could not find valid key in user session keyring for sig specified in mount option: [90e42628446d371b] 2017-06-25T07:04:39.396056+01:00 [localhost] kernel: [140502.266631] One or more global auth toks could not properly register; rc = [-2] 2017-06-25T07:04:39.396072+01:00 [localhost] kernel: [140502.266632] Error parsing options; rc = [-2] $ uname -r 4.11.6-1-default $ grep VERSION_ID /etc/os-release VERSION_ID="20170620" -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 941931] New: GRUB2 graphical menu is extremely slow
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=941931 Bug ID: 941931 Summary: GRUB2 graphical menu is extremely slow Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jmatejek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 643998 --> http://bugzilla.suse.com/attachment.cgi?id=643998&action=edit screen showing output of vbeinfo i'm using an AMD GPU and a 2560x1440 native display. on this configuration, the GRUB2 UI is slow to the point of unusability; it takes a full second to flip from one menu item to another, 3-5s just to display the boot menu, before booting starts. drawing the chameleon logo is visible line-by-line, too lowering the resolution helps, at 1280x960x32 the speed is almost usable, 1280x960x16 is sluggish but OK (so i'm sticking with this resolution for now) my GPU is reported as follows: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] detected graphics modes are attached -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1098354] New: VUL-0: CVE-2018-1002209: quazip: arbitrary file write vulnerability achieved by using a specially crafted zip archive
by bugzilla_noreply＠novell.com 18 Apr '22

18 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098354 Bug ID: 1098354 Summary: VUL-0: CVE-2018-1002209: quazip: arbitrary file write vulnerability achieved by using a specially crafted zip archive Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://smash.suse.de/issue/208490/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: crrodriguez(a)opensuse.org Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1593011 A vulnerability has been found in the way developers have implemented the archive extraction of files. An arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar,xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder. Of course if an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily. This affects multiple libraries that lacks of a high level APIs that provide the archive extraction functionality. References: https://snyk.io/research/zip-slip-vulnerability References: https://bugzilla.redhat.com/show_bug.cgi?id=1593011 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1002209 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1119186] New: KDE:Extra/kdevelop5: Code completion and parser don't work
by bugzilla_noreply＠novell.com 15 Apr '22

15 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1119186 Bug ID: 1119186 Summary: KDE:Extra/kdevelop5: Code completion and parser don't work Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: kde-maintainers(a)suse.de Reporter: krzysio.kurek(a)wp.pl QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- Installed with zypper without any additional parameters. Works with same options on the same project if using AppImage. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1134289] New: ghostscript should not have a hard dependency on AppArmor
by bugzilla_noreply＠novell.com 08 Apr '22

08 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1134289 Bug ID: 1134289 Summary: ghostscript should not have a hard dependency on AppArmor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: max(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As a matter of personal preference I ususally set a "don't install" lock on AppArmor in my installations. But with sr#687694 a hard runtime dependency on apparmor-abstractions was added to the ghostscript package, which in turn pulls other AppArmor packages and makes it impossible to have an AppArmor-free system with ghostscript. As AppArmor is optional, I don't think packages like ghostscript should have such a hard dependency on it. Instead it should either be a weak dependency or no dependency at all. If a hard dependency is needed for some reason the AppArmor stuff for GS should be in an optional subpackage to retain the possibility to install GS without AppArmor. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1115942] New: Fonts in all applications are green and magenta or have a cast of that
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1115942 Bug ID: 1115942 Summary: Fonts in all applications are green and magenta or have a cast of that 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: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've updated to Tumbleweed yesterday morning (2018-11-13) and then all fonts started to have a green an magenta case or are mostly green. See https://xor.cryptomilk.org/pics/fonts.png -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1101663] New: The %_jvmjardir macro is missing from the javapackages-tools package
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1101663 Bug ID: 1101663 Summary: The %_jvmjardir macro is missing from the javapackages-tools package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: tchvatal(a)suse.com Reporter: mls(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While cleaning up obsolete macros in rpm I found that all javapackage macros are now in the javapackages-tools package except %_jvmjardir. %_jvmjardir seems to be used in a couple of packages, so it would be good if that macro also is included in javapackages-tools. The current definition is: %_jvmjardir %{_libdir}/jvm-exports -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1071230] New: java installs symlinks that are not owned by a package
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1071230 Bug ID: 1071230 Summary: java installs symlinks that are not owned by a package Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- java packages install e.g /usr/bin/keytool managed by update-alternatives but those files are not owned by any package. Since the symlink in /usr does not actually change it should be owned by a package. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 994084] New: Tracker bug: make packages own their symlinks in /etc/alternatives/*
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=994084 Bug ID: 994084 Summary: Tracker bug: make packages own their symlinks in /etc/alternatives/* 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: vcuadradojuan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for making all packages using update-alternatives own their symlinks at `/etc/alternatives/*`. Problem: Currently there is a mix of owned and not owned files by packages in `/etc/alternatives/*` (just look at `rpm -qf /etc/alternatives/*`). Currently there seems to be a sizeable chunk of packages not declaring `%ghost %_sysconfdir/alternatives/<binary>`, as specified at [1]. Also, see discussion on opensuse-factory m-l [2]. Once the mass bug filling for the issue is done, I will wait until 1 October for maintainers to action on the bugs, and afterwards I will start fixing each package by hand. Cheers, [1] https://en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines [2] https://lists.opensuse.org/opensuse-factory/2016-08/msg00218.html -- You are receiving this mail because: You are on the CC list for the bug.

2 37

[Bug 931978] New: VUL-0: CVE-2014-9721: zeromq: protocol downgrade attack on sockets using the ZMTP v3 protocol
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=931978 Bug ID: 931978 Summary: VUL-0: CVE-2014-9721: zeromq: protocol downgrade attack on sockets using the ZMTP v3 protocol Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: tchvatal(a)suse.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- rh#1221666 ------------------------------------- It was discovered that zeromq, a lightweight messaging kernel, is susceptible to a protocol downgrade attack on sockets using the ZMTP v3 protocol. This could allow remote attackers to bypass ZMTP v3 security mechanisms by sending ZMTP v2 or earlier headers. CVE request: http://openwall.com/lists/oss-security/2015/05/07/8 Upstream bug report: https://github.com/zeromq/libzmq/issues/1273 Upstream fix: https://github.com/zeromq/zeromq4-x/commit/b6e3e0f601e2c1ec1f3aac880ed6a3fe… ------------------------------------- References: https://bugzilla.redhat.com/show_bug.cgi?id=1221666 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9721 http://seclists.org/oss-sec/2015/q2/515 http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-9721.html -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1105305] New: pencil doesn't run on Leap 15
by bugzilla_noreply＠novell.com 06 Apr '22

06 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1105305 Bug ID: 1105305 Summary: pencil doesn't run on Leap 15 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: aj(a)ajaissle.de Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ pencil Error: Platform version '60.1.0' is not compatible with minVersion >= 4.0 maxVersion <= 52.0 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 953735] New: Change libqt5-creator name to qt5-creator
by bugzilla_noreply＠novell.com 03 Apr '22

03 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=953735 Bug ID: 953735 Summary: Change libqt5-creator name to qt5-creator Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ronisbr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! In Tumbleweed, I have been using the package qt-creator to develop Qt applications for a long time. I have always complained about the old version, since qt-creator is 3.2.2 and the newest version available is 3.5.1. However, it turns out that the newest version is already available in Tumbleweed (and in Leap) under the name libqt5-creator. Is there any good reason to name the package as libqt5-creator? I think this is very confusing. Since it has a lib* in the name, I did not even look at the description, so I was using a very old version all the time. Thus, I am wondering if it is possible to change the name of libqt5-creator to qt5-creator or something else. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1099804] New: Gnucash is unable to retrieve and open guide files in openSUSE LEAP 15.0
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1099804 Bug ID: 1099804 Summary: Gnucash is unable to retrieve and open guide files in openSUSE LEAP 15.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: michele.di.pede(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using openSUSE Leap 15.0 with KDE. Gnucash is not able to locate and open the guide file despite the gnucash-docs package is correctly installed. I tried to dig a bit deeper with this invocation: gnucash --debug --extra --log gnc.gui=debug This is the relevant part of the trace file: [...] * 10:00:08 DEBUG <gnc.gui> [enter ../gnucash/gnome-utils/gnc-file.c:gnc_post_file_open()] filename * 10:00:14 DEBUG <gnc.gui> [gnc_gnome_help] Attempting to opening help uri ghelp:gnucash-guide * 10:00:16 CRIT <gnc.gui> [gnc_gnome_help()] La posizione specificata non è supportata [...] Last trace is the italian translation for "The specified position is not supported". In my system the gnucash configuration file /.gnucash/config.auto is not present despite it is mentioned in gnucash man help file. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1014929] New: GNOME:Apps/gnucash-docs: Bug
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1014929 Bug ID: 1014929 Summary: GNOME:Apps/gnucash-docs: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: adrian.klaver(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Need to add a dependency for yelp to package. Covers the case where the package is being installed on system that is not using GNOME as its desktop, eg using KDE. Without yelp you get the following message when trying to open the GnuCash Help: "GnuCash could not find the files for the help documentation. " even though gnucash-docs is installed. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1091802] New: openldap2: incomplete macro expansion(?) in script
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091802 Bug ID: 1091802 Summary: openldap2: incomplete macro expansion(?) in script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: GuoHouzuo(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com, varkoly(a)suse.com Found By: --- Blocker: --- The following product is going to be upgraded: openSUSE Tumbleweed 20180427-0 -> 20180501-0 x86_64 base openSUSE (38/73) Installing: openldap2-2.4.46-33.1.x86_64 ...................................................[done] Additional rpm output: /usr/sbin/openldap_update_modules_path.sh: line 1: s: command not found Updating /etc/sysconfig/openldap ... -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1040589] New: bash/gcc/gzip/python differ between builds because of profiling
by bugzilla_noreply＠novell.com 31 Mar '22

31 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 Bug ID: 1040589 Summary: bash/gcc/gzip/python differ between builds because of profiling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matz(a)suse.com Found By: Development Blocker: --- In https://build.opensuse.org/project/prjconf/openSUSE:Factory we have %do_profiling 1 and because of that in our bash.spec we enable gcc's 'profile feedback directed optimizations' but that causes the jobs.o and resulting bash binary to differ between builds, even when running on the same build host. And because of that, build-compare always thinks there is a change and triggers a re-publish and rebuild of depending packages We also have such binary diffs in gcc6 and gcc6.spec calls a make profiledbootstrap The do_profiling macro is used in bash gzip hello python3-base python-base sed xz and in http://rb.zq1.de/compare.factory-20170523/bash-compare.out http://rb.zq1.de/compare.factory-20170523/gcc6-compare.out http://rb.zq1.de/compare.factory-20170523/gzip-compare.out http://rb.zq1.de/compare.factory-20170523/python-base-compare.out http://rb.zq1.de/compare.factory-20170523/python3-base-compare.out we have strange diffs in assembler that I could not trace down to other sources of non-determinism until today. Diffs did go away when building without profiling (it was harder to disable for gcc6 and bash though) Do the profiles just count invocations of functions or do they depend on the type and speed of the system? In the first case, it should be possible to fix the profiling runs to be deterministic, but for that it would be useful to be able to see the differences between runs. How could I diff gcc's .gcda files? -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1127000] New: qemu smb share leaves a lot of zombies
by bugzilla_noreply＠novell.com 30 Mar '22

30 Mar '22

http://bugzilla.suse.com/show_bug.cgi?id=1127000 Bug ID: 1127000 Summary: qemu smb share leaves a lot of zombies Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: brogers(a)suse.com Found By: --- Blocker: --- With this commandline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -k en-us -smp 4 -daemonize -pidfile /tmp/qemu.pid.30512 -device virtio-rng-pci -device ich9-usb-ehci1,multifunction=on,id=ehci -device ich9-usb-uhci1,masterbus=ehci.0,multifunction=on -device ich9-usb-uhci2,masterbus=ehci.0,firstport=2,multifunction=on -device ich9-usb-uhci3,masterbus=ehci.0,firstport=4,multifunction=on -drive file=/home/new/win.qcow2,discard=unmap -soundhw ac97 -spice disable-ticketing,gl=on,unix,addr=/tmp/qemu-spice.30512.sock -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -net user,smb=/home/smb,hostfwd=tcp::3389-:3389 -net nic,model=rtl8139 -rtc base=localtime -vga qxl -device usb-tablet -m 1G After some time running, I see a lot of smbd zombie processes: > xslaby 30546 2.4 7.4 2572952 1213920 ? Tl úno24 60:58 /usr/bin/qemu-system-x86_64 -machine accel=kvm -k en-us -smp 4 -daemonize -pidfile /tmp/qemu.pid.30512 -device virtio-rng-pci -device ich9-usb-ehci1,multifunction=on,id=ehci -device ich9-usb-uhci1,masterbus=ehci.0,multifunction=on -device ich9-usb-uhci2,masterbus=ehci.0,firstport=2,multifunction=on -device ich9-usb-uhci3,masterbus=ehci.0,firstport=4,multifunction=on -drive file=/home/new/win.qcow2,discard=unmap -soundhw ac97 -spice disable-ticketing,gl=on,unix,addr=/tmp/qemu-spice.30512.sock -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -net user,smb=/home/smb,hostfwd=tcp::3389-:3389 -net nic,model=rtl8139 -rtc base=loca ltime -vga qxl -device usb-tablet -m 1G > xslaby 30600 0.0 0.1 49892 20088 ? Ss úno24 0:01 \_ /usr/sbin/smbd -l /tmp/qemu-smb.ZIY0XZ -s /tmp/qemu-smb.ZIY0XZ/smb.conf > xslaby 30602 0.0 0.0 45440 4892 ? S úno24 0:00 \_ /usr/sbin/smbd -l /tmp/qemu-smb.ZIY0XZ -s /tmp/qemu-smb.ZIY0XZ/smb.conf > xslaby 30603 0.0 0.0 45432 3328 ? S úno24 0:00 \_ /usr/sbin/smbd -l /tmp/qemu-smb.ZIY0XZ -s /tmp/qemu-smb.ZIY0XZ/smb.conf > xslaby 32070 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 1184 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 2708 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 2902 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 3834 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 4514 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 7508 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 9429 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10975 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 12896 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 14454 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 16387 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 18100 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 19775 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 21479 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 31399 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 2457 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 4636 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 6490 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 8795 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10394 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 12068 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 13606 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 15829 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 17444 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 19211 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 20870 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 22653 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 25946 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 27950 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 29908 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 31403 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 378 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 1887 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 3610 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 5101 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 6557 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 8027 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 9534 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10978 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 12442 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 13894 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 15346 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 16831 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 18284 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 19741 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 21197 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 22659 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 24110 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 25926 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 27476 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 29449 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 30944 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 32378 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 1418 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 2914 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 5694 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 7345 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 8838 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10286 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 11743 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 13175 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 14215 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 15492 0.0 0.0 0 0 ? Z 06:38 0:00 \_ [smbd] <defunct> > xslaby 18349 0.0 0.0 0 0 ? Z 06:53 0:00 \_ [smbd] <defunct> > xslaby 20043 0.0 0.0 0 0 ? Z 07:08 0:00 \_ [smbd] <defunct> > xslaby 21654 0.0 0.0 0 0 ? Z 07:23 0:00 \_ [smbd] <defunct> > xslaby 23364 0.0 0.0 0 0 ? Z 07:38 0:00 \_ [smbd] <defunct> > xslaby 24473 0.0 0.0 0 0 ? Z 07:53 0:00 \_ [smbd] <defunct> > xslaby 26134 0.0 0.0 0 0 ? Z 08:08 0:00 \_ [smbd] <defunct> > xslaby 27373 0.0 0.0 0 0 ? Z 08:23 0:00 \_ [smbd] <defunct> > xslaby 28757 0.0 0.0 0 0 ? Z 08:38 0:00 \_ [smbd] <defunct> > xslaby 29947 0.0 0.0 0 0 ? Z 08:53 0:00 \_ [smbd] <defunct> > xslaby 31154 0.0 0.0 0 0 ? Z 09:08 0:00 \_ [smbd] <defunct> > xslaby 32462 0.0 0.0 0 0 ? Z 09:23 0:00 \_ [smbd] <defunct> > xslaby 1347 0.0 0.0 0 0 ? Z 09:38 0:00 \_ [smbd] <defunct> > xslaby 2581 0.0 0.0 0 0 ? Z 09:53 0:00 \_ [smbd] <defunct> > xslaby 4173 0.0 0.0 0 0 ? Z 10:08 0:00 \_ [smbd] <defunct> > xslaby 5370 0.0 0.0 0 0 ? Z 10:23 0:00 \_ [smbd] <defunct> > xslaby 6652 0.0 0.0 0 0 ? Z 10:38 0:00 \_ [smbd] <defunct> > xslaby 7813 0.0 0.0 0 0 ? Z 10:53 0:00 \_ [smbd] <defunct> > xslaby 9252 0.0 0.0 0 0 ? Z 11:08 0:00 \_ [smbd] <defunct> > xslaby 10823 0.0 0.0 0 0 ? Z 11:23 0:00 \_ [smbd] <defunct> > xslaby 12232 0.0 0.0 0 0 ? Z 11:38 0:00 \_ [smbd] <defunct> > xslaby 13917 0.0 0.0 0 0 ? Z 11:53 0:00 \_ [smbd] <defunct> > xslaby 16442 0.0 0.0 0 0 ? Z 12:08 0:00 \_ [smbd] <defunct> > xslaby 18652 0.0 0.0 0 0 ? Z 12:23 0:00 \_ [smbd] <defunct> They should be reaped when new one starts, IMO. I am using $ qemu-kvm --version QEMU emulator version 3.1.0 from the Virtualization project. But it does not matter, it happens for a long time. -- You are receiving this mail because: You are on the CC list for the bug.

2 9