| Summary: | System Settings crashes when clicking Digital Camera icon | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Rob V <rvalkass> |
| Component: | kcm_kamera | Assignee: | Marcus Meissner <marcus> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | cfeck |
| Priority: | NOR | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Rob V
2011-05-08 10:05:55 UTC
it works for me (as usual) in KDE 4.5.x can you run: valgrind kcmshell4 kamera to see if there is anything special happening? It also does it without the camera plugged in (an obvious thing I forgot to check). Output from valgrind: [rob@rob-laptop ~]$ valgrind kcmshell4 kamera ==2339== Memcheck, a memory error detector ==2339== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==2339== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==2339== Command: kcmshell4 kamera ==2339== ==2339== Conditional jump or move depends on uninitialised value(s) ==2339== at 0x4005339: operator delete[](void*, std::nothrow_t const&) (vg_replace_malloc.c:380) ==2339== by 0xC60CE7: ??? (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0xBD07C8: std::underflow_error::underflow_error(std::string const&) (stdexcept.cc:72) ==2339== by 0xBD0FAD: virtual thunk to std::strstream::~strstream() (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0x9599AD: pthread_once (pthread_once.S:122) ==2339== by 0xBD10A8: std::locale::locale() (strstream.cc:369) ==2339== by 0xBCDF97: std::ios_base::Init::Init() (locale_facets.h:1930) ==2339== by 0x6A8B375: KTar::KTarPrivate::readHeader(char*, QString&, QString&) (ktar.cpp:257) ==2339== by 0x6BCB03C: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x69F3BAB: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x7A88FB: call_init (dl-init.c:68) ==2339== by 0x7A8A18: _dl_init (dl-init.c:132) ==2339== ==2339== Invalid free() / delete / delete[] ==2339== at 0x4005379: operator delete[](void*, std::nothrow_t const&) (vg_replace_malloc.c:380) ==2339== by 0xC60CE7: ??? (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0xBD07C8: std::underflow_error::underflow_error(std::string const&) (stdexcept.cc:72) ==2339== by 0xBD0FAD: virtual thunk to std::strstream::~strstream() (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0x9599AD: pthread_once (pthread_once.S:122) ==2339== by 0xBD10A8: std::locale::locale() (strstream.cc:369) ==2339== by 0xBCDF97: std::ios_base::Init::Init() (locale_facets.h:1930) ==2339== by 0x6A8B375: KTar::KTarPrivate::readHeader(char*, QString&, QString&) (ktar.cpp:257) ==2339== by 0x6BCB03C: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x69F3BAB: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x7A88FB: call_init (dl-init.c:68) ==2339== by 0x7A8A18: _dl_init (dl-init.c:132) ==2339== Address 0xb8cb24 is not stack'd, malloc'd or (recently) free'd ==2339== ==2339== Use of uninitialised value of size 4 ==2339== at 0x4005388: operator delete[](void*, std::nothrow_t const&) (vg_replace_malloc.c:380) ==2339== by 0xBD07C8: std::underflow_error::underflow_error(std::string const&) (stdexcept.cc:72) ==2339== by 0xBD0FAD: virtual thunk to std::strstream::~strstream() (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0x9599AD: pthread_once (pthread_once.S:122) ==2339== by 0xBD10A8: std::locale::locale() (strstream.cc:369) ==2339== by 0xBCDF97: std::ios_base::Init::Init() (locale_facets.h:1930) ==2339== by 0x6A8B375: KTar::KTarPrivate::readHeader(char*, QString&, QString&) (ktar.cpp:257) ==2339== by 0x6BCB03C: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x69F3BAB: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x7A88FB: call_init (dl-init.c:68) ==2339== by 0x7A8A18: _dl_init (dl-init.c:132) ==2339== by 0x79A8AE: ??? (in /lib/ld-2.13.so) ==2339== ==2339== Invalid read of size 1 ==2339== at 0xC60CE8: ??? (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0xBD07C8: std::underflow_error::underflow_error(std::string const&) (stdexcept.cc:72) ==2339== by 0xBD0FAD: virtual thunk to std::strstream::~strstream() (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0x9599AD: pthread_once (pthread_once.S:122) ==2339== by 0xBD10A8: std::locale::locale() (strstream.cc:369) ==2339== by 0xBCDF97: std::ios_base::Init::Init() (locale_facets.h:1930) ==2339== by 0x6A8B375: KTar::KTarPrivate::readHeader(char*, QString&, QString&) (ktar.cpp:257) ==2339== by 0x6BCB03C: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x69F3BAB: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x7A88FB: call_init (dl-init.c:68) ==2339== by 0x7A8A18: _dl_init (dl-init.c:132) ==2339== by 0x79A8AE: ??? (in /lib/ld-2.13.so) ==2339== Address 0x6a00c246 is not stack'd, malloc'd or (recently) free'd ==2339== ==2339== ==2339== Process terminating with default action of signal 11 (SIGSEGV) ==2339== Access not within mapped region at address 0x6A00C246 ==2339== at 0xC60CE8: ??? (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0xBD07C8: std::underflow_error::underflow_error(std::string const&) (stdexcept.cc:72) ==2339== by 0xBD0FAD: virtual thunk to std::strstream::~strstream() (in /usr/lib/libstdc++.so.6.0.14) ==2339== by 0x9599AD: pthread_once (pthread_once.S:122) ==2339== by 0xBD10A8: std::locale::locale() (strstream.cc:369) ==2339== by 0xBCDF97: std::ios_base::Init::Init() (locale_facets.h:1930) ==2339== by 0x6A8B375: KTar::KTarPrivate::readHeader(char*, QString&, QString&) (ktar.cpp:257) ==2339== by 0x6BCB03C: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x69F3BAB: ??? (in /usr/lib/libkdecore.so.5.6.0) ==2339== by 0x7A88FB: call_init (dl-init.c:68) ==2339== by 0x7A8A18: _dl_init (dl-init.c:132) ==2339== by 0x79A8AE: ??? (in /lib/ld-2.13.so) ==2339== If you believe this happened as a result of a stack ==2339== overflow in your program's main thread (unlikely but ==2339== possible), you can try to increase the size of the ==2339== main thread stack using the --main-stacksize= flag. ==2339== The main thread stack size used in this run was 8388608. ==2339== ==2339== HEAP SUMMARY: ==2339== in use at exit: 3,899 bytes in 59 blocks ==2339== total heap usage: 92 allocs, 34 frees, 6,010 bytes allocated ==2339== ==2339== LEAK SUMMARY: ==2339== definitely lost: 0 bytes in 0 blocks ==2339== indirectly lost: 0 bytes in 0 blocks ==2339== possibly lost: 0 bytes in 0 blocks ==2339== still reachable: 3,899 bytes in 59 blocks ==2339== suppressed: 0 bytes in 0 blocks ==2339== Rerun with --leak-check=full to see details of leaked memory ==2339== ==2339== For counts of detected and suppressed errors, rerun with: -v ==2339== Use --track-origins=yes to see where uninitialised values come from ==2339== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 69 from 8) Segmentation fault (core dumped) On 8 May 2011 15:25, Marcus Meissner <marcus@jet.franken.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=272761 > > > > > > --- Comment #1 from Marcus Meissner <marcus jet franken de> 2011-05-08 > 16:25:06 --- > it works for me (as usual) in KDE 4.5.x > > can you run: > > valgrind kcmshell4 kamera > > to see if there is anything special happening? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > [Comment from a bug report cleaner] The backtrace looks related to the one in bug 236844. Regards Marcus, I have another explanation, different from that in bug 236844 comment #7. It could actually be a duplicate of bug 247830. Rob, is there a difference if you double click on the Kamera icon in System Settings or single click? Single click works, double click crashes. I guess this can be closed now - it's my own fault for forgetting to switch double-clicking on in mouse settings I guess! On 11 May 2011 21:13, Christoph Feck <christoph@maxiom.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=272761 > > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |christoph@maxiom.de > > > > > --- Comment #4 from Christoph Feck <christoph maxiom de> 2011-05-11 > 22:13:02 --- > Marcus, I have another explanation, different from that in bug 236844 > comment > #7. It could actually be a duplicate of bug 247830. > > Rob, is there a difference if you double click on the Kamera icon in System > Settings or single click? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Rob, it's not your fault, it is a bug in the module authorization handling. Modules can be loaded twice because of the local event loop that KAuth runs. There is a workaround in 4.7, it probably should be backported. *** This bug has been marked as a duplicate of bug 247830 *** |