[packagekit] Status of x86_64 support?
Matej Cepl
mcepl at redhat.com
Fri Nov 2 09:46:01 PDT 2007
On 2007-11-02, 14:35 GMT, Richard Hughes wrote:
> and then execute "pkcon resolve yumex" in another tab as
> a user.
> When it crashes, please type bt and save that complete output.
My packages are on
http://mcepl.fedorapeople.org/rpms/*ackage*.rpm and when running
per your request (except that I did thread apply all backtrace
instead of pure backtrace) I got (after the crash; sorry the
lines got broken in the slrn):
[pk_debug_init] pk-debug.c:140 (17:39:20): Verbose
debugging enabled
[pk_conf_init] pk-conf.c:129 (17:39:20): config file not
found '../etc/PackageKit.conf'
[pk_conf_init] pk-conf.c:136 (17:39:20): using config
file '/etc/PackageKit/PackageKit.conf'
[main] pk-main.c:214 (17:39:20): daemon shutdown set to
60 seconds
libnm_glib_nm_state_cb: dbus returned an error.
(org.freedesktop.DBus.Error.ServiceUnknown) The name
org.freedesktop.NetworkManager was not provided by any .service
files
[pk_security_init] pk-security-polkit.c:177 (17:39:20): Using
PolicyKit security framework
[pk_transaction_db_init] pk-transaction-db.c:374 (17:39:20):
trying to open database '/var/lib/PackageKit/transactions.db'
[pk_engine_use_backend] pk-engine.c:160 (17:39:20): trying
backend yum
[pk_backend_load] pk-backend.c:158 (17:39:20): Trying to load
: yum
[pk_backend_build_library_path] pk-backend.c:134 (17:39:20):
dlopening '/usr/lib64/packagekit-backend/libpk_backend_yum.so'
[New Thread 1084229968 (LWP 5798)]
[New Thread 46912498489584 (LWP 5795)]
[pk_engine_reset_timer] pk-engine.c:182 (17:39:21): reset
timer
[pk_backend_finalize] pk-backend.c:1753 (17:39:21): freeing
yum (0x63f050)
[pk_inhibit_remove] pk-inhibit.c:201 (17:39:21): cannot
find item 0x63f050
** ERROR **: Error trying to start: Already running on this
machine
aborting...
Program received signal SIGABRT, Aborted.
[Switching to Thread 46912498489584 (LWP 5795)]
0x00000030b2430b65 in *__GI_raise (sig=<value optimized out>)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) thread apply all backtrace
Thread 3 (Thread 46912498489584 (LWP 5795)):
#0 0x00000030b2430b65 in *__GI_raise (sig=<value optimized out>)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00000030b2432610 in *__GI_abort () at abort.c:88
#2 0x0000003baaa374f5 in IA__g_logv (log_domain=0x0,
log_level=<value optimized out>, format=0x417f80 Error trying to
start: %s„, args1=0x7fff09aaffc0)
at gmessages.c:497
#3 0x0000003baaa37593 in IA__g_log (
log_domain=0x16a3 <Address 0x16a3 out of bounds>,
log_level=5795, format=0x6 <Address 0x6 out of bounds>) at
gmessages.c:517
#4 0x0000000000407cd8 in main (argc=1, argv=0x7fff09ab03b8) at
pk-main.c:226
Thread 2 (Thread 1084229968 (LWP 5798)):
#0 0x00000030b24cb0a6 in *__GI___poll (fds=0x6374e0, nfds=2,
timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x0000003baaa31fee in g_main_context_iterate
(context=0x633c90, block=1, dispatch=1, self=<value optimized
out>) at gmain.c:2996
#2 0x0000003baaa324aa in IA__g_main_loop_run (loop=0x6326f0) at
gmain.c:2898
#3 0x0000003bafc064b3 in g_cclosure_marshal_VOID__VOID () at
gmarshal.c:56
#4 0x0000003baaa50774 in g_thread_create_proxy
(data=0x633da0)
at gthread.c:635
#5 0x00000030b3006447 in start_thread () from
/lib64/libpthread.so.0
#6 0x00000030b24d3e5d in clone () from /lib64/libc.so.6
Thread 1 (LWP 5795):
#0 0x00000030b2430b65 in *__GI_raise (sig=<value optimized
out>)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00000030b2432610 in *__GI_abort () at abort.c:88
#2 0x0000003baaa374f5 in IA__g_logv (log_domain=0x0,
log_level=<value optimized out>, format=0x417f80 „Error
trying to start: %s„, args1=0x7fff09aaffc0)
at gmessages.c:497
#3 0x0000003baaa37593 in IA__g_log (
log_domain=0x16a3 <Address 0x16a3 out of bounds>,
log_level=5795, format=0x6 <Address 0x6 out of bounds>) at
gmessages.c:517
#4 0x0000000000407cd8 in main (argc=1, argv=0x7fff09ab03b8) at
pk-main.c:226
0x00000030b2430b65 64 return INLINE_SYSCALL (tgkill,
3, pid, selftid, sig);
(gdb)
> I know you probably know all this, but it may help others of
> the list that are too shy to shout :-)
Sure, as a bugmaster I believe that there is never enough
learning how to get backtraces (hopefully, I haven't missed some
-debuginfo package ;-)).
Best,
Matěj
More information about the PackageKit
mailing list