| 2015-10-12 19:44:59 |
Boris |
bug |
|
|
added bug |
| 2015-10-12 19:55:24 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2015-10-12 19:55:25 |
Apport retracing service |
attachment added |
|
Stacktrace.txt https://bugs.launchpad.net/bugs/1505366/+attachment/4492705/+files/Stacktrace.txt |
|
| 2015-10-12 19:55:26 |
Apport retracing service |
attachment added |
|
StacktraceSource.txt https://bugs.launchpad.net/bugs/1505366/+attachment/4492706/+files/StacktraceSource.txt |
|
| 2015-10-12 19:55:27 |
Apport retracing service |
attachment added |
|
StacktraceTop.txt https://bugs.launchpad.net/bugs/1505366/+attachment/4492707/+files/StacktraceTop.txt |
|
| 2015-10-12 19:55:28 |
Apport retracing service |
attachment added |
|
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1505366/+attachment/4492708/+files/ThreadStacktrace.txt |
|
| 2015-10-12 19:55:30 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1505366/+attachment/4492688/+files/CoreDump.gz |
|
|
| 2015-10-12 19:55:31 |
Apport retracing service |
caja (Ubuntu): importance |
Undecided |
Medium |
|
| 2015-10-12 19:55:32 |
Apport retracing service |
tags |
amd64 apport-crash need-amd64-retrace wily |
amd64 apport-crash wily |
|
| 2017-01-16 08:46:22 |
Launchpad Janitor |
caja (Ubuntu): status |
New |
Confirmed |
|
| 2017-01-16 08:47:21 |
Martin Wimpress |
information type |
Private |
Public |
|
| 2017-01-16 08:55:36 |
Martin Wimpress |
description |
Crash right after starting caja
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: caja 1.10.4-1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Oct 12 21:38:26 2015
ExecutablePath: /usr/bin/caja
ProcCmdline: caja
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: caja
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lp lpadmin netdev plugdev sambashare sudo |
Crash right after starting caja
Some other comments from the duplicate bugs:
* "I had just installed caja-actions and then added "noatime" to my fstab to use when mounting the root partition." LP: (#1564580)
* "Copied a file in split pane mode from local hd to usb drive and removed usb drive after copy." LP: (#1569427)
* "I'm just tinkering with an external SMB server. This report is generated automatically, I'm just a user." LP: (#1570363)
* "I think I traced the source of the crash to me pulling the rug from under Caja. As I'm still learning Samba 4, I changed the name of a connected share while the server was still connected and I think that's what caused the drop out."
* "I installed caja-actions yesterday and received this error when starting up. Ubuntu Yakkety Yak (development branch)" LP: (#1598959)
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: caja 1.10.4-1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Oct 12 21:38:26 2015
ExecutablePath: /usr/bin/caja
ProcCmdline: caja
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: caja
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lp lpadmin netdev plugdev sambashare sudo |
|
| 2017-01-16 08:56:08 |
Martin Wimpress |
description |
Crash right after starting caja
Some other comments from the duplicate bugs:
* "I had just installed caja-actions and then added "noatime" to my fstab to use when mounting the root partition." LP: (#1564580)
* "Copied a file in split pane mode from local hd to usb drive and removed usb drive after copy." LP: (#1569427)
* "I'm just tinkering with an external SMB server. This report is generated automatically, I'm just a user." LP: (#1570363)
* "I think I traced the source of the crash to me pulling the rug from under Caja. As I'm still learning Samba 4, I changed the name of a connected share while the server was still connected and I think that's what caused the drop out."
* "I installed caja-actions yesterday and received this error when starting up. Ubuntu Yakkety Yak (development branch)" LP: (#1598959)
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: caja 1.10.4-1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Oct 12 21:38:26 2015
ExecutablePath: /usr/bin/caja
ProcCmdline: caja
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: caja
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lp lpadmin netdev plugdev sambashare sudo |
Crash right after starting caja
Some other comments from the duplicate bugs:
* "I had just installed caja-actions and then added "noatime" to my fstab to use when mounting the root partition." (LP: #1564580)
* "Copied a file in split pane mode from local hd to usb drive and removed usb drive after copy." (LP: #1569427)
* "I'm just tinkering with an external SMB server. This report is generated automatically, I'm just a user." (LP: #1570363)
* "I think I traced the source of the crash to me pulling the rug from under Caja. As I'm still learning Samba 4, I changed the name of a connected share while the server was still connected and I think that's what caused the drop out."
* "I installed caja-actions yesterday and received this error when starting up. Ubuntu Yakkety Yak (development branch)" (LP: #1598959)
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: caja 1.10.4-1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Oct 12 21:38:26 2015
ExecutablePath: /usr/bin/caja
ProcCmdline: caja
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: caja
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lp lpadmin netdev plugdev sambashare sudo |
|
| 2017-08-26 15:44:15 |
Vlad Orlov |
marked as duplicate |
|
1364349 |
|
