[kde] [Bug 334005] New:=?UTF-8?Q?=20Awaria=20Baloo=20po=20zalogowaniu=20si=C4=99=20do=20Pulpitu=20Plazmy?=.

xa.kasprzyk at gmail.com xa.kasprzyk at gmail.com
Mon Apr 28 11:05:57 BST 2014


https://bugs.kde.org/show_bug.cgi?id=334005

            Bug ID: 334005
           Summary: Awaria Baloo po zalogowaniu siÄ™ do Pulpitu Plazmy.
    Classification: Unclassified
           Product: kde
           Version: unspecified
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: xa.kasprzyk at gmail.com

Application: baloo_file (0.1)
KDE Platform Version: 4.13.0
Qt Version: 4.8.5
Operating System: Linux 3.11.10-7-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: 
Just updated KDE to 4.13 from Repo KDE_Current

- Unusual behavior I noticed:

KWin Crash coz of missing libEGL libs (reinstaled them).

The crash can be reproduced every time.

-- Backtrace:
Application: Plik Baloo (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>,
std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> >
>::operator= (this=this at entry=0x1978330, __x=<error reading variable: Cannot
access memory at address 0x10>) at /usr/include/c++/4.8/bits/vector.tcc:161
#6  0x00007f48eb68d4bc in Xapian::Database::Database (this=0x1978328,
other=...) at api/omdatabase.cc:82
#7  0x00007f48eb69763a in Xapian::Enquire::Internal::Internal (this=0x1978320,
db_=..., errorhandler_=0x0) at api/omenquire.cc:621
#8  0x00007f48eb6977ee in Xapian::Enquire::Enquire (this=0x7fff999c83f0,
databases=..., errorhandler=0x0) at api/omenquire.cc:874
#9  0x0000000000417d93 in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list