Public bug reported:

Distribution/Version: Ubuntu Precise Pangolin
        Description:    Ubuntu precise (development branch)
        Release:        12.04
Package version: 2.24.10-0ubuntu4
Architecture: x86_64

Description:
After the most recent GTK+ update, chromium-browser, and midori both became 
unusable. Both applications crash as soon as they are opened. If 
chromium-browser is invoked from the command line with a valid URL as an 
argument, chromium will open that URL correctly, but crash as soon as the user 
attempts to navigate away from the page or immediately when the address bar is 
clicked on.
The command line output gives no more information than "Segmentation Fault", 
but the output of dmesg is slightly more useful:

[262182.529336] chromium-browse[10421]: segfault at ffffffff965cc200 ip
00007fdf8ee6976e sp 00007fff5d934380 error 4 in
libgdk-x11-2.0.so.0.2400.10[7fdf8ee03000+ad000]

Affected applications:

chromium-browser version: 17.0.963.56~r121963-0ubuntu3
midori: 0.4.3-1ubuntu1
firefox: 11.0~b4+build1-0ubuntu1

note: Firefox does not crash like midori and chromium do, but instead
closes and launches the mozilla-bug-reporter application; however, the
mozilla bug reporter application crashed with a segfault in
libgdk-x11-2.0.so.0.2400.10

** Affects: gtk+2.0 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: chromium gdk-x11 gtk+ gtk2.0 lubuntu midori segfault

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/941797

Title:
  applications crash with SIGSEGV in libgdk-x11.so

Status in “gtk+2.0” package in Ubuntu:
  New

Bug description:
  Distribution/Version: Ubuntu Precise Pangolin
        Description:    Ubuntu precise (development branch)
        Release:        12.04
  Package version: 2.24.10-0ubuntu4
  Architecture: x86_64

  Description:
  After the most recent GTK+ update, chromium-browser, and midori both became 
unusable. Both applications crash as soon as they are opened. If 
chromium-browser is invoked from the command line with a valid URL as an 
argument, chromium will open that URL correctly, but crash as soon as the user 
attempts to navigate away from the page or immediately when the address bar is 
clicked on.
  The command line output gives no more information than "Segmentation Fault", 
but the output of dmesg is slightly more useful:

  [262182.529336] chromium-browse[10421]: segfault at ffffffff965cc200
  ip 00007fdf8ee6976e sp 00007fff5d934380 error 4 in
  libgdk-x11-2.0.so.0.2400.10[7fdf8ee03000+ad000]

  Affected applications:

  chromium-browser version: 17.0.963.56~r121963-0ubuntu3
  midori: 0.4.3-1ubuntu1
  firefox: 11.0~b4+build1-0ubuntu1

  note: Firefox does not crash like midori and chromium do, but instead
  closes and launches the mozilla-bug-reporter application; however, the
  mozilla bug reporter application crashed with a segfault in
  libgdk-x11-2.0.so.0.2400.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/941797/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to