Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1064250
Title:
chromium-browser crashed with SIGSEGV
Status in chromium-browser package in Ubuntu:
Won't Fix
Bug description:
Hi,
simply letting gmail open in chromium and locking my session before
leaving.
On the morrow, chromium has crashed.
regards.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 9 10:38:12 2012
Desktop-Session:
DESKTOP_SESSION = ubuntu
XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
XDG_DATA_DIRS =
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f6b2ecbe61c: mov 0x150(%rax),%r12
PC (0x7f6b2ecbe61c) ok
source "0x150(%rax)" (0x00000150) not located in a known VMA region (needed
readable region)!
destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
Stacktrace:
#0 0x00007f6b2ecbe61c in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fff0e6dce98
StacktraceTop: ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec =
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command =
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled =
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser
%s\n'/desktop/gnome/url-handlers/http/enabled =
b'true\n'/desktop/gnome/session/required_components/windowmanager =
b''/apps/metacity/general/compositing_manager =
b''/desktop/gnome/interface/icon_theme =
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1064250/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
