Bugzilla – Attachment 77640 Details for
Bug 63281
Crash when editing a formula in Writer
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
console output of 2 runs/crashes
libreoffice-bug.txt (text/plain), 1.48 KB, created by
antti.niemi
on 2013-04-08 21:07:32 UTC
(
hide
)
Description:
console output of 2 runs/crashes
Filename:
MIME Type:
Creator:
antti.niemi
Created:
2013-04-08 21:07:32 UTC
Size:
1.48 KB
patch
obsolete
>username@system:~$ libreoffice -writer >Warning: -writer is deprecated. Use --writer instead. >WARNING: gnome-keyring:: couldn't connect to: /home/username/.cache/keyring-<censored>/<censored>: File or directory does not exist >The program 'soffice' received an X Window System error. >This probably reflects a bug in the program. >The error was 'BadAtom (invalid Atom parameter)'. > (Details: serial 129 error_code 5 request_code 17 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) > > >username@system:~$ libreoffice --writer >WARNING: gnome-keyring:: couldn't connect to: /home/username/.cache/keyring-<censored>/<censored>: File or directory does not exist >The program 'soffice' received an X Window System error. >This probably reflects a bug in the program. >The error was 'BadAtom (invalid Atom parameter)'. > (Details: serial 214 error_code 5 request_code 17 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.)
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 63281
: 77640