Summary: | Dolphin crash at startup | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Arnaud Mombrial <arnaud.mombrial> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | MacPorts | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Arnaud Mombrial
2013-07-16 15:43:22 UTC
Thanks for the bug report. Unfortunately, it's all but impossible to do anything about crashes on MacOS without a useful backtrace or other helpful information. (No Dolphin developer is working on MacOS.) (In reply to comment #0) > Program received signal EXC_BAD_ACCESS, Could not access memory. If the cause is an invalid memory access, maybe Valgrind can help (I think it is available for MacOS too). Please run Dolphin in Valgrind and produce a log. On Linux, this is done with valgrind dolphin 2> log.txt Then attach the log here. Thanks for your help. Hi Frank, no luck, valgrind installation failed on my system... : sudo port install valgrind ---> Computing dependencies for valgrind ---> Fetching archive for valgrind ---> Attempting to fetch valgrind-3.8.1_1.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/valgrind ---> Attempting to fetch valgrind-3.8.1_1.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/valgrind ---> Attempting to fetch valgrind-3.8.1_1.darwin_12.x86_64.tbz2 from http://packages.macports.org/valgrind ---> Fetching distfiles for valgrind ---> Attempting to fetch valgrind-3.8.1.tar.bz2 from http://lil.fr.distfiles.macports.org/valgrind ---> Verifying checksum(s) for valgrind ---> Extracting valgrind ---> Applying patches to valgrind ---> Configuring valgrind ---> Building valgrind Error: org.macports.build for port valgrind returned: command execution failed Please see the log file for port valgrind for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_valgrind/valgrind/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port valgrind failed [ arnaud nocheaPad ~ ] sudo port install valgrind-devel ---> Computing dependencies for valgrind-devel ---> Fetching archive for valgrind-devel ---> Attempting to fetch valgrind-devel-3.9.0-r13189_1.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/valgrind-devel ---> Attempting to fetch valgrind-devel-3.9.0-r13189_1.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/valgrind-devel ---> Attempting to fetch valgrind-devel-3.9.0-r13189_1.darwin_12.x86_64.tbz2 from http://packages.macports.org/valgrind-devel ---> Fetching distfiles for valgrind-devel ---> Verifying checksum(s) for valgrind-devel ---> Extracting valgrind-devel ---> Configuring valgrind-devel ---> Building valgrind-devel Error: org.macports.build for port valgrind-devel returned: command execution failed Please see the log file for port valgrind-devel for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_valgrind-devel/valgrind-devel/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port valgrind-devel failed I'm going to fill another bug on macports project for valgrind. Anyway, could you name another pgm that can help ? Best. a. This looks like a duplicate of bug 316209, which should be fixed with 4.10.5. > kde4-baseapps @4.10.3 kde/kde4-baseapps Interesting, all other packages are from 4.10.5, but kde4-baseapps (which contains Dolphin), still is the older version. Arnaud, can you confirm it is fixed in the current version? Good catch, Christoph! At first sight, I only saw the 4.10.5 version number and thought that it must be something different. Arnaud, in the unlikely event that you still see this crash after upgrading kde-baseapps to 4.10.5, please reopen this report. Thanks! Moreover, I would appreciate it if you would *not* change the severity of this report again. There is a reason why I changed it to "crash". Looking for crash reports with similar backtrace patterns is quite easy with the advanced bugzilla search if the reports have the severity "crash", but it's quite hard if you always have to remember that there was a certain user who insists that his report needs a different severity. Thanks for your understanding. BTW, the "severity" of a Dolphin bug report has no influence whatsoever on how quickly a Dolphin bug will be fixed. Reproducible crashes are usually fixed as soon as possible. (In reply to comment #4) > Good catch, Christoph! At first sight, I only saw the 4.10.5 version number > and thought that it must be something different. > > Arnaud, in the unlikely event that you still see this crash after upgrading > kde-baseapps to 4.10.5, please reopen this report. Thanks! > > Moreover, I would appreciate it if you would *not* change the severity of > this report again. There is a reason why I changed it to "crash". Looking > for crash reports with similar backtrace patterns is quite easy with the > advanced bugzilla search if the reports have the severity "crash", but it's > quite hard if you always have to remember that there was a certain user who > insists that his report needs a different severity. Thanks for your > understanding. > > BTW, the "severity" of a Dolphin bug report has no influence whatsoever on > how quickly a Dolphin bug will be fixed. Reproducible crashes are usually > fixed as soon as possible. Hello Frank, Christoph, I've managed to get valgrind up and running on my system, so here's the output (don't know if it can help, seems really short to me) Frank, about the change in the severity of this ticket, I don't know if it's me that made the change, when replying. I just post a reply to your preceeding comment. What I can tell is that by default, Status is set to NEEDSINFO and WAITINGFORINFO when you click on Reply. Am I doing something wrong ? Finaly, I don't see 4.10.5 version of kde4-baseapps when I list this package with MacPorts. I'm going to gather some help on this side. ==11273== Memcheck, a memory error detector ==11273== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==11273== Using Valgrind-3.9.0.SVN and LibVEX; rerun with -h for copyright info ==11273== Command: dolphin.app/Contents/MacOS/dolphin ==11273== ==11273== WARNING: Support on MacOS 10.8 is experimental and mostly broken. ==11273== WARNING: Expect incorrect results, assertions and crashes. ==11273== WARNING: In particular, Memcheck on 32-bit programs will fail to ==11273== WARNING: detect any errors associated with heap-allocated data. ==11273== --11273-- dolphin.app/Contents/MacOS/dolphin: --11273-- dSYM directory is missing; consider using --dsymutil=yes UNKNOWN workq_ops option 32 valgrind: m_syswrap/syswrap-amd64-darwin.c:460 (void wqthread_hijack(Addr, Addr, Addr, Addr, Int, Addr)): Assertion 'VG_(is_valid_tid)(tid)' failed. ==11273== at 0x23803F6CB: ??? ==11273== by 0x23803F670: ??? ==11273== by 0x2380DD027: ??? sched status: running_tid=0 Thread 1: status = VgTs_WaitSys ==11273== at 0x3E15686: mach_msg_trap (in /usr/lib/system/libsystem_kernel.dylib) ==11273== by 0x57FD739: _scsclient_CreateCacheableFromFrameworkSymbol (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x57FD655: SCClientSession::createCacheable(SCCacheableName, char const*) (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x57FD5E0: SCSession::findOrCreateCacheable(SCCacheableName, char const*) (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x57FD4FA: scCreateSystemCacheable (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x57FD4C0: _CLV_GetCacheableOnce() (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x3CAFFEF: pthread_once (in /usr/lib/system/libsystem_c.dylib) ==11273== by 0x57FD350: _standalone_CopyCheckFixForBundleID (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x57FD24F: GetBugsForOurBundleIDFromCoreservicesd (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x57FCEFB: _CSCheckFix (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x5810F5B: _Gestalt_SystemVersion (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x5810D53: Gestalt (in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore) ==11273== by 0x28A8585: global constructors keyed to a (in /opt/local/Library/Frameworks/QtCore.framework/Versions/4/QtCore) ==11273== by 0x7FFF5FC13377: ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC13761: ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC1006D: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0FEB9: ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC01FBF: dyld::initializeMainExecutable() (in /usr/lib/dyld) ==11273== by 0x7FFF5FC05B03: dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC01396: dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) (in /usr/lib/dyld) ==11273== by 0x7FFF5FC0105D: _dyld_start (in /usr/lib/dyld) Best. Thanks for the update. (In reply to comment #5) > I've managed to get valgrind up and running on my system, so here's the > output (don't know if it can help, seems really short to me) Hm, I can't see anything in the log that looks relevant to the crash. > Frank, about the change in the severity of this ticket, I don't know if it's > me that made the change, when replying. I just post a reply to your > preceeding comment. > What I can tell is that by default, Status is set to NEEDSINFO and > WAITINGFORINFO when you click on Reply. Am I doing something wrong ? Thanks for the clarification. Probably you're not doing anything wrong - maybe it's just some bugzilla weirdness, I don't know ;-) > Finaly, I don't see 4.10.5 version of kde4-baseapps when I list this package > with MacPorts. I'm going to gather some help on this side. I can't say much about that - you might indeed want to ask the people who provide the MacPorts packages. If you still see the crash after upgrading, please let us know, but I think that this is rather unlikely. Thanks. Hi, Problem solved with kde4-baseapps @4.10.5 kde4-baseapps was in an old version (@4.10.3) in MacPorts, due to rsync pb on their side. Thanks again a lot for your help. Best. a. (In reply to comment #6) > Thanks for the update. > > (In reply to comment #5) > > I've managed to get valgrind up and running on my system, so here's the > > output (don't know if it can help, seems really short to me) > > Hm, I can't see anything in the log that looks relevant to the crash. > > > Frank, about the change in the severity of this ticket, I don't know if it's > > me that made the change, when replying. I just post a reply to your > > preceeding comment. > > What I can tell is that by default, Status is set to NEEDSINFO and > > WAITINGFORINFO when you click on Reply. Am I doing something wrong ? > > Thanks for the clarification. Probably you're not doing anything wrong - > maybe it's just some bugzilla weirdness, I don't know ;-) > > > Finaly, I don't see 4.10.5 version of kde4-baseapps when I list this package > > with MacPorts. I'm going to gather some help on this side. > > I can't say much about that - you might indeed want to ask the people who > provide the MacPorts packages. If you still see the crash after upgrading, > please let us know, but I think that this is rather unlikely. Thanks. Thanks for the update - it's good to know that it works now :-) Closing, works according to original reporter. |