[Bug 1221763] New: ptrace(PTRACE_ATTACH) fails on processes of the same user
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Bug ID: 1221763 Summary: ptrace(PTRACE_ATTACH) fails on processes of the same user Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: giuliano.belinassi@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Recent updates of tumbleweed broke `ptrace(PTRACE_ATTACH, ...)` when attaching to a process from the same user. This breaks attaching a debugger (gdb) to a process and userspace livepatching. A single line reproducer in a clean system is: ``` $ sleep 5000 & gdb -p $(pidof sleep) ``` If you see the following message: ``` Attaching to process 12606 ptrace: Operation not permitted. ``` This means ptrace is not working. As a contrast, running gdb with sudo works as intended. Value of /proc/sys/kernel/yama/ptrace_scope: ``` $ cat /proc/sys/kernel/yama/ptrace_scope 1 ``` -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c1 --- Comment #1 from Giuliano Belinassi <giuliano.belinassi@suse.com> --- $ uname -a Linux localhost.localdomain 6.7.9-1-default #1 SMP PREEMPT_DYNAMIC Thu Mar 7 06:07:11 UTC 2024 (6049de6) x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240318" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240318" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240318:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240318" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Michael Matz <matz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Martin Jambor <mjambor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjambor@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c2 Michael Matz <matz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com --- Comment #2 from Michael Matz <matz@suse.com> --- Seems to have come in via https://bugzilla.suse.com/show_bug.cgi?id=1128245 CCing Jiri. Maybe it's only the support at all that came in via the above and not the default switch to "on"? Either way, I don't think having this on by default is a good idea, it prevents _each and all_ ptrace to non-childs (and hence debugging of running processes in general), when not being root. People who want system-wide ptrace separation (and for unknown reasons don't want to use real sandboxes, like separate PID namespaces!?#) can enable this on an opt-in basis. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c3 --- Comment #3 from Jiri Slaby <jslaby@suse.com> --- yama (and others) were enabled only in commit 720c38318edb68b138a4bc4c86bb8ff0fbcda672 Author: Jeff Mahoney <jeffm@suse.com> Date: Thu Dec 8 14:32:18 2022 -0500 config: update CONFIG_LSM defaults (bsc#1205603). via bug 1205603. I wonder how it came noone noticed until now? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c4 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |giuliano.belinassi@suse.com Flags| |needinfo?(giuliano.belinass | |i@suse.com) --- Comment #4 from Jiri Slaby <jslaby@suse.com> --- (In reply to Giuliano Belinassi from comment #0)
Recent updates of tumbleweed broke `ptrace(PTRACE_ATTACH, ...)` when attaching to a process from the same user. This breaks attaching a debugger (gdb) to a process and userspace livepatching. A single line reproducer in a clean system is:
``` $ sleep 5000 & gdb -p $(pidof sleep) ```
If you see the following message:
``` Attaching to process 12606 ptrace: Operation not permitted. ``` This means ptrace is not working. As a contrast, running gdb with sudo works as intended.
Value of /proc/sys/kernel/yama/ptrace_scope: ``` $ cat /proc/sys/kernel/yama/ptrace_scope 1 ```
So this actually works as expected and was supposed to work like this forever. Could you clarify what "Recent updates of tumbleweed" broke this? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c5 Tom de Vries <tdevries@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tdevries@suse.com --- Comment #5 from Tom de Vries <tdevries@suse.com> --- I can confirm this. I booted into tumbleweed, and looked at the value of /proc/sys/kernel/yama/ptrace_scope. It was 0. Then I did zypper dup, and it changed to 1. Same after a reboot. I worked around this by adding "kernel.yama.ptrace_scope = 1" in /etc/sysctl.conf. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c6 --- Comment #6 from Martin Jambor <mjambor@suse.com> --- (In reply to Jiri Slaby from comment #4)
Could you clarify what "Recent updates of tumbleweed" broke this?
I'm not sure if it helps but the most recent TW that I can find where /proc/sys/kernel/yama/ptrace_scope still defaults to 0 is "20240209." For example TW with version "20240218" already defaults to 1. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c7 --- Comment #7 from Jiri Slaby <jslaby@suse.com> --- (In reply to Martin Jambor from comment #6)
(In reply to Jiri Slaby from comment #4)
Could you clarify what "Recent updates of tumbleweed" broke this?
I'm not sure if it helps but the most recent TW that I can find where /proc/sys/kernel/yama/ptrace_scope still defaults to 0 is "20240209." For example TW with version "20240218" already defaults to 1.
Do you switch between snapshots or only kernels? 1 is the default for over a decade in the kernel. Maybe we used to set it in some package to 0 in /usr/lib/sysctl.d? Could you: grep -r ptrace_scope /usr/lib/sysctl* /etc/sysctl* in 20240209? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c8 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs@opensuse.org |jsegitz@suse.com Component|Kernel |Basesystem --- Comment #8 from Jiri Slaby <jslaby@suse.com> --- Got it. /usr/lib/sysctl.d/52-yama.conf coming from aaa_base the change is: https://build.opensuse.org/package/rdiff/Base:System/aaa_base?linkrev=base&rev=772 coming from: https://github.com/openSUSE/aaa_base/commit/b59d2fdb3c03b1a85fd49d6f2f4b2b71... Without any explanation or reference. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c9 --- Comment #9 from Jiri Slaby <jslaby@suse.com> --- The PR is more verbose: https://github.com/openSUSE/aaa_base/pull/138 So this boils down to bug 1217051. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c10 --- Comment #10 from Johannes Segitz <jsegitz@suse.com> --- that's how it should be after the change. Users with different needs (which shouldn't be too many, not a lot of users do debugging of running processes) should change the sysctl setting -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c11 --- Comment #11 from Tom de Vries <tdevries@suse.com> --- If ptrace_scope=1 remains the default, this ( https://wiki.archlinux.org/title/Capabilities ) suggests a way of dealing with it without becoming root: ... $ sudo -E capsh --caps="cap_setpcap,cap_setuid,cap_setgid+ep cap_sys_ptrace+eip" --keep=1 --user="$USER" --addamb="cap_sys_ptrace" --shell=/usr/bin/gdb -- -p <pid> ... [ Doesn't work for me though on openSUSE Leap 15.4, I get "usage: capsh [args ...]", to be debugged. ] I've filed a gdb PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=31520 ) pointing out that IWBN to have a script somewhere that supports this. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c12 --- Comment #12 from Tom de Vries <tdevries@suse.com> --- (In reply to Tom de Vries from comment #11)
[ Doesn't work for me though on openSUSE Leap 15.4, I get "usage: capsh [args ...]", to be debugged. ]
Scripting problems... This works: ... $ cat sudo-allow-ptrace.sh #!/bin/sh shell="$1" shift set -x sudo \ -E capsh \ --caps="cap_setpcap,cap_setuid,cap_setgid+ep cap_sys_ptrace+eip" \ --keep=1 \ --user="$USER" \ --addamb="cap_sys_ptrace" \ --shell=$shell -- \ "$@" $ sleep 60 & ./sudo-allow-ptrace.sh gdb -p $(pidof sleep) ... $ ... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c13 --- Comment #13 from Giuliano Belinassi <giuliano.belinassi@suse.com> --- In summary: will this change be reverted or we will have to handle it as a new default? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Giuliano Belinassi <giuliano.belinassi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(giuliano.belinass | |i@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c14 --- Comment #14 from Michael Matz <matz@suse.com> --- (In reply to Johannes Segitz from comment #10)
that's how it should be after the change. Users with different needs (which shouldn't be too many, not a lot of users do debugging of running processes) should change the sysctl setting
So, just to be sure I completely understand that: because "Archer Allstars" complains about chrome sandboxing showing stuff in "red" and somewhere says "no", the security team implemented this change without further discussion (or rather: after it actually got rejected in jira) and without clear documentation of how to get back a working system (or that such a far-reaching change was done at all, a .changes entry in aaa_base reading "Restrict ptrace with Yama LSM by default" goes unnoticed). Well, super. And there I thought the whole namespace container stuff was done for separation, just to see that the non-containerized distro now goes down the drain as well. So, how can I disable yama? The whole module, all of it, not just this ptrace_scope. I don't want to fiddle with it again if the security team decides to further "enhance security" by randomly enabling other good-sounding options like "disable syscalls". -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c15 --- Comment #15 from Johannes Segitz <jsegitz@suse.com> --- That's not really how it came to be, but I get the feeling that you're not really interested in a constructive dialogue, so lets not simulate one. Just set the sysctl that matches your use case, so for you kernel.yama.ptrace_scope=0 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c16 --- Comment #16 from Michael Matz <matz@suse.com> --- (In reply to Johannes Segitz from comment #15)
That's not really how it came to be, but I get the feeling that you're not really interested in a constructive dialogue, so lets not simulate one.
Indeed.
Just set the sysctl that matches your use case, so for you kernel.yama.ptrace_scope=0
After reading https://github.com/torvalds/linux/blob/master/security/yama/yama_lsm.c it's really only ptrace that yama deals with, so that sysctl is indeed the only thing necessary to disable all of it. Further, if I read the kernel docu correctly I should be able to disable all LSMs by adding 'lsm=capability' to the boot command line, which integrates better with the disabling of spectre mitigations I'm doing anyway. So I'll (try to) add that to my list of things to do on new machine installs. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c17 Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert@suse.com --- Comment #17 from Marcus Rückert <mrueckert@suse.com> --- why not just add a sysctl file that gets installed with kernel-obs-build and be done? and i dont see why disabling spectre things in the build time kernel should be done. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c18 --- Comment #18 from Giuliano Belinassi <giuliano.belinassi@suse.com> --- (In reply to Marcus Rückert from comment #17)
why not just add a sysctl file that gets installed with kernel-obs-build and be done? and i dont see why disabling spectre things in the build time kernel should be done.
We are experimenting with a custom package for that: https://build.opensuse.org/package/show/home:gbelinassi/yama-disable-ptrace-... using /usr/sbin/sysctl -w kernel.yama.ptrace_scope=0 on %post seems to work for libpulp on tumbleweed. We will check if it also works for gdb. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c19 --- Comment #19 from Marcus Rückert <mrueckert@suse.com> --- yeah and a much cleaner approach would be shipping a proper file in kernel-obs-build -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Martin Jambor <mjambor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1217051 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c21 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com --- Comment #21 from Ludwig Nussel <lnussel@suse.com> --- RFC https://github.com/openSUSE/aaa_base/pull/149 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c22 --- Comment #22 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-RU-2024:1785-1: An update that has two fixes can now be installed. Category: recommended (moderate) Bug References: 1221763, 1223306 Maintenance Incident: [SUSE:Maintenance:33680](https://smelt.suse.de/incident/33680/) Sources used: openSUSE Leap 15.4 (src): libpulp-0.3.3-150400.3.26.2 openSUSE Leap 15.5 (src): libpulp-0.3.3-150400.3.26.2 openSUSE Leap 15.6 (src): libpulp-0.3.3-150400.3.26.2 SUSE Linux Enterprise Live Patching 15-SP4 (src): libpulp-0.3.3-150400.3.26.2 SUSE Linux Enterprise Live Patching 15-SP5 (src): libpulp-0.3.3-150400.3.26.2 SUSE Linux Enterprise Live Patching 15-SP6 (src): libpulp-0.3.3-150400.3.26.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c25 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #25 from Johannes Segitz <jsegitz@suse.com> --- we have aaa_base-yama-enable-ptrace package now available to make changing behavior easier. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c26 Giuliano Belinassi <giuliano.belinassi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #26 from Giuliano Belinassi <giuliano.belinassi@suse.com> --- (In reply to Johannes Segitz from comment #25)
we have aaa_base-yama-enable-ptrace package now available to make changing behavior easier.
Which seems to not be working. https://build.opensuse.org/projects/home:gbelinassi/packages/libpulp/files/l... This is the specfile for libpulp. The two interesting lines here are:
BuildRequires: aaa_base-yama-enable-ptrace BuildRequires: yama-disable-ptrace-scope
The first one is the package provided in Factory and Tumbleweed. If libpulp is built with only this package testsuite fails. The second package is the one that I created back when this issue showed up that (should) have the same semantic effect. If libpulp is built with it, the testsuite passes. Hence there is something wrong with aaa_base-yama-enable-ptrace. Libpulp checks if ptrace works by forking a dummy process and attempting to ptrace it. If it fails with EPERM then it errors out. Here is the code for yama-disable-ptrace-scope: https://build.opensuse.org/projects/home:gbelinassi/packages/yama-disable-pt... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c27 --- Comment #27 from Johannes Segitz <jsegitz@suse.com> --- the current aaa_base package requires a reboot to become effective. That's suboptimal. You're approach will not survive a reboot. That's also suboptimal ;) I'll combine both and submit for this -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c28 --- Comment #28 from Johannes Segitz <jsegitz@suse.com> --- hm weird, this doesn't happen on non-build environments, there it sets the value directly. I don't see yet why -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c29 --- Comment #29 from Johannes Segitz <jsegitz@suse.com> --- This is strange. There's nothing in the package to set the value upon installation. Yet it happens: $ sysctl kernel.yama.ptrace_scope kernel.yama.ptrace_scope = 1 $ zypper in aaa_base-yama-enable-ptrace $ sysctl kernel.yama.ptrace_scope kernel.yama.ptrace_scope = 0 It's not systemd-sysctl.service, that one only runs on boot. The directory is also not monitored, just moving a file there doesn't change the setting -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c30 --- Comment #30 from Jiri Slaby <jslaby@suse.com> --- rpm says: aaa_base-yama-enable-ptrace-84.87+git2D: create 100644 1 ( 0, 0) 1001 /usr/lib/sysctl.d/52-yama.conf;66b5ca72 ####################################D: Plugin: calling hook fsm_file_prepare in fapolicyd plugin D: Plugin: calling hook fsm_file_prepare in selinux plugin D: lsetfilecon: (10 /usr/lib/sysctl.d/52-yama.conf;66b5ca72, system_u:object_r:lib_t:s0) #### -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c31 --- Comment #31 from Jiri Slaby <jslaby@suse.com> --- (In reply to Jiri Slaby from comment #30)
rpm says: aaa_base-yama-enable-ptrace-84.87+git2D: create 100644 1 ( 0, 0) 1001 /usr/lib/sysctl.d/52-yama.conf;66b5ca72 ####################################D: Plugin: calling hook fsm_file_prepare in fapolicyd plugin D: Plugin: calling hook fsm_file_prepare in selinux plugin D: lsetfilecon: (10 /usr/lib/sysctl.d/52-yama.conf;66b5ca72, system_u:object_r:lib_t:s0) ####
That's not interesting, but: D: %transfiletriggerin(systemd-255.8-1.1.x86_64): running <lua> scriptlet. So this is bottom of: https://build.opensuse.org/projects/Base:System/packages/systemd/files/trigg... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c32 --- Comment #32 from Giuliano Belinassi <giuliano.belinassi@suse.com> --- Any news on this? SLFO milestone deadline is close and libpulp was requested to be there. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c33 --- Comment #33 from Tom de Vries <tdevries@suse.com> --- I've added this to the gdb package in devel:gcc ... BuildRequires: aaa_base-yama-enable-ptrace ... and removed the kfails related to this problem. After committing, the fails are back, so the package doesn't work. For now, I'll add back the kfails. Is anybody working on making the aaa_base-yama-enable-ptrace package work as advertised, given that it doesn't seem to work for the two packages that actually need it? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org Priority|P5 - None |P1 - Urgent -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Libor Miksik <libor.miksik@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1230142 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c35 --- Comment #35 from Johannes Segitz <jsegitz@suse.com> --- The package is working as advertised in normal systems. We have something strange in our build setup that breaks the normal behaviour identified by Jiri in https://bugzilla.suse.com/show_bug.cgi?id=1221763#c31. I'll have a look at this later today and also will bring this to autobuilds attention. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c36 --- Comment #36 from Johannes Segitz <jsegitz@suse.com> --- The automatism in the package doesn't work in our build environments, since we don't use systemd there. As soon as https://github.com/openSUSE/aaa_base/pull/166 is merged I'll submit for openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 Dirk Mueller <dmueller@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c43 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #43 from Johannes Segitz <jsegitz@suse.com> --- Fixed in Factory and SLFO -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com