[krita] [Bug 364323] I get "krita.exe stopped working" after I've opened a file and been working for somewhere between 5 and 15 minutes.

2016-10-04 Thread Savanna Stewart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364323

--- Comment #11 from Savanna Stewart  ---
No, nothing like that.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 364323] I get "krita.exe stopped working" after I've opened a file and been working for somewhere between 5 and 15 minutes.

2016-10-02 Thread Savanna Stewart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364323

--- Comment #9 from Savanna Stewart  ---
I am having a similar problem, I get the same notification, but usually when I
try to open a new document, or before Krita had even fully loaded. I have tried
various settings and even opening an animation.

-- 
You are receiving this mail because:
You are watching all bug changes.


[krita] [Bug 364323] I get "krita.exe stopped working" after I've opened a file and been working for somewhere between 5 and 15 minutes.

2016-10-02 Thread Savanna Stewart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364323

Savanna Stewart  changed:

   What|Removed |Added

 CC||savannarstew...@gmail.com

--- Comment #8 from Savanna Stewart  ---
I am having a similar problem, I get the same notification, but usually when I
try to open a new document, or before Krita had even fully loaded. I have tried
various settings and even opening an animation.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Baloo] [Bug 366805] New: baloo crashed unexpectedly

2016-08-15 Thread stewart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366805

Bug ID: 366805
   Summary: baloo crashed unexpectedly
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: pinak.ah...@gmail.com
  Reporter: stewart_robert...@sky.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-34-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: 

I was changing the settings in a virtualbox vm using the Oracle VM VirtualBox
Manager (V5.1). Specifically i changed the monitor count from 1 to 2...

Suspect VirtualBox activity is unrelated but crash was instanteneous after this
action & made me suspicious they were related so I include the info in case
there is some possible reason why one would cause the other. May well just be a
coincidence.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6f759e18c0 (LWP 4614))]

Thread 2 (Thread 0x7f6e2a845700 (LWP 5313)):
#0  0x7f6f73ab8e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6f70c5839c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f70c584ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f74702a9b in QEventDispatcherGlib::processEvents
(this=0x7f6e240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6f746a9dea in QEventLoop::exec (this=this@entry=0x7f6e2a844bc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00420cd8 in Baloo::FileContentIndexer::run (this=0x17aab80) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/filecontentindexer.cpp:71
#6  0x7f6f744c8343 in QThreadPoolThread::run (this=0x189a590) at
thread/qthreadpool.cpp:93
#7  0x7f6f744cb84e in QThreadPrivate::start (arg=0x189a590) at
thread/qthread_unix.cpp:331
#8  0x7f6f731156fa in start_thread (arg=0x7f6e2a845700) at
pthread_create.c:333
#9  0x7f6f73ac4b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f6f759e18c0 (LWP 4614)):
[KCrash Handler]
#6  0x7f6f739f3418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f6f739f501a in __GI_abort () at abort.c:89
#8  0x7f6f721e5002 in mdb_assert_fail (env=0x17aadd0,
expr_txt=expr_txt@entry=0x7f6f721e6a5f "rc == 0",
func=func@entry=0x7f6f721e7398 <__func__.7098> "mdb_page_dirty",
line=line@entry=2065, file=0x7f6f721e6a40 "mdb.c") at mdb.c:1481
#9  0x7f6f721da6a5 in mdb_page_dirty (txn=0x1763c60, mp=) at
mdb.c:2065
#10 0x7f6f721db863 in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7ffc1cfd0908, mc=0x7ffc1cfd0e40) at mdb.c:2246
#11 0x7f6f721dbac9 in mdb_page_touch (mc=mc@entry=0x7ffc1cfd0e40) at
mdb.c:2364
#12 0x7f6f721dd704 in mdb_cursor_touch (mc=mc@entry=0x7ffc1cfd0e40) at
mdb.c:6267
#13 0x7f6f721e0805 in mdb_cursor_put (mc=0x7ffc1cfd0e40,
key=0x7ffc1cfd1220, data=0x7ffc1cfd1230, flags=) at mdb.c:6401
#14 0x7f6f721e3260 in mdb_put (txn=0x1763c60, dbi=3,
key=key@entry=0x7ffc1cfd1220, data=data@entry=0x7ffc1cfd1230,
flags=flags@entry=0) at mdb.c:8759
#15 0x7f6f74ba3eba in Baloo::PositionDB::put
(this=this@entry=0x7ffc1cfd1310, term=..., list=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/positiondb.cpp:79
#16 0x7f6f74bb6b5a in Baloo::WriteTransaction::commit (this=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:314
#17 0x7f6f74bae032 in Baloo::Transaction::commit
(this=this@entry=0x7ffc1cfd13a0) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:262
#18 0x0042a02b in Baloo::MetadataMover::moveFileMetadata
(this=0x1781f80, from=..., to=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:58
#19 0x7f6f746dae4f in QtPrivate::QSlotObjectBase::call (a=0x7ffc1cfd1500,
r=0x7ffc1cfd1bc0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#20 QMetaObject::activate (sender=sender@entry=0x17373f0,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffc1cfd1500) at kernel/qobject.cpp:3698
#21 0x7f6f746db7d7 in QMetaObject::activate (sender=sender@entry=0x17373f0,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffc1cfd1500)
at kernel/qobject.cpp:3578
#22 0x0042aaba in KInotify::moved (this=this@entry=0x17373f0, _t1=...,
_t2=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330
#23 0x0042cbff in KInotify::slotEvent (this=,
socket=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:421
#

[konqueror] [Bug 350492] reproducible crash on a particular URL

2016-01-17 Thread Stewart via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=350492

Stewart  changed:

   What|Removed |Added

 CC||gsjenk...@gmail.com

--- Comment #1 from Stewart  ---
The website http://www.theguardian.com alone will crash Konqueror. Konqueror
crashes with only one tab open on this website. I have cookies set to prompt.
Crashes occur whether I accept or reject the cookies from this site. I have
java and java script disabled. I have a trace available, but DrKonqi crashed
when logging into the bug tracking system. This has been repeatable for years,
I have finally taken the time to report it. This is reproducible every time.

OS is Debian 7.9 (wheezy) with kernel 3.19.2-custom. The kernal is the only
thing I have compile myself.

-- 
You are receiving this mail because:
You are watching all bug changes.