[arch-general] chromium crash when print dialog is invoked
I started experiencing a severe problem with Chromium recently that makes web browsing a very tedious experience. It took a while to narrow it down, but it seems that whenever the print dialog is invoked, either manually (eg ctrl-P on the keyboard) or by a page when clicking on the "printer friendly format" link, the entire browser crashes. This happens on two separate Arch installs. I personally would love a method to disable the printer dialog from ever popping up anyway, since I don't even have one (so if someone can suggest a method, I'd love to hear it), but this bug is a serious problem, as the crash is unrecoverable. And if my session ends up with a page that invokes the dialog on its own, I have to clear out the entire session. Has anyone else experienced this problem? Can anyone suggest a solution?
Scott Weisman <sweisman@pobox.com> writes:
I started experiencing a severe problem with Chromium recently that makes web browsing a very tedious experience.
It took a while to narrow it down, but it seems that whenever the print dialog is invoked, either manually (eg ctrl-P on the keyboard) or by a page when clicking on the "printer friendly format" link, the entire browser crashes. This happens on two separate Arch installs.
I personally would love a method to disable the printer dialog from ever popping up anyway, since I don't even have one (so if someone can suggest a method, I'd love to hear it), but this bug is a serious problem, as the crash is unrecoverable. And if my session ends up with a page that invokes the dialog on its own, I have to clear out the entire session.
Has anyone else experienced this problem? Can anyone suggest a solution?
I had not, but I can confirm the behaviour with chromium 20.0.1132.57-2 on x86_64, running xmonad. I get a total freeze of chromium (have to kill -9) if I hit C-p, or hit "print" from the menu. -- Jeremiah Dodds github : https://github.com/jdodds freenode : exhortatory
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/01/2012 12:42 AM, Jeremiah Dodds wrote:
Scott Weisman <sweisman@pobox.com> writes:
Has anyone else experienced this problem? Can anyone suggest a solution?
I had not, but I can confirm the behaviour with chromium 20.0.1132.57-2 on x86_64, running xmonad. I get a total freeze of chromium (have to kill -9) if I hit C-p, or hit "print" from the menu.
We could spend a lot of time trying to eliminate possible causes. I am not seeing this behavior and I am not running xmonad but I am running on x86_64. - -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQGYoOAAoJELT202JKF+xpe4IP/0/ckne3gYF5WJPdQNms1uLl yJD+Hp3W4o9MMBHw7K37MiARnzfDiNT0ZjEhi71BgAWGoaiMWNNpZiwP4FPIZXTJ qmKGspPXKx/H+ZNRvm6w8tKKdTFP9T+kIjYvrwOs2xl6Eqob8DeQGF3Sigr17O6M /5tLJp5wpH0mRR3YeLXvZQpJMyLHS7V7lhfoFXfZdREb1sF/YLMdzBYB6GKYg7Ws 1MW7S51w/rU0yV3HGUZVrcrYuhQeEI2wisE4/rarRKrH7NlT+WLIl99qRg+OIROb YjPXxlhiqMasi/JauxlZoszwYXEFSWcEWz/4c333EkelLJdovZRqFBzwsO1yq/vR iS6WM5eyCwnmtQLURNt1+0RHkzHYtiWe0/a7vaXl6qv2+i+MESBujLMHx4r6R5E9 f3Q6FHCu9dG4IlBM2ZzCXxKDbuqM3SZiBMCq0Xnw8Tse/HTmgK4cOoLfWNilXaIu YjWPeiqghKHYyRS8CaTrFsFy7vWaQjt6fq0n77rT8XzVBAzmgP9ZKXLkR+TirPPv +hRBWFCF8B+Q7f2Kqz/lgtDgAFlbtTtD6iAhIDK+sbkq1Sh4Mri1c4boAHqjAPn/ 2wo349MxzBz9I8tYI6ZD1g4/lXA68nqjTPe4+FXQCq5c2wNLyOdLB0+J1VAuFdQ5 jXNMUmqggUAeGtoTJwE1 =kB2i -----END PGP SIGNATURE-----
Running x86_64. Using awesome, no problem showing the print dialog window here. On Wed, Aug 1, 2012 at 4:57 PM, David Benfell <benfell@parts-unknown.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/01/2012 12:42 AM, Jeremiah Dodds wrote:
Scott Weisman <sweisman@pobox.com> writes:
Has anyone else experienced this problem? Can anyone suggest a solution?
I had not, but I can confirm the behaviour with chromium 20.0.1132.57-2 on x86_64, running xmonad. I get a total freeze of chromium (have to kill -9) if I hit C-p, or hit "print" from the menu.
We could spend a lot of time trying to eliminate possible causes. I am not seeing this behavior and I am not running xmonad but I am running on x86_64.
- -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJQGYoOAAoJELT202JKF+xpe4IP/0/ckne3gYF5WJPdQNms1uLl yJD+Hp3W4o9MMBHw7K37MiARnzfDiNT0ZjEhi71BgAWGoaiMWNNpZiwP4FPIZXTJ qmKGspPXKx/H+ZNRvm6w8tKKdTFP9T+kIjYvrwOs2xl6Eqob8DeQGF3Sigr17O6M /5tLJp5wpH0mRR3YeLXvZQpJMyLHS7V7lhfoFXfZdREb1sF/YLMdzBYB6GKYg7Ws 1MW7S51w/rU0yV3HGUZVrcrYuhQeEI2wisE4/rarRKrH7NlT+WLIl99qRg+OIROb YjPXxlhiqMasi/JauxlZoszwYXEFSWcEWz/4c333EkelLJdovZRqFBzwsO1yq/vR iS6WM5eyCwnmtQLURNt1+0RHkzHYtiWe0/a7vaXl6qv2+i+MESBujLMHx4r6R5E9 f3Q6FHCu9dG4IlBM2ZzCXxKDbuqM3SZiBMCq0Xnw8Tse/HTmgK4cOoLfWNilXaIu YjWPeiqghKHYyRS8CaTrFsFy7vWaQjt6fq0n77rT8XzVBAzmgP9ZKXLkR+TirPPv +hRBWFCF8B+Q7f2Kqz/lgtDgAFlbtTtD6iAhIDK+sbkq1Sh4Mri1c4boAHqjAPn/ 2wo349MxzBz9I8tYI6ZD1g4/lXA68nqjTPe4+FXQCq5c2wNLyOdLB0+J1VAuFdQ5 jXNMUmqggUAeGtoTJwE1 =kB2i -----END PGP SIGNATURE-----
-- Saludos, Germán Delivering common sense since 1969 <Epoch Fail!>. The Nature is not amiable; It treats impartially to all the things. The wise person is not amiable; He treats all people impartially.
I should have added more details. I am using OpenBox on an X86_64 install. Two different systems (desktop and notebook) but otherwise largely similar setups. Scott On Wed, Aug 1, 2012 at 8:27 AM, Scott Weisman <sweisman@pobox.com> wrote:
I started experiencing a severe problem with Chromium recently that makes web browsing a very tedious experience.
It took a while to narrow it down, but it seems that whenever the print dialog is invoked, either manually (eg ctrl-P on the keyboard) or by a page when clicking on the "printer friendly format" link, the entire browser crashes. This happens on two separate Arch installs.
I personally would love a method to disable the printer dialog from ever popping up anyway, since I don't even have one (so if someone can suggest a method, I'd love to hear it), but this bug is a serious problem, as the crash is unrecoverable. And if my session ends up with a page that invokes the dialog on its own, I have to clear out the entire session.
Has anyone else experienced this problem? Can anyone suggest a solution?
-- "I just am not frightened by a free society. I'm frightened by those individuals who prevent us from having a free society." -- Ron Paul
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?
2012/8/2 Ray Kohler <ataraxia937@gmail.com>:
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?
Indeed, that’s the problem. On my system I also have a pure openbox x86_64 environment but without cups and without systemd (yet), and I noticed the same freeze when pressing Ctrl-P. But then I installed cups and started the daemon and now the print dialog shows immediately and there is no freeze anymore. So a workaround is to install cups and start the daemon at boot.
On Thu, Aug 2, 2012 at 6:41 PM, Guillaume Brunerie <guillaume.brunerie@gmail.com> wrote:
2012/8/2 Ray Kohler <ataraxia937@gmail.com>:
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?
Indeed, that’s the problem. On my system I also have a pure openbox x86_64 environment but without cups and without systemd (yet), and I noticed the same freeze when pressing Ctrl-P. But then I installed cups and started the daemon and now the print dialog shows immediately and there is no freeze anymore. So a workaround is to install cups and start the daemon at boot.
I was just bitten by this too, and I can confirm it strikes both through Ctrl+P and when clicking on "print links". I've searched for a bug reported upstream on this, but can't find one, has anyone with a stronger goggle-fu had more success finding one? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
On Fri, Aug 3, 2012 at 1:17 PM, Magnus Therning <magnus@therning.org> wrote:
On Thu, Aug 2, 2012 at 6:41 PM, Guillaume Brunerie <guillaume.brunerie@gmail.com> wrote:
2012/8/2 Ray Kohler <ataraxia937@gmail.com>:
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?
Indeed, that’s the problem. On my system I also have a pure openbox x86_64 environment but without cups and without systemd (yet), and I noticed the same freeze when pressing Ctrl-P. But then I installed cups and started the daemon and now the print dialog shows immediately and there is no freeze anymore. So a workaround is to install cups and start the daemon at boot.
I was just bitten by this too, and I can confirm it strikes both through Ctrl+P and when clicking on "print links". I've searched for a bug reported upstream on this, but can't find one, has anyone with a stronger goggle-fu had more success finding one?
/M
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
using xfce without cups installed. same problem here.
On Fri, Aug 3, 2012 at 1:17 PM, Magnus Therning <magnus@therning.org> wrote:
On Thu, Aug 2, 2012 at 6:41 PM, Guillaume Brunerie <guillaume.brunerie@gmail.com> wrote:
2012/8/2 Ray Kohler <ataraxia937@gmail.com>:
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?
Indeed, that’s the problem. On my system I also have a pure openbox x86_64 environment but without cups and without systemd (yet), and I noticed the same freeze when pressing Ctrl-P. But then I installed cups and started the daemon and now the print dialog shows immediately and there is no freeze anymore. So a workaround is to install cups and start the daemon at boot.
I was just bitten by this too, and I can confirm it strikes both through Ctrl+P and when clicking on "print links". I've searched for a bug reported upstream on this, but can't find one, has anyone with a stronger goggle-fu had more success finding one?
Probably the only people running Linux systems without cups are the DIY distro groups (Arch, gentoo etc.) as I don't think this would have been caught in the bigger distros where if I'm not mistaken cups is installed by default....
On Fri, Aug 3, 2012 at 7:34 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
On Fri, Aug 3, 2012 at 1:17 PM, Magnus Therning <magnus@therning.org> wrote:
On Thu, Aug 2, 2012 at 6:41 PM, Guillaume Brunerie <guillaume.brunerie@gmail.com> wrote:
2012/8/2 Ray Kohler <ataraxia937@gmail.com>:
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?
Indeed, that’s the problem. On my system I also have a pure openbox x86_64 environment but without cups and without systemd (yet), and I noticed the same freeze when pressing Ctrl-P. But then I installed cups and started the daemon and now the print dialog shows immediately and there is no freeze anymore. So a workaround is to install cups and start the daemon at boot.
I was just bitten by this too, and I can confirm it strikes both through Ctrl+P and when clicking on "print links". I've searched for a bug reported upstream on this, but can't find one, has anyone with a stronger goggle-fu had more success finding one?
Probably the only people running Linux systems without cups are the DIY distro groups (Arch, gentoo etc.) as I don't think this would have been caught in the bigger distros where if I'm not mistaken cups is installed by default....
I think you are spot on. Correct me if I'm wrong, but print-to-file is available without having cups running, right? (I'm nowhere near any of my Linux machines at the moment so I can't test it for myself.) /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
On Fri, Aug 03, 2012 at 10:15:33AM +0200, Magnus Therning wrote:
On Fri, Aug 3, 2012 at 7:34 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
Probably the only people running Linux systems without cups are the DIY distro groups (Arch, gentoo etc.) as I don't think this would have been caught in the bigger distros where if I'm not mistaken cups is installed by default....
I think you are spot on. Correct me if I'm wrong, but print-to-file is available without having cups running, right? (I'm nowhere near any of my Linux machines at the moment so I can't test it for myself.)
Yes, I often use print to file (mainly with firefox), and it does not require the cups daemon to be running. Also, I am experiencing chromium hanging when trying to print on a non-DE environment.
gt [2012.08.03 1526 +0530]:
On Fri, Aug 03, 2012 at 10:15:33AM +0200, Magnus Therning wrote:
On Fri, Aug 3, 2012 at 7:34 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
Probably the only people running Linux systems without cups are the DIY distro groups (Arch, gentoo etc.) as I don't think this would have been caught in the bigger distros where if I'm not mistaken cups is installed by default....
I think you are spot on. Correct me if I'm wrong, but print-to-file is available without having cups running, right? (I'm nowhere near any of my Linux machines at the moment so I can't test it for myself.)
Yes, I often use print to file (mainly with firefox), and it does not require the cups daemon to be running.
Also, I am experiencing chromium hanging when trying to print on a non-DE environment.
To add to this discussion, my experience with chromium is a bit different from what people are suggesting here. I'm running xmonad and use systemd's socket method to start cups when needed. It doesn't matter whether cups is running or not, chromium never actually crashes on me, but the tab where I invoke Ctrl-P or select Print from the menu becomes unresponsive. Having cups running or not has no effect whatsoever on this on my machine. Really annoying. Cheers, Norbert
Norbert Zeh [2012.08.03 1943 -0300]:
gt [2012.08.03 1526 +0530]:
On Fri, Aug 03, 2012 at 10:15:33AM +0200, Magnus Therning wrote:
On Fri, Aug 3, 2012 at 7:34 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
Probably the only people running Linux systems without cups are the DIY distro groups (Arch, gentoo etc.) as I don't think this would have been caught in the bigger distros where if I'm not mistaken cups is installed by default....
I think you are spot on. Correct me if I'm wrong, but print-to-file is available without having cups running, right? (I'm nowhere near any of my Linux machines at the moment so I can't test it for myself.)
Yes, I often use print to file (mainly with firefox), and it does not require the cups daemon to be running.
Also, I am experiencing chromium hanging when trying to print on a non-DE environment.
To add to this discussion, my experience with chromium is a bit different from what people are suggesting here. I'm running xmonad and use systemd's socket method to start cups when needed. It doesn't matter whether cups is running or not, chromium never actually crashes on me, but the tab where I invoke Ctrl-P or select Print from the menu becomes unresponsive. Having cups running or not has no effect whatsoever on this on my machine. Really annoying.
Ignore what I said. The problem was related to cups "not running" after all. I'm running chromium in a chroot, and the host's cups daemon was not visible to the chroot. Once I fixed that, no more hangs...at all. Even if I don't have cups running, it seems to fire up instantaneously using systemd's socket activation even when the request comes from within the chroot. Cheers, Norbert
participants (11)
-
Auguste Pop
-
David Benfell
-
Germán Gutiérrez
-
gt
-
Guillaume Brunerie
-
Jeremiah Dodds
-
Magnus Therning
-
Norbert Zeh
-
Oon-Ee Ng
-
Ray Kohler
-
Scott Weisman