[Bug 965314] Re: core dumped - segmentation fault

2014-01-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2014-01-20 Thread Christopher M. Penalver
** No longer affects: chromium-browser (Ubuntu)

** Changed in: chromium-browser
   Importance: Unknown => Undecided

** Changed in: chromium-browser
   Status: Unknown => New

** Changed in: chromium-browser
 Remote watch: code.google.com/p/chromium/issues #121660 => None

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2014-01-20 Thread Christopher M. Penalver
Lucazade, thank you for reporting this and helping make Ubuntu better. However, 
your crash report is missing. Please follow these instructions to have apport 
report a new bug about your crash that can be dealt with by the automatic 
retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && 
sudo apt-get -y install chromium-browser-dbg && sudo service apport start 
force_start=1

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your 
/var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'. If you run the command against the crash 
report and a window pops up asking you to report this, but then never opens a 
new report, you would be affected by 
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to 
WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Project changed: chromium-browser => chromium-browser (Ubuntu)

** Changed in: chromium-browser (Ubuntu)
   Status: New => Invalid

** Attachment removed: "chromium.core.20120429.gz"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120504/+files/chromium.core.20120429.gz

** Attachment removed: "chromium.core.20120430.gz"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120508/+files/chromium.core.20120430.gz

** Attachment removed: "chromium.bug.20120430"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120526/+files/chromium.bug.20120430

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2013-06-02 Thread papukaija
** Also affects: chromium-browser via
   http://code.google.com/p/chromium/issues/detail?id=121660
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-07-20 Thread Cinquero
have this problem, too. But has nothing to do with sync. Happens even
after deleting ~/.config/chromium.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-05-05 Thread Maarten Jacobs
Actually - the work-around for this issue is to disable sync. If you
cannot get Chromium to stay up, you'll have to delete your Chromium
configuration:

1. cd ~/.config
2. rm -rf chromium
3. restart chromium - it should now stay up, as long as you don't "sign in" to 
chromium

These steps work for me and prevent Chromium from failing - if somebody
has a case where Chromium still fails, even with sync disabled, then
that's a different problem from what I'm observing on my installation.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-05-01 Thread Maarten Jacobs
The same, or similar issue is being tracked here:

http://code.google.com/p/chromium/issues/detail?id=121660

** Bug watch added: code.google.com/p/chromium/issues #121660
   http://code.google.com/p/chromium/issues/detail?id=121660

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-04-30 Thread Maarten Jacobs
Here's data on my configuration:

Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
RelatedPackageVersions:
 chromium-browser 18.0.1025.151~r130497-0ubuntu1
 chromium-browser-l10n18.0.1025.151~r130497-0ubuntu1
 chromium-browser-inspector   N/A
 chromium-browser-dbg N/A
 chromium-codecs-ffmpeg   N/A
 chromium-codecs-ffmpeg-extra 18.0.1025.151~r130497-0ubuntu1

I've attached the complete apport-bug output for reference.


** Attachment added: "chromium.bug.20120430"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120526/+files/chromium.bug.20120430

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-04-30 Thread Maarten Jacobs
I seem to be experiencing a similar issue - Chromium seems to core dump
immediately when it loads. Only occassionally it doesn't - I'm actually
writing this bug in Firefox as I can't seem to get Chromium to stay up.

I ran Chromium from the command line, and collected some information:

jacobsma@snellebak:~$ chromium-browser 
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
[11259:11273:165486117836:ERROR:native_backend_gnome_x.cc(664)] Keyring find 
failed: Error communicating with gnome-keyring-daemon
[11259:11259:165486445951:ERROR:browser_main_loop.cc(138)] Gdk: 
IA__gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed
[11259:11259:165486446253:ERROR:browser_main_loop.cc(138)] GLib-GObject: 
g_object_ref: assertion `G_IS_OBJECT (object)' failed
[11259:11259:165487584864:ERROR:browser_main_loop.cc(138)] GLib-GObject: 
g_object_unref: assertion `G_IS_OBJECT (object)' failed
[11259:11259:165527533125:ERROR:x11_util.cc(1121)] X Error detected: serial 
27968, error_code 10 (BadAccess (attempt to access private resource denied)), 
request_code 140, minor_code 1 (X_ShmAttach)
[11259:11259:165527535112:ERROR:x11_util.cc(1121)] X Error detected: serial 
27969, error_code 148 (BadShmSeg (invalid shared segment parameter)), 
request_code 140, minor_code 3 (X_ShmPutImage)
[11259:11259:165527536294:ERROR:x11_util.cc(1121)] X Error detected: serial 
28044, error_code 148 (BadShmSeg (invalid shared segment parameter)), 
request_code 140, minor_code 2 (X_ShmDetach)

>> During this session Chromium stayed up - however I figured perhaps
the output was relevant.

Further sessions always result in the same output:

jacobsma@snellebak:~$ chromium-browser 
chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: 
cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' 
failed.
Aborted (core dumped)

>> The "cairo" error has been reported in varios other bugs (is it ever
going to be fixed??) - and does not seem to be related to this problem
as the core happens a fraction of time after the "cairo" error is
logged.

I've collected two core dumps and will attach them to this bug report.


** Attachment added: "chromium.core.20120429.gz"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120504/+files/chromium.core.20120429.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-04-30 Thread Maarten Jacobs
** Attachment added: "chromium.core.20120430.gz"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120508/+files/chromium.core.20120430.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-03-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 965314] Re: core dumped - segmentation fault

2012-03-26 Thread Lucazade
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965314

Title:
  core dumped - segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs