Bug 318075

Summary: Marble crashes on startup
Product: [Applications] marble Reporter: Peter Brecke <peter.brecke>
Component: generalAssignee: marble-bugs
Status: RESOLVED FIXED    
Severity: critical    
Priority: NOR    
Version: 1.5 (KDE 4.10)   
Target Milestone: ---   
Platform: macOS (DMG)   
OS: macOS   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot showing versions of Marble and Qt in running program

Description Peter Brecke 2013-04-09 02:27:17 UTC
Marble 1.5.0 on MacBook (5,1) running Mac OSX 10.7.5 crashes immediately with the following error messages in the system log:

4/8/13 9:36:59.999 PM ReportCrash: Failed to create CSSymbolicatorRef for launchd[16886]
4/8/13 9:37:00.109 PM ReportCrash: Failed to create dSYM-less CSSymbolicatorRef for launchd[16886]
4/8/13 9:37:00.218 PM com.apple.launchd.peruser.503: ([0x0-0x573573].Marble[16886]) Job appears to have crashed: Segmentation fault: 11

and the following user diagnostic report:

Process:         launchd [16886]
Path:            /Applications/Marble.app/Contents/MacOS/marble
Identifier:      launchd
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  launchd [166]

Date/Time:       2013-04-08 21:36:59.865 -0400
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9

Crashed Thread:  Unknown

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000055  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000
  rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x0000000000000000
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
  rip: 0x00007fff5fc01028  rfl: 0x0000000000010203  cr2: 0x00007fff5fc01028
Logical CPU: 0

Binary images description not available


External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 1
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 22586
    thread_create: 0
    thread_set_state: 0

 


Reproducible: Always

Steps to Reproduce:
1. download Marble 1.5.0 from download page
2. install application into Applications folder
3. double-click on Marble icon
Actual Results:  
Immediate crash with the error reports given above generated

Expected Results:  
It should not have crashed at such an early stage.

I see that other programs generate the same error messages as the first two given above.  In some instances the crashing goes away if the computer is upgraded to Mac OS X 10.8.x.
Comment 1 Dieudonné 2013-05-30 13:35:13 UTC
I confirm this bug. Thanks for any help ; )
Comment 2 Andrew Crouthamel 2018-11-10 03:24:50 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:23:23 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-02 07:43:45 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-17 05:15:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Peter Brecke 2023-01-17 13:44:02 UTC
Created attachment 155380 [details]
Screenshot showing versions of Marble and Qt in running program

I don't know when or how it got fixed, but Marble runs fine now.
Comment 7 Bug Janitor Service 2023-02-01 05:03:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Peter Brecke 2023-02-01 17:16:24 UTC
I have told you previously, and included screenshots to verify, the problem no longer exists.  You have fixed the bug.  Why oh why do you continue to ask me about the bug (a rhetorical question)?