http://bugzilla.opensuse.org/show_bug.cgi?id=905369 Mikhail Kasimov changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Summary|systemdadm segfaults on |systemadm segfaults on |error 4 libc-2.19.so while |error 4 libc-2.19.so while |changing service status in |changing service status in |console |console -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905369 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |bwiedemann@suse.com Component|Other |Other Version|Final |13.2 Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | Product|openSUSE 13.1 |openSUSE Distribution Target Milestone|Final |--- --- Comment #1 from Bernhard Wiedemann --- #0 0x00007f4c9bcb2bda in strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x00007f4c9c52d703 in g_strdup (str=0x1 ) at gstrfuncs.c:355 #2 0x00007f4c9c80a9ad in value_collect_string (value=0x7fffc968cd90, n_collect_values=<optimized out>, collect_values=<optimized out>, collect_flags=<optimized out>) at gvaluetypes.c:291 #3 0x00007f4c9cf84b7e in gtk_list_store_set_valist_internal (list_store=list_store@entry=0x110dcc0 [GtkListStore], iter=iter@entry=0x7fffc968cfc0, emit_signal=emit_signal@entry=0x7fffc968ce38, maybe_need_sort=maybe_need_sort@entry=0x7fffc968ce3c, var_args=var_args@entry=0x7fffc968ce68) at gtkliststore.c:1033 #4 0x00007f4c9cf855d7 in gtk_list_store_set_valist (list_store=0x110dcc0 [GtkListStore], iter=0x7fffc968cfc0, var_args=var_args@entry=0x7fffc968ce68) at gtkliststore.c:1137 #5 0x00007f4c9cf856e7 in gtk_list_store_set (list_store=list_store@entry=0x110dcc0 [GtkListStore], iter=iter@entry=0x7fffc968cfc0) at gtkliststore.c:1179 #6 0x000000000040992a in main_window_update_job_iter (self=self@entry=0xf36350 [MainWindow], iter=iter@entry=0x7fffc968d0b0, id=id@entry=1451, j=j@entry=0x161a870) at /home/kay/data/src/systemd-ui/src/systemadm.vala:765 #7 0x000000000040b249 in main_window_on_job_new (self=0xf36350 [MainWindow], id=1451, path=0x1cf5960 "/org/freedesktop/systemd1/job/1451") at /home/kay/data/src/systemd-ui/src/systemadm.vala:793 #11 0x00007f4c9c7fd532 in

http://bugzilla.opensuse.org/show_bug.cgi?id=905369 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com Flags| |needinfo?(fcrozat@suse.com) --- Comment #3 from Dr. Werner Fink --- I'm not familiar with systemd-ui nor with systemdadm. @Frederic? What's going on here? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905369 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |GNOME Flags|needinfo?(fcrozat@suse.com) | --- Comment #5 from Frederic Crozat --- Reassignig to GNOME people, it looks like a bug in this application, which is a vala application. Easy way to reproduce: start the application and switch to a new VT : it will cause a getty@... to be started (it looks like the bug is related to instanciated units). systemd-ui is more or less in limbo, unfortunately upstream. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905369 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |dimstar@opensuse.org Resolution|--- |FIXED --- Comment #7 from Dominique Leuenberger --- Can;t really see how this is a GNOME bug (you maintain a program that interacts invalud with a license and are surprised it crashes) Submitted an update for systemd-ui to version 3 (from upstream) plus a patch taking care of better handling notifications (also from upstream). With the new version, I can have systemadm started, switch to vtty5 (spawning a new process) and switch back to 7 without it crashing (did not work with version 2). so: all in all: I fail to see how this was even considered to be a GNOME bug. -- You are receiving this mail because: You are on the CC list for the bug.