from:"Stephan Diestelhorst"

[neon] [Bug 456968] KDE Wallet Manager window is blank

2022-07-25 Thread Stephan Diestelhorst

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

--- Comment #5 from Stephan Diestelhorst  ---
Another way to at least get some wallet functionality back while leaving the
conflict:

$ apt download libkf5wallet-bin
Get:1 http://archive.neon.kde.org/testing focal/main amd64 libkf5wallet-bin
amd64 5.96.0+p20.04+tunstable+git20220716.0119-0 [198 kB]
Fetched 198 kB in 2s (103 kB/s)
$ sudo dpkg -i --force-depends
libkf5wallet-bin_5.96.0+p20.04+tunstable+git20220716.0119-0_amd64.deb
(Reading database ... 173607 files and directories currently installed.)
Preparing to unpack
libkf5wallet-bin_5.96.0+p20.04+tunstable+git20220716.0119-0_amd64.deb ...
Unpacking libkf5wallet-bin (5.96.0+p20.04+tunstable+git20220716.0119-0) over
(5.68.0-0ubuntu2) ...
dpkg: libkf5wallet-bin: dependency problems, but configuring anyway as you
requested:
 libkf5wallet-bin depends on libqca-qt5-2 (>=
2.3.4+p20.04+tunstable+git20220715.0127); however:
  Version of libqca-qt5-2:amd64 on system is
2.3.4+p20.04+tstable+git20220713.0040-0.

Setting up libkf5wallet-bin (5.96.0+p20.04+tunstable+git20220716.0119-0) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...

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

[neon] [Bug 456968] KDE Wallet Manager window is blank

2022-07-25 Thread Stephan Diestelhorst

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

--- Comment #4 from Stephan Diestelhorst  ---
This seems to exist due to a dependency problem that Hugues describes.  Getting
the exact same thing:

> $ sudo aptitude install kwalletcli
> The following NEW packages will be installed:
>   kwalletcli libkf5wallet-bin{ab} mksh{a} 
> 0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
> Need to get 198 kB/798 kB of archives. After unpacking 2,419 kB will be used.
> The following packages have unmet dependencies:
>  libkf5wallet-bin : Depends: libqca-qt5-2 (>= 
> 2.3.4+p20.04+tunstable+git20220715.0127) but 
> 2.3.4+p20.04+tstable+git20220713.0040-0 is installed
> The following actions will resolve these dependencies:
> 
> Keep the following packages at their current version:
> 1) kwalletcli [Not Installed] 
> 2) libkf5wallet-bin [Not Installed]   
> 
> Accept this solution? [Y/n/q/?] n
> The following actions will resolve these dependencies:
> 
> Install the following packages:   
>  
> 1) libkf5wallet-bin [5.68.0-0ubuntu2 (focal)] 
>   
> 
> Downgrade the following packages: 
>  
> 2) libkf5wallet-data [5.96.0+p20.04+tunstable+git20220716.0119-0 (focal, 
> now) -> 5.68.0-0ubuntu2 (focal)]   
> 3) libkf5wallet5 [5.96.0+p20.04+tunstable+git20220716.0119-0 (focal, now) 
> -> 5.68.0-0ubuntu2 (focal)]   
> 4) libkwalletbackend5-5 [5.96.0+p20.04+tunstable+git20220716.0119-0 
> (focal, now) -> 5.68.0-0ubuntu2 (focal)]
> 
> Accept this solution? [Y/n/q/?] n
>  *** No more solutions available ***

$ dpkg -l libqca-qt5-2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture
Description
+++-==-===--===>
ii  libqca-qt5-2:amd64 2.3.4+p20.04+tstable+git20220713.0040-0 amd64   
libraries for the Qt Cryptographic >

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

[kwalletmanager] [Bug 456968] KDE Wallet Manager window is blank

2022-07-22 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[kdeconnect] [Bug 438319] KDE Connect crashes when pairing from phone

2021-06-09 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Stephan Diestelhorst  ---
This now works again with updating to
21.04.1-0xneon+20.04+focal+release+build21 for kdeconnect in KDE Neon.

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

[kdeconnect] [Bug 438319] New: KDE Connect crashes when pairing from phone

2021-06-09 Thread Stephan Diestelhorst

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

Bug ID: 438319
   Summary: KDE Connect crashes when pairing from phone
   Product: kdeconnect
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: stephan.diestelho...@gmail.com
  Target Milestone: ---

Application: kdeconnectd (21.04.1)

Qt Version: 5.15.3
Frameworks Version: 5.82.0
Operating System: Linux 5.9.2-050902-generic x86_64
Windowing System: X11
Drkonqi Version: 5.21.5
Distribution: KDE neon User Edition 5.21

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

Trying to pair my phone (Xiaomi Mi8) in the same WiFi network using the F-Droid
app (version 1.17.0) and the desktop app crashes everytime I initiate the
pairing process from the phone.  Both devices see each other, the same key is
displayed in the pop-up, and I click on the "accept" button in the pop-up, and
then the KDE Connect Deamon crashes with the attached backtrace.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[New LWP 585258]
[New LWP 585259]
[New LWP 585260]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3630611aff in __GI___poll (fds=0x7ffde197e9a8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f362cae4d40 (LWP 585257))]

Thread 4 (Thread 0x7f3628f53700 (LWP 585260)):
#0  0x7f362f153508 in g_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f362f10628e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f362f1064a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3630bdfb3b in QEventDispatcherGlib::processEvents
(this=0x7f362b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3630b83dcb in QEventLoop::exec (this=this@entry=0x7f3628f52ce0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f363099dbb2 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f363099ed4c in QThreadPrivate::start (arg=0x55c5621365c0) at
thread/qthread_unix.cpp:329
#7  0x7f362fb27609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f363061e293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f362a164700 (LWP 585259)):
#0  0x7f3630611aff in __GI___poll (fds=0x7f361c0132a0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f362f10636e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f362f1064a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3630bdfb3b in QEventDispatcherGlib::processEvents
(this=0x7f361c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3630b83dcb in QEventLoop::exec (this=this@entry=0x7f362a163cb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f363099dbb2 in QThread::exec (this=this@entry=0x7f363158cd80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f3631508f4b in QDBusConnectionManager::run (this=0x7f363158cd80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:179
#7  0x7f363099ed4c in QThreadPrivate::start (arg=0x7f363158cd80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:329
#8  0x7f362fb27609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f363061e293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f362bcec700 (LWP 585258)):
#0  0x7f3630611aff in __GI___poll (fds=fds@entry=0x7f362bcebbe8,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f362ec72c1a in poll (__timeout=-1, __nfds=1, __fds=0x7f362bcebbe8)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x55c562024810, cond=cond@entry=0x55c562024850,
vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:480
#3  0x7f362ec7490a in xcb_wait_for_event (c=c@entry=0x55c562024810) at
../../src/xcb_in.c:697
#4  0x7f362c422e88 in QXcbEventQueue::run (this=0x55c562014790) at
qxcbeventqueue.cpp:228
#5  0x7f363099ed4c in QThreadPrivate::start (arg=0x55c562014790) at
thread/qthread_unix.cpp:329
#6  0x7f362fb27609 in start_thread (arg=) at
pthread_create.c:477
#7  0x7f363061e293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f362cae4d40 (LWP 585257)):
[KCrash Handler]
#4

[neon] [Bug 396138] Baloo Crashes on laptop unlock / disconnect from docking station

2021-01-01 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |UNMAINTAINED

--- Comment #4 from Stephan Diestelhorst  ---
Yeah, this was either a packaging bug, or I screwed up something during the
upgrade.  Let's close this one!  Thanks!

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

[systemsettings] [Bug 355354] Swap CapsLock and Escape feature disabled spontaneously

2020-11-19 Thread Stephan Diestelhorst

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

--- Comment #4 from Stephan Diestelhorst  ---
I am not the OP, but I have not noticed this behaviour for quite a while.  So
from my POV, this can be closed, thanks!

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

[kwin] [Bug 424780] Wayland session crash upon login

2020-08-20 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #5 from Stephan Diestelhorst  ---
Does this need any tagging as a packaging bug for KDE Neon User?  Or a way to
expedite the backport?

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-18 Thread Stephan Diestelhorst

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

--- Comment #12 from Stephan Diestelhorst  ---
Cherry-picking packages from KDE Neon Testing makes this work again.  Versions:

$ apt policy libkf5waylandclient5 libkwaylandserver5 plasma-wayland-protocols
kwayland-data 
libkf5waylandclient5:
  Installed: 4:5.73.0+p20.04+git20200817.1942-0
  Candidate: 4:5.73.0+p20.04+git20200817.1942-0
  Version table:
 *** 4:5.73.0+p20.04+git20200817.1942-0 100
100 /var/lib/dpkg/status
 4:5.72.0-0xneon+20.04+focal+build3 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
 4:5.70.0-1 -1
 -1 http://ftp.uk.debian.org/debian sid/main amd64 Packages
 4:5.68.0-0ubuntu1 500
500 http://mirror.sov.uk.goscomb.net/ubuntu focal/universe amd64
Packages
libkwaylandserver5:
  Installed: 5.19.4-0xneon+20.04+focal+build8
  Candidate: 5.19.4-0xneon+20.04+focal+build8
  Version table:
 *** 5.19.4-0xneon+20.04+focal+build8 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
100 /var/lib/dpkg/status
plasma-wayland-protocols:
  Installed: 1.1.1+p18.04+git20200731.1041-0
  Candidate: 1.1.1+p18.04+git20200731.1041-0
  Version table:
 *** 1.1.1+p18.04+git20200731.1041-0 100
100 /var/lib/dpkg/status
 1.1.1-0xneon+20.04+focal+build4 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
kwayland-data:
  Installed: 4:5.73.0+p20.04+git20200817.1942-0
  Candidate: 4:5.73.0+p20.04+git20200817.1942-0
  Version table:
 *** 4:5.73.0+p20.04+git20200817.1942-0 100
100 /var/lib/dpkg/status
 4:5.72.0-0xneon+20.04+focal+build3 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
500 http://archive.neon.kde.org/user focal/main i386 Packages
500 http://archive.neon.kde.org/user focal/main all Packages
 4:5.70.0-1 -1
 -1 http://ftp.uk.debian.org/debian sid/main amd64 Packages
 -1 http://ftp.uk.debian.org/debian sid/main i386 Packages
 4:5.68.0-0ubuntu1 500
500 http://mirror.sov.uk.goscomb.net/ubuntu focal/universe amd64
Packages
500 http://mirror.sov.uk.goscomb.net/ubuntu focal/universe i386
Packages

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-18 Thread Stephan Diestelhorst

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

--- Comment #11 from Stephan Diestelhorst  ---
Upgrading (on User edition) still has the crash.  Package versions as per
below:

$ apt policy libkf5waylandclient5 libkwaylandserver5 plasma-wayland-protocols
libkf5waylandclient5:
  Installed: 4:5.72.0-0xneon+20.04+focal+build3
  Candidate: 4:5.72.0-0xneon+20.04+focal+build3
  Version table:
 *** 4:5.72.0-0xneon+20.04+focal+build3 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
100 /var/lib/dpkg/status
 4:5.70.0-1 -1
 -1 http://ftp.uk.debian.org/debian sid/main amd64 Packages
 4:5.68.0-0ubuntu1 500
500 http://mirror.sov.uk.goscomb.net/ubuntu focal/universe amd64
Packages
libkwaylandserver5:
  Installed: 5.19.4-0xneon+20.04+focal+build8
  Candidate: 5.19.4-0xneon+20.04+focal+build8
  Version table:
 *** 5.19.4-0xneon+20.04+focal+build8 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
100 /var/lib/dpkg/status
plasma-wayland-protocols:
  Installed: 1.1.1-0xneon+20.04+focal+build4
  Candidate: 1.1.1-0xneon+20.04+focal+build4
  Version table:
 *** 1.1.1-0xneon+20.04+focal+build4 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages
100 /var/lib/dpkg/status

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-18 Thread Stephan Diestelhorst

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

--- Comment #10 from Stephan Diestelhorst  ---
Just installing plasma-wayland-protocols 1.1.1-0xneon+20.04+focal+build4 by
itself does not make the crash go away.  Just FYI, the other (hopefully)
relevant packages where this occurs are:

$ apt policy libkf5waylandclient5
libkf5waylandclient5:
  Installed: 4:5.72.0-0xneon+20.04+focal+build3
  Candidate: 4:5.72.0-0xneon+20.04+focal+build3
  Version table:
 *** 4:5.72.0-0xneon+20.04+focal+build3 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages

$ apt policy libkwaylandserver5
libkwaylandserver5:
  Installed: 5.19.4-0xneon+20.04+focal+build8
  Candidate: 5.19.4-0xneon+20.04+focal+build8
  Version table:
 *** 5.19.4-0xneon+20.04+focal+build8 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages

I'll go and upgrade and see if Neon packaging already picked up the right
versions.

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-18 Thread Stephan Diestelhorst

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

--- Comment #9 from Stephan Diestelhorst  ---
Version of plasma-wayland-protocols => it seems I have no version of this
installed... will install and see if it goes away.

$ apt policy plasma-wayland-protocols
plasma-wayland-protocols:
  Installed: (none)
  Candidate: 1.1.1-0xneon+20.04+focal+build4
  Version table:
 1.1.1-0xneon+20.04+focal+build4 500
500 http://archive.neon.kde.org/user focal/main amd64 Packages

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-04 Thread Stephan Diestelhorst

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

--- Comment #5 from Stephan Diestelhorst  ---
(gdb) print *resource
$20 = {object = {interface = 0x7fc68d91ec00
, implementation = 0x7fc68d83d1e0
, id =
32},
  destroy = 0x7fc68d7b77c0
,
link = {prev = 0x101, next = 0x0}, deprecated_destroy_signal =
{listener_list = {prev = 0x564c4bf4b5d0, next = 0x564c4bf4b5d0}},
  client = 0x564c4bf69cf0, data = 0x564c4b164b50, version = 11, dispatcher =
0x0, destroy_signal = {listener_list = {prev = 0x564c4bf4b600, next =
0x564c4bf4b600}, emit_list = {prev = 0x564c4bf4b610, next = 0x564c4bf4b610}}}

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-04 Thread Stephan Diestelhorst

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

--- Comment #4 from Stephan Diestelhorst  ---
Seems like someone is calling get_next_argument with signature= 0 here:
https://gitlab.freedesktop.org/wayland/wayland/blob/master/src/connection.c#L442

And it is either jumping in with a NULL string signature into
wl_argument_from_va_list here:
https://gitlab.freedesktop.org/wayland/wayland/blob/master/src/connection.c#L499
or a not properly terminated signature.

Seems like opcode 3 that is used ehre (
https://gitlab.freedesktop.org/wayland/wayland/-/blob/master/src/wayland-server.c#L242
) is not properly initialised:

(gdb) up
#2  0x7fc68a741fc5 in wl_resource_post_event (resource=0x564c4bf4b5a0,
opcode=3) at ../src/wayland-server.c:249
249 ../src/wayland-server.c: No such file or directory.

(gdb) print object->interface->events[3]
$10 = {name = 0x0, signature = 0x0, types = 0x0}


The other opcodes look sensible:
(gdb) print object->interface->events[0]
$11 = {name = 0x7fc68d8fb83a "show_desktop_changed", signature = 0x7fc68d8fb519
"u", types = 0x7fc68d928a20}
(gdb) print object->interface->events[1]
$12 = {name = 0x7fc68d8fb6a2 "window", signature = 0x7fc68d8fb519 "u", types =
0x7fc68d928a20}
(gdb) print object->interface->events[2]
$13 = {name = 0x7fc68d8fb84f "stacking_order_changed", signature =
0x7fc68d8fb866 "11a", types = 0x7fc68d928a20}
(gdb) print object->interface->events[3]
$14 = {name = 0x0, signature = 0x0, types = 0x0}
(gdb) print object->interface->events[4]
$15 = {name = 0x7fc68d8fb86a "show_desktop", signature = 0x7fc68d8fb519 "u",
types = 0x7fc68d928a20}
(gdb) print object->interface->events[5]
$16 = {name = 0x7fc68d8fb877 "get_window", signature = 0x7fc68d8fb78d "nu",
types = 0x7fc68d928a40}

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-04 Thread Stephan Diestelhorst

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

--- Comment #3 from Stephan Diestelhorst  ---
(gdb) disas
Dump of assembler code for function get_next_argument:
   0x7fc68a7463c0 <+0>: endbr64
   0x7fc68a7463c4 <+4>: movl   $0x0,0x4(%rsi)
=> 0x7fc68a7463cb <+11>:movzbl (%rdi),%edx
   0x7fc68a7463ce <+14>:test   %dl,%dl
   0x7fc68a7463d0 <+16>:je 0x7fc68a746403 
   0x7fc68a7463d2 <+18>:lea0x3def(%rip),%rcx#
0x7fc68a74a1c8
   0x7fc68a7463d9 <+25>:lea-0x3f(%rdx),%eax
   0x7fc68a7463dc <+28>:cmp$0x36,%al
   0x7fc68a7463de <+30>:ja 0x7fc68a7463f7 
   0x7fc68a7463e0 <+32>:movzbl %al,%eax
   0x7fc68a7463e3 <+35>:movslq (%rcx,%rax,4),%rax
   0x7fc68a7463e7 <+39>:add%rcx,%rax
   0x7fc68a7463ea <+42>:notrack jmpq *%rax
   0x7fc68a7463ed <+45>:nopl   (%rax)
   0x7fc68a7463f0 <+48>:movl   $0x1,0x4(%rsi)
   0x7fc68a7463f7 <+55>:movzbl 0x1(%rdi),%edx
   0x7fc68a7463fb <+59>:add$0x1,%rdi
   0x7fc68a7463ff <+63>:test   %dl,%dl
   0x7fc68a746401 <+65>:jne0x7fc68a7463d9 
   0x7fc68a746403 <+67>:movb   $0x0,(%rsi)
   0x7fc68a746406 <+70>:mov%rdi,%rax
   0x7fc68a746409 <+73>:retq
   0x7fc68a74640a <+74>:nopw   0x0(%rax,%rax,1)
   0x7fc68a746410 <+80>:mov%dl,(%rsi)
   0x7fc68a746412 <+82>:lea0x1(%rdi),%rax
   0x7fc68a746416 <+86>:retq

(gdb) info reg
rax0x1319
rbx0x564c4b164b50  94885677255504
rcx0x7d91f508  140737447589128
rdx0x1420
rsi0x7d91f4e0  140737447589088
rdi0x0 0
rbp0x564c4bf4b5a0  0x564c4bf4b5a0
rsp0x7d91f4d8  0x7d91f4d8
r8 0x7fc68a74a3a0  140490703152032
r9 0x7d91f520  140737447589152
r100x7d91f5c0  140737447589312
r110x7d91f508  140737447589128
r120x3 3
r130x7d91f520  140737447589152
r140x564c4b1a9490  94885677536400
r150x7d91f7fc  140737447589884
rip0x7fc68a7463cb  0x7fc68a7463cb 
eflags 0x10206 [ PF IF RF ]
cs 0x3351
ss 0x2b43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-04 Thread Stephan Diestelhorst

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

--- Comment #2 from Stephan Diestelhorst  ---
Backtrace:
(gdb) bt
#0  get_next_argument (signature=0x0, details=0x7d91f4e0) at
../src/connection.c:445
#1  0x7fc68a746b4d in wl_argument_from_va_list (signature=,
args=args@entry=0x7d91f520, count=count@entry=20,
ap=ap@entry=0x7d91f508) at ../src/connection.c:508
#2  0x7fc68a741fc5 in wl_resource_post_event (resource=0x564c4bf4b5a0,
opcode=3) at ../src/wayland-server.c:249
#3  0x7fc68d7b74a1 in
KWaylandServer::PlasmaWindowManagementInterface::Private::sendStackingOrderChanged(wl_resource*)
() at /usr/lib/x86_64-linux-gnu/libKWaylandServer.so.5
#4  0x7fc68d7b7567 in
KWaylandServer::PlasmaWindowManagementInterface::Private::sendStackingOrderChanged()
() at /usr/lib/x86_64-linux-gnu/libKWaylandServer.so.5
#5  0x7fc68d7b76a8 in
KWaylandServer::PlasmaWindowManagementInterface::Private::bind(wl_client*,
unsigned int, unsigned int) () at
/usr/lib/x86_64-linux-gnu/libKWaylandServer.so.5
#6  0x7fc689112ff5 in  () at /usr/lib/x86_64-linux-gnu/libffi.so.7
#7  0x7fc68911240a in  () at /usr/lib/x86_64-linux-gnu/libffi.so.7
#8  0x7fc68a747628 in wl_closure_invoke
(closure=closure@entry=0x564c4c02f020, flags=flags@entry=2, target=, target@entry=0x564c4bf67070, opcode=opcode@entry=0, data=,
data@entry=0x564c4bf69cf0) at ../src/connection.c:1018
#9  0x7fc68a7439e2 in wl_client_connection_data (fd=,
mask=, data=0x564c4bf69cf0) at ../src/wayland-server.c:432
#10 0x7fc68a74565a in wl_event_loop_dispatch (loop=0x564c4b160ed0,
timeout=) at ../src/event-loop.c:1027
#11 0x7fc68d79e6e3 in KWaylandServer::Display::Private::dispatch() () at
/usr/lib/x86_64-linux-gnu/libKWaylandServer.so.5
#12 0x7fc68cbfc51e in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7d91fe30, r=0x564c4b16be80, this=0x564c4b1610a0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x564c4b161080,
signal_index=3, argv=0x7d91fe30) at kernel/qobject.cpp:3870
#14 0x7fc68cbf6af7 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=sender@entry=0x564c4b161080, m=m@entry=0x7fc68cea2ba0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7d91fe30)
at kernel/qobject.cpp:3930
#15 0x7fc68cbffd95 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x564c4b161080,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#16 0x7fc68cc000f1 in QSocketNotifier::event(QEvent*) (this=0x564c4b161080,
e=0x7d9200f0) at kernel/qsocketnotifier.cpp:266
#17 0x7fc68d016cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x564c4b13f1d0, receiver=receiver@entry=0x564c4b161080,
e=e@entry=0x7d9200f0) at kernel/qapplication.cpp:3685
#18 0x7fc68d01ff40 in QApplication::notify(QObject*, QEvent*)
(this=0x7d9204d0, receiver=0x564c4b161080, e=0x7d9200f0) at
kernel/qapplication.cpp:3431
#19 0x7fc68cbc678a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x564c4b161080, event=0x7d9200f0) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#20 0x7fc68cc1c40b in
QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x564c4b145870) at
kernel/qeventdispatcher_unix.cpp:304
#21 0x7fc68cc1c86b in
QEventDispatcherUNIX::processEvents(QFlags)
(this=, flags=...) at kernel/qeventdispatcher_unix.cpp:509
#22 0x7fc6865f37c1 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/KWinQpaPlugin.so
#23 0x7fc68cbc524b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7d920280, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#24 0x7fc68cbcd296 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#25 0x564c4a9797ec in  ()
#26 0x7fc68c5490b3 in __libc_start_main (main=0x564c4a977970, argc=2,
argv=0x7d920738, init=, fini=,
rtld_fini=, stack_end=0x7d920728) at ../csu/libc-start.c:308

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-03 Thread Stephan Diestelhorst

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

--- Comment #1 from Stephan Diestelhorst  ---
Got the same thing on KDE Neon Stable upgraded to 20.04. Was trying to get a
backtrace, but I could not VT switch when running kwin_wayland in GDB.  With
some more experimentation, I found that this dies only when starting
plasmashell or plasma_wayland.  Running without that seems to work somewhat
(krunner, konsole, hotkey daemon).

Will try to get a meaningful backtrace!

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

[kwin] [Bug 424834] Segfault in libwayland-server.so after upgrading to 5.19.4

2020-08-03 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[Akonadi] [Bug 408897] ItemRetrievalManager crash

2020-06-14 Thread Stephan Diestelhorst

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

--- Comment #21 from Stephan Diestelhorst  ---
Thanks Daniel, for marking as duplicate and resolving the bug.  I got confused
with the version numbering scheme between KDE PIM (5.14.x) and Plasma (5.19)
and had hoped this would be fixed in Neon already.  Will build from git
instead.

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

[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail

2020-06-11 Thread Stephan Diestelhorst

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

--- Comment #8 from Stephan Diestelhorst  ---
I'm doing some debugging on this myself, and it seems that in 
ItemRetrievalManager::retrievalJobFinished the request->resourceId is getting
deallocated (looking at the faults either in reference counting, or CRC
computation) while this function is still active.

Don't quite understand the logging regime here and who owns what data, but I
hope that with a bit of logging and inspection, I can find out what is
happening here.

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

[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail

2020-06-10 Thread Stephan Diestelhorst

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

--- Comment #7 from Stephan Diestelhorst  ---
Created attachment 129188
  --> https://bugs.kde.org/attachment.cgi?id=129188=edit
New crash information added by DrKonqi

akonadiserver (5.14.1 (20.04.0)) using Qt 5.14.2

- What I was doing when the application crashed:

Same thing, syncing my mailbox with GMail.  System freshly updated to 5.19, and
crash still happens.

-- Backtrace (Reduced):
#4  0x7fa092076d1c in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x3030305c3030305c) at
/usr/include/c++/7/bits/atomic_base.h:396
#5  QAtomicOps::loadRelaxed (_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=0x3030305c3030305c) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
[...]
#8  QString::operator= (this=this@entry=0x7fa01c159e58, other=...) at
text/qstring.cpp:2398
#9  0x55b66cde in
Akonadi::Server::ItemRetrievalManager::retrievalJobFinished
(this=0x55b66d219810, request=0x7fa01c159e40, errorMsg=...) at
./src/server/storage/itemretrievalmanager.cpp:176

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

[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

--- Comment #6 from Stephan Diestelhorst  ---
Bug 419229 and bug 420495 definitely look related.

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

[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

--- Comment #5 from Stephan Diestelhorst  ---
Bugs #419229 and #420495 definitely look very similar.

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

[Akonadi] [Bug 422092] Akonadi Server crashing while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

--- Comment #4 from Stephan Diestelhorst  ---
On some more cursory looking, the second crash is slightly different than the
first, but they both seem to originate from
Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (lines 176 and
182).

First:
Thread 5 (Thread 0x7f2c0954b700 (LWP 6087)):
[KCrash Handler]
#4  0x7f2c1d545d1c in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/7/bits/atomic_base.h:396
#5  QAtomicOps::loadRelaxed (_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=0x0) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::deref (this=0x0) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:66
#8  QString::operator= (this=this@entry=0x7f2bc40e0418, other=...) at
text/qstring.cpp:2398
#9  0x55c813140555 in
Akonadi::Server::ItemRetrievalManager::retrievalJobFinished
(this=0x55c813aa7000, request=0x7f2bc40e0400, errorMsg=...) at
./src/server/storage/-|itemretrievalmanager.cpp:176
#10 0x7f2c1d6e96d7 in QtPrivate::QSlotObjectBase::call (a=0x7f2c0954a810,
r=0x55c813aa7000, this=) at
../../include/QtCore/../../src/corelib/kernel/   -|qobjectdefs_impl.h:398
#11 doActivate (sender=0x7f2ca340, signal_index=3,
argv=0x7f2c0954a810) at kernel/qobject.cpp:3870
#12 0x7f2c1d6e3f92 in QMetaObject::activate
(sender=sender@entry=0x7f2ca340, m=m@entry=0x55c81342f800
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7f2c0954a810) at kernel/qobject.cpp:3930
#13 0x55c813190274 in
Akonadi::Server::AbstractItemRetrievalJob::requestCompleted
(this=this@entry=0x7f2ca340, _t1=, _t2=...) at ./obj-x86_64-
   
-|linux-gnu/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136
#14 0x55c813143ace in Akonadi::Server::ItemRetrievalJob::callFinished
(this=0x7f2ca340, watcher=) at
./src/server/storage/itemretrievaljob.cpp:76
#15 0x7f2c1d6e96d7 in QtPrivate::QSlotObjectBase::call (a=0x7f2c0954a9e0,
r=0x7f2ca340, this=) at
../../include/QtCore/../../src/corelib/kernel/   -|qobjectdefs_impl.h:398
#16 doActivate (sender=0x7f2bdc0adb70, signal_index=3,
argv=0x7f2c0954a9e0) at kernel/qobject.cpp:3870
#17 0x7f2c1d6e3f92 in QMetaObject::activate (sender=,
m=m@entry=0x7f2c1e04e5e0 ,  
 -|local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7f2c0954a9e0) at kernel/qobject.cpp:3930
#18 0x7f2c1de30ecf in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#19 0x7f2c1d6e157b in QObject::event (this=0x7f2bdc0adb70,
e=0x7f2c10002580) at kernel/qobject.cpp:1339
#20 0x7f2c1d6ae491 in doNotify (event=0x7f2c10002580,
receiver=0x7f2bdc0adb70) at kernel/qcoreapplication.cpp:1165
#21 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1151
#22 QCoreApplication::notifyInternal2 (receiver=0x7f2bdc0adb70,
event=0x7f2c10002580) at kernel/qcoreapplication.cpp:1075
#23 0x7f2c1d6ae67e in QCoreApplication::sendEvent
(receiver=receiver@entry=0x7f2bdc0adb70, event=event@entry=0x7f2c10002580) at
kernel/qcoreapplication.cpp:1470
#24 0x7f2c1d6b1121 in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x55c813aff900) at kernel/  -|qcoreapplication.cpp:1815
#25 0x7f2c1d6b16b8 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1674
#26 0x7f2c1d70e103 in postEventSourceDispatch (s=0x7f2c4b90) at
kernel/qeventdispatcher_glib.cpp:277
#27 0x7f2c19982417 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f2c19982650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7f2c199826dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7f2c1d70d7ac in QEventDispatcherGlib::processEvents
(this=0x7f2c0b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#31 0x7f2c1d6acd2a in QEventLoop::exec (this=this@entry=0x7f2c0954ada0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#32 0x7f2c1d4bd757 in QThread::exec (this=) at
thread/qthread.cpp:536
#33 0x7f2c1d4bec2c in QThreadPrivate::start (arg=0x55c813a86be0) at
thread/qthread_unix.cpp:342
#34 0x7f2c1b5c56db in start_thread (arg=0x7f2c0954b700) at
pthread_create.c:463
#35 0x7f2c1cb5088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Second:
Thread 5 (Thread 0x7fc7b234c700 (LWP 19533)):
[KCrash Handler]
#4  QListData::size (this=0x7fc77c148d80) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:115
#5  QList::operator== (l=..., this=0x7fc77c148d80) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:874
#6  Akonadi::Server::ItemRetrievalManager::retrievalJobFinished
(this=0x5598b86df040, request=0x7fc77c090be0, errorMsg

[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

Summary|Akonadi Server crashing |Akonadi Server crashing in
   |while syncing GMail |ItemRetrievalManager while
   ||syncing GMail

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

[Akonadi] [Bug 422092] Akonadi Server crashing while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

--- Comment #3 from Stephan Diestelhorst  ---
Created attachment 128798
  --> https://bugs.kde.org/attachment.cgi?id=128798=edit
DrKonqi report #2

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

[Akonadi] [Bug 422092] Akonadi Server crashing while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

--- Comment #2 from Stephan Diestelhorst  ---
Created attachment 128797
  --> https://bugs.kde.org/attachment.cgi?id=128797=edit
DrKonqi report including backtrace

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

[Akonadi] [Bug 422092] Akonadi Server crashing while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

--- Comment #1 from Stephan Diestelhorst  ---
Just happened again multiple times and seems to be reproducible.  Will attach
two full backtraces, somehow DrKonqi can't add them here.

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

[Akonadi] [Bug 422092] Akonadi Server crashing while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[Akonadi] [Bug 422092] New: Akonadi Server crashing while syncing GMail

2020-05-26 Thread Stephan Diestelhorst

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

Bug ID: 422092
   Summary: Akonadi Server crashing while syncing GMail
   Product: Akonadi
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: stephan.diestelho...@gmail.com
  Target Milestone: ---

Application: akonadiserver (5.14.1 (20.04.0))

Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.5.13-050513-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18

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

Just updated Akonadi and was  very happy to see that GMail is back.  This
crashes doing some reference counting on the NULL object in Thread 5 but should
be a pretty recent Akonadi build.

-- Backtrace (Reduced):
#4  0x7f2c1d545d1c in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/7/bits/atomic_base.h:396
#5  QAtomicOps::loadRelaxed (_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=0x0) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
[...]
#8  QString::operator= (this=this@entry=0x7f2bc40e0418, other=...) at
text/qstring.cpp:2398
#9  0x55c813140555 in
Akonadi::Server::ItemRetrievalManager::retrievalJobFinished
(this=0x55c813aa7000, request=0x7f2bc40e0400, errorMsg=...) at
./src/server/storage/itemretrievalmanager.cpp:176


Possible duplicates by query: bug 421812, bug 421668, bug 421501, bug 420495,
bug 420184.

Reported using DrKonqi

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2020-03-11 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[frameworks-baloo] [Bug 397644] baloo_file crashes in Baloo::DocumentTimeDB::get()

2018-12-09 Thread Stephan Diestelhorst

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

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[taglib] [Bug 316093] Amarok crashes when repopulating dynamic random playlist

2018-11-13 Thread Stephan Diestelhorst

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

--- Comment #4 from Stephan Diestelhorst  ---
Sorry, missed the updates here.  Will get back and test tonight and see what
happens.

Thanks!

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

[systemsettings] [Bug 386190] Excessive redraws in system settings

2018-07-20 Thread Stephan Diestelhorst

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

--- Comment #2 from Stephan Diestelhorst  ---
Problem is that there was nothing changing, and the app consuming a huge amount
of CPU power for effectively a static window.

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

[kde] [Bug 396138] New: Baloo Crashes on laptop unlock / disconnect from docking station

2018-07-03 Thread Stephan Diestelhorst

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

Bug ID: 396138
   Summary: Baloo Crashes on laptop unlock / disconnect from
docking station
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: stephan.diestelho...@gmail.com
  Target Milestone: ---

Application: akonadi_baloo_indexer (4.14)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.13.10-041310-generic x86_64
Distribution: KDE neon User Edition 5.13

-- Information about the crash:
It seems that Balloo just crashed on me after trying to unlock my screen and
failing; so I ended up removing my laptop from the docking station.  Also seems
that the machine has been running quite hot, so it may have been doing sth CPU
heavy before.

I know this is a rubbish report, but maybe the backtrace is helpful!

KDE neon dev/stable

The crash can be reproduced sometimes.

-- Backtrace:
Application:  (akonadi_baloo_indexer), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7fd31ec80428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fd31ec8202a in __GI_abort () at abort.c:89
#8  0x7fd322857f15 in qt_message_output(QtMsgType, char const*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7fd32139cd47 in  () at /usr/lib/libakonadi-kde.so.4
#10 0x7fd32139c20a in  () at /usr/lib/libakonadi-kde.so.4
#11 0x7fd32298cd21 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x7fd31fed8fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7fd31fedff16 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x7fd320c3f6ba in KApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkdeui.so.5
#15 0x7fd3229728bd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x7fd322976376 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x7fd3229a30ae in  () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7fd31e349197 in g_main_context_dispatch (context=0x21f78b0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3154
#19 0x7fd31e349197 in g_main_context_dispatch
(context=context@entry=0x21f78b0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3769
#20 0x7fd31e3493f0 in g_main_context_iterate
(context=context@entry=0x21f78b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3840
#21 0x7fd31e34949c in g_main_context_iteration (context=0x21f78b0,
may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#22 0x7fd3229a321e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x7fd31ff86616 in  () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#24 0x7fd32297113f in
QEventLoop::processEvents(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x7fd3229714a5 in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7fd322977469 in QCoreApplication::exec() () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x7fd3213994bd in Akonadi::AgentBase::init(Akonadi::AgentBase*) () at
/usr/lib/libakonadi-kde.so.4
#28 0x004e in  ()
#29 0x7fd31ec6b830 in __libc_start_main (main=0x40a090, argc=3,
argv=0x7fff78c6d698, init=, fini=,
rtld_fini=, stack_end=0x7fff78c6d688) at ../csu/libc-start.c:291
#30 0x0040a129 in _start ()

Reported using DrKonqi

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

[systemsettings] [Bug 386190] New: Excessive redraws in system settings

2017-10-25 Thread Stephan Diestelhorst

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

Bug ID: 386190
   Summary: Excessive redraws in system settings
   Product: systemsettings
   Version: 5.11.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: treeview
  Assignee: sourtooth+ssb...@gmail.com
  Reporter: stephan.diestelho...@gmail.com
  Target Milestone: ---

Enabling the "Show Paint" effect shows a high number of unneccessary repaints
of the left pane of the system settings dialog.  I found that while having a
look at bug #381000.

Please have a look here:

https://www.youtube.com/watch?v=TAC14Izfbas
https://www.youtube.com/watch?v=-m6D3vi7za4

KDE Frameworks 5.39.0
Qt 5.9.1 (built against 5.9.1)

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-10-15 Thread Stephan Diestelhorst

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

2017-05-07 Thread Stephan Diestelhorst

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

--- Comment #5 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Okay, here is what I did:
* started with a fresh user account
* started KMail
* manually enter bogus account credentials for bogus server into wizard
* wizard complains (might not have a proper connection, please configure
manually)
* attaching GDB (to the single imap agent)
* clicking configure
* crash -> backtrace
* closing KMail
* akonadictl restart
* and I get an _empty_ account (no server configured in akonadiconsole) and
pretty much config file in ~/.config/../agent*imap*

Backtrace:
#0  MailTransport::ServerTest::secureProtocols (this=0x0) at
/workspace/build/src/kmailtransport/servertest.cpp:608
#1  0x004274b7 in SetupServer::slotSafetyChanged (this=0x9d3560) at
/workspace/build/resources/imap/setupserver.cpp:619
#2  0x7fd99a0341f6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd99ab3caa2 in QAbstractButton::toggled(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x7fd99ab3ce95 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7fd99ab3eecc in QAbstractButton::setChecked(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x7fd99ab3eeb1 in QAbstractButton::setChecked(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x0042618e in SetupServer::readSettings (this=this@entry=0x9d3560)
at /workspace/build/resources/imap/setupserver.cpp:394
#8  0x004294e1 in SetupServer::SetupServer (this=0x9d3560,
parentResource=, parent=)
at /workspace/build/resources/imap/setupserver.cpp:190
#9  0x004207fd in ImapResource::createConfigureDialog (this=0x985970,
windowId=65011774)
at /workspace/build/resources/imap/imapresource.cpp:75
#10 0x00434dcd in ImapResourceBase::configure (this=0x985970,
windowId=)
at /workspace/build/resources/imap/imapresourcebase.cpp:223
#11 0x7fd99ca76195 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#12 0x7fd99e750923 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7fd99e75472a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#14 0x7fd99e75503b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#15 0x7fd99e7577fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7fd99a034d99 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fd99aa55ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fd99aa5d8c6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fd99a0090c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fd99a00b78b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fd99a05c333 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fd9942d8197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fd9942d83f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fd9942d849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fd99a05c73f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fd99a0070ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7fd99a00f6cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fd99ca5dfde in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
()
   from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#29 0x00420535 in Akonadi::ResourceBase::init (argc=3,
argv=)
at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:196
#30 0x7fd99944c830 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#31 0x004203d9 in _start ()

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

2017-05-07 Thread Stephan Diestelhorst

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

--- Comment #4 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
This is a little more complex than necessary.

The back traces ending in ServerTest::normalProtocols() are for my Office 365
work email account, but I have a separate GMail account in Akonadi.  The
crashing imap agents are the O365 (non-GMail) ones, though.

The back trace ending in MailTransport::ServerTest::secureProtocols is one of
an empty IMAP resource that I created after a half configured GMail account
(which I deleted).  That empty IMAP resource I simply added in KMail and it
would crash whenever I tried to configure it.

In both cases, the back traces are from an non-GMail resource, but there was a
parallel (lingering) GMail account in both.

I will retry with a truly empty non-GMail account and not go through the
wizard.

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

2017-05-05 Thread Stephan Diestelhorst

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=379155

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

2017-05-05 Thread Stephan Diestelhorst

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

--- Comment #2 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
After installing sasl2-bin and checking that the symlinks are correct, I still
get the same / similar error (now with my old profile):

(gdb) bt
#0  MailTransport::ServerTest::normalProtocols (this=0x0) at
/workspace/build/src/kmailtransport/servertest.cpp:593
#1  0x00427434 in SetupServer::slotSafetyChanged (this=0x1520ff0)   
at /workspace/build/resources/imap/setupserver.cpp:616  
#2  0x7f33317611f6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5  
#3  0x7f33322bee32 in QLineEdit::textChanged(QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5  
#4  0x7f33322c5449 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7f3331760e89 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5  
#6  0x7f333234d435 in QWidgetLineControl::textChanged(QString const&) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 
#7  0x7f3332350876 in QWidgetLineControl::finishChange(int, bool, bool) ()  
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f3332350b27 in QWidgetLineControl::internalSetText(QString const&,
int, bool) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f33322c0be2 in QLineEdit::setText(QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5  
#10 0x00426071 in SetupServer::readSettings (this=this@entry=0x1520ff0) 
at /workspace/build/resources/imap/setupserver.cpp:374  
#11 0x004294e1 in SetupServer::SetupServer (this=0x1520ff0,
parentResource=, parent=)
at /workspace/build/resources/imap/setupserver.cpp:190  
#12 0x004207fd in ImapResource::createConfigureDialog (this=0x1413110,
windowId=71303178)  
at /workspace/build/resources/imap/imapresource.cpp:75  
#13 0x00434dcd in ImapResourceBase::configure (this=0x1413110,
windowId=)   
at /workspace/build/resources/imap/imapresourcebase.cpp:223 
#14 0x7f33341a3195 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5   
#15 0x7f3335e7d923 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5  
#16 0x7f3335e8172a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5  
#17 0x7f3335e8203b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5  
#18 0x7f3335e847fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5  
#19 0x7f3331761d99 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f3332182ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() 
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f333218a8c6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 
#22 0x7f33317360c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f333173878b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f3331789333 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f332ba05197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f332ba053f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f332ba0549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f333178973f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f33317340ba in
QEventLoop::exec(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f333173c6cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f333418afde in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
()
   from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#32 0x00420535 in Akonadi::ResourceBase::init (argc=3,
argv=)
at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:196
#33 0x7f3330b79830 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#34 0x004203d9 in _start ()

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

2017-05-05 Thread Stephan Diestelhorst

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

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Tried with a clean user profile, and it still crashes, see below.  Also pulled
out newer package information and installed bebug symbols.  Will also have a
look if it is related to bug #379089

libkf5mailtransportakonadi5:
  Installed: 17.04.0+p16.04+git20170502.0236-0  
  Candidate: 17.04.0+p16.04+git20170502.0236-0
  Version table:
 *** 17.04.0+p16.04+git20170502.0236-0 500
500 http://archive.neon.kde.org/dev/stable xenial/main amd64 Packages

Backtrace
(gdb) bt
#0  MailTransport::ServerTest::secureProtocols (this=0x0) at
/workspace/build/src/kmailtransport/servertest.cpp:608
#1  0x004274b7 in SetupServer::slotSafetyChanged (this=0x27fa080) at
/workspace/build/resources/imap/setupserver.cpp:619
#2  0x7fa759d9a1f6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa75a8a2aa2 in QAbstractButton::toggled(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x7fa75a8a2e95 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7fa75a8a4ecc in QAbstractButton::setChecked(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x7fa75a8a4eb1 in QAbstractButton::setChecked(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x0042618e in SetupServer::readSettings (this=this@entry=0x27fa080)
at /workspace/build/resources/imap/setupserver.cpp:394
#8  0x004294e1 in SetupServer::SetupServer (this=0x27fa080,
parentResource=, parent=)
at /workspace/build/resources/imap/setupserver.cpp:190
#9  0x004207fd in ImapResource::createConfigureDialog (this=0x2743410,
windowId=100663358)
at /workspace/build/resources/imap/imapresource.cpp:75
#10 0x00434dcd in ImapResourceBase::configure (this=0x2743410,
windowId=)
at /workspace/build/resources/imap/imapresourcebase.cpp:223
#11 0x7fa75c7dc195 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#12 0x7fa75e4b6923 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7fa75e4ba72a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#14 0x7fa75e4bb03b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#15 0x7fa75e4bd7fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7fa759d9ad99 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fa75a7bbecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fa75a7c38c6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fa759d6f0c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
#20 0x7fa759d7178b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()   
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
#21 0x7fa759dc2333 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5  
#22 0x7fa75403e197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0  
#23 0x7fa75403e3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 
#24 0x7fa75403e49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0  
#25 0x7fa759dc273f in
QEventDispatcherGlib::processEvents(QFlags) ()   
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
#26 0x7fa759d6d0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
#27 0x7fa759d756cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
#28 0x7fa75c7c3fde in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
()  
   from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5   
#29 0x00420535 in Akonadi::ResourceBase::init (argc=3,
argv=)   
at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:196 
#30 0x7fa7591b2830 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6 
#31 0x004203d9 in _start () 
(gdb)

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

[Akonadi] [Bug 379548] New: IMAP resource crashes on configure operation

2017-05-05 Thread Stephan Diestelhorst

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

Bug ID: 379548
   Summary: IMAP resource crashes on configure operation
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: stephan.diestelho...@gmail.com
CC: kdepim-b...@kde.org, vkra...@kde.org
  Target Milestone: ---

I am on KDE Neon with recent packages (below), and whenever I want to configure
an existing IMAP account, the according akonadi IMAP instance dies with back
trace attached.  I have tried to start with a clean Akonadi setup, but somehow
my account data lives on.  Will try with a fresh user profile in a minute.

Backtrace:
Thread 1 "akonadi_imap_re" received signal SIGSEGV, Segmentation fault.
0x7f30e4affa41 in MailTransport::ServerTest::normalProtocols() const ()
from /usr/lib/x86_64-linux-gnu/libKF5MailTransport.so.5
(gdb) bt
#0  0x7f30e4affa41 in MailTransport::ServerTest::normalProtocols() const ()
from /usr/lib/x86_64-linux-gnu/libKF5MailTransport.so.5
#1  0x00427434 in ?? ()
#2  0x7f30e108a1f6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f30e1be7e32 in QLineEdit::textChanged(QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x7f30e1bee449 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7f30e1089e89 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f30e1c76435 in QWidgetLineControl::textChanged(QString const&) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f30e1c79876 in QWidgetLineControl::finishChange(int, bool, bool) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f30e1c79b27 in QWidgetLineControl::internalSetText(QString const&,
int, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f30e1be9be2 in QLineEdit::setText(QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00426071 in ?? ()
#11 0x004294e1 in ?? ()
#12 0x004207fd in ?? ()
#13 0x00434dcd in ?? ()
#14 0x7f30e3acc195 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#15 0x7f30e57a6923 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7f30e57aa72a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#17 0x7f30e57ab03b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#18 0x7f30e57ad7fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#19 0x7f30e108ad99 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f30e1aabecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f30e1ab38c6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f30e105f0c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f30e106178b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f30e10b2333 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f30db32e197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f30db32e3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f30db32e49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f30e10b273f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f30e105d0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f30e10656cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f30e3ab3fde in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
() from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#32 0x00420535 in ?? ()
#33 0x7f30e04a2830 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#34 0x004203d9 in _start ()

$ apt-cache policy 'akonadi*'
akonadi-server:
  Installed: 4:17.04.0+p16.04+git20170429.0513-0
  Candidate: 4:17.04.0+p16.04+git20170429.0513-0
  Version table:
 *** 4:17.04.0+p16.04+git20170429.0513-0 500
500 http://archive.neon.kde.org/dev/stable xenial/main amd64 Packages
100 /var/lib/dpkg/status
 4:15.12.3-0ubuntu6 500
500 http://uk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

[Akonadi] [Bug 373519] baloo indexer crashed at restart akonadi

2017-02-19 Thread Stephan Diestelhorst

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

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Created attachment 104119
  --> https://bugs.kde.org/attachment.cgi?id=104119=edit
New crash information added by DrKonqi

akonadi_baloo_indexer (4.14) on KDE Platform 4.14.22 using Qt 4.8.7

KDE neon here, seems like it crashes with the same issue other people have. 
Somehow cannot access the log.

-- Backtrace (Reduced):
#6  0x7fd27b53c428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fd27b53e02a in __GI_abort () at abort.c:89
[...]
#11 0x7fd27f247d21 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x7fd27c793fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7fd27c79af16 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4

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

[Akonadi] [Bug 373519] baloo indexer crashed at restart akonadi

2017-02-19 Thread Stephan Diestelhorst

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[kmail2] [Bug 368060] Replying to html email that has a PDF attachment creates junk in the reply

2016-09-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #3 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Erm... no?  This is still a bug and you closing your account does not make the
bug disappear.  I'll just rereport the same thing. :-S

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

[kmail2] [Bug 368060] Replying to html email that has a PDF attachment creates junk in the reply

2016-09-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #4 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
What I am saying is: please reopen; thanks!

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

[kmail2] [Bug 367997] regression: clicking on HTML Side Bar can no longer toggle html/plain text

2016-09-20 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #2 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Is that related to the hotkey for "Toggle HTML Display Mode" stopped working?

Version 5.3.0 (QtWebEngine)
Using:
KDE Frameworks 5.27.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

via KDE/neon 4:16.08.1+p16.04+git20160918.0030-0

May also be related to bug 363027

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

[kmail2] [Bug 368060] Replying to html email that has a PDF attachment creates junk in the reply

2016-09-20 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Got the same with a PNG attached.  Current workaround: mark the text you are
replying to and then reply -> will only copy out the text of the reply.

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

[kmail2] [Bug 363027] KMail2 5.3.1: Per folder HTML settings are not working

2016-09-20 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #8 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
It seems that the hotkey to "Toggle HTML Display Mode" is ineffective, as well.
  I am on

Version 5.3.0 (QtWebEngine)
Using:
KDE Frameworks 5.27.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

via KDE/neon 4:16.08.1+p16.04+git20160918.0030-0

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

[kmail2] [Bug 368766] KMail crashes when moving mail in reference counting code

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #2 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Please see the duplicate for a very similar crash that does *not* use threaded
view (but instead Current Activity, Flat).  Still crashes in the same code.

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

[kmail2] [Bug 368766] KMail crashes when moving mail in reference counting code

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
*** Bug 368767 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 368767] KMail crashes when moving messages.

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Could not add to other report in DrKonqi.

*** This bug has been marked as a duplicate of bug 368766 ***

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

[kmail2] [Bug 368767] New: KMail crashes when moving messages.

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

Bug ID: 368767
   Summary: KMail crashes when moving messages.
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: stephan.diestelho...@gmail.com

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: KDE neon User Edition 5.7

-- Information about the crash:
- What I was doing when the application crashed:
Moving a message to another folder in unthreaded view.  KMail crashes with the
same backtrace as bug 368766, but I cannot attache in the Crash Reporter :-S

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5638090a00 (LWP 4381))]

Thread 40 (Thread 0x7f54c48dd700 (LWP 4954)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5653d6f7af in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f5653d6fdc9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f5653d6ff80 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f5653d6c947 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f565d32f6fa in start_thread (arg=0x7f54c48dd700) at
pthread_create.c:333
#6  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 39 (Thread 0x7f55901b3700 (LWP 4912)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5653d6f7af in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f5653d6fdc9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f5653d6ff80 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f5653d6c947 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f565d32f6fa in start_thread (arg=0x7f55901b3700) at
pthread_create.c:333
#6  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 38 (Thread 0x7f54ca467700 (LWP 4910)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5658b86863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f5658ea7051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f565d32f6fa in start_thread (arg=0x7f54ca467700) at
pthread_create.c:333
#4  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 37 (Thread 0x7f54cac68700 (LWP 4909)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5658b86863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f5658ea7051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f565d32f6fa in start_thread (arg=0x7f54cac68700) at
pthread_create.c:333
#4  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 36 (Thread 0x7f54cb469700 (LWP 4908)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5658b86863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f5658ea7051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f565d32f6fa in start_thread (arg=0x7f54cb469700) at
pthread_create.c:333
#4  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 35 (Thread 0x7f54cbc6a700 (LWP 4907)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5658b85834 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f5658ea7051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f565d32f6fa in start_thread (arg=0x7f54cbc6a700) at
pthread_create.c:333
#4  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 34 (Thread 0x7f550c56f700 (LWP 4906)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5658e7742b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f5658e77469 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f565d32f6fa in start_thread (arg=0x7f550c56f700) at
pthread_create.c:333
#4  0x7f56668d0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 33 (Thread 0x7f558d69f700 (LWP 4905)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1

[kmail2] [Bug 368766] New: KMail crashes when moving mail in reference counting code

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

Bug ID: 368766
   Summary: KMail crashes when moving mail in reference counting
code
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: stephan.diestelho...@gmail.com

Version 5.3.0 (QtWebEngine)
Using:
KDE Frameworks 5.25.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system
--
Project Neon User
--
I am using threaded view, but was moving a non-threaded message to a different
folder.  This smells like a race condition to me, maybe someone is free-ing
memory while the reference counter is non-zero, and someone still has a
reference to it and tries to set that to zero?
--
Related: bug 368496 and bug 364994.
Thread 1 "kmail" received signal SIGSEGV, Segmentation fault.
0x72160efc in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5MimeTreeParser.so.5
(gdb) bt
#0  std::__atomic_base::load (__m=std::memory_order_relaxed, this=)
at /usr/include/c++/5/bits/atomic_base.h:396
#1  QAtomicOps::load (_q_value=)   
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:103 
#2  QBasicAtomicInteger::load (this=)   
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:99   
#3  QtPrivate::RefCount::ref (this=) 
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55  
#4  QVector::QVector
(v=..., this=)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:363   
#5 
QForeachContainer const>::QForeachContainer (t=...,
this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:944  
#6  MimeTreeParser::toplevelTextNode (messageTree=...) at
/workspace/build/mimetreeparser/src/bodyformatter/utils.cpp:55
#7  0x7216127a in MimeTreeParser::toplevelTextNode (messageTree=...)
at /workspace/build/mimetreeparser/src/bodyformatter/utils.cpp:64   
#8  0x72175d04 in MimeTreeParser::ObjectTreeParser::parseObjectTree
(this=this@entry=0x7fffcd80, node=node@entry=0x2b63550)
at /workspace/build/mimetreeparser/src/viewer/objecttreeparser.cpp:185
#9  0x72ab4d27 in MessageViewer::ViewerPrivate::parseContent
(this=this@entry=0xae7670, content=0x2b63550)
at /workspace/build/messageviewer/src/viewer/viewer_p.cpp:969
#10 0x72ab531d in MessageViewer::ViewerPrivate::displayMessage
(this=this@entry=0xae7670)
at /workspace/build/messageviewer/src/viewer/viewer_p.cpp:842
#11 0x72ab5d8a in MessageViewer::ViewerPrivate::updateReaderWin
(this=0xae7670)
at /workspace/build/messageviewer/src/viewer/viewer_p.cpp:2133
#12 0x75ea9f36 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x75eb64e8 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x75eaaa93 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7676a89c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x76772296 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x75e7eda8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x75ed123e in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x75ed1771 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fffea2b71a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fffea2b7400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fffea2b74ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x75ed22ef in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x75e7cd9a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x75e853ac in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00403984 in ?? ()
#27 0x752b7830 in __libc_start_main (main=0x4028d0, argc=1,
argv=0x7fffded8, init=, fini=, 
rtld_fini=, stack_end=0x7fffdec8) at
../csu/libc-start.c:291
#28 0x00404079 in _start ()
(gdb) q


Reproducible: Sometimes

Steps to Reproduce:
1. (Not sure: enable threaded view)
2. Move a few messages to other folders


Actual Results:  
KMail crashes with the backtrace

[kdepim] [Bug 364994] Kmail crash when deleting message in thread view

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[kmail2] [Bug 368496] KMail crashes in memcpy

2016-09-13 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #2 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Yep, I am using those, quite extensively.  Will retry that in GDB to see what
is happening.  Also got another one, this time very different backtrace from
either.

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

[kmail2] [Bug 368496] New: KMail crashes in memcpy

2016-09-09 Thread Stephan Diestelhorst via KDE Bugzilla

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

Bug ID: 368496
   Summary: KMail crashes in memcpy
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: stephan.diestelho...@gmail.com

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.4.0-36-generic x86_64
Distribution: KDE neon User Edition 5.7

-- Information about the crash:
- What I was doing when the application crashed:
Moving emails around and checking my inbox; this crashes fairly frequently. 
Running on NEON Dev channel.

- Custom settings of the application:
Running this in VirtualBox on Mac OSX, might be a glitch with virtualisation?

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9242e2ba00 (LWP 16833))]

Thread 38 (Thread 0x7f911009b700 (LWP 16926)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f925f1407af in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f925f140dc9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f925f140f80 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f925f13d947 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f92687006fa in start_thread (arg=0x7f911009b700) at
pthread_create.c:333
#6  0x7f9271ca7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 37 (Thread 0x7f91d9c64700 (LWP 16925)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f925f1407af in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f925f140dc9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f925f140f80 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f925f13d947 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f92687006fa in start_thread (arg=0x7f91d9c64700) at
pthread_create.c:333
#6  0x7f9271ca7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 36 (Thread 0x7f911265f700 (LWP 16923)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9263f57863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f9264278051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f92687006fa in start_thread (arg=0x7f911265f700) at
pthread_create.c:333
#4  0x7f9271ca7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 35 (Thread 0x7f9112e60700 (LWP 16922)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9263f56834 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f9264278051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f92687006fa in start_thread (arg=0x7f9112e60700) at
pthread_create.c:333
#4  0x7f9271ca7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 34 (Thread 0x7f9153663700 (LWP 16921)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f926424842b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f9264248469 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f92687006fa in start_thread (arg=0x7f9153663700) at
pthread_create.c:333
#4  0x7f9271ca7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 33 (Thread 0x7f91d4693700 (LWP 16920)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f925a6a35c4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f925a6a3609 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f92687006fa in start_thread (arg=0x7f91d4693700) at
pthread_create.c:333
#4  0x7f9271ca7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 32 (Thread 0x7f91d4e94700 (LWP 16918)):
#0  0x7f9266bbac47 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9266bbb340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9266bbb4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f92727dc23b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9272786cea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f92725abfb4 in

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2016-06-10 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #54 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
For me mysql complained about "You can't specify target for update in FROM
clause".  Wrapping things into another layer of SELECT did the trick:

DELETE FROM pimitemtable WHERE pimitemtable.id in (
  SELECT id FROM (
SELECT id FROM pimitemtable
LEFT OUTER JOIN (
  SELECT MIN(pimitemtable.id) as RowId, pimitemtable.remoteId,
pimitemtable.collectionId FROM pimitemtable GROUP by pimitemtable.remoteId,
pimitemtable.collectionId )
as KeepRows ON pimitemtable.id = KeepRows.RowId
WHERE KeepRows.RowId IS NULL)
  AS foo)

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

[Akonadi] [Bug 355743] akonadiconsole shows now enties in the 'Browser' tab

2016-03-30 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #4 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
This is a regression, by the way.

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

[Akonadi] [Bug 355743] akonadiconsole shows now enties in the 'Browser' tab

2016-03-30 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #3 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Could you please fix the bug title?  It should read "akonadiconsole shows no
entries in 'Browser' tab".  Thanks!  Also.. same here.

akonadiconsole Version 0.99
Using:
  KDE Frameworks 5.15.0
  Qt 5.4.2 (built against 5.4.2)
  The xcb windowing system

$ apt-cache policy akonadiconsole
akonadiconsole:
  Installed: 4:15.08.2-0ubuntu1
  Candidate: 4:15.08.2-0ubuntu1
  Version table:
 *** 4:15.08.2-0ubuntu1 0
500 http://mirror.sov.uk.goscomb.net/ubuntu/ wily/universe amd64
Packages
100 /var/lib/dpkg/status

$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"

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

[kmail2] [Bug 354055] system freeze when trying to send email via ctrl + return with "spellcheck before send" activated

2016-03-29 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #2 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
I think I have a similar issue, I have checked "confirm before send" and am
enforcing a spell check, too via "Check spelling before sending".

I have created a small video showing the state of affairs:
https://www.youtube.com/watch?v=Bg_JF5FLhac

Versions:
Kmail Version 5.0.2
Using:
KDE Frameworks 5.15.0
Qt 5.4.2 (built against 5.4.2)
The xcb windowing system

$ apt-cache policy kmail
kmail:
  Installed: 4:15.08.2-0ubuntu1
  Candidate: 4:15.08.2-0ubuntu1
$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"
NAME="Ubuntu"
VERSION="15.10 (Wily Werewolf)"

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

[systemsettings] [Bug 355354] Swap CapsLock and Escape feature disabled spontaneously

2016-02-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

--- Comment #2 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
I meant bug 356851.  If I look at my log output, it seems that sometimes (for
me it is after resume and undocking / docking) the keyboard settings get reset
from

symbols: pc+us+inet(evdev) geometry: pc(pc105)

to

symbols: pc+us+inet(evdev)+capslock(escape) geometry: pc(pc101)

My config in KDE suggests the latter (pc101) and the caps as an additional
escape.

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

[systemsettings] [Bug 338361] After swapping Esc and Caps Lock and assigning new action to shortcut which includes Esc, it doesn't work.

2016-02-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #3 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
Maybe similar to bug 356851 and bug 355354?  I also have a similar bug with
detaild log output here:
https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293

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

[systemsettings] [Bug 356851] System keyboard layout ctrl capslock requires re-apply after log out

2016-02-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
I have a similar problem and investigated it here:
https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293

Also, bug 355354 might be related.

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

[systemsettings] [Bug 355354] Swap CapsLock and Escape feature disabled spontaneously

2016-02-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

--- Comment #1 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
This might be related to #356851 and to my recent report Kubuntu bugs:
https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1545293

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

[kmail2] [Bug 359823] New: Scrolling in message view window only updates window partially

2016-02-26 Thread Stephan Diestelhorst via KDE Bugzilla

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

Bug ID: 359823
   Summary: Scrolling in message view window only updates window
partially
   Product: kmail2
   Version: 5.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: stephan.diestelho...@gmail.com

After a while of using kmail (5.0.2 KDE Frameworks: 5.15.0, Qt 5.4.2), it seems
that the message preview below the message list stops scrolling properly.  I
can still scroll, but if I scroll down, only the lower ~50 pixels (~2 lines of
text) get updated.  When I scroll up, it is only the top 50 pixels in that
window.  The rest stays exactly flat.

I have tried disabling Desktop Effects (Alt + Shift + F12), but that does not
resolve the problem once it has occurred.  I also played with the KDE
compositor settings and selected all different tearing options, GL versions
etc, but nothing helped.

The only way to fix this seems to be to restart KMail for now.  Then it
continues working for a while, I have not yet identified when this happens.  I
usually can work for (felt) 30 mins to several hours until this turns up again.

This happens for both HTML and text emails.  Going to the next message will
render the full view correctly.  Resizing the preview pane does not have an
effect, other than temporarily rendering the screen correctly.

Reproducible: Always

Steps to Reproduce:
1. browse emails and use the preview window and scroll
2. do this for a while
3. observe the scrolling not affecting the middle of the window

Actual Results:  
the middle of the rendered email does not move on the screen

Expected Results:  
the entire message scrolls up and down

kubuntu package: 4:15.08.2-0ubuntu1

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

[muon] [Bug 358359] HIgh cpu consumption and apt-check process infinte fork

2016-02-22 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[plasmashell] [Bug 358211] Plasma crash when re-activating screen

2016-02-18 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

2016-02-18 Thread Stephan Diestelhorst via KDE Bugzilla

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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

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

70 matches

Mail list logo