from:"Robby Engelmann"

[korganizer] [Bug 479351] It is not possible to add Sub-ToDos in Kontact ToDo-List

2024-02-22 Thread Robby Engelmann

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

--- Comment #7 from Robby Engelmann  ---
appears to work here, thanks!

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

[kontact] [Bug 473673] Calendar Reminders: I click on "remind in 1 hour" and get the same reminder 30 seconds afterwards.

2024-02-09 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

   Keywords||qt6
 CC||robby.engelmann@r-engelmann
   ||.de
Version|5.23.3  |GIT (master)

--- Comment #2 from Robby Engelmann  ---
same here:
Operating System: openSUSE Tumbleweed 20240208
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page

2024-02-09 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REOPENED|RESOLVED

--- Comment #7 from Robby Engelmann  ---
(In reply to Daniel Vrátil from comment #6)
> If you are using Kontact, there should be a standalone "To-do List" action
> in the Kontact side-panel that opens the "Todo View" that you would
> otherwise normally get in standalone KOrganizer toolbar - I'm pretty sure
> this hasn't changed in the Qt6 build.
> 
> Or am I misunderstanding the problem?

I was referring to the todo-view that can be shown within the "Calender" tab.
For whatever reason this is fine again here since 1-2 days again.

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

[korganizer] [Bug 479351] It is not possible to add Sub-ToDos in Kontact ToDo-List

2024-02-09 Thread Robby Engelmann

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

--- Comment #4 from Robby Engelmann  ---
Still the menu point to add Sub-To Dos is gray here.

The merge should be integrate into the last night build of git master in
openSUSE unstable KDE repos (I think at least).

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

[kmail2] [Bug 480038] Kmail crash everytime when closing

2024-01-19 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

   Keywords||qt6

--- Comment #2 from Robby Engelmann  ---
it appears since the transition to qt6

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

[kmail2] [Bug 480038] Kmail crash everytime when closing

2024-01-19 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #1 from Robby Engelmann  ---
Created attachment 165032
  --> https://bugs.kde.org/attachment.cgi?id=165032=edit
backtrace

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

[kmail2] [Bug 480038] New: Kmail crash everytime when closing

2024-01-19 Thread Robby Engelmann

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

Bug ID: 480038
   Summary: Kmail crash everytime when closing
Classification: Applications
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
Kmail crash everytime I close it. Same if I close Kontact.

STEPS TO REPRODUCE
1. open kmail
2. close kmail

OBSERVED RESULT
crash

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240118
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Kernel Version: 6.6.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page

2024-01-17 Thread Robby Engelmann

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

--- Comment #5 from Robby Engelmann  ---
in current git master still no ToDo-View in the Calendar tab in Kontact.

Operating System: openSUSE Tumbleweed 20240115
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Kernel Version: 6.6.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[korganizer] [Bug 479351] It is not possible to add Sub-ToDos in Kontact ToDo-List

2024-01-17 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #1 from Robby Engelmann  ---
still valid in master:
Operating System: openSUSE Tumbleweed 20240115
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Kernel Version: 6.6.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[korganizer] [Bug 479351] New: It is not possible to add Sub-ToDos in Kontact ToDo-List

2024-01-03 Thread Robby Engelmann

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

Bug ID: 479351
   Summary: It is not possible to add Sub-ToDos in Kontact
ToDo-List
Classification: Applications
   Product: korganizer
   Version: GIT (master)
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: todoview
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
It is not possible to add Sub-ToDos in Kontact ToDo-List. Menu item is grayed
oit

Operating System: openSUSE Tumbleweed 20231228
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.6.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page

2024-01-03 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
   Keywords||qt6

--- Comment #4 from Robby Engelmann  ---
The ToDo panel in the Kontact Calender View is empty. It is shown in ToDo-List,
however.
Using current git master snapshot.

Operating System: openSUSE Tumbleweed 20231228
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.6.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[kontact] [Bug 411968] Kontact crashed after forwarding an email inline with attachment

2023-12-29 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED
 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #6 from Robby Engelmann  ---
did not see this for quite some time

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

[kaddressbook] [Bug 478456] kaddressbook crash since yesterdays master git builds

2023-12-29 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #1 from Robby Engelmann  ---
works again

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-29 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #10 from Robby Engelmann  ---
works again since >1 week in git master snapshot builds

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-29 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #12 from Robby Engelmann  ---
Works in recent git master snapshots (for over one week)

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-15 Thread Robby Engelmann

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

--- Comment #9 from Robby Engelmann  ---
The last working snapshot is from 2023-12-05. If I boot into this snapshot,
pop'ing and sending emails works fine and no crash of kaddressbook.
Thus, there must be a change in between until the bug was first reported -4
days = until 2023-12-10, which is approx 5 days.

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-15 Thread Robby Engelmann

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

--- Comment #8 from Robby Engelmann  ---
removing the dat-files did not help; still crashing.
how can I get a backtrace for this?

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-15 Thread Robby Engelmann

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

--- Comment #7 from Robby Engelmann  ---
I use the daily git master builds provided by the openSUSE people.

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-15 Thread Robby Engelmann

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

--- Comment #5 from Robby Engelmann  ---
this is what I got:
localhost:~> kmail
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"stateChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMState
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"connectivityChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMConnectivityState
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"deviceTypeChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMDeviceType
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"meteredChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMMetered
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
/usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future
release, use '/usr/bin/mariadb-check' instead
akonadi.collectionattributetable   OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation  OK
akonadi.collectiontableOK
akonadi.flagtable  OK
akonadi.mimetypetable  OK
akonadi.parttable  OK
akonadi.parttypetable  OK
akonadi.pimitemflagrelationOK
akonadi.pimitemtable   OK
akonadi.pimitemtagrelation OK
akonadi.relationtable  OK
akonadi.relationtypetable  OK
akonadi.resourcetable  OK
akonadi.schemaversiontable OK
akonadi.tagattributetable  OK
akonadi.tagremoteidresourcerelationtable   OK
akonadi.tagtable   OK
akonadi.tagtypetable   OK
/usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future
release, use '/usr/bin/mariadb-upgrade' instead
FATAL ERROR: Can't execute '/usr/bin/mariadb'
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadicontrol: Akonadi server is now operational.
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c002180) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c01c380) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f9c7c002180) identified as
"PlasmaEventModelMonitor - 93877899591264"
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c031e90) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c03b6d0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c044d20) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c04e2d0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c057920) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c060e80) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c06a290) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f9c7c01c380) identified as
"ETMCalendarMonitor - 93999645851136"
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c082d70) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c080570) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c081980) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c0b5d10) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c0bf240) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f9c7c0c8730) )
org.kde.pim.akonadiserver: New notification connection

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-15 Thread Robby Engelmann

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

--- Comment #3 from Robby Engelmann  ---
I can boot into a former snapper snapshot and then it works. But not with
current git master.

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-15 Thread Robby Engelmann

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

--- Comment #2 from Robby Engelmann  ---
but this is no crash, but a not-working functionality that worked before, which
means = regression ?!
If I can collect more information for you, just let me know.

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-14 Thread Robby Engelmann

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

--- Comment #10 from Robby Engelmann  ---
akonadictl fsck did not help here,
nor directly try to send nor after a restart.
still crashing.

BTW, this bug started with the same timing:
https://bugs.kde.org/show_bug.cgi?id=478504

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

[kmail2] [Bug 478504] Git master qt6 version fails to pop emails

2023-12-14 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de
   Keywords||qt6

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

[kmail2] [Bug 478504] New: Git master qt6 version fails to pop emails

2023-12-14 Thread Robby Engelmann

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

Bug ID: 478504
   Summary: Git master qt6 version fails to pop emails
Classification: Applications
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
Since about 3-4 days I do not get mails via pop. However, another ews ressource
works and I get new emails


STEPS TO REPRODUCE
1. Having a POP receiving account
2. check Mail

OBSERVED RESULT
no mails are received

EXPECTED RESULT
present mails (seen in webmailer) are received


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20231213
KDE Plasma Version: 5.90.90
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Kernel Version: 6.6.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-14 Thread Robby Engelmann

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

--- Comment #7 from Robby Engelmann  ---
This is right, the EWS fails here as well in terms of sending.

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

[kaddressbook] [Bug 478456] kaddressbook crash since yesterdays master git builds

2023-12-12 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de
   Keywords||qt6

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

[kaddressbook] [Bug 478456] New: kaddressbook crash since yesterdays master git builds

2023-12-12 Thread Robby Engelmann

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

Bug ID: 478456
   Summary: kaddressbook crash since yesterdays master git builds
Classification: Applications
   Product: kaddressbook
   Version: GIT
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
kaddressbook crash since yesterdays master git builds


STEPS TO REPRODUCE
1. Start kaddressbook


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20231211
KDE Plasma Version: 5.90.90
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

The only backtrace I got:
(gdb) bt
#0  main(int, char**) (argc=1, argv=0x7fffd828) at
/usr/src/debug/kaddressbook-24.01.80git.20231212T021451~563dcf3/src/main.cpp:50
(gdb)

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-12 Thread Robby Engelmann

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

--- Comment #5 from Robby Engelmann  ---
does this:
>qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to 
>"stateChanged" : Type not registered with QtDBus in parameter list: 
>QNetworkManagerInterface::NMState
>qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to 
>"connectivityChanged" : Type not registered with QtDBus in parameter list: 
>QNetworkManagerInterface::NMConnectivityState
>qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to 
>"deviceTypeChanged" : Type not registered with QtDBus in parameter list: 
>QNetworkManagerInterface::NMDeviceType
>qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to 
>"meteredChanged" : Type not registered with QtDBus in parameter list: 
>QNetworkManagerInterface::NMMetered

hint, that kmail is not able to establish a network connection and this is why
no mails can be pop'ed and the sending fails.
And the failed sending triggers a crash?
And the ews ressource works because making use of another connection protocol?
...I am only wildly guessing...

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-11 Thread Robby Engelmann

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

--- Comment #4 from Robby Engelmann  ---
(gdb) bt
#0  0x7fffe9f536de in Akonadi::ItemCreateJob::doStart() () at
/lib64/libKPim6AkonadiCore.so.6
#1  0x7fffe9f59278 in  () at /lib64/libKPim6AkonadiCore.so.6
#2  0x7fffebdcb2ae in QObject::event(QEvent*) (this=0x5607e930,
e=0x7ffe840026a0)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qobject.cpp:1437
#3  0x7fffecfc094e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5607e930, e=0x7ffe840026a0)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/widgets/kernel/qapplication.cpp:3296
#4  0x7fffebd878b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5607e930, event=0x7ffe840026a0)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qcoreapplication.cpp:1121
#5  0x7fffebd878f9 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qcoreapplication.cpp:1539
#6  0x7fffebd87c17 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x555adee0)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qcoreapplication.cpp:1901
#7  0x7fffebfad9e3 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x556051a0)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qeventdispatcher_glib.cpp:243
#8  0x7fffe8cb1f30 in  () at /lib64/libglib-2.0.so.0
#9  0x7fffe8cb3b58 in  () at /lib64/libglib-2.0.so.0
#10 0x7fffe8cb420c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#11 0x7fffebfabc6c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x555962e0, flags=...)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qeventdispatcher_glib.cpp:393
#12 0x7fffebd9211b in
QEventLoop::exec(QFlags) (this=0x7fffc780,
flags=...)
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/build/include/QtCore/../../../src/corelib/global/qflags.h:34
#13 0x7fffebd8bd46 in QCoreApplication::exec() ()
at
/usr/src/debug/qtbase-everywhere-src-6.6.1/build/include/QtCore/../../../src/corelib/global/qflags.h:74
#14 0x7fffec5e268c in QGuiApplication::exec() () at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/gui/kernel/qguiapplication.cpp:1925
#15 0x7fffecfbdd85 in QApplication::exec() () at
/usr/src/debug/qtbase-everywhere-src-6.6.1/src/widgets/kernel/qapplication.cpp:2574
#16 0x9138 in main(int, char**) (argc=,
argv=)
at
/usr/src/debug/kmail-24.01.80git.20231211T021212~c1635d35/src/main.cpp:174

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-11 Thread Robby Engelmann

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

--- Comment #3 from Robby Engelmann  ---
this is what shows up in konsole:
>kmail
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"stateChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMState
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"connectivityChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMConnectivityState
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"deviceTypeChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMDeviceType
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to
"meteredChanged" : Type not registered with QtDBus in parameter list:
QNetworkManagerInterface::NMMetered
org.kde.pim.kmail_expertplugin: toggle_mimeparttree is not defined 
 lstFilters  0
 lstFilters  7
doh set to ""  --  SystemOnly
gpg.qgpgme: found no group for entry verbose of component "tpm2daemon"
gpg.qgpgme: found no group for entry quiet of component "tpm2daemon"
gpg.qgpgme: found no group for entry debug-level of component "tpm2daemon"
gpg.qgpgme: found no group for entry log-file of component "tpm2daemon"
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
KCrash: Application 'kmail' crashing... crashRecursionCounter = 2
Segmentation fault (core dumped)

The crash occurred when trying to send an email

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

[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built

2023-12-11 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #2 from Robby Engelmann  ---
BTW, there is also no pop3 working, but the ews ressource did its job

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

[kmail2] [Bug 473849] Invitations shown as plain text and not ask for import

2023-12-11 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||robby.engelmann@r-engelmann
   ||.de
 Status|REPORTED|RESOLVED

--- Comment #1 from Robby Engelmann  ---
seem to work again after switched to qt6 builds

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

[kmail2] [Bug 478416] New: Crash on eMail sending since yesterdays git master snapshot built

2023-12-11 Thread Robby Engelmann

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

Bug ID: 478416
   Summary: Crash on eMail sending since yesterdays git master
snapshot built
Classification: Applications
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
Since yesterdays git master snapshot of the qt6 megarelease as being provided
by openSUSE, Email sending does not work anymore



SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20231210
KDE Plasma Version: 5.90.90
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[akregator] [Bug 477678] Crispy text in kmail, akregator and others

2023-11-29 Thread Robby Engelmann

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

--- Comment #8 from Robby Engelmann  ---
I am quite sure, that the answer is YES, but I cannot look it up, because the
Display & Monitor KCM is crashing here every time

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

[akregator] [Bug 477678] Crispy text in kmail, akregator and others

2023-11-28 Thread Robby Engelmann

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

--- Comment #6 from Robby Engelmann  ---
Created attachment 163603
  --> https://bugs.kde.org/attachment.cgi?id=163603=edit
clear in panel

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

[akregator] [Bug 477678] Crispy text in kmail, akregator and others

2023-11-28 Thread Robby Engelmann

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

--- Comment #5 from Robby Engelmann  ---
Created attachment 163602
  --> https://bugs.kde.org/attachment.cgi?id=163602=edit
crispy in panel

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

[akregator] [Bug 477678] Crispy text in kmail, akregator and others

2023-11-28 Thread Robby Engelmann

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

--- Comment #4 from Robby Engelmann  ---
until now I recognized it for:
-Texts in Akregator and Kmail (always
-Texts in Plasma notes (I think if it is not active; when click into it, the
text changes from crispy to clear)
-Titles in the plasma panel (might be, that here only the lower part is not
rendered if full screen app touches the panel) - see attachments

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

[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page

2023-11-28 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Robby Engelmann  ---
Now I switched to the qt6-based master builds in openSUSE and it works

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

[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page

2023-10-23 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #2 from Robby Engelmann  ---
I am still using the qt5 branch via Tumbleweed KDE:unstable repos. Qt6 builds
are not available there currently.
If newest git builds from qt5 branch should do the job, they do not here. ToDo
view still empty.

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

[kmail2] [Bug 473849] New: Invitations shown as plain text and not ask for import

2023-08-28 Thread Robby Engelmann

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

Bug ID: 473849
   Summary: Invitations shown as plain text and not ask for import
Classification: Applications
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Invitations received are shown as plain-text ical and there is no dialogue
anymore asking to add it to korganizer.

Operating System: openSUSE Tumbleweed 20230823
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[korganizer] [Bug 473847] To-Do View empty but To-Dos shown in Kontact summary page

2023-08-28 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de
Summary|To-Do View empty but shown  |To-Do View empty but To-Dos
   |in Kontact summary page |shown in Kontact summary
   ||page

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

[korganizer] [Bug 473847] New: To-Do View empty but shown in Kontact summary page

2023-08-28 Thread Robby Engelmann

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

Bug ID: 473847
   Summary: To-Do View empty but shown in Kontact summary page
Classification: Applications
   Product: korganizer
   Version: GIT (master)
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Since 1-2 weeks the To-Do View is empty, although Todos are shown in the
Kontact Summary page.

Operating System: openSUSE Tumbleweed 20230823
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-13700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)

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

[kmail2] [Bug 456578] recipient auto-completion does not work in master git snapshots

2022-08-02 Thread Robby Engelmann

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

--- Comment #9 from Robby Engelmann  ---
confirm, is fixed here.
Thanx!

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

[kmail2] [Bug 456578] recipient auto-completion does not work in master git snapshots

2022-07-29 Thread Robby Engelmann

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

--- Comment #6 from Robby Engelmann  ---
Yes, I do.

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

[kmail2] [Bug 456578] recipient auto-completion does not work in master git snapshots

2022-07-29 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Robby Engelmann  ---
thanks a lot!

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

[kmail2] [Bug 456578] recipient auto-completion does not work in master git snapshots

2022-07-29 Thread Robby Engelmann

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

--- Comment #2 from Robby Engelmann  ---
Any news on this?
Still no auto-completion here with todays snapshots...

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

[kmail2] [Bug 343770] Messages list becomes empty after deleting one message

2022-07-19 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[kmail2] [Bug 343770] Messages list becomes empty after deleting one message

2022-07-19 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #6 from Robby Engelmann  ---
also true here using a EWS ressource under git master snapshots..

Operating System: openSUSE Tumbleweed 20220718
KDE Plasma Version: 5.25.80
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.18.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO
System Version: Not Applicable

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

[kmail2] [Bug 456578] recipient auto-completion does not work in master git snapshots

2022-07-19 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

Summary|recipient auto-completion   |recipient auto-completion
   |does not work since 1-2 |does not work in master git
   |days|snapshots
 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #1 from Robby Engelmann  ---
is still valid here in master git snapshots from openSUSE Tumbleweed.
Can anybody confirm this?

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

[kmail2] [Bug 456578] New: recipient auto-completion does not work since 1-2 days

2022-07-11 Thread Robby Engelmann

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

Bug ID: 456578
   Summary: recipient auto-completion does not work since 1-2 days
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
recipient auto-completion does not work since 1-2 days

STEPS TO REPRODUCE
1. Write new mail
2. start typing in TO field
3. 

OBSERVED RESULT
no auto-completion results shown

EXPECTED RESULT
auto-completion results shown

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220709
KDE Plasma Version: 5.25.80
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.18.9-2-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO
System Version: Not Applicable

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

[kontact] [Bug 446104] QtWebengine-based views broken in master - affects Kmail + Akregator + more in wayland session

2022-05-12 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de
 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

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

[kontact] [Bug 393796] pulseaudio shows constant 18% cpu when kontact is running

2022-03-29 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de
 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

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

[kontact] [Bug 446104] New: QtWebengine-based views broken in master - affects Kmail + Akregator + more in wayland session

2021-11-25 Thread Robby Engelmann

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

Bug ID: 446104
   Summary: QtWebengine-based views broken in master - affects
Kmail + Akregator + more in wayland session
   Product: kontact
   Version: GIT (master)
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
***
Since 2-3 days I have issues with showing Qtwebview-based things, like
Mail-content or pages in Akregator. They are sometimes simply white blank, are
flickering between the content / white blank when scrolling.

It has been confirmed in openSUSE and appears to be wayland-specific.
***


STEPS TO REPRODUCE
1. install openSUSE Tumbleweed with Unstable repos for Frameworks and Apps
2. start into wayland session
3. try to open mails

OBSERVED RESULT
white blank / flickering

EXPECTED RESULT
works fine

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211124
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL:
https://bugzilla.opensuse.org/show_bug.cgi?id=1193036

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

[kmail2] [Bug 446052] Drag Mails in Kmail does not work using git-master snapshots since 2-3 days

2021-11-25 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #2 from Robby Engelmann  ---
tested ... fixed. great!

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

[kmail2] [Bug 446052] New: Drag Mails in Kmail does not work using git-master snapshots since 2-3 days

2021-11-24 Thread Robby Engelmann

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

Bug ID: 446052
   Summary: Drag Mails in Kmail does not work using
git-master snapshots since 2-3 days
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
***
Drag Mails in Kmail does not work using git-master snapshots since 2-3
days
***
STEPS TO REPRODUCE
1. use OpenSuse Unstable = git master snapshots for frameworks+plasma+gear
2.  open kmail, try to move mail to another folder

OBSERVED RESULT
cannot move to another folder, but move is possible if folder is added to
favorite folders

EXPECTED RESULT
works as normal

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211123
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION
downstream bug: http://bugzilla.opensuse.org/show_bug.cgi?id=1193055

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

[kontact] [Bug 411968] New: Kontact crashed after forwarding an email inline with attachment

2019-09-16 Thread Robby Engelmann

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

Bug ID: 411968
   Summary: Kontact crashed after forwarding an email inline with
attachment
   Product: kontact
   Version: 5.12.1
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Application: kontact (5.12.1)

Qt Version: 5.13.1
Frameworks Version: 5.62.0
Operating System: Linux 5.2.13-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
right-click mail to forward --> forward --> inline --> crash occurs

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8e70e84a80 (LWP 15682))]

Thread 28 (Thread 0x7f8d5affd700 (LWP 15785)):
#0  0x7f8e7fbc616c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8e79206fc6 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f8e79207993 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f8e79207b11 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f8e791bfc81 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f8e791c2b1d in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f8e791c3214 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f8e79209e05 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f8e7fbbffaa in start_thread () from /lib64/libpthread.so.0
#9  0x7f8e8212d73f in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f8d5b7fe700 (LWP 15769)):
#0  0x7f8e7fbc5e05 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8e79206ecc in base::ConditionVariable::Wait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75
#2  0x7f8e792079a0 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:232
#3  0x7f8e79207acf in base::WaitableEvent::Wait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155
#4  0x7f8e791bfc56 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:35
#5  0x7f8e791c2e6b in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331
#6  0x7f8e791c3254 in base::internal::SchedulerWorker::RunSharedWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:241
#7  0x7f8e79209e05 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f8e7fbbffaa in start_thread () from /lib64/libpthread.so.0
#9  0x7f8e8212d73f in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f8d5bfff700 (LWP 15746)):
#0  0x7f8e8211e8af in write () from /lib64/libc.so.6
#1  0x7f8e820b0565 in _IO_file_write@@GLIBC_2.2.5 () from /lib64/libc.so.6
#2  0x7f8e820af8f6 in new_do_write () from /lib64/libc.so.6
#3  0x7f8e820b0c6e in __GI__IO_file_xsputn () from /lib64/libc.so.6
#4  0x7f8e8209d259 in buffered_vfprintf () from /lib64/libc.so.6
#5  0x7f8e8209a384 in __vfprintf_internal () from /lib64/libc.so.6
#6  0x7f8e8213c64f in __fprintf_chk () from /lib64/libc.so.6
#7  0x7f8e756c2d3e in event_logv_ () from /usr/lib64/libevent-2.1.so.7
#8  0x7f8e756c5925 in event_warn () from /usr/lib64/libevent-2.1.so.7
#9  0x7f8e756c7488 in ?? () from /usr/lib64/libevent-2.1.so.7
#10 0x7f8e756d7df5 in event_base_loop () from /usr/lib64/libevent-2.1.so.7
#11 0x7f8e7920dc68 in base::MessagePumpLibevent::Run () at
./../../3rdparty/chromium/base/message_loop/message_pump_libevent.cc:214
#12 0x7f8e79199de7 in base::RunLoop::Run () at
./../../3rdparty/chromium/base/run_loop.cc:150
#13 base::RunLoop::Run () at ./../../3rdparty/chromium/base/run_loop.cc:121
#14 0x7f8e791d0f8f in base::Thread::Run () at
./../../3rdparty/chromium/base/threading/thread.cc:251
#15 base::Thread::ThreadMain () at
./../../3rdparty/chromium/base/threading/thread.cc:333
#16 0x7f8e79209e05 in ThreadFunc () at

[kontact] [Bug 410956] New: Kontact crashed upon sending SMS

2019-08-15 Thread Robby Engelmann

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

Bug ID: 410956
   Summary: Kontact crashed upon sending SMS
   Product: kontact
   Version: 5.12.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Application: kontact (5.12.0)

Qt Version: 5.13.0
Frameworks Version: 5.61.0
Operating System: Linux 5.2.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I tried the new feature of sending SMS out of the Addressbook

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f31845d1a40 (LWP 3100))]

Thread 28 (Thread 0x7f3169397700 (LWP 7978)):
#0  0x7f319219b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f318b7ec546 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f318b7ecf13 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f318b7ed091 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f318b7a51f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f318b7a808d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f318b7a8784 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f318b7ef385 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f3192194faa in start_thread () at /lib64/libpthread.so.0
#9  0x7f319470473f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f3168b96700 (LWP 7977)):
#0  0x7f319219b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f318b7ec546 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f318b7ecf13 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f318b7ed091 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f318b7a51f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f318b7a83db in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331
#6  0x7f318b7a8784 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f318b7ef385 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f3192194faa in start_thread () at /lib64/libpthread.so.0
#9  0x7f319470473f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f309700 (LWP 7974)):
#0  0x7f319219b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f318b7ec546 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f318b7ecf13 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f318b7ed091 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f318b7a51f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f318b7a808d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f318b7a8784 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f318b7ef385 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8

[Akonadi] [Bug 409641] Akonadi Server crashs upon start of Kontact

2019-07-24 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #6 from Robby Engelmann  ---
I finally removed some mails popping up shortly before the issue and now the
issue is solved for me. Feel free to close this, if the needed info is needed
to track down the issue as it will not be possible for me anymore to provide
these information.

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

[Akonadi] [Bug 409641] Akonadi Server crashs upon start of Kontact

2019-07-09 Thread Robby Engelmann

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

--- Comment #2 from Robby Engelmann  ---
Created attachment 121411
  --> https://bugs.kde.org/attachment.cgi?id=121411=edit
akonadictl fchk result

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

[Akonadi] [Bug 409641] Akonadi Server crashs upon start of Kontact

2019-07-09 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #1 from Robby Engelmann  ---
Created attachment 121410
  --> https://bugs.kde.org/attachment.cgi?id=121410=edit
Backtrace

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

[Akonadi] [Bug 409641] New: Akonadi Server crashs upon start of Kontact

2019-07-09 Thread Robby Engelmann

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

Bug ID: 409641
   Summary: Akonadi Server crashs upon start of Kontact
   Product: Akonadi
   Version: 5.11.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Start System and Kontact
2. 
3. 

OBSERVED RESULT
crash

EXPECTED RESULT
no crash

see attachments

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

[kontact] [Bug 409410] New: Kontact crashed directly upon start

2019-07-02 Thread Robby Engelmann

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

Bug ID: 409410
   Summary: Kontact crashed directly upon start
   Product: kontact
   Version: 5.11.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Application: kontact (5.11.2)

Qt Version: 5.13.0
Frameworks Version: 5.59.0
Operating System: Linux 5.1.10-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I delete a multitude (>3000) of spam mails, then Kontact crashed already. Then
I did an akonadictl fchk and vacuum. Then I started Kontact again and
voila...crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6a4551ca40 (LWP 3038))]

Thread 26 (Thread 0x7f6921beb700 (LWP 18868)):
#0  0x7f6a553f97ec in read () from /lib64/libc.so.6
#1  0x7f6a539cc3bf in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6a5398585e in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6a53985cd2 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f6a53985e4f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f6a559b6ceb in QEventDispatcherGlib::processEvents
(this=0x7f695c0097f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f6a5595f2eb in QEventLoop::exec (this=this@entry=0x7f6921beab60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f6a55797f91 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f6a55799112 in QThreadPrivate::start (arg=0x560fee232900) at
thread/qthread_unix.cpp:360
#9  0x7f6a543fffaa in start_thread () from /lib64/libpthread.so.0
#10 0x7f6a5540871f in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f692b7fe700 (LWP 18867)):
#0  0x7f6a5440616c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6a4d8bf646 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f6a4d8c0013 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f6a4d8c0191 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f6a4d878451 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f6a4d87b2ed in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f6a4d87b9e4 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f6a4d8c2485 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f6a543fffaa in start_thread () from /lib64/libpthread.so.0
#9  0x7f6a5540871f in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f6923fff700 (LWP 18856)):
#0  0x7f6a5440616c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6a4d8bf646 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f6a4d8c0013 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f6a4d8c0191 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f6a4d878451 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f6a4d87b63b in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331
#6  0x7f6a4d87b9e4 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f6a4d8c2485 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f6a543fffaa in start_thread () from /lib64/libpthread.so.0
#9  0x7f6a5540871f in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7f695b7fe700 (LWP 18847)):
#0  0x7f6a5440616c in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6a4d8bf646 in base::ConditionVariable::TimedWait () at

[Akonadi] [Bug 409110] Akonadi Server crash after some time of having Kontact running

2019-06-24 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelmann@r-engelmann
   ||.de
Version|unspecified |5.11.2

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

[Akonadi] [Bug 409110] New: Akonadi Server crash after some time of having Kontact running

2019-06-24 Thread Robby Engelmann

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

Bug ID: 409110
   Summary: Akonadi Server crash after some time of having Kontact
running
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

Created attachment 121108
  --> https://bugs.kde.org/attachment.cgi?id=121108=edit
crash information from Drkonqi

SUMMARY
Akonadi Server crash after some time of having Kontact running. I do not
observe any special events going on, when it happens. Also akonadictl fschk /
vacuum does not solve it (worked often in the past to solve such crashes for
me).

STEPS TO REPRODUCE
1. Start Kontact
2. Have E-mail coming in from time to time
3. see the crash

OBSERVED RESULT
crash

EXPECTED RESULT
no crash

All crash information attached...

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

[kontact] [Bug 403359] Kontact crashes when closing email window

2019-03-25 Thread Robby Engelmann

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

--- Comment #1 from Robby Engelmann  ---
Created attachment 119018
  --> https://bugs.kde.org/attachment.cgi?id=119018=edit
New crash information added by DrKonqi

kontact (5.10.3) using Qt 5.12.2

- What I was doing when the application crashed:
Kontakt crashed when closing an Email that was viewed

-- Backtrace (Reduced):
#6  std::_Rb_tree > >,
std::_Select1st > > >, std::less, std::allocator > > > >::_M_lower_bound () at
/usr/include/c++/8/bits/stl_tree.h:1904
#7  std::_Rb_tree > >,
std::_Select1st > > >, std::less, std::allocator > > > >::find () at
/usr/include/c++/8/bits/stl_tree.h:2552
#8  std::map >, std::less,
std::allocator > > > >::find () at
/usr/include/c++/8/bits/stl_map.h:1194
#9  base::SupportsUserData::GetUserData () at
./../../3rdparty/chromium/base/supports_user_data.cc:19
#10 0x7f81df8fd6a0 in
content::BrowserContext::GetServiceManagerConnectionFor () at
../../3rdparty/chromium/content/browser/browser_context.cc:634

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

[kontact] [Bug 403359] Kontact crashes when closing email window

2019-03-25 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

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

[kontact] [Bug 403309] New: akregator crash when switching to it in Kontact

2019-01-17 Thread Robby Engelmann

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

Bug ID: 403309
   Summary: akregator crash when switching to it in Kontact
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.10.1)

Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.20.0-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
akregator crash when switching to it in Kontact. Happened first time here.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0ed640a0c0 (LWP 3391))]

Thread 30 (Thread 0x7f0daa7db700 (LWP 24626)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f0daafdc700 (LWP 24625)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f0dbd70b700 (LWP 24624)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f0dbdf0c700 (LWP 24623)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f0dbe70d700 (LWP 24622)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f0ebcff9700 (LWP 24621)):

[kontact] [Bug 401419] Kmail crashes on trying to open any email

2018-12-14 Thread Robby Engelmann

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

--- Comment #3 from Robby Engelmann  ---
The bug is still valid for me in the final release. I released though, that
when I activate the mail preview pane in kmail settings, I can again open mails
by double-click. Having previews deactivated again the crashes are back.

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

[kontact] [Bug 401419] Kmail crashes on trying to open any email

2018-12-14 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

Summary|[18.12 beta + RC]Kontact|Kmail crashes on trying to
   |crashed on trying to open   |open any email
   |an unread email |

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

[kontact] [Bug 401419] [18.12 beta + RC]Kontact crashed on trying to open an unread email

2018-12-06 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

Version|unspecified |GIT (master)
Summary|Kontact crashed on trying   |[18.12 beta + RC]Kontact
   |to open an unread email |crashed on trying to open
   ||an unread email

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

[kontact] [Bug 401419] Kontact crashed on trying to open an unread email

2018-12-04 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

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

[kontact] [Bug 401419] Kontact crashed on trying to open an unread email

2018-12-04 Thread Robby Engelmann

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

--- Comment #2 from Robby Engelmann  ---
Created attachment 116683
  --> https://bugs.kde.org/attachment.cgi?id=116683=edit
New crash information added by DrKonqi

kmail (5.9.90 rc) using Qt 5.11.2

- What I was doing when the application crashed:
Opening an Mail in Kontacts Kmail or Kmail. 
In konsole I get: "[warn] epoll_wait: Bad file descriptor" if that helps

This bug is still appearing in KDE Apps 18.12 RC

-- Backtrace (Reduced):
#6  KMReaderWin::viewer (this=0x0) at
/usr/src/debug/kmail-18.11.90-86.1.x86_64/src/kmreaderwin.cpp:219
#7  0x7fa8527af72e in KMMainWidget::slotItemsFetchedForActivation
(this=0x55fee29c97d0, command=) at
/usr/src/debug/kmail-18.11.90-86.1.x86_64/src/kmmainwidget.cpp:2589
#8  0x7fa8517961d0 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc48e5220,
r=0x55fee29c97d0, this=0x55fee3a87c40) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376
[...]
#10 0x7fa8528b0182 in KMCommand::completed (this=this@entry=0x55fee3a50660,
_t1=, _t1@entry=0x55fee3a50660) at
/usr/src/debug/kmail-18.11.90-86.1.x86_64/build/src/kmailprivate_autogen/EWIEGA46WW/moc_kmcommands.cpp:196
#11 0x7fa8527967f3 in KMCommand::slotPostTransfer (this=0x55fee3a50660,
result=KMCommand::OK) at
/usr/src/debug/kmail-18.11.90-86.1.x86_64/src/kmcommands.cpp:289

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

[kontact] [Bug 401419] New: Kontact crashed on trying to open an unread email

2018-11-26 Thread Robby Engelmann

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

Bug ID: 401419
   Summary: Kontact crashed on trying to open an unread email
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.9.80 beta)

Qt Version: 5.11.2
Frameworks Version: 5.52.0
Operating System: Linux 4.19.2-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: Kontact crashed on trying to
open an unread email. Not yet sure, whether this happens for every mail.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd75d34fa40 (LWP 14644))]

Thread 38 (Thread 0x7fd62e95d700 (LWP 14765)):
#0  0x7fd770a98d34 in read () from /lib64/libc.so.6
#1  0x7fd76e509a00 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd76e4c3a4b in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd76e4c3ef0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fd76e4c406c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7fd7711c2adb in QEventDispatcherGlib::processEvents
(this=0x7fd6e4005070, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7fd77116fadb in QEventLoop::exec (this=this@entry=0x7fd62e95cb60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7fd770fbede6 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7fd770fc89b7 in QThreadPrivate::start (arg=0x55a220a8b1f0) at
thread/qthread_unix.cpp:367
#9  0x7fd76f6f9554 in start_thread () from /lib64/libpthread.so.0
#10 0x7fd770aa7ccf in clone () from /lib64/libc.so.6

Thread 37 (Thread 0x7fd635884700 (LWP 14745)):
#0  0x7fd76f6ff8c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd768941d37 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fd768943a0a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fd768943af2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fd7689488b1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fd768949d91 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fd7689541c1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fd76f6f9554 in start_thread () from /lib64/libpthread.so.0
#8  0x7fd770aa7ccf in clone () from /lib64/libc.so.6

Thread 36 (Thread 0x7fd636085700 (LWP 14744)):
#0  0x7fd76f6ff8c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd768941d37 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fd768943a0a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fd768943af2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fd7689488b1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fd768949baf in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fd7689541c1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fd76f6f9554 in start_thread () from /lib64/libpthread.so.0
#8  0x7fd770aa7ccf in clone () from /lib64/libc.so.6

Thread 35 (Thread 0x7fd636886700 (LWP 14743)):
#0  0x7fd76f6ff8c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd768941d37 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fd768943a0a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fd768943af2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fd7689488b1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fd768949d91 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fd7689541c1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fd76f6f9554 in start_thread () from /lib64/libpthread.so.0
#8  0x7fd770aa7ccf in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7fd6377fe700 (LWP 14723)):
#0  0x7fd76e4c349d in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7fd76e4c3e7b in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd76e4c406c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd7711c2adb in QEventDispatcherGlib::processEvents
(this=0x7fd644001ee0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fd77116fadb in QEventLoop::exec (this=this@entry=0x7fd6377fdb60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fd770fbede6 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fd770fc89b7 in QThreadPrivate::start

[kmail2] [Bug 397225] New: newly generated gpg key not shown in kmail

2018-08-06 Thread Robby Engelmann

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

Bug ID: 397225
   Summary: newly generated gpg key not shown in kmail
   Product: kmail2
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

I generated a new key in kleopatra, but in kmail it is not shown, when I want
to set it to an identity. However, generating a new key (only with kind of
standard settings) directly in kmail works. The key is also shown in kleopatra
with no obviously different properties (expect for no expiration and only
2024bit instead of 4048bit).

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

[kaddressbook] [Bug 396685] Edit Location not possible with dark theme

2018-07-20 Thread Robby Engelmann

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

Robby Engelmann  changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

--- Comment #1 from Robby Engelmann  ---
Created attachment 114023
  --> https://bugs.kde.org/attachment.cgi?id=114023=edit
the problem

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

[kaddressbook] [Bug 396685] New: Edit Location not possible with dark theme

2018-07-20 Thread Robby Engelmann

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

Bug ID: 396685
   Summary: Edit Location not possible with dark theme
   Product: kaddressbook
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
CC: to...@kde.org
  Target Milestone: ---

It is currently not possible to edit edit an existing location because text and
symbols seem to white on white background.

Reproduce:
-switch to breeze dark theme
-open a contact with an existing address
-switch to the Location tab
-you will recognize the issue

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

[kontact] [Bug 393796] New: pulseaudio shows constant 18% cpu when kontact is running

2018-05-03 Thread Robby Engelmann

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

Bug ID: 393796
   Summary: pulseaudio shows constant 18% cpu when kontact is
running
   Product: kontact
   Version: 5.8.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

My first guess for that would be the text-to-speech module?

1. Start Kontact --> see pulseaudio draw cpu power
2. Close Kontact --> see pulseaudio cpu dropping after 2-5 sec.

Can anybody confirm that?

I am using a Tuxedo Infinity Book.

See also https://bugzilla.suse.com/show_bug.cgi?id=1091752.

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

[kontact] [Bug 385855] New: Kontact crashed upon reply to an email

2017-10-17 Thread Robby Engelmann

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

Bug ID: 385855
   Summary: Kontact crashed upon reply to an email
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.6.1)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.5-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was just right-clicked an email and selected reply -> reply...

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f35bda70900 (LWP 3397))]

Thread 28 (Thread 0x7f3581632700 (LWP 10175)):
#0  0x7f35b63f7b5c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f35ab299782 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f35ab26f999 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f35ab26fefb in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f35ab2687db in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f35b63f1558 in start_thread () at /lib64/libpthread.so.0
#6  0x7f35ba45845f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f3580e31700 (LWP 5845)):
#0  0x7f35b43d2b0e in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f35b43d30f0 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f35b43d325c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f35baf8d69b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f35baf3634a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f35bad6631a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f35bad6ad2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f35b63f1558 in start_thread () at /lib64/libpthread.so.0
#8  0x7f35ba45845f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f34631d8700 (LWP 4493)):
#0  0x7f35b63f782d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f35ab26ae95 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f35ab26b377 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f35ab26c111 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f35ab2687db in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f35b63f1558 in start_thread () at /lib64/libpthread.so.0
#6  0x7f35ba45845f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f3472904700 (LWP 4473)):
#0  0x7f35ba44dcab in poll () at /lib64/libc.so.6
#1  0x7f35b43d3149 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f35b43d325c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f35baf8d69b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f35baf3634a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f35bad6631a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f35bad6ad2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f35b63f1558 in start_thread () at /lib64/libpthread.so.0
#8  0x7f35ba45845f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f3479f03700 (LWP 3441)):
#0  0x7f35baf8d070 in QElapsedTimer::clockType() () at
/usr/lib64/libQt5Core.so.5
#1  0x7f35baf8d089 in QElapsedTimer::isMonotonic() () at
/usr/lib64/libQt5Core.so.5
#2  0x7f35baf8beae in QTimerInfoList::repairTimersIfNeeded() () at
/usr/lib64/libQt5Core.so.5
#3  0x7f35baf8bf13 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f35baf8d44e in timerSourcePrepare(_GSource*, int*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f35b43d2688 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f35b43d307b in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7f35b43d325c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#8  0x7f35baf8d69b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#9  0x7f35baf3634a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#10 0x7f35bad6631a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#11 0x7f35bad6ad2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#12 0x7f35b63f1558 in start_thread () at /lib64/libpthread.so.0
#13 0x7f35ba45845f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f3488b43700 (LWP 3430)):
#0  0x7f35b4418714 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f35b43d3266 in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2

[akregator] [Bug 378513] kontact or akregator crash after close/restart

2017-09-11 Thread Robby Engelmann

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

--- Comment #28 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
I think it should be reopened, see last crash report...

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

[akregator] [Bug 378513] kontact or akregator crash after close/restart

2017-09-11 Thread Robby Engelmann

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

--- Comment #27 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
Created attachment 107806
  --> https://bugs.kde.org/attachment.cgi?id=107806=edit
New crash information added by DrKonqi

akregator (5.6.1) using Qt 5.9.1

- What I was doing when the application crashed:

Starting Akregator; this patch:
https://commits.kde.org/akregator/d0a5f4159cddcca656ca8bbcbd6e551e3499c166
should be integrated already. Either the patch did not cure the bug or this is
distinct case?

-- Backtrace (Reduced):
#8  0x7f3d9c420f4c in qobject_cast<Akregator::WebEngineFrame*>
(object=0x5610d6dcf050) at /usr/include/qt5/QtCore/qobject.h:514
#9  Akregator::FrameManager::saveProperties (this=0x5610d6e9a860, config=...)
at /usr/src/debug/akregator-17.08.1/src/frame/framemanager.cpp:278
#10 0x7f3d6a0dd973 in Akregator::MainWidget::saveProperties
(this=0x5610d6f6a490, config=...) at
/usr/src/debug/akregator-17.08.1/src/mainwidget.cpp:1227
#11 0x7f3d6a0d63ac in Akregator::Part::saveCrashProperties
(this=0x5610d6f8ca80) at
/usr/src/debug/akregator-17.08.1/src/akregator_part.cpp:777
#12 0x7f3d6a0d6425 in Akregator::Part::slotAutoSave (this=)
at /usr/src/debug/akregator-17.08.1/src/akregator_part.cpp:782

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

[akregator] [Bug 378513] kontact or akregator crash after close/restart

2017-07-05 Thread Robby Engelmann

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

--- Comment #20 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
Systemsettings --> Application Style --> Widget Style --> Fine Tuning --> Set
"Menubar Style" to "Title Bar Button"

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

[akregator] [Bug 381416] Crash on kontact launch

2017-07-05 Thread Robby Engelmann

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

--- Comment #2 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
Created attachment 106445
  --> https://bugs.kde.org/attachment.cgi?id=106445=edit
New crash information added by DrKonqi

kontact (5.5.2) using Qt 5.9.0

- What I was doing when the application crashed:
The same here. Qt 5.9, Frameworks 5.34, Apps 17.04.2 and also trouble with
akregator feeds

-- Backtrace (Reduced):
#6  0x7fd04134b7b4 in Akregator::MainWidget::setFeedList (this=0x0,
list=...) at /usr/src/debug/akregator-17.04.2/src/mainwidget.cpp:459
#7  0x7fd04133c4e6 in Akregator::Part::feedListLoaded (this=0x5592871362c0,
list=...) at /usr/src/debug/akregator-17.04.2/src/akregator_part.cpp:507
[...]
#9  0x7fd041316d69 in Akregator::LoadFeedListCommand::result (_t1=...,
this=) at
/usr/src/debug/akregator-17.04.2/build/src/akregatorpart_autogen/include/moc_loadfeedlistcommand.cpp:140
#10 Akregator::LoadFeedListCommand::Private::emitResult
(this=this@entry=0x55928734e870, list=...) at
/usr/src/debug/akregator-17.04.2/src/command/loadfeedlistcommand.cpp:64
#11 0x7fd04131720d in
Akregator::LoadFeedListCommand::Private::handleDocument
(this=this@entry=0x55928734e870, doc=...) at
/usr/src/debug/akregator-17.04.2/src/command/loadfeedlistcommand.cpp:88

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

[akregator] [Bug 381416] Crash on kontact launch

2017-07-05 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

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

[akregator] [Bug 378513] kontact or akregator crash after close/restart

2017-07-05 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

--- Comment #18 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
I can confirm that for openSUSE Tumbleweed and latest Qt, Frameworks, Plasma,
Apps...
"Title bar button Menubar style, as soon as I switched from Title bar button to
In application Akregator stopped crashing"

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

[akregator] [Bug 381683] Akregator crash when starting

2017-06-28 Thread Robby Engelmann

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

--- Comment #1 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
Created attachment 106351
  --> https://bugs.kde.org/attachment.cgi?id=106351=edit
New crash information added by DrKonqi

akregator (5.5.2) using Qt 5.9.0

- What I was doing when the application crashed:
Starting akregator as standalone results in a crash. Starting Kontact and
switching over to akregator is not crashing it, but some tabs that should be
open are not shown and sometimes new tabs are not opened (or opened in
background and thus not visible).

-- Backtrace (Reduced):
#8  0x7ff1d8bfbf4c in qobject_cast<Akregator::WebEngineFrame*>
(object=0x5583b2560dc0) at /usr/include/qt5/QtCore/qobject.h:514
#9  Akregator::FrameManager::saveProperties (this=0x5583b25a3fc0, config=...)
at /usr/src/debug/akregator-17.04.2/src/frame/framemanager.cpp:281
#10 0x7ff1a319ad93 in Akregator::MainWidget::saveProperties
(this=0x5583b2524f90, config=...) at
/usr/src/debug/akregator-17.04.2/src/mainwidget.cpp:1237
#11 0x7ff1a319336c in Akregator::Part::saveCrashProperties
(this=0x5583b2613540) at
/usr/src/debug/akregator-17.04.2/src/akregator_part.cpp:807
#12 0x7ff1a31933e5 in Akregator::Part::slotAutoSave (this=)
at /usr/src/debug/akregator-17.04.2/src/akregator_part.cpp:812

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

[akregator] [Bug 381683] Akregator crash when starting

2017-06-28 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

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

[kontact] [Bug 379623] New: Kontact crashed after trying to open a link with middle-mouse click out of an email in Kmail

2017-05-08 Thread Robby Engelmann

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

Bug ID: 379623
   Summary: Kontact crashed after trying to open a link with
middle-mouse click out of an email in Kmail
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.4.80 beta1)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.10.13-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Kontact crashed after trying to open a link with middle-mouse click out of an
email in Kmail

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0a5ae0b8c0 (LWP 2774))]

Thread 31 (Thread 0x7f0a25ffb700 (LWP 4869)):
#0  0x7f0a53771db3 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0a4a8d9052 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0a4a8e7eb0 in base::PosixDynamicThreadPool::WaitForTask() () from
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0a4a8e83e3 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0a4a8e199c in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0a5376b537 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0a5784804f in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f09195cc700 (LWP 4862)):
#0  0x7f0a53771db3 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0a4a8d9052 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0a4a8e7eb0 in base::PosixDynamicThreadPool::WaitForTask() () from
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0a4a8e83e3 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0a4a8e199c in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0a5376b537 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0a5784804f in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f0a267fc700 (LWP 4560)):
#0  0x7f0a515642c4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f0a5151ea4a in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f0a5151ebac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f0a583791bb in QEventDispatcherGlib::processEvents
(this=0x7f0a0c02a7f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0a58322b1a in QEventLoop::exec (this=this@entry=0x7f0a267fbcf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f0a58150813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f0a581554c8 in QThreadPrivate::start (arg=0x14ea080) at
thread/qthread_unix.cpp:368
#7  0x7f0a5376b537 in start_thread () from /lib64/libpthread.so.0
#8  0x7f0a5784804f in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f08fdbd0700 (LWP 2908)):
#0  0x7f0a58154351 in get_thread_data () at thread/qthread_unix.cpp:189
#1  QThreadData::current (createIfNecessary=112, createIfNecessary@entry=true)
at thread/qthread_unix.cpp:244
#2  0x7f0a5837890a in postEventSourcePrepare (s=0x7f08f40012d0,
timeout=0x7f08fdbcfb24) at kernel/qeventdispatcher_glib.cpp:252
#3  0x7f0a5151df8d in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f0a5151e9bb in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f0a5151ebac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f0a583791bb in QEventDispatcherGlib::processEvents
(this=0x7f08f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f0a58322b1a in QEventLoop::exec (this=this@entry=0x7f08fdbcfcf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7f0a58150813 in QThread::exec (this=) at
thread/qthread.cpp:507
#9  0x7f0a581554c8 in QThreadPrivate::start (arg=0x4d6da00) at
thread/qthread_unix.cpp:368
#10 0x7f0a5376b537 in start_thread () from /lib64/libpthread.so.0
#11 0x7f0a5784804f in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f090a5b2700 (LWP 2891)):
#0  0x7f0a5783e7bd in poll () from /lib64/libc.so.6
#1  0x7f0a5151ea96 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f0a5151ebac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f0a583791bb in QEventDispatcherGlib::processEvents
(this=0x7f08f80008c0,

[kontact] [Bug 367791] Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze

2017-05-02 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

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

[akregator] [Bug 351547] Akregator5 crashes with websites opened

2017-05-02 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

2017-03-20 Thread Robby Engelmann

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

--- Comment #37 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
Hi,
I also updated to 16.12.3 and it still has some issues with the filter agents
as described in the previous post.
I figured out now, that filtering spams with bogofilter or spamassassin does
work now, not sure whether that is new. However, adding additional filters,
e.g. move all incoming mails which contain a specific string to another
subfolder still leads to the problems described: doubling of mails, not able to
delete mails.

I also use pop. Not sure whether that also applies to imap.

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

[kontact] [Bug 375577] Kontact crashed after opening a contact

2017-02-01 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

--- Comment #2 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
Done: https://bugreports.qt.io/browse/QTBUG-58565

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

[kmail2] [Bug 375149] Kmail deletes emails from folder after switching to folder

2017-01-28 Thread Robby Engelmann

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

--- Comment #5 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
This morning I saw the very same issue using latest openSUSE Tumbleweed. The
hint, that mails were moved rather than delete was quite helpful.
Here, it were also inbox folders from different accounts. That sounds to me,
that Mail Filter Agent got crazy. I have one Filter set-up here, which moved
mails of a mailing list to a subfolder. And I did find the missing mails within
that mailing list folder.

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

[kontact] [Bug 375577] New: Kontact crashed after opening a contact

2017-01-26 Thread Robby Engelmann

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

Bug ID: 375577
   Summary: Kontact crashed after opening a contact
   Product: kontact
   Version: 5.4.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.4.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
1. open kontact
2. switch to kaddressbook
3. open a contact in order to modify
4. see Kontact crashing

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Illegal instruction
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4dc1338440 (LWP 2658))]

Thread 36 (Thread 0x7f4c123bc700 (LWP 7717)):
#0  0x7f4db7a37e74 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4db79f287a in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4db79f299c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4dbe89818b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4d60001d10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f4dbe841aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4c123bbc80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f4dbe66f813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f4dbe6744c8 in QThreadPrivate::start(void*) (arg=0x77c7240) at
thread/qthread_unix.cpp:368
#7  0x7f4db9c03454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4dbdd6a37f in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f4c210d1700 (LWP 7338)):
#0  0x7f4db79f1c21 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f4db79f27ab in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4db79f299c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4dbe89818b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4d44001980, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f4dbe841aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4c210d0c80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f4dbe66f813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f4dbe6744c8 in QThreadPrivate::start(void*) (arg=0x6b45dd0) at
thread/qthread_unix.cpp:368
#7  0x7f4db9c03454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4dbdd6a37f in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7f4c135fe700 (LWP 7302)):
#0  0x7f4db9c094b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4db0d96b22 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f4db0da5980 in base::PosixDynamicThreadPool::WaitForTask() () at
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f4db0da5eb3 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f4db0d9f46c in base::(anonymous namespace)::ThreadFunc(void*) () at
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f4db9c03454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4dbdd6a37f in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f4d8d982700 (LWP 7301)):
#0  0x7f4db9c094b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4db0d96b22 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f4db0da5980 in base::PosixDynamicThreadPool::WaitForTask() () at
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f4db0da5eb3 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f4db0d9f46c in base::(anonymous namespace)::ThreadFunc(void*) () at
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f4db9c03454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4dbdd6a37f in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f4c12bbd700 (LWP 5493)):
#0  0x7f4dbdcb7690 in getenv () at /lib64/libc.so.6
#1  0x7f4dbdcb0044 in __dcigettext () at /lib64/libc.so.6
#2  0x7f4dbdd027ec in strerror_r () at /lib64/libc.so.6
#3  0x7f4dbdd0271f in strerror () at /lib64/libc.so.6
#4  0x7f4da9066751 in event_warn () at /usr/lib64/libevent-2.0.so.5
#5  0x7f4da906aee8 in  () at /usr/lib64/libevent-2.0.so.5
#6  0x7f4da9054e8a in event_base_loop () at /usr/lib64/libevent-2.0.so.5
#7  0x7f4db0d4fece in
base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at
/usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f4db0d8adba in base::RunLoop::Run() () at
/usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f4db0d75855

[Akonadi] [Bug 375450] New: akonadiserver crashes on system shudown

2017-01-23 Thread Robby Engelmann

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

Bug ID: 375450
   Summary: akonadiserver crashes on system shudown
   Product: Akonadi
   Version: 5.4.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

akonadiserver crashes on almost every system shutdown using openSUSE
Tumbleweed:

gdb) bt
#0  0x7f8bac7115af in raise () from /lib64/libc.so.6
#1  0x7f8bae3f6b84 in KCrash::defaultCrashHandler(int) () from
/usr/lib64/libKF5Crash.so.5
#2  
#3  QScopedPointer::data
(this=0x8)
at ../../src/corelib/tools/qscopedpointer.h:141
#4  qGetPtrHelper (p=...) at
../../src/corelib/global/qglobal.h:980
#5  QIODevice::d_func (this=0x0) at ../../src/corelib/io/qiodevice.h:178
#6  QIODevice::write (this=0x0, data=0x7f8b52ffc3ec "\227", maxSize=1) at
io/qiodevice.cpp:1596
#7  0x7f8bae1afbc0 in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5
#8  0x7f8bae1b332f in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5
#9  0x7f8bae19a9b4 in Akonadi::Protocol::serialize(QIODevice*,
Akonadi::Protocol::Command const&) ()
   from /usr/lib64/libKF5AkonadiPrivate.so.5
#10 0x0042c9b3 in Akonadi::Server::Connection::sendResponse
(this=0x211c1e0, tag=10, response=...)
at /usr/src/debug/akonadi-16.12.1/src/server/connection.cpp:404
#11 0x00430e42 in Akonadi::Server::Handler::sendResponse (response=...,
this=0x7f8b48052fb0)
at /usr/src/debug/akonadi-16.12.1/src/server/handler.cpp:268
#12 Akonadi::Server::Handler::sendResponse
(this=0x7f8b48052fb0, response=...)
at /usr/src/debug/akonadi-16.12.1/src/server/handler.h:152
#13 Akonadi::Server::Handler::failureResponse (this=this@entry=0x7f8b48052fb0,
failureMessage=...)
at /usr/src/debug/akonadi-16.12.1/src/server/handler.cpp:261
#14 0x00430fff in Akonadi::Server::Handler::failureResponse
(this=0x7f8b48052fb0, failureMessage=)
at /usr/src/debug/akonadi-16.12.1/src/server/handler.cpp:252
#15 0x0042eb8d in Akonadi::Server::Connection::slotNewData
(this=0x211c1e0)
at /usr/src/debug/akonadi-16.12.1/src/server/connection.cpp:252
#16 0x7f8bad2cba7e in QtPrivate::QSlotObjectBase::call (a=0x7f8b52ffc8d0,
r=0x211c1e0, this=)
at ../../src/corelib/kernel/qobject_impl.h:101
#17 QMetaObject::activate (sender=0x7f8b48002cd0, signalOffset=,
local_signal_index=,
argv=) at kernel/qobject.cpp:3723
#18 0x7f8bad2cb709 in QMetaObject::activate (sender=0x7f8b48002dc8,
signalOffset=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3740
#19 0x7f8baded6265 in ?? () from /usr/lib64/libQt5Network.so.5
---Type  to continue, or q  to quit---
#20 0x7f8baded631c in ?? () from /usr/lib64/libQt5Network.so.5
#21 0x7f8badee1121 in ?? () from /usr/lib64/libQt5Network.so.5
#22 0x7f8bad29faeb in doNotify (event=0x7f8b52ffcae0,
receiver=0x7f8b48003060) at kernel/qcoreapplication.cpp:1063
#23 QCoreApplication::notify (event=, receiver=,
this=)
at kernel/qcoreapplication.cpp:1049
#24 QCoreApplication::notifyInternal2 (receiver=0x7f8b48003060,
event=event@entry=0x7f8b52ffcae0)
at kernel/qcoreapplication.cpp:988
#25 0x7f8bad2f461d in QCoreApplication::sendEvent (event=0x7f8b52ffcae0,
receiver=)
at ../../src/corelib/kernel/qcoreapplication.h:231
#26 socketNotifierSourceDispatch (source=0x7f8b48002a00) at
kernel/qeventdispatcher_glib.cpp:106
#27 0x7f8ba9445687 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#28 0x7f8ba94458f0 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x7f8ba944599c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#30 0x7f8bad2f416f in QEventDispatcherGlib::processEvents
(this=0x7f8b480008c0, flags=...)
at kernel/qeventdispatcher_glib.cpp:423
#31 0x7f8bad29daea in QEventLoop::exec (this=this@entry=0x7f8b52ffcd00,
flags=..., flags@entry=...)
at kernel/qeventloop.cpp:212
#32 0x7f8bad0cb813 in QThread::exec (this=) at
thread/qthread.cpp:507
#33 0x7f8bad0d04c8 in QThreadPrivate::start (arg=0x21138c0) at
thread/qthread_unix.cpp:368
#34 0x7f8bab35d454 in start_thread () from /lib64/libpthread.so.0
#35 0x7f8bac7c637f in clone () from /lib64/libc.so.6

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

[kontact] [Bug 372345] New: Kontact crashed after opening a contact from addressbook

2016-11-11 Thread Robby Engelmann

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

Bug ID: 372345
   Summary: Kontact crashed after opening a contact from
addressbook
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Kontact crashed immediately after opening a contact in order to edit it. Did
not find a reproducible way to trigger that bug. Restarting and opening the
contact worked.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa107deae00 (LWP 2593))]

Thread 58 (Thread 0x7f9f567e3700 (LWP 18153)):
#0  0x7fa10480c68d in poll () at /lib64/libc.so.6
#1  0x7fa0fe4d2876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa0fe4d298c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa10534279b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa1052ec1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa10511a8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa10511f558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fa1006be454 in start_thread () at /lib64/libpthread.so.0
#8  0x7fa10481539f in clone () at /lib64/libc.so.6

Thread 57 (Thread 0x7f9f56fe4700 (LWP 18147)):
#0  0x7fa1048086fd in read () at /lib64/libc.so.6
#1  0x7fa0fe516b00 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa0fe4d2325 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa0fe4d2814 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa0fe4d298c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fa10534279b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fa1052ec1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fa10511a8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fa10511f558 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fa1006be454 in start_thread () at /lib64/libpthread.so.0
#10 0x7fa10481539f in clone () at /lib64/libc.so.6

Thread 56 (Thread 0x7f9f577e5700 (LWP 18129)):
#0  0x7ffe97d47a98 in clock_gettime ()
#1  0x7fa104822246 in clock_gettime () at /lib64/libc.so.6
#2  0x7fa1051c46e1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fa105340419 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fa1053409c5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa105341d6e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fa0fe4d1d79 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fa0fe4d279b in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fa0fe4d298c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fa10534279b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fa1052ec1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fa10511a8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fa10511f558 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fa1006be454 in start_thread () at /lib64/libpthread.so.0
#14 0x7fa10481539f in clone () at /lib64/libc.so.6

Thread 55 (Thread 0x7f9f57fe6700 (LWP 18127)):
#0  0x7fa104821bbf in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7fa10480c682 in poll () at /lib64/libc.so.6
#2  0x7fa0fe4d2876 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fa0fe4d298c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fa10534279b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fa1052ec1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fa10511a8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fa10511f558 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fa1006be454 in start_thread () at /lib64/libpthread.so.0
#9  0x7fa10481539f in clone () at /lib64/libc.so.6

Thread 54 (Thread 0x7fa0c77fe700 (LWP 18125)):
#0  0x7fa105116aa9 in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5
#1  0x7fa105342085 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7fa0fe4d2269 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa0fe4d2814 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa0fe4d298c in

[kontact] [Bug 367791] Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze

2016-10-10 Thread Robby Engelmann via KDE Bugzilla

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

  Component|Icons   |general
Product|Breeze  |kontact
Version|5.8.0   |5.3.1

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

[Breeze] [Bug 367791] Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze

2016-10-10 Thread Robby Engelmann via KDE Bugzilla

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

--- Comment #5 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
it still sometimes appear using frameworks 5.27, qt 5.7 under plasma 5.8

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

[Breeze] [Bug 367791] Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze

2016-10-10 Thread Robby Engelmann via KDE Bugzilla

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

Robby Engelmann <robby.engelm...@igfs-ev.de> changed:

   What|Removed |Added

Version|GIT (master)|5.8.0
  Component|mail|Icons
Product|kontact |Breeze
 CC||kain...@gmail.com

--- Comment #4 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
possibly a frameworks bug?

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

[kontact] [Bug 370111] New: Kontact crashed on checking mails

2016-10-05 Thread Robby Engelmann via KDE Bugzilla

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

Bug ID: 370111
   Summary: Kontact crashed on checking mails
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.7.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: Kontact crashed after I
started, switched to kmail and checking all accounts

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f30d50e2e00 (LWP 2910))]

Thread 38 (Thread 0x7f2f7cde4700 (LWP 3052)):
#0  0x7f30d1b046ed in poll () at /lib64/libc.so.6
#1  0x7f30cb7ca876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f30cb7ca98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f30d263a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f30d25e41ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f30d24128b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f30d2417558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f30cd9b4454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f30d1b0d3ff in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f2f7dff5700 (LWP 2995)):
#0  0x7f30cd9ba10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f30c4b60659 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f30c4b60c79 in base::SequencedWorkerPool::Worker::Run() () at
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f30c4b60e30 in base::SimpleThread::ThreadMain() () at
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f30c4b5dab7 in base::(anonymous namespace)::ThreadFunc(void*) () at
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f30cd9b4454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f30d1b0d3ff in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7f2f86ffd700 (LWP 2966)):
#0  0x7f30d1b046ed in poll () at /lib64/libc.so.6
#1  0x7f30cb7ca876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f30cb7ca98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f30d263a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f30d25e41ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f30d24128b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f30d2417558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f30cd9b4454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f30d1b0d3ff in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f2f877fe700 (LWP 2964)):
#0  0x7f30d1b046ed in poll () at /lib64/libc.so.6
#1  0x7f30cb7ca876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f30cb7ca98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f30d263a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f30d25e41ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f30d24128b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f30d2417558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f30cd9b4454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f30d1b0d3ff in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7f2f87fff700 (LWP 2962)):
#0  0x7f30cb7c9fa0 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f30cb7ca7e8 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f30cb7ca98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f30d263a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f30d25e41ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f30d24128b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f30d2417558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f30cd9b4454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f30d1b0d3ff in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f2f94d90700 (LWP 2960)):
#0  0x7f30cb7c78bf in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f30cb7c9d1b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f30cb7ca79b in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f30cb7ca98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f30d263a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5

[kontact] [Bug 367791] Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze

2016-09-13 Thread Robby Engelmann via KDE Bugzilla

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

--- Comment #3 from Robby Engelmann <robby.engelm...@igfs-ev.de> ---
I played a little bit around and found the following:
-removing cache did not help
-deinstalling oxygen5-icons results in no icons shown which means for some
reason the fallback theme is used
-I only see it in PIM Apps, no other KDE apps.
-it is not only the folder-icons but sometime also some toolbar icons

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

1 2 >

1 - 100 of 163 matches

Mail list logo