Bug#1054362: The PackageKit daemon has crashed
Subject: packagekit: The PackageKit daemon has crashed Package: packagekit Version: 1.2.7-1 Severity: normal Dear Maintainer, When I update the system with apper or discover, they stop with message "The PackageKit daemon has crashed I reinstall all the system, same problem occur. Same thing in a VM fresh install Here the log : 22/10/2023 16:40 packagekitd PackageKit:ERROR:../src/pk-transaction.c:5528:pk_transaction> 22/10/2023 16:40 packagekitd Bail out! PackageKit:ERROR:../src/pk-transaction.c:5528:pk_t> 22/10/2023 16:40 systemd Started systemd-coredump@17-462144-0.service - Process Core Dump (PI> 22/10/2023 16:40 systemd Started drkonqi-coredump-processor@17-462144-0.service - Pass system> 22/10/2023 16:40 systemd-coredump Process 461772 (packagekitd) of user 0 dumped core. Module libudev.so.1 from deb systemd-254.5-1.amd64 Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64 Module libsystemd.so.0 from deb systemd-254.5-1.amd64 Stack trace of thread 461772: #0 0x7f9a10fc n/a (libc.so.6 + 0x8a0fc) #1 0x7f953472 raise (libc.so.6 + 0x3c472) #2 0x7f93d4b2 abort (libc.so.6 + 0x264b2) #3 0x7ffdaf08 n/a (libglib-2.0.so.0 + 0x1ef08) #4 0x7fddde041e4e g_assertion_message_expr (libglib-2.0.so.0 + 0x85e4e) #5 0x55bb171fdddc n/a (packagekitd + 0xfddc) #6 0x7ff769c0 g_object_unref (libgobject-2.0.so.0 + 0x1b9c0) #7 0x7ff98dc0 g_value_unset (libgobject-2.0.so.0 + 0x3ddc0) #8 0x7ff85ebd n/a (libgobject-2.0.so.0 + 0x2aebd) #9 0x7ff8c186 g_signal_emit_valist (libgobject-2.0.so.0 + 0x31186) #10 0x7ff8c243 g_signal_emit (libgobject-2.0.so.0 + 0x31243) #11 0x55bb17200992 pk_transaction_set_state (packagekitd + 0x12992) #12 0x55bb1720728d n/a (packagekitd + 0x1928d) #13 0x7fe7fc9c n/a (libgio-2.0.so.0 + 0x111c9c) #14 0x7fddde013099 n/a (libglib-2.0.so.0 + 0x57099) #15 0x7fddde0162d7 n/a (libglib-2.0.so.0 + 0x5a2d7) #16 0x7fddde016bdf g_main_loop_run (libglib-2.0.so.0 + 0x5abdf) #17 0x55bb171fbef1 main (packagekitd + 0xdef1) #18 0x7f93e6ca n/a (libc.so.6 + 0x276ca) #19 0x7f93e785 __libc_start_main (libc.so.6 + 0x27785) #20 0x55bb171fc091 _start (packagekitd + 0xe091) Stack trace of thread 462141: #0 0x7fdddad165fd _ZN13debListParser12ParseDependsEPKcS1_RN3APT10StringViewES4_RjbbbNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libapt-pkg.so.6.0 + 0x1165fd) #1 0x7fdddad17ba4 n/a (libapt-pkg.so.6.0 + 0x117ba4) #2 0x7fdddad19685 n/a (libapt-pkg.so.6.0 + 0x119685) #3 0x7fdddad9f0c2 n/a (libapt-pkg.so.6.0 + 0x19f0c2) #4 0x7fdddada1776 n/a (libapt-pkg.so.6.0 + 0x1a1776) #5 0x7fdddad7f1d5 _ZN18pkgDebianIndexFile5MergeER17pkgCacheGeneratorP10OpProgress (libapt-pkg.so.6.0 + 0x17f1d5) #6 0x7fdddad9b091 n/a (libapt-pkg.so.6.0 + 0x19b091) #7 0x7fdddad9cf87 n/a (libapt-pkg.so.6.0 + 0x19cf87) #8 0x7fdddada46ba n/a (libapt-pkg.so.6.0 + 0x1a46ba) #9 0x7fdddacb98f1 _ZN12pkgCacheFile11BuildCachesEP10OpProgressb (libapt-pkg.so.6.0 + 0xb98f1) #10 0x7fdddacb9c48 _ZN12pkgCacheFile4OpenEP10OpProgressb (libapt-pkg.so.6.0 + 0xb9c48) #11 0x7f3399e0 _ZN12AptCacheFile4OpenEb (libpk_backend_apt.so + 0x219e0) #12 0x7f33f244 _ZN6AptJob4initEPPc (libpk_backend_apt.so + 0x27244) #13 0x7f3361e1 n/a (libpk_backend_apt.so + 0x1e1e1) #14 0x55bb17211e4a n/a (packagekitd + 0x23e4a) #15 0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1) #16 0x7f99f3ec n/a (libc.so.6 + 0x883ec) #17 0x7fa1fa4c n/a (libc.so.6 + 0x108a4c) Stack trace of thread 461778: #0 0x7fa12a1f __poll (libc.so.6 + 0xfba1f) #1 0x7fddde016237 n/a (libglib-2.0.so.0 + 0x5a237) #2 0x7fddde016bdf g_main_loop_run (libglib-2.0.so.0 + 0x5abdf) #3 0x7fe90dfa n/a (libgio-2.0.so.0 + 0x122dfa) #4 0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1) #5 0x7f99f3ec n/a (libc.so.6 + 0x883ec) #6 0x7fa1fa4c n/a (libc.so.6 + 0x108a4c) Stack trace of thread 461779: #0 0x7fa17ee9 syscall (libc.so.6 + 0x100ee9) #1 0x7fddde071b70 g_cond_wait_until (libglib-2.0.so.0 + 0xb5b70) #2 0x7ffe0133 n/a (libglib-2.0.so.0 + 0x24133) #3 0x7fddde0443ea n/a (libglib-2.0.so.0 + 0x883ea) #4 0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1) #5 0x7f99f3ec n/a (libc.so.6 + 0x883ec) #6 0x7fa1fa4c n/a (libc.so.6 + 0x108a4c) Stack trace of thread 461777: #0 0x7fa12a1f __poll (libc.so.6 + 0xfba1f) #1 0x7fddde016237 n/a (libglib-2.0.so.0 + 0x5a237) #2 0x7fddde0168f0 g_main_context_iteration (libglib-2.0.so.0 + 0x5a8f0) #3 0x7fddde016941 n/a (libglib-2.0.so.0 + 0x5a941) #4 0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1) #5 0x7f99f3ec n/a (libc.so.6 + 0x883ec) #6 0x7fa1fa4c n/a (libc.so.6 + 0x108a4c) Stack trace of thread 461776: #0 0x7fa17ee9 syscall (libc.so.6 + 0x100ee9) #1
Bug#795556: konsole loop continously after close with core up 100%
Package: konsole Version: 4:15.04.3-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable-updates'), (800, 'stable'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages konsole depends on: ii konsole-kpart 4:15.04.3-2 ii konsole4-kpart 4:4.14.2-3 ii libc6 2.19-19 ii libkf5completion5 5.12.0-1 ii libkf5configcore5 5.12.0-1 ii libkf5configgui55.12.0-1 ii libkf5configwidgets55.12.0-1 ii libkf5coreaddons5 5.12.0-1 ii libkf5i18n5 5.12.0-1 ii libkf5iconthemes5 5.12.0-1 ii libkf5kdelibs4support5 5.12.0-2 ii libkf5kiowidgets5 5.12.0-1 ii libkf5notifyconfig5 5.12.0-1 ii libkf5widgetsaddons55.12.0-1 ii libkf5windowsystem5 5.12.0-1 ii libkf5xmlgui5 5.12.0-1 ii libqt5core5a5.4.2+dfsg-5 ii libqt5gui5 5.4.2+dfsg-5 ii libqt5widgets5 5.4.2+dfsg-5 ii libstdc++6 5.1.1-14 konsole recommends no packages. konsole suggests no packages. -- no debconf information
Bug#795471: kdegames: no possibility to launch kdegames
Package: kdegames Version: 4:4.12+5.88 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable-updates'), (800, 'stable'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdegames depends on: ii bomber4:4.12.4-1 ii bovo 4:4.11.3-2 ii granatier 4:4.14.2-1 ii kapman4:4.12.4-1 ii katomic 4:4.12.4-1 ii kblackbox 4:4.11.3-2 ii kblocks 4:4.14.2-1 ii kbounce 4:4.14.0-1 ii kbreakout 4:4.13.1-1 ii kdiamond 4:4.13.3-1 ii kfourinline 4:4.14.0-1 ii kgoldrunner 4:4.12.2-2 ii kigo 4:4.14.1-1 ii killbots 4:4.14.0-1 ii kiriki4:4.13.2-1 ii kjumpingcube 4:4.13.1-1 ii klickety 4:4.12.4-1 ii klines4:4.12.2-2 ii kmahjongg 4:4.14.0-1 ii kmines4:4.13.1-1 ii knavalbattle 4:4.13.3-1 ii knetwalk 4:4.12.4-1 ii kolf 4:4.14.1-1 ii kollision 4:4.12.4-1 ii konquest 4:4.14.0-1 ii kpat 4:4.13.1-1 ii kreversi 4:4.13.1-1 ii kshisen 4:4.13.1-1 ii ksirk 4:4.14.0-1 ii ksnakeduel4:15.04.3-1 ii kspaceduel4:4.12.2-2 ii ksquares 4:4.12.2-2 ii ksudoku 4:4.13.3-1 ii ktuberling4:4.14.0-1 ii kubrick 4:4.12.2-2 ii lskat 4:4.14.0-1 ii palapeli 4:4.14.0-1 ii picmi 4:4.13.3-1 Versions of packages kdegames recommends: ii kajongg 4:4.14.1-1 kdegames suggests no packages. -- no debconf information
Bug#767201: virtualbox: After update to 4.3.18-dfsg-1 guests doesn't start
After update to the last VirtualBox Extension Pack, the problem went away also. Inthenextupdatetovirtualbox,itwill haveto thinkabout it... -- Pascal Raton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767201: virtualbox: After update to 4.3.18-dfsg-1 guests doesn't start
HI. I have also this problem after update to 4.3.18-dfsg-1. I started virtualbox with this command: virtualbox --dbg --startvm Win7 and i have only this message when virtualbox crash : Erreur de segmentation (or segmentation error in english). No others messages. Thanks for your help -- Pascal Raton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
