Groups
Groups
Sign in
Groups
Groups
qubes-users
Conversations
About
Send feedback
Help
Updating Dom0: pkcon crashed
24 views
Skip to first unread message
Ulrich Windl
unread,
Apr 22, 2020, 6:56:07 PM
4/22/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to qubes...@googlegroups.com
When updating Dom0 manually via Qubes Manager, I see these messages in
the journal:
Apr 23 00:44:08 dom0 widget-wrapper[9086]: **
Apr 23 00:44:08 dom0 widget-wrapper[9086]:
PackageKit:ERROR:pk-progress-bar.c:371:pk_progress_bar_init: assertion
failed: (self->priv->tty_fd > 0)
Apr 23 00:44:08 dom0 audit[6590]: ANOM_ABEND auid=1000 uid=1000 gid=1001
ses=3 pid=6590 comm="pkcon" exe="/usr/bin/pkcon" sig=6 res=1
Apr 23 00:44:08 dom0 systemd[1]: Created slice
system-systemd\x2dcoredump.slice.
Apr 23 00:44:08 dom0 systemd[1]: Started Process Core Dump (PID 6592/UID 0).
Apr 23 00:44:08 dom0 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-coredump@0-6592-0 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 23 00:44:08 dom0 widget-wrapper[9086]: /usr/bin/qubes-dom0-update:
line 277: 6590 Aborted (core dumped) pkcon refresh force
Apr 23 00:44:09 dom0 systemd-coredump[6593]: Process 6590 (pkcon) of
user 1000 dumped core.
Stack trace of thread 6590:
#0 0x0000734ee40168df
raise (libc.so.6)
#1 0x0000734ee40184da
abort (libc.so.6)
#2 0x0000734ee4905d55
g_assertion_message (libglib-2.0.so.0)
#3 0x0000734ee4905dea
g_assertion_message_expr (libglib-2.0.so.0)
#4 0x0000561d84a89c86
pk_progress_bar_init (pkcon)
#5 0x0000734ee4bda7fb
g_type_create_instance (libgobject-2.0.so.0)
#6 0x0000734ee4bbc69b
g_object_new_internal (libgobject-2.0.so.0)
#7 0x0000734ee4bbe0ad
g_object_newv (libgobject-2.0.so.0)
#8 0x0000734ee4bbe864
g_object_new (libgobject-2.0.so.0)
#9 0x0000561d84a8a332
pk_progress_bar_new (pkcon)
#10 0x0000561d84a83bf4
main (pkcon)
#11 0x0000734ee4001431
__libc_start_main (libc.so.6)
#12 0x0000561d84a8684a
_start (pkcon)
Stack trace of thread 6591:
#0 0x0000734ee40dcf3d
poll (libc.so.6)
#1 0x0000734ee48df166
g_main_context_iterate.isra.24 (libglib-2.0.so.0)
#2 0x0000734ee48df27c
g_main_context_iteration (libglib-2.0.so.0)
#3 0x0000734ee48df2c1
glib_worker_main (libglib-2.0.so.0)
#4 0x0000734ee4906b93
g_thread_proxy (libglib-2.0.so.0)
#5 0x0000734ee354873a
start_thread (libpthread.so.0)
#6 0x0000734ee40e8e7f
__clone (libc.so.6)
Apr 23 00:44:09 dom0 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-coredump@0-6592-0 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
At that time a terminal was opened asking whether to install the updates.
(I was running manual update as the system seemed to fail suggesting
updates for Dom0)
Reply all
Reply to author
Forward
0 new messages