Issue 34903 in chromium: Trace/Breakpoint Trap
chro...@googlecode.com
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined
New issue 34903 by cunninghamlouis: Trace/Breakpoint Trap
http://code.google.com/p/chromium/issues/detail?id=34903
Chrome Version : Most recent from daily-build repository as of Feb.
6th 18:37 PST
After and upgrade receives error:
@up2:~$ chromium-browser
(chromium-browser:30703): Gtk-WARNING **: Unable to locate theme engine in
module_path: "ubuntulooks",
[30703:30724:345293114806:FATAL:chrome/browser/sync/syncable/directory_backing_store.cc(565)]
Check failed: SQLITE_DONE == statement.step().
Trace/breakpoint trap
From gdb:
@up2:~$ chromium-browser -g
# Env:
# LD_LIBRARY_PATH=/usr/lib/chromium-browser
#
PATH=/usr/lib/chromium-browser:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
# GTK_PATH=
# CHROMIUM_USER_FLAGS=
# CHROMIUM_FLAGS=
/usr/bin/gdb /usr/lib/chromium-browser/chromium-browser -x
/tmp/chromiumargs.myoxbW
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb) run
Starting program: /usr/lib/chromium-browser/chromium-browser
...
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
...
[New Thread 0xb6d34b50 (LWP 30774)]
(no debugging symbols found)
...
(chromium-browser:30774): Gtk-WARNING **: Unable to locate theme engine in
module_path: "ubuntulooks",
(no debugging symbols found)
[New Thread 0xb6b3fb90 (LWP 30782)]
(no debugging symbols found)
[New Thread 0xb61c8b90 (LWP 30783)]
[New Thread 0xb59c7b90 (LWP 30784)]
[New Thread 0xb51c6b90 (LWP 30785)]
[New Thread 0xb49c5b90 (LWP 30786)]
[New Thread 0xb41c4b90 (LWP 30787)]
[New Thread 0xb39c3b90 (LWP 30788)]
[New Thread 0xb31c2b90 (LWP 30789)]
[New Thread 0xb2902b90 (LWP 30790)]
[New Thread 0xb27e3b90 (LWP 30791)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb28b1b90 (LWP 30792)]
[New Thread 0xb2890b90 (LWP 30793)]
[New Thread 0xb272ab90 (LWP 30794)]
[New Thread 0xb2573b90 (LWP 30795)]
(no debugging symbols found)
[New Thread 0xb2552b90 (LWP 30796)]
[New Thread 0xb22e8b90 (LWP 30797)]
[New Thread 0xb1ae7b90 (LWP 30798)]
[Thread 0xb1ae7b90 (LWP 30798) exited]
[New Thread 0xb1ae7b90 (LWP 30799)]
[New Thread 0xb12e6b90 (LWP 30800)]
[New Thread 0xb0ae5b90 (LWP 30801)]
[New Thread 0xb02e4b90 (LWP 30802)]
[30774:30797:345377001458:FATAL:chrome/browser/sync/syncable/directory_backing_store.cc(565)]
Check failed: SQLITE_DONE == statement.step().
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0xb22e8b90 (LWP 30797)]
0x085b57e4 in ?? ()
(gdb)
Using a different/new data-profile works however.
I don't really want to start all of this over, what is up?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
chro...@googlecode.com
Comment #1 on issue 34903 by cunninghamlouis: Trace/Breakpoint Trap
http://code.google.com/p/chromium/issues/detail?id=34903
This has something to do with the "Preferences" file located in
~/.config/chromium
I have been trying to restore Chromium, and preferences and whatnot, and
once i
delete ~/.config/chromium/preferences chromium starts up fine.
I am attaching my preferences file, maybe something is corrupted in this?
Thanks all!
Any help that I can give, I am here for!
Attachments:
Preferences 30.4 KB
chro...@googlecode.com
Comment #2 on issue 34903 by cunninghamlouis: Trace/Breakpoint Trap
http://code.google.com/p/chromium/issues/detail?id=34903
Semi fixed;
I realized this was an error within the Sync data, and so I copied
everything over
from a backup data dir I had, and simply removed everything in "Sync Data"
Folder, and
everything works fine now.
Weird bug...