November 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1155809] MuseScore-3.3 built in debug mode
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155809 http://bugzilla.suse.com/show_bug.cgi?id=1155809#c2 --- Comment #2 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1155809) was mentioned in https://build.opensuse.org/request/show/745467 Factory / musescore -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155836] sporadic workqueue lockups in sound_hda_core
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155836 http://bugzilla.suse.com/show_bug.cgi?id=1155836#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Assignee|kernel-maintainers(a)forge.pr |tiwai(a)suse.com |ovo.novell.com | --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Hmm, Takashi, it looks like snd_hdac_bus_process_unsol_events is in an infinite loop. I do not see how it could except some weird compiler optimization (negative after reading the assembler). Also, I do not immediately see how a race between snd_hdac_bus_queue_event and already running work is avoided? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155917] New: Recent xrpd update breaks login
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1155917 Bug ID: 1155917 Summary: Recent xrpd update breaks login 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: ginkobonsai(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A recent xrdp update (I suspect the one from Sep 16 2019) broke xrdp login on my TW system. When I tried to log into the TW system with my normal user via xrdp, I got login failed. /var/log/messages showed this: 2019-11-05T12:10:44.277453+01:00 tw_system xrdp-sesman: PAM _pam_load_conf_file: unable to open config for system-auth 2019-11-05T12:10:52.797480+01:00 tw_system xrdp-sesman: message repeated 7 times: [ PAM _pam_load_conf_file: unable to open config for system-auth] Contents of /etc/pam.d/xrdp-sesman: #%PAM-1.0 auth include system-auth account include system-auth password include system-auth session include system-auth /etc/pam.d/system-auth is *NOT* present on my system. Checking the xrdp rpm package from Leap 15.1, I found this xrdp-sesman: #%PAM-1.0 auth include common-auth account include common-account session include common-session password include common-password session required pam_loginuid.so When I replace the first xrdp-sesman pam config with the second, xrdp accepts logins again and I can work normally. Is this some sort of regression or am I missing a package that should contain /etc/pam.d/system-auth? (Or something completely different?) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155824] Cursor lags with mouse and touchpad during CPU spikes
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1155824 http://bugzilla.suse.com/show_bug.cgi?id=1155824#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |pointedstick(a)zoho.com Flags| |needinfo?(pointedstick@zoho | |.com) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Could you check whether the behaviour is the same with the kernel from: https://build.opensuse.org/project/monitor/Kernel:openSUSE-15.0 ? It has preemption completely disabled. And from here: https://build.opensuse.org/project/monitor/home:tiwai:kernel:4.9 It is the last one to have full preemption enabled. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144782] File system filling up? (usr/lib/YaST2/bin/cut-messages: cpio: rename failed - No space left on device)
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1144782 http://bugzilla.suse.com/show_bug.cgi?id=1144782#c30 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com, | |mvidner(a)suse.com Flags| |needinfo?(mvidner(a)suse.com) --- Comment #30 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #29) > > I guess those descriptions are created by the libzypp snapper plugin. > Martin, since you are working in that plugin right now, can you confirm that? Setting the needinfo (got lost by a conflict). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144782] File system filling up? (usr/lib/YaST2/bin/cut-messages: cpio: rename failed - No space left on device)
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1144782 http://bugzilla.suse.com/show_bug.cgi?id=1144782#c29 --- Comment #29 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ulrich Windl from comment #23) > (In reply to Stefan Hundhammer from comment #19) > I had been expecting a state of "dynamic equilibrium" where new snapshots > created would compensate for old snapshots to be deleted. As this was not > the case (and still doesn't look like that), I thought there may be a bug > not reclaiming space from obsolete snapshots. > Such bug could be not deleting obsolete snapshots in the first place, or it > could be a problem with deleted snapshots not freeing up space in a way that > the user sees it, or can use it. > As it turned out during discussion of this issue, at least the descriptions > of the snapshots that are created automatically leaves some potential for > improvement. Descriptions I see today are: > "current" (OK) > "before update" (OK) > "after update" (OK) > "zypp(ruby.ruby2.5)" (not really helpful) > "" (not helpful at all) > "yast online_update" (OK) > "zypp(zypper)" (not really helpful) > > If (just for example) the description would contain a simple statistic > similar to "zypper pchk" (number and type of patches installed) it would be > much more useful. In contrast if you consider this snapshot: > 79 | pre | | 2019-10-28 08:33:55 | root | number | > zypp(ruby.ruby2.5) | important=yes > > What does the output tell you besides that the snapshot was created at > 2019-10-28 08:33:55? I guess those descriptions are created by the libzypp snapper plugin. Martin, since you are working in that plugin right now, can you confirm that? > Finally those systemd snapper services all use systemd-helper that has no > manual page: > ExecStart=/usr/lib/snapper/systemd-helper --cleanup > ExecStart=/usr/lib/snapper/systemd-helper --timeline > # man systemd-helper > No manual entry for systemd-helper > # cat /etc/sysconfig/snapper > ## Path: System/Snapper > ## Type: string > ## Default: "" > # List of snapper configurations. There is a quite extensive and comprehensive documentation regarding snapshots and snapper in (open)SUSE systems. See https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-snapper.html I guess we can try to include some more information in the manpages, for people who still use that instead of the online documentation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1139820] [aarch64] btrfs oops at end of Tumbleweed installation
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1139820 http://bugzilla.suse.com/show_bug.cgi?id=1139820#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber(a)suse.com, | |jslaby(a)suse.com Assignee|kernel-maintainers(a)forge.pr |nborisov(a)suse.com |ovo.novell.com | Flags| |needinfo?(afaerber(a)suse.com | |) --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- Not sure if this still happens with 5.3? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136293] Getting complete system lockups since last week
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1136293 http://bugzilla.suse.com/show_bug.cgi?id=1136293#c18 --- Comment #18 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Shawn Peterson from comment #16) > One last note. I was able to add the following commands to force the gpu to > run at max power. I have done this for the last 3 days whenever testing / > playing a game, and no crashes: > > # echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level > # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk Yes, that is described as a workaround here: https://bugs.freedesktop.org/show_bug.cgi?id=109955#c122 And there is also a patch here: https://bugs.freedesktop.org/show_bug.cgi?id=110777#c47 It might help, but it is not upstream yet. So waiting for upstream to decide what to do with this. (Use the workaround above in the meantime.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144782] File system filling up? (usr/lib/YaST2/bin/cut-messages: cpio: rename failed - No space left on device)
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1144782 http://bugzilla.suse.com/show_bug.cgi?id=1144782#c26 --- Comment #26 from Stefan Hundhammer <shundhammer(a)suse.com> --- (In reply to Ladislav Slezák from comment #24) > Keep in mind that "zypper install foo" and then "zypper remove foo" does not > free any space. The installed package will still be part of a snapshot. That is certainly correct; but with a reasonable cleanup strategy for snapper (see "man snapper") those operations should cancel each other out pretty quickly. Yes, you'll consume the disk space for that package temporarily in one in-between snapshot, but it shouldn't take long until it gets cleaned up, and then that disk space is freed again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144782] File system filling up? (usr/lib/YaST2/bin/cut-messages: cpio: rename failed - No space left on device)
by bugzilla_noreply＠novell.com 05 Nov '19

05 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1144782 http://bugzilla.suse.com/show_bug.cgi?id=1144782#c25 --- Comment #25 from Ladislav Slezák <lslezak(a)suse.com> --- (In reply to Ulrich Windl from comment #23) > "zypp(ruby.ruby2.5)" (not really helpful) > "zypp(zypper)" (not really helpful) These are created by the snapper-zypp-plugin, "zypp" means it was created by the libzypp library, the name in the parenthesis is the process name. That "ruby.ruby2.5" likely belongs to YaST. They could use a full command line (like "/usr/bin/ruby.ruby2.5 --encoding=utf-8 /usr/lib/YaST2/bin/y2start sw_single qt -name YaST2 -icon yast") but that would probably also do not look nice... :-/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0