Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#47900 - Pacman servise crash system.
Attached to Project:
Pacman
Opened by Lubomir (lubo08) - Tuesday, 26 January 2016, 08:29 GMT
Last edited by Allan McRae (Allan) - Tuesday, 26 January 2016, 08:44 GMT
Opened by Lubomir (lubo08) - Tuesday, 26 January 2016, 08:29 GMT
Last edited by Allan McRae (Allan) - Tuesday, 26 January 2016, 08:44 GMT
|
DetailsSummary and Info:
I'm behinde the proxy connection so pacman not work here at all. Just problem is that daemon servise sometime crash the system down on my laptop Samsung 900x series. jan 25 13:19:23 lubo08-pclntb systemd[1]: pamac.service: Main process exited, code=killed, status=11/SEGV jan 25 13:19:23 lubo08-pclntb systemd[1]: pamac.service: Unit entered failed state. jan 25 13:19:23 lubo08-pclntb systemd[1]: pamac.service: Failed with result 'signal'. jan 25 13:19:23 lubo08-pclntb systemd-coredump[3685]: Process 611 (pamac-daemon) of user 0 dumped core. Stack trace of thread 1257: #0 0x00007f2f5ce41a40 n/a (libglib-2.0.so.0) #1 0x00007f2f5ce3e434 g_variant_builder_add_value #2 0x000000000043bc6f n/a (pamac-daemon) #3 0x0000000000434acd n/a (pamac-daemon) #4 0x00007f2f5d0db015 g_closure_invoke (libgobject #5 0x00007f2f5d0ed061 n/a (libgobject-2.0.so.0) #6 0x00007f2f5d0f5dfc g_signal_emit_valist (libgob #7 0x00007f2f5d0f65f5 g_signal_emit_by_name (libgo #8 0x0000000000440a3a n/a (pamac-daemon) #9 0x00007f2f5ddd1e32 n/a (libalpm.so.9) #10 0x00007f2f5ddce9ba n/a (libalpm.so.9) #11 0x00007f2f5ddc8458 alpm_db_update (libalpm.so.9 #12 0x000000000041e4d6 n/a (pamac-daemon) #13 0x000000000041e825 n/a (pamac-daemon) #14 0x00007f2f5ce2d715 n/a (libglib-2.0.so.0) #15 0x00007f2f5cba74a4 start_thread (libpthread.so. #16 0x00007f2f5c8e513d __clone (libc.so.6) Stack trace of thread 614: #0 0x00007f2f5c8dc18d poll (libc.so.6) #1 0x00007f2f5ce06fbc n/a (libglib-2.0.so.0) #2 0x00007f2f5ce07342 g_main_loop_run (libglib-2.0 #3 0x00007f2f5d3fd236 n/a (libgio-2.0.so.0) #4 0x00007f2f5ce2d715 n/a (libglib-2.0.so.0) #5 0x00007f2f5cba74a4 start_thread (libpthread.so. #6 0x00007f2f5c8e513d __clone (libc.so.6) Stack trace of thread 611: #0 0x00007f2f5c877aa4 __libc_free (libc.so.6) #1 0x00007f2f5ddc1eba alpm_list_free_inner (libalp #2 0x00007f2f5ddca4d4 n/a (libalpm.so.9) Steps to Reproduce: System crash sometime. CapsLock start blicking and after few second is system restarted. |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 26 January 2016, 08:44 GMT
Reason for closing: Not a bug
Additional comments about closing: pamac issue
Tuesday, 26 January 2016, 08:44 GMT
Reason for closing: Not a bug
Additional comments about closing: pamac issue
Comment by Allan McRae (Allan) -
Tuesday, 26 January 2016, 08:44 GMT
pamac is not pacman. Unless you can replicate using pacman itself, this is a pamac issue.