Bug#945920: Random Chromium crashes
Hello, Been running Chromium for the last 6 hours now, no crash since, so it looks like that last patch finally got it. - Michel
Bug#945920: Random Chromium crashes
Hello, Same here unfortunately. It has fixed the SIGSEGV when opening the Task Manager, but as feared, that crash seems to be separate from the randomly occurring one. - Michel
Bug#945920: Chromium segfaults - backtraces
Thanks to Jaap Joris Vens for helping me figure out why my dumb ass couldn't find the debug package with apt-cache (they're in a separate repo now as the README points out). I've discovered two interesting things, the first one is possibly unrelated: 1. I can reliably cause Chromium to SIGSEGV by opening the Task Manager (Ctrl+Esc). Here's a backtrace from such a crash: Thread 1 "chromium" received signal SIGSEGV, Segmentation fault. 0x5a77cf87 in memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint(int, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () (gdb) bt #0 0x5a77cf87 in memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint(int, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () #1 0x591baaa9 in task_manager::TaskManagerImpl::Refresh() () #2 0x593e7c76 in base::RepeatingTimer::RunUserTask() () #3 0x593b5165 in base::TaskAnnotator::RunTask(char const*, base::PendingTask*) () #4 0x593c466b in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, bool*) () #5 0x593c5fec in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() () #6 0x59376aca in base::(anonymous namespace)::WorkSourceDispatch(_GSource*, int (*)(void*), void*) () #7 0x77064f2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x770651c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7706525c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x59376dd0 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () #11 0x593c62a9 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) () #12 0x593a22fa in base::RunLoop::Run() () #13 0x58ea8217 in ChromeBrowserMainParts::MainMessageLoopRun(int*) () #14 0x571cd1c6 in content::BrowserMainLoop::RunMainMessageLoopParts() () #15 0x571cd375 in content::BrowserMainRunnerImpl::Run() () #16 0x571a35f7 in content::BrowserMain(content::MainFunctionParams const&) () #17 0x58e30101 in content::RunBrowserProcessMain(content::MainFunctionParams const&, content::ContentMainDelegate*) () #18 0x58e30338 in content::ContentMainRunnerImpl::RunServiceManager(content::MainFunctionParams&, bool) () #19 0x58e306a7 in content::ContentMainRunnerImpl::Run(bool) () #20 0x58e66802 in service_manager::Main(service_manager::MainParams const&) () #21 0x58e2e0c6 in content::ContentMain(content::ContentMainParams const&) () #22 0x5635c3e5 in ChromeMain () #23 0x704a1bbb in __libc_start_main (main= 0x56339f80 , argc=1, argv=0x7fffe168, init=out>, fini=, rtld_fini=, stack_end=0x7fffe158) at ../csu/libc-start.c:308 #24 0x5635c22a in _start () (gdb) Might be an unrelated issue though. 2. While running in gbd and watching a YouTube video in full screen, I tried to pause it and couldn't (no cursor, YouTube UI not showing up), only to find it had segfaulted randomly. The video continued to play until I killed the process. This is that backtrace: Thread 1 "chromium" received signal SIGSEGV, Segmentation fault. 0x5a77cee7 in memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vectorstd::char_traits, std::allocator >, std::allocator, std::allocator > > > const&, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () (gdb) bt #0 0x5a77cee7 in memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vectorstd::char_traits, std::allocator >, std::allocator, std::allocator > > > const&, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () #1 0x58f8ddb0 in ProcessMemoryMetricsEmitter::FetchAndEmitProcessMemoryMetrics() () #2 0x58f85e82 in (anonymous namespace)::RecordMemoryMetrics() () #3 0x593b5165 in base::TaskAnnotator::RunTask(char const*, base::PendingTask*) () #4 0x593c466b in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, bool*) () #5 0x593c5fec in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() () #6 0x59376aca in base::(anonymous namespace)::WorkSourceDispatch(_GSource*, int (*)(void*), void*) () #7 0x77064f2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x770651c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7706525c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x59376dd0 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () #11 0x593c62a9 in
Bug#945920: Chromium randomly crashes in the latest version.
Package: chromium Version: 79.0.3945.79-1 Followup-For: Bug #945920 Hello, Seeing these crashes too. HP Elitebook 8470p with Intel i5-3320M and integrated Intel GPU. Running Xfce4. Hopefully the package info is useful in debugging. - Michel -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 79.0.3945.79-1 ii libasound2 1.1.8-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libatomic1 8.3.0-6 ii libatspi2.0-02.30.0-7 ii libavcodec58 7:4.2.1-2 ii libavformat587:4.2.1-2 ii libavutil56 7:4.2.1-2 ii libc62.29-3 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libcups2 2.2.10-6+deb10u1 ii libdbus-1-3 1.12.16-1 ii libdrm2 2.4.97-1 ii libevent-2.1-7 2.1.11-stable-1 ii libexpat12.2.6-2+deb10u1 ii libflac8 1.3.2-3 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.10.1-2 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libharfbuzz0b2.3.1-1 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjsoncpp1 1.7.4-3 ii liblcms2-2 2.9-3 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1+deb10u2 ii libopenjp2-7 2.3.0-2 ii libopus0 1.3-1 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpci3 1:3.5.2-1 ii libpng16-16 1.6.36-6 ii libpulse012.2-4+deb10u1 ii libre2-5 20190101+dfsg-2 ii libsnappy1v5 1.1.7-1 ii libstdc++6 9.2.1-21 ii libva2 2.5.0-2 ii libvpx6 1.8.1-2 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb1 1.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-2 ii libxdamage1 1:1.1.4-3+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.32-2.2~deb10u1 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages chromium recommends: ii chromium-sandbox 78.0.3904.108-1~deb10u1 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+4 ii xdg-utils 1.1.3-1 Versions of packages chromium-common recommends: ii chromium-sandbox 78.0.3904.108-1~deb10u1 ii fonts-liberation 1:1.07.4-9 ii libgl1-mesa-dri 18.3.6-2 ii libu2f-udev 1.1.9-1 ii notification-daemon 3.20.0-4 ii system-config-printer1.5.11-4 ii upower 0.99.10-1 ii xfce4-notifyd [notification-daemon] 0.4.3-1 Versions of packages chromium-sandbox depends on: ii libatomic1 8.3.0-6 ii libc6 2.29-3 ii libgcc1 1:8.3.0-6 ii libstdc++6 9.2.1-21 -- no debconf information
Bug#815319:
Got the same issue here. Applying the suggestions from this bug helped: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813339 (Setting INTERFACESv4 to an actual interface rather than leaving it empty) - Michel
Bug#717312: 'TypeError: daemonize() takes exactly 2 arguments (0 given)' while upgrading
Package: pymsnt Version: 0.11.3-5 Severity: grave Tags: patch Justification: renders package unusable While upgrading the pymsnt package, dpkg bails out in the pre-removal script: dpkg: error processing pymsnt_0.11.3-5.1_all.deb (--install): subprocess new pre-removal script returned error exit status 1 Starting MSN transport for Jabber: Traceback (most recent call last): File /usr/share/pymsnt/PyMSNt.py, line 14, in module main.main() File /usr/share/pymsnt/src/main.py, line 390, in main app = App() File /usr/share/pymsnt/src/main.py, line 331, in __init__ twistd.daemonize() TypeError: daemonize() takes exactly 2 arguments (0 given) invoke-rc.d: initscript pymsnt, action start failed. dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: pymsnt_0.11.3-5.1_all.deb The problem seems to be in line 331 of /usr/share/pymsnt/src/main.py: twistd.daemonize() Changing it to: twistd.daemonize(reactor, os) seems to make it start up. - Michel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pymsnt depends on: ii adduser 3.113+nmu3 ii python 2.7.5-2 ii python-central 0.6.17 ii python-crypto 2.6-5 ii python-openssl 0.13-2+b1 ii python-twisted 13.0.0-1 Versions of packages pymsnt recommends: ii python-imaging 1.1.7-4 Versions of packages pymsnt suggests: ii ejabberd 2.1.10-5 -- Configuration Files: /etc/pymsnt.conf.xml changed [not included] -- no debconf information --- src/main.py 2013-07-19 10:02:34.0 +0200 +++ src/main.py 2013-07-19 10:02:50.0 +0200 @@ -328,7 +328,7 @@ # Daemonise the process and write the PID file if config.background and os.name == posix: - twistd.daemonize() + twistd.daemonize(reactor, os) if config.pid: self.writePID()
Bug#683727: closed by Dmitry Smirnov only...@member.fsf.org (Done: zabbix-server-mysql: Upgrade to 2.0 fails)
As we emphasised in NEWS, README and TODO files, the database upgrade procedure is now completely manual. I read the README.Debian (for the zabbix-server-mysql package) and it didn't mention it. The NEWS file however did, my bad. - Michel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683727: zabbix-server-mysql: Upgrade to 2.0 fails
Package: zabbix-server-mysql Version: 1:2.0.1+dfsg-1 Severity: grave Justification: renders package unusable Hello, During the recent package upgrade, Zabbix-Server was upgraded from 1.8 to 2.0 which resulted in a load of problems, probably due to issues with the DB upgrade (the web interface is complaining about missing fields, graphs, data etc is missing, I'm currently running the /usr/share/zabbix-server-mysql/patch.sql.gz file against my database to see if that can fix it. - Michel -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.37-1-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zabbix-server-mysql depends on: ii adduser 3.113+nmu3 ii debconf 1.5.45 ii fping 3.2-1 ii libc6 2.13-35 ii libcurl3-gnutls 7.26.0-1 ii libiksemel3 1.2-4 ii libldap-2.4-2 2.4.31-1 ii libmysqlclient18 5.5.25a-rel27.1-277.squeeze ii libopenipmi0 2.0.16-1.3 ii libsnmp15 5.4.3~dfsg-2.5 ii libssh2-1 1.4.2-1 ii lsb-base 4.1+Debian7 ii ucf 3.0025+nmu3 Versions of packages zabbix-server-mysql recommends: ii percona-server-server-5.5 [mysql-server] 5.5.25a-rel27.1-277.squeeze ii snmpd 5.4.3~dfsg-2.5 Versions of packages zabbix-server-mysql suggests: ii logrotate3.8.1-4 ii zabbix-frontend-php 1:2.0.1+dfsg-1 -- Configuration Files: /etc/default/zabbix-server changed [not included] -- debconf information: zabbix-server-mysql/password-confirm: (password omitted) zabbix-server-mysql/mysql/admin-pass: (password omitted) zabbix-server-mysql/mysql/app-pass: (password omitted) zabbix-server-mysql/app-password-confirm: (password omitted) zabbix-server-mysql/upgrade-backup: true zabbix-server-mysql/import-oldsettings: zabbix-server-mysql/remote/host: zabbix-server-mysql/dbconfig-remove: zabbix-server-mysql/internal/skip-preseed: false zabbix-server-mysql/remove-error: abort * zabbix-server-mysql/server: zabbix-server-mysql/passwords-do-not-match: zabbix-server-mysql/missing-db-package-error: abort zabbix-server-mysql/db/dbname: zabbix zabbix-server-mysql/remote/newhost: * zabbix-server-mysql/dbconfig-install: true * zabbix-server-mysql/dbconfig-upgrade: true zabbix-server-mysql/mysql/admin-user: root zabbix-server-mysql/remote/port: zabbix-server-mysql/db/app-user: zabbix zabbix-server-mysql/database-type: mysql zabbix-server-mysql/purge: false zabbix-server-mysql/internal/reconfiguring: false zabbix-server-mysql/mysql/method: unix socket * zabbix-server-mysql/upgrade-error: retry (skip questions) zabbix-server-mysql/dbconfig-reinstall: false zabbix-server-mysql/install-error: retry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683727: (no subject)
Update: Running the patch.sql.gz script manually (with -f as it does give some errors) appears to have brought my Zabbix installation back to life. Not sure if the package upgrade wass supposed to do that and skipped it for some reason, or if the schema upgrade was forgotten entirely. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#419888: Maybe working with newer version of spandsp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've managed to recompile asterisk with a snapshot release of spandsp (probably what is to be 0.0.4 once it is released) http://www.soft-switch.org/downloads/spandsp/spandsp-0.0.4pre1.tgz I used: http://www.soft-switch.org/downloads/snapshots/spandsp/spandsp-20070427.tar.gz In addition to that, you need new apps from: http://www.soft-switch.org/downloads/snapshots/spandsp/test-apps-asterisk-1.4/ The patch (use with -p0 in asterisk's root source dir) doesn't apply cleanly (but the failed hunks can be added with some manual work). Apart from that plc.h needs to be copied from that spandsp archive to include/asterisk/plc.h. Note though that I haven't performed anything but basic tests on the app (it doesn't crash on me any more and seems to try to accept a fax). Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGRIIH2Vs+MkscAyURAsFJAJ9PCn+t+zPmAsc704EJFrRRWzFU7ACg1VSk zPxSvNBT0eIX03K7hqYCiAM= =AEGW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419888: asterisk-app-fax: Doesn't work with Asterisk 1.4.x
Package: asterisk-app-fax Version: 0.0.20060218-4 Severity: grave Justification: renders package unusable After installing asterisk 1.4.2~dfsg-4, app-rxfax and app-txfax fail to load with: [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_rxfax.so' did not register itself during load [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_rxfax.so' could not be loaded. [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_txfax.so' did not register itself during load [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_txfax.so' could not be loaded. Not sure which package should handle this but I guess some dependency directives are needed to make sure these packets stay in sync. (I'm currently trying to manually compile a newer version of the spandsp apps but without success so far) Greetings, Michel -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages asterisk-app-fax depends on: ii libc6 2.5-1GNU C Library: Shared libraries ii libspandsp1 0.0.2pre26-1 Telephony signal processing librar Versions of packages asterisk-app-fax recommends: ii gs-common 0.3.11 Common files for different Ghostsc ii libconfig-tiny-perl 2.08-1 Read/Write .ini style files with a ii libfile-sync-perl 0.09-4 Perl interface to sync() and fsync ii liblocale-gettext-perl1.05-1 Using libc functions for internati ii libmime-lite-perl 3.01-8 Perl5 module for convenient genera ii libpaper-utils1.1.21 Library for handling paper charact ii libtiff-tools 3.8.2-7TIFF manipulation and conversion t ii psutils 1.17-24A collection of PostScript documen -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
