[kmail2] [Bug 395910] KMail segfaults upon exit

2018-12-06 Thread Øystein Olsen 
https://bugs.kde.org/show_bug.cgi?id=395910

--- Comment #5 from Øystein Olsen  ---
Based on the backtrace and given the correct bug number, I can see that this is
an unrelated bug.

Now, I do not use kontact and I do exactly the same as described in this bug.
Start kmail, then exit through the system tray icon (or Ctrl+Q). The
segmentation fault happens without ever opening an email in a subwindow. 

Two different users found a bug with an exact matching description. How were we
supposed to figure out that this was an unrelated bug and find the correct one,
which has completely different description?

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

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-11-29 Thread Øystein Olsen 
https://bugs.kde.org/show_bug.cgi?id=395910

Øystein Olsen  changed:

   What|Removed |Added

 CC||dr.sci...@gmail.com

--- Comment #2 from Øystein Olsen  ---
I have the same issue with kmail 18.08.3. 

Qt version: 5.11.2
Framework: 5.52.0
OS: OpenSUSE Tumbleweed.

I believe this back-trace should be more useful:


Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
28return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7f53c794ba40 (LWP 3780))]

Thread 31 (Thread 0x7f529d801700 (LWP 3859)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f529d8008c0,
expected=0, futex_word=0x7f529d800aa8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f529d800960, mutex=0x7f529d800a58,
cond=0x7f529d800a80) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f529d800a80, mutex=0x7f529d800a58,
abstime=0x7f529d800960) at pthread_cond_wait.c:667
#3  0x7f53d38b7d37 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120
#4  0x7f53d38b9a0a in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221
#5  0x7f53d38b9af2 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161
#6  0x7f53d38be8b1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171
#7  0x7f53d38bfbaf in base::internal::SchedulerWorker::Thread::ThreadMain
() at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42
#8  0x7f53d38ca1c1 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75
#9  0x7f53dab27554 in start_thread (arg=) at
pthread_create.c:463
#10 0x7f53dd49cccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30 (Thread 0x7f529ede5700 (LWP 3857)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f529ede48c0,
expected=0, futex_word=0x7f529ede4aa8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f529ede4960, mutex=0x7f529ede4a58,
cond=0x7f529ede4a80) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f529ede4a80, mutex=0x7f529ede4a58,
abstime=0x7f529ede4960) at pthread_cond_wait.c:667
#3  0x7f53d38b7d37 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120
#4  0x7f53d38b9a0a in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221
#5  0x7f53d38b9af2 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161
#6  0x7f53d38be8b1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171
#7  0x7f53d38bfbaf in base::internal::SchedulerWorker::Thread::ThreadMain
() at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42
#8  0x7f53d38ca1c1 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75
#9  0x7f53dab27554 in start_thread (arg=) at
pthread_create.c:463
#10 0x7f53dd49cccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7f529f5e6700 (LWP 3856)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f529f5e58c0,
expected=0, futex_word=0x7f529f5e5aa8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f529f5e5960, mutex=0x7f529f5e5a58,
cond=0x7f529f5e5a80) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f529f5e5a80, mutex=0x7f529f5e5a58,
abstime=0x7f529f5e5960) at pthread_cond_wait.c:667
#3  0x7f53d38b7d37 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120
#4  0x7f53d38b9a0a in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221
#5  0x7f53d38b9af2 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161
#6  0x7f53d38be8b1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171
#7  0x7f53d38bfd91 in base::internal::SchedulerWorker::Thread::ThreadMain
() at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68
#8  0x7f53d38ca1c1 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75
#9  0x7f53dab27554 in start_t

[frameworks-baloo] [Bug 382117] Exclude folders ignores wildcard patterns

2017-12-12 Thread Øystein Olsen 
https://bugs.kde.org/show_bug.cgi?id=382117

Øystein Olsen <dr.sci...@gmail.com> changed:

   What|Removed |Added

 CC||dr.sci...@gmail.com

--- Comment #2 from Øystein Olsen <dr.sci...@gmail.com> ---
I have the same problem on KDE Neon. I have large number of differen build
folders for different projects. They area usually called
build-project_name-something, and I have to manually specify each of them to
stop baloo from indexing them during building or testing.

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

[kdenlive] [Bug 368259] Selecting output folder gives an error message when default file already exists

2016-09-19 Thread Øystein Olsen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368259

Øystein Olsen <dr.sci...@gmail.com> changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #5 from Øystein Olsen <dr.sci...@gmail.com> ---
Tested with Frameworks 5.26 on openSUSE Tumbleweed and KDE Neon. This issue has
been fixed.

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

[kdenlive] [Bug 368259] Selecting output folder gives an error message when default file already exists

2016-09-08 Thread Øystein Olsen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368259

Øystein Olsen <dr.sci...@gmail.com> changed:

   What|Removed |Added

Summary|Selecting output folder |Selecting output folder
   |gives an error message when |gives an error message when
   |rendering to mp4|default file already exists

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

[kdenlive] [Bug 368259] Selecting output folder gives an error message when rendering to mp4

2016-09-05 Thread Øystein Olsen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368259

--- Comment #2 from Øystein Olsen <dr.sci...@gmail.com> ---
On both my machines back home (openSUSE Tumbleweed):

Version 16.08.0
KDE Frameworks 5.25.0
Qt 5.6.1 (built against 5.6.1)

I see the reported problem on both machines. (I also rebuilt kdenlive  just to
see if that had any effect.)

I just tested on a machine with KDE Neon. The problem does not show up there,
although I did see it a while back.

Version 16.08.0
KDE Frameworks 5.25.0
Qt 5.7.0 (built against 5.7.0)

I'll test with a new user on my home machines when I get back from work.

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

[kdenlive] [Bug 368259] New: Selecting output folder gives an error message when rendering to mp4

2016-09-05 Thread Øystein Olsen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368259

Bug ID: 368259
   Summary: Selecting output folder gives an error message when
rendering to mp4
   Product: kdenlive
   Version: 16.08.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: dr.sci...@gmail.com

I get the following error message when I attempt to select an output folder in
the rendering step:

/srv/multimedia/kdenlive/untitled.mp4 is a file, but a folder was expected.

This only happens if the output format is mp4.  WebM and MEPG-2 works as
expected, i.e. the open file dialog is positioned in /srv/multimedia/kdenlive/

Reproducible: Always

Steps to Reproduce:
1. Open kdenlive
2. Add a clip (to the timeline)
3. Click render
4. Select MP4 as format
5. Hit button (next to the lineedit with filename) to select output folder


Actual Results:  
An error box pops up over the open file dialog:

/srv/multimedia/kdenlive/untitled.mp4 is a file, but a folder was expected.


Expected Results:  
An open file dialog positioned in /srv/multimedia/kdenlive/

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

[kontact] [Bug 367797] Kmail crashes trying to reply an email / Can't start after that

2016-08-25 Thread Øystein Olsen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=367797

Øystein Olsen <dr.sci...@gmail.com> changed:

   What|Removed |Added

 CC||dr.sci...@gmail.com

--- Comment #2 from Øystein Olsen <dr.sci...@gmail.com> ---
I have  the same problem. A possible work-around is to remove sonnet-plugins:

$ sudo apt-get purge sonnet-plugins*

You then loose spellchecking, but kmail started again on my machine.

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

[systemsettings] [Bug 365790] New: Touchpad module crashes System Settings

2016-07-17 Thread Øystein Olsen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365790

Bug ID: 365790
   Summary: Touchpad module crashes System Settings
   Product: systemsettings
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dr.sci...@gmail.com

Application: systemsettings5 (5.7.0)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160625) (x86_64)"

-- Information about the crash:
Selecting touchpad module in System Settings crashes System Settings.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe4885dc8c0 (LWP 1642))]

Thread 2 (Thread 0x7fe472cb6700 (LWP 1644)):
#0  0x7fe47fe12063 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7fe47fe1454b in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe47fe14f7b in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe47fe1516c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fe484b6caeb in QEventDispatcherGlib::processEvents
(this=0x7fe46c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fe484b1476a in QEventLoop::exec (this=this@entry=0x7fe472cb5cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fe48493a3b3 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7fe48546e9b5 in ?? () from /usr/lib64/libQt5DBus.so.5
#8  0x7fe48493f2d8 in QThreadPrivate::start (arg=0x7fe4856e1d20) at
thread/qthread_unix.cpp:341
#9  0x7fe480334474 in start_thread () from /lib64/libpthread.so.0
#10 0x7fe48424a3ed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe4885dc8c0 (LWP 1642)):
[KCrash Handler]
#6  0x7fe45a4f539e in TouchpadConfig::TouchpadConfig (this=0x18edf40,
parent=, args=...) at
/usr/src/debug/plasma-desktop-5.7.0/kcms/touchpad/src/kcm/touchpadconfig.cpp:185
#7  0x7fe45a4f2498 in KPluginFactory::createInstance (parentWidget=, parent=, args=...) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:477
#8  0x7fe484fa9e0b in KPluginFactory::create (this=this@entry=0x1796480,
iface=0x7fe487605608 "KCModule", parentWidget=parentWidget@entry=0x0,
parent=parent@entry=0x17be600, args=..., keyword=...) at
/usr/src/debug/kcoreaddons-5.24.0/src/lib/plugin/kpluginfactory.cpp:145
#9  0x7fe487fc7a04 in KPluginFactory::create (args=...,
keyword=..., parent=0x17be600, parentWidget=0x0, this=0x1796480) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:519
#10 KService::createInstance (error=0x7ffcad291380, args=...,
parent=0x17be600, parentWidget=0x0, this=0x12e3230) at
/usr/include/KF5/KService/kservice.h:526
#11 KService::createInstance (error=0x7ffcad291380, args=...,
parent=0x17be600, this=) at
/usr/include/KF5/KService/kservice.h:501
#12 KCModuleLoader::loadModule (mod=...,
report=report@entry=KCModuleLoader::Inline, parent=0x17be600, args=...) at
/usr/src/debug/kcmutils-5.24.0/src/kcmoduleloader.cpp:92
#13 0x7fe487fcf05f in KCModuleProxyPrivate::loadModule
(this=this@entry=0x17be550) at
/usr/src/debug/kcmutils-5.24.0/src/kcmoduleproxy.cpp:109
#14 0x7fe487fcfc55 in KCModuleProxy::realModule (this=this@entry=0x17be600)
at /usr/src/debug/kcmutils-5.24.0/src/kcmoduleproxy.cpp:82
#15 0x7fe487fd01a3 in KCModuleProxy::showEvent (this=0x17be600,
ev=0x7ffcad291920) at /usr/src/debug/kcmutils-5.24.0/src/kcmoduleproxy.cpp:195
#16 0x7fe48672f5c8 in QWidget::event (this=0x17be600, event=0x7ffcad291920)
at kernel/qwidget.cpp:9114
#17 0x7fe4866e9aec in QApplicationPrivate::notify_helper (this=, receiver=0x17be600, e=0x7ffcad291920) at kernel/qapplication.cpp:3804
#18 0x7fe4866eef8f in QApplication::notify (this=0x7ffcad293130,
receiver=0x17be600, e=0x7ffcad291920) at kernel/qapplication.cpp:3561
#19 0x7fe484b16a20 in QCoreApplication::notifyInternal2
(receiver=receiver@entry=0x17be600, event=event@entry=0x7ffcad291920) at
kernel/qcoreapplication.cpp:1015
#20 0x7fe48672c1f8 in QCoreApplication::sendEvent (event=0x7ffcad291920,
receiver=0x17be600) at ../../src/corelib/kernel/qcoreapplication.h:225
#21 QWidgetPrivate::show_helper (this=0x17be6c0) at kernel/qwidget.cpp:7882
#22 0x7fe48672c026 in QWidgetPrivate::show_recursive (this=)
at kernel/qwidget.cpp:7753
#23 0x7fe48672c137 in QWidgetPrivate::showChildren
(this=this@entry=0x17ce220, spontaneous=spontaneous@entry=false) at
kernel/qwidget.cpp:8259
#24 0x7fe48672c1cf in QWidgetPrivate::show_helper
(this=this@entry=0x17ce220) at kernel/qwidget.cpp:7829
#25 0x7fe48672f015 in QWidget::setVisible (this=0x17c1930,
visible=) at kernel/qwidget.cpp:8178
#26 0x7fe48672c148 in