#11971 closed bug (not reproducible)
Crash during libtracker global initialization
| Reported by: | vidrep | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Kits/libtracker.so | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Booted up hrev49036 x86_gcc2 and debugger activated as soon as the Desktop appeared. Could not save reports, and killing the debugger would activate another. Tried to reboot and was greeted with a string of debugger calls...print server, media server etc.
Attachments (4)
Change History (17)
by , 10 years ago
| Attachment: | previous_syslog added |
|---|
by , 10 years ago
comment:1 by , 10 years ago
comment:2 by , 10 years ago
comment:3 by , 10 years ago
Tracker crashed again today on hrev49046 x86_gcc2 while navigating an old BeOS 5 installation CD. Debug report and syslog attached.
by , 10 years ago
| Attachment: | Tracker-485-debug-17-04-2015-15-27-01.report added |
|---|
comment:4 by , 10 years ago
The backtrace in that report looks completely unrelated to the originally reported crash, and probably merits its own separate ticket.
by , 10 years ago
comment:5 by , 10 years ago
Can you rename this ticket title to something more appropriate for the bug in question? I'll open another ticket for the latest crash.
comment:6 by , 10 years ago
| Summary: | Tracker crash → Crash during libtracker global initialization |
|---|
comment:8 by , 9 years ago
| Blocked By: | 11982 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
comment:9 by , 9 years ago
| Blocked By: | 11982 removed |
|---|---|
| Resolution: | duplicate |
| Status: | closed → reopened |
@Diver, no, these are two separate tickets. Read the entire ticket history again.
comment:10 by , 9 years ago
Hmm, isn't the crash in the attached debug report is at BCompressionAlgorithm::BAbstractInputStream::Read function which #11982 is about?
comment:11 by , 9 years ago
It is, but as AnEvilYak pointed out, that's unrelated to the crashes shown in the syslogs.
comment:12 by , 6 years ago
| Resolution: | → not reproducible |
|---|---|
| Status: | reopened → closed |
comment:13 by , 5 years ago
| Milestone: | Unscheduled |
|---|
Remove milestone for tickets with status = closed and resolution != fixed
Seems to be crashing while handling libtracker's global initialization. However, I don't see any obviously suspicious recent revisions, and I'm not able to reproduce it here. Is this happening on an existing upgraded installation, or does e.g. a clean image booted off a USB stick exhibit the same behavior? If so, can you narrow down what revision it starts appearing at for you?