https://bugs.kde.org/show_bug.cgi?id=463576
Nick Leverton <n...@leverton.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@leverton.org
--- Comment #1 from Nick Leverton <n...@leverton.org> ---
Created attachment 155001
--> https://bugs.kde.org/attachment.cgi?id=155001&action=edit
kded5 backtrace
I think I have the same problem and I am able to provide a bit more detail
about it.
The problem seems to occur when the apper background service finds new updates,
e.g. apper check for updates, Discover check for updates, or periodic checks
configured by kcm_updates. I think that it doesn't always happen, perhaps if
the package cache is already updated by another package manager e.g. apt-get.
gdb against the core dump shows this is where the SIGSEGV occurs in Thread #1:
#3 0x00007f555edf9bd9 in KCrash::defaultCrashHandler(int) (sig=11) at
./src/kcrash.cpp:632
crashRecursionCounter = 2
#4 0x00007f555e391f90 in <signal handler called> () at
/lib/x86_64-linux-gnu/libc.so.6
#5 0x00007f5508377ba4 in PackageKit::Transaction::role() const
(this=this@entry=0x558e597802b0) at ./src/transaction.cpp:297
d = 0x29c704afb29f
#6 0x00007f550880daae in TransactionWatcher::watchTransaction(QDBusObjectPath
const&, bool) (this=this@entry=0x558e5993d170, tid=...,
interactive=interactive@entry=false) at ./apperd/TransactionWatcher.cpp:104
transaction = 0x558e597802b0
#7 0x00007f550880db99 in
TransactionWatcher::transactionListChanged(QStringList const&)
(this=0x558e5993d170, tids=<optimized out>) at
./apperd/TransactionWatcher.cpp:85
tid = @0x7f554c00d190: {d = 0x558e5993d1b0}
__for_range = <optimized out>
There are several other instances with backtraces at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026062
--
You are receiving this mail because:
You are watching all bug changes.
