[kwin] [Bug 15329] Save and remember positions of all windows

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

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

[plasmashell] [Bug 492931] Plasma crashes on or shortly after resuming from suspend-to-ram

[Erik Quaeghebeur]

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

--- Comment #3 from Erik Quaeghebeur  ---
(In reply to cwo from comment #1) 
> Given that the crash seems to be related to themes, are you using a custom
> theme or a default breeze one?
Breeze.

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

[Akonadi] [Bug 492817] Akonadi EWS resource nonreliability and crash after authentication issues

[Erik Quaeghebeur]

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

--- Comment #1 from Erik Quaeghebeur  ---
By looking at my logs right after restarting the agent, I now am quite
confident that the crash happens when restarting the agent and is reproducible.
(I typically have to restart the agent twice, as the first time is not
successful.)

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

[plasmashell] [Bug 492931] New: Plasma crashes on or shortly after resuming from suspend-to-ram

[Erik Quaeghebeur]

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

Bug ID: 492931
   Summary: Plasma crashes on or shortly after resuming from
suspend-to-ram
Classification: Plasma
   Product: plasmashell
   Version: 6.1.4
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: 1.0

Application: plasmashell (6.1.4)
 (Compiled from sources)
Qt Version: 6.7.2
Frameworks Version: 6.5.0
Operating System: Linux 6.6.47-gentoo-a x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 6.1.4 [CoredumpBackend]

-- Information about the crash:
I had just resumed my laptop after suspending-to-ram. At that time or briefly
after, Plasma seems to have crashed. My interactions with the machine was (1)
unlocking the machine and (2) clicking on the bluetooth icon in the task bar to
check whether my headset was connected.

The crash can be reproduced sometimes.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault

[New LWP 115062]
[New LWP 115320]
[New LWP 115301]
[New LWP 115406]
[New LWP 115310]
[New LWP 115097]
[New LWP 115076]
[New LWP 115241]
[New LWP 115096]
[New LWP 232412]
[New LWP 115110]
[New LWP 115119]
[New LWP 115105]
[New LWP 117490]
[New LWP 115749]
[New LWP 115107]
[New LWP 115118]
[New LWP 115108]
[New LWP 115109]
[New LWP 117485]
[New LWP 115121]
[New LWP 230012]
[New LWP 117488]
[New LWP 230010]
[New LWP 115751]
[New LWP 117487]
[New LWP 120514]
[New LWP 117486]
[New LWP 115117]
[New LWP 115103]
[New LWP 115123]
[New LWP 120512]
[New LWP 230059]
[New LWP 115754]
[New LWP 115755]
[New LWP 115120]
[New LWP 230065]
[New LWP 115753]
[New LWP 230062]
[New LWP 117491]
[New LWP 230063]
[New LWP 115750]
[New LWP 230013]
[New LWP 230014]
[New LWP 230064]
[New LWP 115268]
[New LWP 230015]
[New LWP 120513]
[New LWP 230016]
[New LWP 120516]
[New LWP 230061]
[New LWP 120517]
[New LWP 230011]
[New LWP 115752]
[New LWP 232413]
[New LWP 120511]
[New LWP 120101]
[New LWP 120515]
[New LWP 117489]
[New LWP 230060]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7bc92eec3afc in ?? () from /usr/lib64/libc.so.6
[Current thread is 1 (Thread 0x7bc92995a9c0 (LWP 115062))]
Cannot QML trace cores :(
Unexpectedly stumbled over an objfile (/usr/bin/plasmashell) without build_id.
Not creating payload.
[Current thread is 1 (Thread 0x7bc92995a9c0 (LWP 115062))]

Thread 60 (Thread 0x7bc822ffd6c0 (LWP 230060)):
#0  0x7bc92eebe7c5 in ??? () at /usr/lib64/libc.so.6
#1  0x7bc92eec0ff2 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2  0x7bc922273d0b in ??? () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7bc92227ef57 in ??? () at /usr/lib64/dri/radeonsi_dri.so
#4  0x7bc92eec1e21 in ??? () at /usr/lib64/libc.so.6
#5  0x7bc92ef2f518 in ??? () at /usr/lib64/libc.so.6

Thread 59 (Thread 0x7bc8988736c0 (LWP 117489)):
#0  0x7bc92eebe7c5 in ??? () at /usr/lib64/libc.so.6
#1  0x7bc92eec0ff2 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2  0x7bc922273d0b in ??? () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7bc92227ef57 in ??? () at /usr/lib64/dri/radeonsi_dri.so
#4  0x7bc92eec1e21 in ??? () at /usr/lib64/libc.so.6
#5  0x7bc92ef2f518 in ??? () at /usr/lib64/libc.so.6

Thread 58 (Thread 0x7bc806ffd6c0 (LWP 120515)):
#0  0x7bc92eebe7c5 in ??? () at /usr/lib64/libc.so.6
#1  0x7bc92eec0ff2 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2  0x7bc922273d0b in ??? () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7bc92227ef57 in ??? () at /usr/lib64/dri/radeonsi_dri.so
#4  0x7bc92eec1e21 in ??? () at /usr/lib64/libc.so.6
#5  0x7bc92ef2f518 in ??? () at /usr/lib64/libc.so.6

Thread 57 (Thread 0x7bc8227fc6c0 (LWP 120101)):
#0  0x7bc92eebe7c5 in ??? () at /usr/lib64/libc.so.6
#1  0x7bc92eec0ff2 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2  0x7bc922273d0b in ??? () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7bc92227ef57 in ??? () at /usr/lib64/dri/radeonsi_dri.so
#4  0x7bc92eec1e21 in ??? () at /usr/lib64/libc.so.6
#5  0x7bc92ef2f518 in ??? () at /usr/lib64/libc.so.6

Thread 56 (Thread 0x7bc8213fb6c0 (LWP 120511)):
#0  0x7bc92eebe7c5 in ??? () at /usr/lib64/libc.so.6
#1  0x7bc92eec0ff2 in pthread_cond_wait () at /usr/lib64/libc.so.6
#2  0x7bc92f5cd43b in QWaitConditionPrivate::wait (deadline=...,
this=0x5eb2473fce10) at
/var/tmp/portage/dev-qt/qtbase-6.7.2-r4/work/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:102
#3  QWaitCondition::wait (this=this@entry=0x5eb24b331810,
mutex=mutex@entry=0x5eb24b331808, deadline=...) at
/var/tmp/

[Akonadi] [Bug 492817] New: Akonadi EWS resource nonreliability and crash after authentication issues

[Erik Quaeghebeur]

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

Bug ID: 492817
   Summary: Akonadi EWS resource nonreliability and crash after
authentication issues
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 6.1.2
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu, kri...@op.pl
  Target Milestone: ---

Created attachment 173444
  --> https://bugs.kde.org/attachment.cgi?id=173444&action=edit
Excerpt from system log including backtrace for crash

SUMMARY
I recently updated from KDE5 to KDE6. The EWS resource for 5 wasn't all too
stable, but for 6 it has become dramatically bad. Effectively, the resource
becomes disabled very soon after restarting and I need to manually restart it
in akonadiconsole to fetch my mail (and then later I find it deactivated
again).

I do not know whether there is a crash associated to this deactivation or not,
also because DrKonqi seems to not work any more for me on KDE6. In any case, in
my logs I found a backtrace for the EWS resource, which I'm attaching here,
with some context.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.6.47-gentoo-a (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 49.7 GB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION
I can install more debug symbol packages, if needed. Tell me which, as I don't
have DrKonqi's input about this.

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

[plasmashell] [Bug 466193] Plasmashell sometimes tries to load before kactivitymanagerd has finished loading, and fails

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

Version|5.26.5  |6.1.4

--- Comment #20 from Erik Quaeghebeur  ---
Still an issue with Plasma 6.1.4.

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

[krusader] [Bug 492248] New: Krusader crashes after resume from suspend

[Erik Quaeghebeur]

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

Bug ID: 492248
   Summary: Krusader crashes after resume from suspend
Classification: Applications
   Product: krusader
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.8.1 "A New Day")
 (Compiled from sources)
Qt Version: 5.15.14
Frameworks Version: 5.116.0
Operating System: Linux 6.6.47-gentoo-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
The laptop had resumed from suspend and I was doing things elsewhere (not
interacting with any Krusader instance) when I was notified Krusader had
crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x7afff5903dea in
std::__atomic_base::load
(__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/atomic_base.h:837
#5  std::atomic::load
(__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/atomic:577
#6 
QAtomicOps::loadRelaxed
(_q_value=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#7  QBasicAtomicPointer::loadRelaxed
(this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#8  QtSharedPointer::ExternalRefCountData::getAndRef (obj=0x634c752666c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/tools/qsharedpointer.cpp:1445
#9  0x7afff6d4708d in ?? () from /usr/lib64/libKF5JobWidgets.so.5
#10 0x7afff5aaf015 in QtPrivate::QSlotObjectBase::call (a=0x7ffdecbd7f20,
r=0x634c74517b90, this=0x634c751d9ad0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x7afff6d57060, signal_index=3,
argv=0x7ffdecbd7f20) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3925
#12 0x7afff5aaf015 in QtPrivate::QSlotObjectBase::call (a=0x7ffdecbd8040,
r=0x7afff6d57060, this=0x634c74f89d80) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x634c74c18f50, signal_index=5,
argv=0x7ffdecbd8040) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3925
#14 0x7afff5aa8d47 in QMetaObject::activate
(sender=sender@entry=0x634c74c18f50, m=m@entry=0x7afff5dfdde0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdecbd8040)
at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3985
#15 0x7afff5de3566 in QDBusServiceWatcher::serviceOwnerChanged
(this=this@entry=0x634c74c18f50, _t1=..., _t2=..., _t3=...) at
.moc/moc_qdbusservicewatcher.cpp:242
#16 0x7afff5de3fae in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged
(newOwner=..., oldOwner=..., service=..., this=) at
/var/tmp/portage/dev-qt/qtdbus-5.15.14/work/qtbase-everywhere-src-5.15.14/src/dbus/qdbusservicewatcher.cpp:76
#17 QDBusServiceWatcher::qt_static_metacall (_o=_o@entry=0x634c74c18f50,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=3,
_a=_a@entry=0x7ffdecbd81c0) at .moc/moc_qdbusservicewatcher.cpp:116
#18 0x7afff5de4393 in QDBusServiceWatcher::qt_metacall
(this=0x634c74c18f50, _c=QMetaObject::InvokeMetaMethod, _id=3,
_a=0x7ffdecbd81c0) at .moc/moc_qdbusservicewatcher.cpp:197
#19 0x7afff5d92d1b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at
/var/tmp/portage/dev-qt/qtdbus-5.15.14/work/qtbase-everywhere-src-5.15.14/src/dbus/qdbusintegrator.cpp:1001
#20 0x7afff5aa6f87 in QObject::event (this=0x634c74c18f50,
e=0x7affec0332b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:1347
#21 0x7afff64fa19e in QApplicationPrivate::notify_helper (this=, receiver=0x634c74c18f50, e=0x7affec0332b0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.14/work/qtbase-everywhere-src-5.15.14/src/widgets/kernel/qapplication.cpp:3640
#22 0x7afff5a7beb8 in QCoreApplication::notifyInternal2
(receiver=0x634c74c18f50, event=0x7affec0332b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qcoreapplication.cpp:1064
#23 0x7afff5a7c0ae in QCoreApplication::s

[plasmashell] [Bug 466649] [Activity Pager] Panel activity switcher text sometimes disappears

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #10 from Erik Quaeghebeur  ---
(In reply to TraceyC from comment #9)
> Just following up on this report. Were you ever able to reproduce the
> problem?

No. Likely, it was fixed somehow in the meantime. So it now works for me as it
should.

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

[plasmashell] [Bug 491022] ksmserver spams logs with "[warn] epoll_wait: Bad file descriptor"

[Erik Quaeghebeur]

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

--- Comment #2 from Erik Quaeghebeur  ---
(In reply to Harald Sitter from comment #1)
> Rate limiting is solved by journald
> https://www.freedesktop.org/software/systemd/man/latest/journald.conf.
> html#RateLimitIntervalSec=

That is too crude: it is global over all units and removes all log entries from
a unit. I need a massively repeated log line to be removed.
It may be that this component is not the one to blame, but that the issue lies
in a supporting framework/library. Namely, I saw that the kalendarac unit also
does spamming like this.

In any case, this report is bigger than just a request for rate limiting. The
fact that KDE components can trigger this warning lots of times per
*micro*second and multiple times in a session (e.g., I've got stretches at
17:38:55.887024, 17:38:55.868863, 17:38:55.854864,…) does seem to suggest there
is some kind of bug. Already the fact that bad file descriptors are passed
could be considered a bug, let alone repeatedly doing so in a massive way.

So, please reopen this bug and help me find out which component is misbehaving.

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

[plasmashell] [Bug 491022] New: ksmserver spams logs with "[warn] epoll_wait: Bad file descriptor"

[Erik Quaeghebeur]

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

Bug ID: 491022
   Summary: ksmserver spams logs with "[warn] epoll_wait: Bad file
descriptor"
Classification: Plasma
   Product: plasmashell
   Version: 5.27.11
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
In my logs, there are thousands of repetitions of "ksmserver[522058]: [warn]
epoll_wait: Ongeldige bestandsdescriptor". ('Ongeldige bestandsdescriptor'
translates to 'Bad file descriptor' or 'Invalid file descriptor'.) These
repetitions happen within the same microsecond re-occur during a single
session.

STEPS TO REPRODUCE
1. Start session
2. Do some work
3. Look at logs

OBSERVED RESULT
Log spam as described in the summary.

EXPECTED RESULT
No log spam, repetitions are either rate limited or something smarter is done
dealing with the underlying issue

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.11.1
KDE Frameworks Version: 5.116
Qt Version: 5.15.14

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

[Merkuro] [Bug 472793] merkuro-calendar crashes on startup

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu
Version|23.08.4 |23.08.5

--- Comment #10 from Erik Quaeghebeur  ---
Confirmed this still happens with version 23.08.5.

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

[kde] [Bug 490078] New: EWS resource crashes on restart of akonadi server

[Erik Quaeghebeur]

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

Bug ID: 490078
   Summary: EWS resource crashes on restart of akonadi server
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: akonadi_ews_resource (5.24.5 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.14
Frameworks Version: 5.116.0
Operating System: Linux 6.6.37-gentoo-f x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
The EWS resource was not responding, so I restarted akonadi. Then the EWS
resource crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: TUe (akonadi_ews_resource), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base::operator++ (this=0x18) at
/usr/include/qt5/QtCore/qbasicatomic.h:118
#5  QAtomicOps::ref (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:283
#6  QBasicAtomicInteger::ref (this=0x18) at
/usr/include/qt5/QtCore/qbasicatomic.h:118
#7  QSharedPointer::ref (this=0x7ffd3e1c8520) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:509
#8 
QSharedPointer::QSharedPointer (other=..., this=0x7ffd3e1c8520) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:371
#9  EwsFetchCalendarDetailJob::exceptionItemsFetched (this=,
job=) at
/var/tmp/portage/kde-apps/kdepim-runtime-23.08.5/work/kdepim-runtime-23.08.5/resources/ews/calendar/ewsfetchcalendardetailjob.cpp:179
#10 0x787a5aeaf015 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3e1c86b0,
r=0x59feb6ec81e0, this=0x59feb72d0440) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x59feb7089f40, signal_index=6,
argv=0x7ffd3e1c86b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3925
#12 0x787a5aea8d47 in QMetaObject::activate
(sender=sender@entry=0x59feb7089f40, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd3e1c86b0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3985
#13 0x787a63b5d303 in KJob::result (this=this@entry=0x59feb7089f40,
_t1=, _t1@entry=0x59feb7089f40, _t2=...) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#14 0x787a63b630bb in KJob::finishJob (this=0x59feb7089f40,
emitResult=) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0/src/lib/jobs/kjob.cpp:98
#15 0x787a5aeaf015 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3e1c87e0,
r=0x59feb7089f40, this=0x59feb6fabc80) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate (sender=0x59feb72d0410, signal_index=6,
argv=0x7ffd3e1c87e0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3925
#17 0x787a5aea8d47 in QMetaObject::activate
(sender=sender@entry=0x59feb72d0410, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd3e1c87e0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3985
#18 0x787a63b5d303 in KJob::result (this=this@entry=0x59feb72d0410,
_t1=, _t1@entry=0x59feb72d0410, _t2=...) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#19 0x787a63b630bb in KJob::finishJob (this=0x59feb72d0410,
emitResult=) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0/src/lib/jobs/kjob.cpp:98
#20 0x787a5aeaf015 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3e1c88b0,
r=0x59feb72d0410, this=0x59feb6ecd630) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x59feb6a175b0, signal_index=7,
argv=0x7ffd3e1c88b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3925
#22 0x787a5aea8d47 in QMetaObject::activate
(sender=sender@entry=0x59feb6a175b0, m=,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3985
#23 0x787a63ce9313 in KIO::SlaveInterface::finished
(this=this@entry=0x59feb6a175b0) at
/var/tmp/portage/kde-frameworks/kio-5.116.0/work/kio-5.116.0_build/src/core/KF5KIOCore_autogen/include/moc

[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1

[Erik Kurzinger]

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

Erik Kurzinger  changed:

   What|Removed |Added

 CC||ekurzin...@gmail.com

--- Comment #33 from Erik Kurzinger  ---
Also encountering this issue after an update. It looks like the sshfs command
is failing with the following error message...

fuse: unknown option(s): `-o ssh-rsa'

If I modify plugins/sftp/mounter.cpp and delete the
"HostKeyAlgorithms=+ssh-dss\\,ssh-rsa" line then it works again. Maybe sshfs or
fuse changed how they parse options and is now getting confused by the comma?
But it's not entirely clear to me why this option is even necessary. It is for
compatibility with older systems or something?

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

[krdc] [Bug 485726] crash while scrolling

[Erik Boritsch]

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

Erik Boritsch  changed:

   What|Removed |Added

 CC||e...@boritsch.de

--- Comment #4 from Erik Boritsch  ---
Have the same issue, also a Lenovo laptop.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0

I have a Lenovo V130-14IKB laptop. 

The issue only occurs with touchpad scrolling on wayland. With X11 an RDP
session in KRDC works fine with both touchpad and mouse. On wayland mouse
scrolling works, touchpad scrolling crashes.

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

[okular] [Bug 449709] Print Color Mode: not possible to print in black-white

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

--- Comment #9 from Erik Quaeghebeur  ---
Created attachment 171292
  --> https://bugs.kde.org/attachment.cgi?id=171292&action=edit
system-config-printer printer option window on job options page with
print-color-mode option highlighted

My guess is, that this bug is related to a changed CUPS behavior. See
https://github.com/OpenPrinting/cups/issues/421 and
https://github.com/OpenPrinting/system-config-printer/issues/312. Namely, a
default job option is set (print-color-mode monochrome/color) that does not
seem to be overridden when selecting the color mode in the Advanced settings
tab. It is not clear to me whether Okular is at fault here, but it possibly is,
as system-config-printer does expose this job option.

In any case—but this is likely bigger than this bug—it would be good if the
print dialog also exposes the color mode for physical printers as it now does
for print-to-pdf in the Options tab, next to the Double Sided Printing option.

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

[okular] [Bug 449709] Print Color Mode: not possible to print in black-white

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||aman...@kde.org

--- Comment #8 from Erik Quaeghebeur  ---
*** Bug 478631 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 478631] Printing settings are ignored

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Erik Quaeghebeur  ---


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

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

[krusader] [Bug 488510] New: Krusader crashes after waking from sleep (suspend)

[Erik Quaeghebeur]

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

Bug ID: 488510
   Summary: Krusader crashes after waking from sleep (suspend)
Classification: Applications
   Product: krusader
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.8.1 "A New Day")
 (Compiled from sources)
Qt Version: 5.15.14
Frameworks Version: 5.116.0
Operating System: Linux 6.6.30-gentoo-f x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
When I woke my laptop from sleep (suspend), krusader (had) crashed. Other
possibly relevant information: it may be that some network connection had been
open in some tab.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x787b15d5a5e3 in std::_Hashtable >,
std::allocator > >, std::__detail::_Select1st,
std::equal_to, QtPrivate::NetworkConfigurationHash,
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash,
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_get_previous_node (__n=0x5a11ae105cb0, __bkt=0,
this=0x5a11af0666d0) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/hashtable.h:2070
#5  std::_Hashtable >,
std::allocator > >, std::__detail::_Select1st,
std::equal_to, QtPrivate::NetworkConfigurationHash,
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash,
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::erase (__it=..., this=0x5a11af0666d0) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/hashtable.h:2327
#6  std::unordered_map,
QtPrivate::NetworkConfigurationHash, std::equal_to,
std::allocator > > >::erase (__position=...,
this=0x5a11af0666d0) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/unordered_map.h:748
#7  maybe_prune_expired, QtPrivate::NetworkConfigurationHash> >
(c=std::unordered_map with 17 elements = {...}) at
/var/tmp/portage/dev-qt/qtnetwork-5.15.14/work/qtbase-everywhere-src-5.15.14/src/network/bearer/qsharednetworksession.cpp:73
#8  QSharedNetworkSessionManager::getSession (config=...) at
/var/tmp/portage/dev-qt/qtnetwork-5.15.14/work/qtbase-everywhere-src-5.15.14/src/network/bearer/qsharednetworksession.cpp:83
#9  0x787b15cda055 in QNetworkAccessManagerPrivate::createSession
(this=0x5a11aedd87d0, config=...) at
/var/tmp/portage/dev-qt/qtnetwork-5.15.14/work/qtbase-everywhere-src-5.15.14/src/network/access/qnetworkaccessmanager.cpp:1947
#10 0x787b15cda5d1 in QNetworkAccessManagerPrivate::_q_onlineStateChanged
(this=0x5a11aedd87d0, isOnline=true) at
/var/tmp/portage/dev-qt/qtnetwork-5.15.14/work/qtbase-everywhere-src-5.15.14/src/network/access/qnetworkaccessmanager.cpp:2089
#11 0x787b166af13c in doActivate (sender=0x5a11aedd8880,
signal_index=6, argv=0x74aa7bd0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3937
#12 0x787b166a8d47 in QMetaObject::activate (sender=,
m=m@entry=0x787b15e2fd00 ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x74aa7bd0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:3985
#13 0x787b15d54fa2 in QNetworkConfigurationManager::onlineStateChanged
(this=, _t1=) at
.moc/moc_qnetworkconfigmanager.cpp:236
#14 0x787b166a6f87 in QObject::event (this=0x5a11aedd8880,
e=0x787acc008fd0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qobject.cpp:1347
#15 0x787b170fa19e in QApplicationPrivate::notify_helper (this=, receiver=0x5a11aedd8880, e=0x787acc008fd0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.14/work/qtbase-everywhere-src-5.15.14/src/widgets/kernel/qapplication.cpp:3640
#16 0x787b1667beb8 in QCoreApplication::notifyInternal2
(receiver=0x5a11aedd8880, event=0x787acc008fd0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qcoreapplication.cpp:1064
#17 0x787b1667c0ae in QCoreApplication::sendEvent (receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qcoreapplication.cpp:1462
#18 0x787b1667f423 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5a11ae0369a0) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywhere-src-5.15.14/src/corelib/kernel/qcoreapplication.cpp:1821
#19 0x787b1667f6d8 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
/var/tmp/portage/dev-qt/qtcore-5.15.14/work/qtbase-everywh

[Akonadi] [Bug 486861] Memory leak in EWS resource

[Erik Duisters]

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

Erik Duisters  changed:

   What|Removed |Added

 CC||e.duiste...@gmail.com

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

[kwalletmanager] [Bug 487712] New: Does not ask for password on boot + throws GPG error "no secret key" + crashes when attempting to manually open wallet

[Erik von Nastase]

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

Bug ID: 487712
   Summary: Does not ask for password on boot + throws GPG error
"no secret key" + crashes when attempting to manually
open wallet
Classification: Applications
   Product: kwalletmanager
   Version: 24.02.1
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: e...@vonnasta.se
  Target Milestone: ---

SUMMARY
The wallet manager doesn't ask for a password when booting up, instead throwing
the following error:

>Error when attempting to decrypt the wallet kdewallet using GPG. If you're 
>using a SmartCard, please ensure it's inserted then try again.
>GPG error was No secret key

Attempting to open the wallet manually via "open" button in the wallet manager
causes it to hang until suse prompts the user to terminate the application.

STEPS TO REPRODUCE
1. Create wallet using GPG encryption
2. ??? (various usage, it worked fine for a short while)
3. Boot up, experience this problem.

OBSERVED RESULT
Wallet manager does not ask for password, and cannot be opened manually either.

EXPECTED RESULT
Wallet asks for password, then unlocks once it is entered.

NOTES
I may try to investigate further and see if I am able to narrow down the cause
a bit. Not right now though.

SYSTEM INFORMATION:
Operating System: openSUSE Tumbleweed 20240524
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.9.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 5900HS with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G15 GA503QR_GA503QR
System Version: 1.0

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

[kde] [Bug 487367] New: Exchange resource crashes upon reconnection to the internet

[Erik Quaeghebeur]

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

Bug ID: 487367
   Summary: Exchange resource crashes upon reconnection to the
internet
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: akonadi_ews_resource (5.24.5 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.6.30-gentoo-f x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
After the computer awaking from standby, the exchange resource crashed upon
reconnection.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: TUe (akonadi_ews_resource), signal: Segmentation fault

[KCrash Handler]
#4  QString::QString (other=, this=0x7ffca9f3a480, this=, other=) at /usr/include/qt5/QtCore/qstring.h:1093
#5  EwsSettingsBase::eventSubscriptionId (this=Python Exception : Cannot access memory at address 0x90
#6  EwsSubscriptionManager::start (this=0x0) at
/var/tmp/portage/kde-apps/kdepim-runtime-23.08.5/work/kdepim-runtime-23.08.5/resources/ews/ewssubscriptionmanager.cpp:47
#7  EwsResource::rootFolderFetchFinished (this=0x7ffca9f3b750, job=) at
/var/tmp/portage/kde-apps/kdepim-runtime-23.08.5/work/kdepim-runtime-23.08.5/resources/ews/ewsresource.cpp:227
#8  0x7604134b0745 in QtPrivate::QSlotObjectBase::call (a=0x7ffca9f3a5d0,
r=0x7ffca9f3b750, this=0x60bec64bd0a0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9  doActivate (sender=0x60bec6908610, signal_index=6,
argv=0x7ffca9f3a5d0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:3925
#10 0x7604134aa477 in QMetaObject::activate
(sender=sender@entry=0x60bec6908610, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffca9f3a5d0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:3985
#11 0x76041c122303 in KJob::result (this=this@entry=0x60bec6908610,
_t1=, _t1@entry=0x60bec6908610, _t2=...) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.115.0/work/kcoreaddons-5.115.0_build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#12 0x76041c1280bb in KJob::finishJob (this=0x60bec6908610,
emitResult=) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.115.0/work/kcoreaddons-5.115.0/src/lib/jobs/kjob.cpp:98
#13 0x7604134b0745 in QtPrivate::QSlotObjectBase::call (a=0x7ffca9f3a700,
r=0x60bec6908610, this=0x60bec69607b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate (sender=0x60bec6934860, signal_index=6,
argv=0x7ffca9f3a700) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:3925
#15 0x7604134aa477 in QMetaObject::activate
(sender=sender@entry=0x60bec6934860, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffca9f3a700)
at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:3985
#16 0x76041c122303 in KJob::result (this=this@entry=0x60bec6934860,
_t1=, _t1@entry=0x60bec6934860, _t2=...) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.115.0/work/kcoreaddons-5.115.0_build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#17 0x76041c1280bb in KJob::finishJob (this=0x60bec6934860,
emitResult=) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.115.0/work/kcoreaddons-5.115.0/src/lib/jobs/kjob.cpp:98
#18 0x7604134b0745 in QtPrivate::QSlotObjectBase::call (a=0x7ffca9f3a7d0,
r=0x60bec6934860, this=0x60bec63b07f0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate (sender=0x60bec64a1aa0, signal_index=7,
argv=0x7ffca9f3a7d0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:3925
#20 0x7604134aa477 in QMetaObject::activate
(sender=sender@entry=0x60bec64a1aa0, m=,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:3985
#21 0x76041c2ae303 in KIO::SlaveInterface::finished
(this=this@entry=0x60bec64a1aa0) at
/var/tmp/portage/kde-frameworks/kio-5.115.0/work/kio-5.115.0_build/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:464
#22 0x76041c2b3540 in KIO::SlaveInterface::dispatch (this=0x60be

[okular] [Bug 481362] Okular crashes right after adding signature

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

Version|23.08.4 |23.08.5

--- Comment #4 from Erik Quaeghebeur  ---
Still present in 23.08.5

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

[Akonadi] [Bug 486627] New: Akonadi crashes a while after a restart

[Erik Quaeghebeur]

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

Bug ID: 486627
   Summary: Akonadi crashes a while after a restart
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadiserver (5.24.5 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.6.21-gentoo-g x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
I had restarted akonadi because one (IMAP) resource was stuk and usually,
restarting fixes that. This time, I restarted and went to do something else on
my computer. Then, a while later (10 minutes?) it crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted

[KCrash Handler]
#4  0x7be7e2ec481c in ?? () from /usr/lib64/libc.so.6
#5  0x7be7e2e74142 in raise () from /usr/lib64/libc.so.6
#6  0x7be7e2e5c4ef in abort () from /usr/lib64/libc.so.6
#7  0x7be7e309bca9 in ?? () from
/usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6
#8  0x7be7e30ae338 in ?? () from
/usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6
#9  0x7be7e30ae3a3 in std::terminate() () from
/usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6
#10 0x7be7e347a18e in qTerminate () at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/global/qglobal.cpp:3383
#11 0x7be7e347c10b in (anonymous
namespace)::terminate_on_exception >
(t=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:297
#12 QThreadPrivate::start (arg=0x557797794000) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:310
#13 0x7be7e2ec2ac9 in ?? () from /usr/lib64/libc.so.6
#14 0x7be7e2f36ec8 in ?? () from /usr/lib64/libc.so.6

Thread 7 (Thread 0x7be7dca776c0 (LWP 702492) "IntervalCheck-T"):
#1  0x7be7e1b2160c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#2  0x7be7e36cf1be in QEventDispatcherGlib::processEvents
(this=0x7be7b8000b70, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#3  0x7be7e367c00b in QEventLoop::exec (this=this@entry=0x7be7dca76d10,
flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/global/qflags.h:69
#4  0x7be7e34c0aea in QThread::exec (this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/global/qflags.h:121
#5  0x7be7e34c1e17 in operator() (__closure=) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:350
#6  (anonymous
namespace)::terminate_on_exception >
(t=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:287
#7  QThreadPrivate::start (arg=0x557797770460) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:310
#8  0x7be7e2ec2ac9 in ?? () from /usr/lib64/libc.so.6
#9  0x7be7e2f36ec8 in ?? () from /usr/lib64/libc.so.6

Thread 6 (Thread 0x7be7dd2786c0 (LWP 702491) "SearchTaskManag"):
#1  0x7be7e2ec1de2 in pthread_cond_wait () from /usr/lib64/libc.so.6
#2  0x7be7e34c776b in QWaitConditionPrivate::wait (deadline=...,
this=0x5577977d7e60) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qwaitcondition_unix.cpp:146
#3  QWaitCondition::wait (this=this@entry=0x557797792a98,
mutex=mutex@entry=0x557797792aa0, deadline=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qwaitcondition_unix.cpp:225
#4  0x557796cabcc6 in Akonadi::Server::SearchTaskManager::searchLoop
(this=0x557797792a70) at
/var/tmp/portage/kde-apps/akonadi-23.08.5/work/akonadi-23.08.5/src/server/search/searchtaskmanager.cpp:195
#5  0x7be7e36a86b7 in QObject::event (this=0x557797792a70,
e=0x557797792ef0) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:1347
#6  0x7be7e367d5b5 in doNotify (event=0x557797792ef0,
receiver=0x557797792a70) at
/var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qcoreapplication.cpp:1154
#7  QCoreApplication::notify (event=, receiver=,
this=) at
/var/tmp/portage/dev-qt/qtcore-5

[Merkuro] [Bug 485995] New: Merkuro- calendar always crashes on startup since some unknown event

[Erik Quaeghebeur]

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

Bug ID: 485995
   Summary: Merkuro- calendar always crashes on startup since some
unknown event
Classification: Applications
   Product: Merkuro
   Version: 23.08.5
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 168825
  --> https://bugs.kde.org/attachment.cgi?id=168825&action=edit
Merkuro-calendar stack trace (copy-pasted from journal)

SUMMARY
Merkuro-calendar worked (more-or-less, it is clearly still quite young and
buggy) until some days ago. Since then, it always crashes on startup. I see the
calendar grid for a moment and then it's gone. KDE's crash handler does not
handle it. I copy-pasted the stack trace from my journal in the attached file.

I really need this to work, because I have no other alternative software for
some TODO functionality. (Zanshin too easily breaks Akonadi when editing
TODOs.)

STEPS TO REPRODUCE
1. Start merkuro-calendar

OBSERVED RESULT
crash

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION
I've seen that this report may be a duplicate of multiple other bug reports,
but I'm not sure based on my stack trace, as that doesn't look similar enough.

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

[Reminder Daemon] [Bug 485863] New: log flooded with messages when EWS cannot reach outlook server

[Erik Quaeghebeur]

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

Bug ID: 485863
   Summary: log flooded with messages when EWS cannot reach
outlook server
Classification: Frameworks and Libraries
   Product: Reminder Daemon
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

My log is filled with innumerable repetitions of lines of the following kind:

```
kalendarac[1883]: org.kde.pim.ews.client: Failed to process EWS request:
Unknown host outlook.office365.com: Host not found
```

This suggests to me that whatever process is trying to create a connection is
trying again and again even if there is no internet connection. Would it be
possible to make this process act a bit smarter, as it would avoid having
relevant messages in logs being drowned out by these?


***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)

[Erik Quaeghebeur]

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

--- Comment #4 from Erik Quaeghebeur  ---
(In reply to Christophe Marin from comment #3)
> (In reply to Erik Quaeghebeur from comment #2)
> > This is still an issue in latest KDE 5 versions. (I again had to apply my 
> > manual SQL fix.)
> 
> If you mean akonadi < 24.02, it won't get the fix. This branch is closed,
> you need to backport the change manually.
Ah, nice, it seems the great commit
https://invent.kde.org/pim/akonadi/-/commit/fcc37ce297df718430f83f7feb669573c9b135f2?page=3#995e689d409482037d49b6b0893848ff42e9f64f
likely fixed the issue. (The function is now at
https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L301.)

AFAIU, It does seem though that the fix still passes through a C++ data
structure and uses a two-step approach. Namely, first a list of orphans is
queried, it is copied to a QList
(https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L325),
which is fed back into a second query that sets the orphaned items'
collectionId to the lost+found one. This might be done more efficiently by
directly selecting anything that qualifies as an orphan item using SQL directly
in the WHERE of the UPDATE statement (cf.
https://www.sqlite.org/lang_update.html, like in the DELETE statement in my
Comment #1).

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

[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

Version|5.18.3  |5.24.5

--- Comment #2 from Erik Quaeghebeur  ---
This is still an issue in latest KDE 5 versions. (I again had to apply my
manual SQL fix.)

I believe this issue should be taken seriously. It points to a a sometimes very
inefficient approach to using SQL in Akonadi's code. Namely, that things which
are easy/efficient to do in SQL are instead done inefficiently in C++.

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

[Akonadi] [Bug 480543] Akonadis sqlite backend does not honor sql limits

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

--- Comment #5 from Erik Quaeghebeur  ---
Related: Bug #451620

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

[kwin] [Bug 480964] XWayland crash while scrolling using mouse after 2024-02-04 update

[Erik Boritsch]

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

--- Comment #8 from Erik Boritsch  ---
I had to update following packages from Neon testing to make the error stop:

libwayland-bin libwayland-client0 libwayland-cursor0 libwayland-egl1

They should be included in neon user repository IMO.

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

[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

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

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

[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available

[Erik Quaeghebeur]

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

--- Comment #3 from Erik Quaeghebeur  ---
(In reply to Nick from comment #2)
> Hi. Thanks for raising this. Can you please provide a full list of commands
> you are issuing to cause this, plus any associated apps which need to be
> installed? I will then try to duplicate this. Thanks, Nick

Install akonadiconsole. Stop akonadi. Replace your akonadiserverrc file with
the first one of Comment 1. Restart akonadi.

My feeling is that the behavior with those settings are not interesting. It
would rather be interesting to know whether those settings can occur without
user interaction.

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

[Akonadi] [Bug 483364] akonadiconsole crashes after trying to restart server

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

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

--- Comment #2 from Erik Quaeghebeur  ---
(In reply to Nick from comment #1)
> Hi - thanks for raising this. Can you please provide a full list of commands
> you issued to cause this, plus any apps installed relating to this? I will
> then try to duplicate it. Thanks, Nick.

I cannot provide more info than what is in the original report. If the
backtrace doesn't point to a specific code path, I guess this report cannot be
followed up.

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

[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available

[Erik Quaeghebeur]

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

--- Comment #1 from Erik Quaeghebeur  ---
I investigated a bit further. My akonadiserverrc file looked as follows:

---
[Debug]
Tracer=null

[%General]
Driver=QSQLITE3

[QSQLITE]
Name=/home/USERNAME/.local/share/akonadi/akonadi.db

[QSQLITE3]
Name=/home/USERNAME/.local/share/akonadi/akonadi.db
---

I am very sure I did not add the multiple [QSQLITE.?] lines, but only had one
in the past. (Can't remember which.)

When stopping the server, changing to the config below and restarting the
server and akonadiconsole, I do not get an error message anymore and DB-Browser
in akonadiconsole is working again, so that seemed to have been the problem. So
the bugreport now only still pertains to the configuration issue.

---
[Debug]
Tracer=null

[%General]
Driver=QSQLITE

[QSQLITE]
Name=/home/USERNAME/.local/share/akonadi/akonadi.db
---

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

[Akonadi] [Bug 483365] New: akonadiconsole wants QSQLITE3, while only QSQLITE is available

[Erik Quaeghebeur]

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

Bug ID: 483365
   Summary: akonadiconsole wants QSQLITE3, while only QSQLITE is
available
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
When starting akonadi, I twice get the message that the database driver is not
loaded. When looking at the startup log in akonadiconsole when restarting the
server, it becomes clear that akonadiconsole wants QSQLITE3, while only QSQLITE
is available. I assume it is akonadiconsole and not akonadi, because the latter
functions, but the former's DB-Browser tab doesn't work.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.11
KDE Frameworks Version:  5.115.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
I think this may be related to “Remove the QSQLITE3 driver”
https://invent.kde.org/pim/akonadi/-/commit/e70a7a5521b4d8fe0bb36a5b3392c547851507b0

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

[Akonadi] [Bug 483364] New: akonadiconsole crashes after trying to restart server

[Erik Quaeghebeur]

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

Bug ID: 483364
   Summary: akonadiconsole crashes after trying to restart server
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadiconsole (5.24.5 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.12
Frameworks Version: 5.115.0
Operating System: Linux 6.6.21-gentoo-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
I tried to restart the akonadi server from within akonadiconsole, but then it
crashed.

Perhaps related: I had run akonadictl fsck before this.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Akonadi-console (akonadiconsole), signal: Segmentation fault

[KCrash Handler]
#4  0x72871414c181 in AgentConfigModel::~AgentConfigModel
(this=0x7286f4007c20, this=) at
/var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5/src/agentconfigmodel.cpp:20
#5  0x72871414c259 in AgentConfigModel::~AgentConfigModel
(this=0x7286f4007c20, this=) at
/var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5/src/agentconfigmodel.cpp:21
#6  0x728712ebe682 in QObjectPrivate::deleteChildren
(this=this@entry=0x5fec46907340) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:2137
#7  0x7287139a27d6 in QWidget::~QWidget (this=this@entry=0x5fec468f6ed0,
__in_chrg=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:1524
#8  0x728713b7878a in QDialog::~QDialog (this=this@entry=0x5fec468f6ed0,
__in_chrg=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/dialogs/qdialog.cpp:426
#9  0x72871413e1ea in AgentConfigDialog::~AgentConfigDialog
(this=0x5fec468f6ed0, this=) at
/var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5_build/src/libakonadiconsole_autogen/EWIEGA46WW/../../../../akonadiconsole-23.08.5/src/agentconfigdialog.h:15
#10 AgentConfigDialog::~AgentConfigDialog (this=0x5fec468f6ed0, this=) at
/var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5_build/src/libakonadiconsole_autogen/EWIEGA46WW/../../../../akonadiconsole-23.08.5/src/agentconfigdialog.h:15
#11 0x728714141076 in AgentWidget::configureAgentRemote (this=) at
/var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5/src/agentwidget.cpp:230
#12 0x728712ec6b64 in QtPrivate::QSlotObjectBase::call (a=0x7ffc74b11270,
r=0x5fec45c7b4f0, this=0x5fec46039cb0) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x5fec46039980, signal_index=4,
argv=0x7ffc74b11270) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3925
#14 0x728712ec0897 in QMetaObject::activate
(sender=sender@entry=0x5fec46039980, m=m@entry=0x728713e90c80
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffc74b11270) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3985
#15 0x72871395c642 in QAction::triggered (this=this@entry=0x5fec46039980,
_t1=) at .moc/moc_qaction.cpp:376
#16 0x72871395f41f in QAction::activate (this=0x5fec46039980,
event=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qaction.cpp:1161
#17 0x728713aee8aa in QMenuPrivate::activateCausedStack
(this=this@entry=0x5fec46066b70, causedStack=...,
action=action@entry=0x5fec46039980, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qmenu.cpp:1384
#18 0x728713af68d0 in QMenuPrivate::activateAction (this=0x5fec46066b70,
action=0x5fec46039980, action_e=, self=true) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qmenu.cpp:1461
#19 0x7287139a6fa8 in QWidget::event (this=0x5fec45ec6e20,
event=0x7ffc74b11880) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:9045
#20 0x7287139631ee in QApplicationPrivate::notify_helper
(this=this@entry=0x5fec4584bfe0, receiver=receiver@entry=0x5fec45ec6e20,
e=e@entry=0x7ffc74b11880) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/wi

[kwin] [Bug 480964] XWayland crash while scrolling using mouse after 2024-02-04 update

[Erik Boritsch]

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

Erik Boritsch  changed:

   What|Removed |Added

Version|5.27.10 |6.0.0

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

[kwin] [Bug 480964] XWayland crash while scrolling using mouse after 2024-02-04 update

[Erik Boritsch]

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

Erik Boritsch  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 CC||e...@boritsch.de

--- Comment #7 from Erik Boritsch  ---
I have similar behaviour on wayland-1.22 with plasma6

E.g. libreoffice crashes when I scroll with the mouse (not with the touchpad
though), in the logs I see the following:

XWAYLAND: interface "wl_pointer" has no event 9

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

[kde] [Bug 482925] New: On external screens when window is off-screen, mouse gets an offset

[erik]

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

Bug ID: 482925
   Summary: On external screens when window is off-screen, mouse
gets an offset
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bozic.e...@gmail.com
  Target Milestone: ---

Created attachment 166740
  --> https://bugs.kde.org/attachment.cgi?id=166740&action=edit
screen capture (video) of bug

SUMMARY
(Upgraded to KDE6, using X11)

When using external screens, but not the built-in laptop screen cursor gets an
offset if the window is off screen.
If the whole window is fullscreen of inside the screen it's accurate.
Also if I enable my bultin-monitor, but keep the window on the external (and
partly on the built-in) it works fine.

See attached video (first the brave window is off-screen a bit and the mouse
get's an offset. Then I move it back fully on-screen and it's accurate again -
e.g. it click where the cursor is)

It reproduces every time I try it.




SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux on kernel 6.7.9-arch1-1 (64bit)
(available in About System)
KDE Plasma Version:  6.0.1
KDE Frameworks Version:  6.0.0
Qt Version:  6.6.2

ADDITIONAL INFORMATION
Running X11

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

[okular] [Bug 481362] Okular crashes right after adding signature

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

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

--- Comment #3 from Erik Quaeghebeur  ---
(In reply to Albert Astals Cid from comment #1)
> Can you share the pdf you signed (before signing it) or it contains private
> info?
Sorry, it contains private info.

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

[dolphin] [Bug 482524] New: dolphin svn plugin: ODR violations when building with LTO

[Erik Quaeghebeur]

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

Bug ID: 482524
   Summary: dolphin svn plugin: ODR violations when building with
LTO
Classification: Applications
   Product: dolphin
   Version: 23.08.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plugins: svn
  Assignee: sebast...@sebastian-doerner.de
  Reporter: bugs.kde@e3q.eu
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
When compiling the dolphin svn plugin with LTO enabled (compiler flag:
-flto=auto) and treating some LTO-problematic warnings as errors (compiler
flags: -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing), the
build fails as follows:

```
/var/tmp/portage/kde-apps/dolphin-plugins-subversion-23.08.5/work/dolphin-plugins-23.08.5/svn/svncommitdialog.cpp:70:6:
error: type ‘columns_t’ violates the C++ One Definition Rule [-Werror=odr]
   70 | enum columns_t {
  |  ^
/var/tmp/portage/kde-apps/dolphin-plugins-subversion-23.08.5/work/dolphin-plugins-23.08.5/svn/svnlogdialog.cpp:67:6:
note: an enum with different value name is defined in another translation unit
   67 | enum columns_t {
  |  ^
/var/tmp/portage/kde-apps/dolphin-plugins-subversion-23.08.5/work/dolphin-plugins-23.08.5/svn/svncommitdialog.cpp:71:5:
note: name ‘columnPath’ differs from name ‘columnRevision’ defined in another
translation unit
   71 | columnPath,
  | ^
/var/tmp/portage/kde-apps/dolphin-plugins-subversion-23.08.5/work/dolphin-plugins-23.08.5/svn/svnlogdialog.cpp:68:5:
note: mismatching definition
   68 | columnRevision,
  | ^
lto1: some warnings being treated as errors
lto-wrapper: fatal error: /usr/bin/x86_64-pc-linux-gnu-g++ returned 1 exit
status
compilation terminated.
```

SOFTWARE/OS VERSIONS
Linux: 6.6.13-gentoo-a #1 SMP
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
GCC: 13.2.1_p20240113

ADDITIONAL INFORMATION
Downstream bug: https://bugs.gentoo.org/926233

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

[okular] [Bug 481362] New: Okular crashes right after adding signature

[Erik Quaeghebeur]

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

Bug ID: 481362
   Summary: Okular crashes right after adding signature
Classification: Applications
   Product: okular
   Version: 23.08.4
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: okular (23.08.4)
 (Compiled from sources)
Qt Version: 5.15.12
Frameworks Version: 5.113.0
Operating System: Linux 6.6.13-gentoo-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I was signing a pdf form. Right after signing, Okular crashed. (The signed pdf
was properly generated, though.) In all recent times I used Okular to sign a
pdf, it did not crash. The only thing that was different now is that I had
mistyped my smartcard pin code once.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault

[KCrash Handler]
#4  0x7b225c7857d3 in Okular::Page::number (this=0x56d4feb285e0) at
/var/tmp/portage/kde-apps/okular-23.08.4/work/okular-23.08.4/core/page.cpp:162
#5  0x7b226ff86126 in SignaturePartUtils::signUnsignedSignature
(form=0x56d4febece70, pageView=0x56d4fe1f7950, doc=0x56d4fe0608d0) at
/var/tmp/portage/kde-apps/okular-23.08.4/work/okular-23.08.4/part/signaturepartutils.cpp:409
#6  0x7b22818c6b64 in QtPrivate::QSlotObjectBase::call (a=0x7fff560a4ed0,
r=0x56d4fecc7f40, this=0x56d4fecc7d90) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7  doActivate (sender=0x56d4fecc7f40, signal_index=9,
argv=0x7fff560a4ed0) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3925
#8  0x7b22818c0897 in QMetaObject::activate
(sender=sender@entry=0x56d4fecc7f40, m=m@entry=0x7b2282896240
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff560a4ed0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3985
#9  0x7b228245b182 in QAbstractButton::clicked
(this=this@entry=0x56d4fecc7f40, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#10 0x7b228245b3da in QAbstractButtonPrivate::emitClicked
(this=0x56d4fe12f520) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qabstractbutton.cpp:416
#11 0x7b228245cf97 in QAbstractButtonPrivate::click (this=0x56d4fe12f520)
at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qabstractbutton.cpp:409
#12 0x7b228245d1c3 in QAbstractButton::mouseReleaseEvent
(this=0x56d4fecc7f40, e=0x7fff560a5480) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qabstractbutton.cpp:1045
#13 0x7b22823a6fa8 in QWidget::event (this=0x56d4fecc7f40,
event=0x7fff560a5480) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:9045
#14 0x7b22823631ee in QApplicationPrivate::notify_helper
(this=this@entry=0x56d4fdd026e0, receiver=receiver@entry=0x56d4fecc7f40,
e=e@entry=0x7fff560a5480) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3640
#15 0x7b228236b8f2 in QApplication::notify (this=,
receiver=0x56d4fecc7f40, e=0x7fff560a5480) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3084
#16 0x7b2281893a08 in QCoreApplication::notifyInternal2
(receiver=0x56d4fecc7f40, event=0x7fff560a5480) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1064
#17 0x7b2281893c0e in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1474
#18 0x7b2282369bf4 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x56d4fecc7f40, event=event@entry=0x7fff560a5480,
alienWidget=, nativeWidget=0x56d4fde232d0,
buttonDown=buttonDown@entry=0x7b22828bf9d0 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:2622
#19 0x7b22823c0553 in QWidgetWindow::handleMouseEvent
(this=this@entry=0x56d4fe9627e0, event=event@entry=0x7fff560a5750) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidgetwindow.cpp:684
#20 0x7b22823c396f in QWidgetWindow::event (this=0x56d4fe9627e0,
event=0x7fff

[kdeconnect] [Bug 480522] New: kdeconnect plasmoid fails to compile with LTO enabled

[Erik Quaeghebeur]

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

Bug ID: 480522
   Summary: kdeconnect plasmoid fails to compile with LTO enabled
Classification: Applications
   Product: kdeconnect
   Version: 23.08.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

SUMMARY
kdeconnect does not compile with LTO enabled [lto-type-mismatch warnings as
errors]:

---
/var/tmp/portage/kde-misc/kdeconnect-23.08.4/work/kdeconnect-kde-23.08.4/smsapp/gsmasciimap.h:10:13:
error: type of ‘gsm_ascii_map’ does not match original declaration
[-Werror=lto-type-mismatch] 
   10 | extern bool gsm_ascii_map[128]; 
  | ^   
/var/tmp/portage/kde-misc/kdeconnect-23.08.4/work/kdeconnect-kde-23.08.4/smsapp/gsmasciimap.cpp:12:6:
note: array types have different bounds 
   12 | bool gsm_ascii_map[] = {
  |  ^  
/var/tmp/portage/kde-misc/kdeconnect-23.08.4/work/kdeconnect-kde-23.08.4/smsapp/gsmasciimap.cpp:12:6:
note: ‘gsm_ascii_map’ was previously declared here  
lto1: some warnings being treated as errors 
lto-wrapper: fatal error: /usr/bin/x86_64-pc-linux-gnu-g++ returned 1 exit
status  
compilation terminated.   
---

STEPS TO REPRODUCE
1. compile with LTO enabled and warnings that indicate LTO-unsafe constructs
promoted to errors (see at end of report)

OBSERVED RESULT
Compile fails

EXPECTED RESULT
Compile succeeds

SOFTWARE/OS VERSIONS
GCC: 13.2.1_p20240113
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
Downstream bug report: https://bugs.gentoo.org/921648

GCC flags used:
WARNING_FLAGS="-Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing"
COMMON_FLAGS="-march=native -O2 -pipe -flto=auto ${WARNING_FLAGS}"

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

[frameworks-kwayland] [Bug 466767] kwayland 5.103.0 fails to compile with LTO enabled due to ODR violations and lto type mismatch

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

--- Comment #1 from Erik Quaeghebeur  ---
Downstream bug report: https://bugs.gentoo.org/866575

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

[krita] [Bug 480520] Krita does not compile with LTO enabled

[Erik Quaeghebeur]

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

--- Comment #1 from Erik Quaeghebeur  ---
Downstream bug: https://bugs.gentoo.org/922520

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

[krita] [Bug 480520] New: Krita does not compile with LTO enabled

[Erik Quaeghebeur]

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

Bug ID: 480520
   Summary: Krita does not compile with LTO enabled
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

SUMMARY
Krita does not compile with LTO enabled:

---
/var/tmp/portage/media-gfx/krita-5.1.5/work/krita-5.1.5/plugins/tools/tool_transform2/kis_free_transform_strategy.cpp:26:6:
error: type ‘StrokeFunction’ violates the C++ One Definition Rule [-Werror=odr] 
   26 | enum StrokeFunction {   
  |  ^  
/var/tmp/portage/media-gfx/krita-5.1.5/work/krita-5.1.5/plugins/tools/tool_transform2/kis_perspective_transform_strategy.cpp:27:6:
note: an enum with different value name is defined in another translation unit  
   27 | enum StrokeFunction {   
  |  ^  
/var/tmp/portage/media-gfx/krita-5.1.5/work/krita-5.1.5/plugins/tools/tool_transform2/kis_free_transform_strategy.cpp:27:5:
note: name ‘ROTATE’ differs from name ‘DRAG_HANDLE’ defined in another
translation unit  
   27 | ROTATE = 0, 
  | ^   
/var/tmp/portage/media-gfx/krita-5.1.5/work/krita-5.1.5/plugins/tools/tool_transform2/kis_perspective_transform_strategy.cpp:28:5:
note: mismatching definition
   28 | DRAG_HANDLE = 0,
  | ^   
lto1: some warnings being treated as errors 
lto-wrapper: fatal error: /usr/bin/x86_64-pc-linux-gnu-g++ returned 1 exit
status 
compilation terminated.  
---

STEPS TO REPRODUCE
1. compile with LTO enabled

OBSERVED RESULT
Compile fails

EXPECTED RESULT
Compile succeeds

SOFTWARE/OS VERSIONS
GCC: 13.2.1_p20240113
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

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

[plasma-pa] [Bug 351818] Shortcuts are not working to control the volume

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC|bugs.kde@e3q.eu |

--- Comment #9 from Erik Quaeghebeur  ---
Not for me.

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

[digikam] [Bug 478131] dK 8.2.0 very slow and crashes in Windows 10

[Erik Herlé]

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

--- Comment #8 from Erik Herlé  ---
Aha, understood. Merci.
Everything running smooth now without crashes.

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

[digikam] [Bug 478131] dK 8.2.0 very slow and crashes in Windows 10

[Erik Herlé]

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

--- Comment #6 from Erik Herlé  ---
Tested 8.3.0. No crashes sofar and faster startup than 8.2.0 with Qt6. However
feels slower than 8.2.0 with Qt5.
One other issue is HiDPI parameter. Enabling and disabling does not make a
difference, the font is too small now.

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

[digikam] [Bug 478131] dK 8.2.0 very slow and crashes in Windows 10

[Erik Herlé]

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

--- Comment #4 from Erik Herlé  ---
I am using 8.2.0 and do not want to upgrade yet to a release that is still in
development.
Can I test 8.3.0 without disrupting my 8.2.0 setup?

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

[digikam] [Bug 477853] digiKam 8.3.0 slow startup on Windows 10 operating system

[Erik Herlé]

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

Erik Herlé  changed:

   What|Removed |Added

 CC|erik.herle+...@mailbox.org  |

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

[digikam] [Bug 478298] Please add button to filter on no stars

[Erik Herlé]

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

--- Comment #3 from Erik Herlé  ---
Yep, the functionality is there, but the UI is not clear how you can use it.
There are dedicated buttons for 'No colour label' and 'No flag', so users will
also expects a button for 'No stars'.

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

[digikam] [Bug 478298] New: Please add button to filter on no stars

[Erik Herlé]

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

Bug ID: 478298
   Summary: Please add button to filter on no stars
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Albums-Filters
  Assignee: digikam-bugs-n...@kde.org
  Reporter: erik.herle+...@mailbox.org
  Target Milestone: ---

SUMMARY
***
Add button to filter on no stars
***
The UI is unclear how you can filter all photos with no stars. There are sepate
buttons to select photos with no color label or no acceptance flag. There is no
button to select photos with no stars. You have to do it pretty complicated
using the 'None' button of the colour label buttons plus a change in the rating
filter options (equal to or less than). Even for multi-year users, like myself,
this is not very straight forward, especially when working with software like
darktable that do have a separate filter button for photos with no stars.
So, can you please add button to select no stars (left to the already existing
star buttons)?

STEPS TO REPRODUCE
1. Select an album
2. apply filter
3. 

OBSERVED RESULT
see above

EXPECTED RESULT
see above

SOFTWARE/OS VERSIONS
Windows: 10 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5

ADDITIONAL INFORMATION
 https://discuss.pixls.us/t/how-to-filter-photos-with-no-stars-solved

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

[digikam] [Bug 478131] New: dK 8.2.0 very slow and crashes in Windows 10

[Erik Herlé]

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

Bug ID: 478131
   Summary: dK 8.2.0 very slow and crashes in Windows 10
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: erik.herle+digi...@gmail.com
  Target Milestone: ---

SUMMARY
New version 8.2.0 of digikam is very slow and crashes multiple times.

NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Install new version with Chocolatey
2. Start digiKam
3. query some photos, edit face tags

OBSERVED RESULT
1. dK starts very slowly.
2. different crashes during simple actions

EXPECTED RESULT
1. Same startup time as previous versions.
2. No crashes

SOFTWARE/OS VERSIONS
Windows: 10
Qt Version: 6

ADDITIONAL INFORMATION
After reading bug 478075 (https://bugs.kde.org/show_bug.cgi?id=478075), I
downloaded the Qt5 version of digiKam 8.2.0 and that runs OK. Same startup
times as before and no crashes.

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

[digikam] [Bug 433732] Google Maps labelled "For development purposes only"

[Erik Krause]

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

Erik Krause  changed:

   What|Removed |Added

 CC|erik.kra...@gmx.de  |

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

[Akonadi] [Bug 477637] New: Synchronization of EWS resource blocks other resources

[Erik Quaeghebeur]

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

Bug ID: 477637
   Summary: Synchronization of EWS resource blocks other resources
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 5.24.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu, kri...@op.pl
  Target Milestone: ---

I've noticed that whenever the EWS resource is syncing, other resources are
blocked. This is especially problematic when for example trying to compose a
response to an email in another (e.g., IMAP) resource. It ‘hangs’ with a dialog
saying that it is retrieving the message.

Can the EWS resource's activity be split off into some separate process? (I do
not understand why it could be necessary to block composing a response to a
message in another resource.)

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

[okular] [Bug 475798] Okular crashes right after applying digital signature

[Erik Quaeghebeur]

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

--- Comment #8 from Erik Quaeghebeur  ---
(In reply to Albert Astals Cid from comment #3)
> Any chance you can upgrade to KF5 5.111 and see if that fixes the issue?
Tried with 5.112 and I could not reproduce the issue. (Running with Valgrind
still gives many “blocks are possibly lost in loss record” messages.)

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

[okular] [Bug 475798] Okular crashes right after applying digital signature

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

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

--- Comment #7 from Erik Quaeghebeur  ---
(In reply to Albert Astals Cid from comment #3)
> Any chance you can upgrade to KF5 5.111 and see if that fixes the issue?

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

[konqueror] [Bug 205276] Feature request: Vertical tabs & additional tab functionality for Konqueror

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC|bugs.kde@e3q.eu |

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

[konqueror] [Bug 166085] Tabs on left/right side

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||bugs.kde@e3q.eu

--- Comment #5 from Erik Quaeghebeur  ---
While the other bugreport is younger, it is where the activity is, so closing
this one.

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

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

[konqueror] [Bug 205276] Feature request: Vertical tabs & additional tab functionality for Konqueror

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||kde-2011...@dotancohen.com

--- Comment #6 from Erik Quaeghebeur  ---
*** Bug 166085 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 475798] Okular crashes right after applying digital signature

[Erik Quaeghebeur]

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

--- Comment #6 from Erik Quaeghebeur  ---
(In reply to Bug Janitor Service from comment #5)
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. Please provide the requested information as soon as
> possible and set the bug status as REPORTED. Due to regular bug
> tracker maintenance, if the bug is still in NEEDSINFO status with
> no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> due to lack of needed information.
Please keep this open. I'm aware, but just awaiting stabilization for my
distribution.

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

[okular] [Bug 475798] Okular crashes right after applying digital signature

[Erik Quaeghebeur]

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

--- Comment #4 from Erik Quaeghebeur  ---
(In reply to Albert Astals Cid from comment #3)
> Any chance you can upgrade to KF5 5.111 and see if that fixes the issue?

I'll do that once my distribution stabilizes it. I'll report back once that
happens.

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

[okular] [Bug 475798] Okular crashes right after applying digital signature

[Erik Quaeghebeur]

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

--- Comment #2 from Erik Quaeghebeur  ---
Created attachment 162445
  --> https://bugs.kde.org/attachment.cgi?id=162445&action=edit
output of valgrind when running okular to sign a document using a smartcard

(In reply to Albert Astals Cid from comment #1)
> Can you install valgrind and run
> 
> valgrind okular
> 
> It will be slow. And then do the same thing you do to make it crash?
> 
> Once done, even if it doesn't crash, please attach the output of valgrind 
> here.

Attached. It did not crash this time. (I closed the okular windows, so also the
one opened after creating the signed document, to stop the processing by
valgrind.)

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

[okular] [Bug 475798] New: Okular crashes right after applying digital signature

[Erik Quaeghebeur]

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

Bug ID: 475798
   Summary: Okular crashes right after applying digital signature
Classification: Applications
   Product: okular
   Version: 23.04.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: okular (23.04.3)
 (Compiled from sources)
Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.1.53-gentoo-r1-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
When signing a pdf form in okular (with a certificate on a smartcard), it often
but  not always crashes right after the signature is applied. So I can reopen
pdf and verify that the signature has been applied.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault

[KCrash Handler]
#4  0x7a6152f368e3 in Okular::Page::number (this=0x5ccebd63cc90) at
/var/tmp/portage/kde-apps/okular-23.04.3/work/okular-23.04.3/core/page.cpp:162
#5  0x7a615238649d in SignaturePartUtils::signUnsignedSignature
(form=0x5ccebda8beb0, pageView=0x5ccebcc68350, doc=0x5ccebca9d8b0) at
/var/tmp/portage/kde-apps/okular-23.04.3/work/okular-23.04.3/part/signaturepartutils.cpp:120
#6  0x7a617a4c5ea4 in QtPrivate::QSlotObjectBase::call (a=0x7ffeea71a4d0,
r=0x5ccebd87ac30, this=0x5ccebd87aa80) at
/var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7  doActivate (sender=0x5ccebd87ac30, signal_index=9,
argv=0x7ffeea71a4d0) at
/var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3925
#8  0x7a617a4bfbd7 in QMetaObject::activate
(sender=sender@entry=0x5ccebd87ac30, m=m@entry=0x7a617b496240
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffeea71a4d0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3985
#9  0x7a617b05b0a2 in QAbstractButton::clicked
(this=this@entry=0x5ccebd87ac30, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#10 0x7a617b05b2fa in QAbstractButtonPrivate::emitClicked
(this=0x5ccebd084c10) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/widgets/qabstractbutton.cpp:416
#11 0x7a617b05ceb7 in QAbstractButtonPrivate::click (this=0x5ccebd084c10)
at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/widgets/qabstractbutton.cpp:409
#12 0x7a617b05d0e3 in QAbstractButton::mouseReleaseEvent
(this=0x5ccebd87ac30, e=0x7ffeea71aa80) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/widgets/qabstractbutton.cpp:1045
#13 0x7a617afa6fa8 in QWidget::event (this=0x5ccebd87ac30,
event=0x7ffeea71aa80) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qwidget.cpp:9045
#14 0x7a617af631de in QApplicationPrivate::notify_helper
(this=this@entry=0x5ccebc7606e0, receiver=receiver@entry=0x5ccebd87ac30,
e=e@entry=0x7ffeea71aa80) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qapplication.cpp:3640
#15 0x7a617af6b8e2 in QApplication::notify (this=,
receiver=0x5ccebd87ac30, e=0x7ffeea71aa80) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qapplication.cpp:3084
#16 0x7a617a492d48 in QCoreApplication::notifyInternal2
(receiver=0x5ccebd87ac30, event=0x7ffeea71aa80) at
/var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qcoreapplication.cpp:1064
#17 0x7a617a492f4e in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qcoreapplication.cpp:1474
#18 0x7a617af69be4 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x5ccebd87ac30, event=event@entry=0x7ffeea71aa80,
alienWidget=, nativeWidget=0x5ccebc89a1c0,
buttonDown=buttonDown@entry=0x7a617b4bf9d0 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qapplication.cpp:2622
#19 0x7a617afc0573 in QWidgetWindow::handleMouseEvent
(this=this@entry=0x5ccebd39ee60, event=event@entry=0x7ffeea71ad50) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qwidgetwindow.cpp:684
#20 0x7a617afc398f in QWidgetWindow::event (this=0x5ccebd39ee60,
event=0x7ffeea71ad50) at
/var/tmp/portage/dev-qt/

[plasma-nm] [Bug 475459] New: Please follow BinaryUnitDialect or use decimal multiples of bits in network speed graph

[Erik Quaeghebeur]

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

Bug ID: 475459
   Summary: Please follow BinaryUnitDialect or use decimal
multiples of bits in network speed graph
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

SUMMARY
The applet uses binary prefixes (KiB/s) for transmission speeds in the graph
showing up/down network traffic over a connection. That means it does not seem
to follow the BinaryUnitDialect config option. Likely it is just a matter of
replacing some function with some higher-level ones, as other apps do the right
thing (e.g., Krusader).

STEPS TO REPRODUCE
1. Set BinaryUnitDialect=2 in [Locale] section of $KDEHOME/.config/kdeglobals
(setting to metric/SI instead of IEC)
2. Open network applet
3. Look at a network traffic graph

OBSERVED RESULT
IEC formatting is used instead of metric

EXPECTED RESULT
Metric formatting is used (given existing conventions for network speed being
expressed in kbps/Mbps/Gbps , an
alternative might be to use metric multiples of *bits*, as is done in the
applet for connection speed in the Details tab)

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
The BinaryUnitDialect config option is described in Bug 57240. This option is
for now still without a GUI, but Bug 364321 makes it clear this should change.
So apps like this applet should be made ready to follow BinaryUnitDialect (or,
because of network speed conventions, use metric multiples of bits).

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

[systemsettings] [Bug 364321] GUI to switch from JEDEC to SI units

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

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

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

[Powerdevil] [Bug 434486] Powerdevil bug killing my bluetooth?

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kdevelop] [Bug 473894] kdevelop hangs when copying a file

[Erik Vande Velde]

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

--- Comment #2 from Erik Vande Velde  ---
I'm pretty sure it was the other way around:  I first saw the "File Already
Exists" window, and tried to close it, without success. Only then did I notice
the progress bar dialog, thinking that stopping/closing that one would solve my
issue. In the end none of both dialog boxes could be closed, and I decided to
'kill kdevelop'  & file this bug after making a screenshot...

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

[kdevelop] [Bug 473894] kdevelop hangs when copying a file

[Erik Vande Velde]

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

Erik Vande Velde  changed:

   What|Removed |Added

 CC||erik.vandevelde@dierickxley
   ||s.be

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

[kdevelop] [Bug 473894] New: kdevelop hangs when copying a file

[Erik Vande Velde]

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

Bug ID: 473894
   Summary: kdevelop hangs when copying a file
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: erik.vandeve...@dierickxleys.be
  Target Milestone: ---

Created attachment 161263
  --> https://bugs.kde.org/attachment.cgi?id=161263&action=edit
screenshot neverending 'progress' dialog box

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. right click Makefile in base dir of the project 
2. paste the same file under the 'src' subdir

OBSERVED RESULT
the copy operation hangs forever, see attachment that shows the eternal
'progress bar' 

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 


ADDITIONAL INFORMATION

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

[gwenview] [Bug 472351] Subliminal white screen interleaved at picture transition

[erik viva]

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

erik viva  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||erikv...@gmx.de

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

[kate] [Bug 431683] Kate should detach when launched from a terminal

[Erik Quaeghebeur]

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

--- Comment #12 from Erik Quaeghebeur  ---
(In reply to Waqar Ahmed from comment #11)
> You can just check the help command, it would have saved you from writing
> such a long comment.
> 
> kate -b # run in blocking mode

Thanks for pointing out that is the option I need.

For the record:

(In reply to Erik Quaeghebeur from comment #10)
> […] From the help, I see no option that would be the one I need. […]

I did read the help. It did not help me, as I explicitly mentioned.

The help text for that option (translated from Dutch) is “If using an already
running kate process, block until ready, if URLs to open have been given.” and
not “Run in blocking mode.”. In the context of my comment, there is no ‘already
running kate process’. So I guess the help text could be improved.

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

[kate] [Bug 431683] Kate should detach when launched from a terminal

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

--- Comment #10 from Erik Quaeghebeur  ---
(In reply to Waqar Ahmed from comment #9)
> https://invent.kde.org/utilities/kate/-/merge_requests/1151
Apparently this feature was merged and made the default silently. It apparently
is in the version that my distro has recently started shipping. This new
‘feature’ breaks my setup, where I launch kate from a Python script using
subprocess as part of a kmail filter. Because subprocess now thinks kate has
finished (it gets the pid of the intermediate process, not of the kate instance
itself), it doesn't block anymore and the script does not work anymore. :-(

(In reply to Christoph Cullmann from comment #6)
> I have no issue if we have this as option, one can then still think about
> what should be the default.
I do hope there is an option to get the previous behavior back, as otherwise a
regression was introduced breaking functionality just for the sake of getting
rid of some visual annoyance. From the help, I see no option that would be the
one I need. Please advise to at least get a workaround until the regression
reverted or an option is added (which'll still take months to propagate to my
distro).

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

[kde] [Bug 471559] Wayland plasma session does not get along with egl-wayland 1.1.12

[Erik Kurzinger]

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

--- Comment #2 from Erik Kurzinger  ---
I've determined that this is a bug in the NVIDIA EGL library. Kwin is not doing
anything wrong, we're just not correctly processing the dma-buf feedback that
it sends us.

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

[kde] [Bug 471559] Wayland plasma session does not get along with egl-wayland 1.1.12

[Erik Kurzinger]

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

Erik Kurzinger  changed:

   What|Removed |Added

 CC||ekurzin...@nvidia.com

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

[Akonadi] [Bug 398783] Error message when sending emails, likely linked to failure to add "replied" tag

[Erik Boritsch]

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

Erik Boritsch  changed:

   What|Removed |Added

 CC||e...@boritsch.de

--- Comment #5 from Erik Boritsch  ---
Confirming the issue with KDE Frameworks Version 5.107.0, Qt Version 5.15.10
akonadictl 5.23.2 (23.04.2). 

Disabling the "Sent" folder makes the message disappear, but the sent messages
are not in "Sent" folder then.

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

[kmail2] [Bug 471834] New: KMail crashes after being stuck sending an email

[Erik Quaeghebeur]

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

Bug ID: 471834
   Summary: KMail crashes after being stuck sending an email
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: kmail (5.22.3 (22.12.3))
 (Compiled from sources)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.1.31-gentoo-b x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
I was trying to send an email. Because it didn't go (grayed out) and nothing
happened, I closed and restarting KMail, which then crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x72d99e56f297 in std::__atomic_base::load(std::memory_order)
const (__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:488
#5  QAtomicOps::loadRelaxed(std::atomic const&)
(_q_value=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed() const (this=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::isShared() const (this=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/tools/qrefcount.h:101
#8  QList::append(QWidget* const&) (this=0x586361e94e60,
t=@0x7ffddce91470: 0x5863616e8cb0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/tools/qlist.h:622
#9  0x72d99e59d4b0 in QWidget::insertAction(QAction*, QAction*)
(this=this@entry=0x5863616e8cb0, before=, before@entry=0x0,
action=0x5863618acb60) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/src/widgets/kernel/qwidget.cpp:3138
#10 0x72d99d3bad92 in KXMLGUI::ActionList::plug(QWidget*, int) const
(this=this@entry=0x586361ac2030, container=0x5863616e8cb0, index=) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:33
#11 0x72d99d3bf4d3 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&,
QTypedArrayData::iterator const&)
(this=this@entry=0x5863619f18d0, state=..., mergingIdxIt=...) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:209
#12 0x72d99d3bf712 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&)
(this=0x5863619f18d0, state=...) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:181
#13 0x72d99d3bf745 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:185
#14 0x72d99d3bf745 in
KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:185
#15 0x72d99d3b8437 in KXMLGUIFactory::plugActionList(KXMLGUIClient*,
QString const&, QList const&) (this=0x586361a21200,
client=client@entry=0x586368a0d4f0, name=..., actionList=...) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory.cpp:564
#16 0x72d99d3af01d in KXMLGUIClient::plugActionList(QString const&,
QList const&) (this=this@entry=0x586368a0d4f0, name=...,
actionList=...) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguiclient.cpp:697
#17 0x72d99c58051b in
PimCommon::PluginInterface::initializePluginActions(QString const&,
KXMLGUIClient*) (this=, prefix=..., guiClient=0x586368a0d4f0) at
/var/tmp/portage/kde-apps/pimcommon-22.12.3/work/pimcommon-22.12.3/src/pimcommonakonadi/genericplugins/plugininterface.cpp:154
#18 0x72d9a6e0dc8e in KMMainWidget::initializePluginActions()
(this=this@entry=0x5863718fc130) at
/var/tmp/portage/kde-apps/kmail-22.12.3/work/kmail-22.12.3/src/kmmainwidget.cpp:4190
#19 0x72d9a6e18a73 in KMMainWidget::slotShowStartupFolder()
(this=0x5863718fc130) at
/var/tmp/portage/kde-apps/kmail-22.12.3/work/kmail-22.12.3/src/kmmainwidget.cpp:4096
#20 0x72d99daaf8c4 in QObject::event(QEvent*) (this=0x5863718fc130,
e=0x58636492d000) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347
#21 0x72d99e56344e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5863718fc130, e=0x586364

[Akonadi] [Bug 469789] New: Akonadi crashes when akonadiserver is restarted

[Erik Quaeghebeur]

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

Bug ID: 469789
   Summary: Akonadi crashes when akonadiserver is restarted
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadiserver (5.22.3 (22.12.3))
 (Compiled from sources)
Qt Version: 5.15.9
Frameworks Version: 5.104.0
Operating System: Linux 6.1.27-gentoo-r1-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
Akonadi resources often get stuck synchronizing. One way of working around that
is to restart akonadiserver. Sometimes akonadi then crashes, as with this
crash.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  std::default_delete::operator() (__ptr=0x211,
this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/unique_ptr.h:89
#5  std::unique_ptr >::~unique_ptr
(this=, __in_chrg=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/unique_ptr.h:396
#6  std::__new_allocator >
>::destroy > > (__p=,
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/new_allocator.h:181
#7 
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/alloc_traits.h:535
#8  std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {...},
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/vector.tcc:181
#9  std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {...},
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/stl_vector.h:1530
#10 Akonadi::Server::AkonadiServer::connectionDisconnected
(this=0x7ffd41125a60) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/server/akonadi.cpp:234
#11 0x787ce9aaf8d4 in QObject::event (this=0x7ffd41125a60,
e=0x787c3c02dfe0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347
#12 0x787ce9a83f25 in doNotify (event=0x787c3c02dfe0,
receiver=0x7ffd41125a60) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1154
#13 QCoreApplication::notify (event=, receiver=,
this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1140
#14 QCoreApplication::notifyInternal2 (receiver=0x7ffd41125a60,
event=0x787c3c02dfe0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1064
#15 0x787ce9a8414e in QCoreApplication::sendEvent (receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1462
#16 0x787ce9a87493 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x65001f79d9c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1821
#17 0x787ce9a87738 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1680
#18 0x787ce9ad66f3 in postEventSourceDispatch (s=0x65001f7a0550) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#19 0x787ce858f51c in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#20 0x787ce858f7c8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x787ce858f85c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#22 0x787ce9ad61f6 in QEventDispatcherGlib::processEvents
(this=0x65001f7a02e0, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#23 0x787ce9a8297b in QEventLoop::exec (this=this@entry=0x7ffd41125940,
flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x787ce9a8ac56 in QCoreApplication::exec () at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x65001dee2d45 in AkApplicationBase::exec
(this=this@entry=0x7ffd41125a30) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/shared/akapplication.cpp:109
#26 0x65001dd6e8a0 in main (argc=, argv=) at
/var/t

[kmail2] [Bug 469694] New: KMail crash when akonadiserver is restarted

[Erik Quaeghebeur]

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

Bug ID: 469694
   Summary: KMail crash when akonadiserver is restarted
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: kmail (5.22.3 (22.12.3))
 (Compiled from sources)
Qt Version: 5.15.9
Frameworks Version: 5.104.0
Operating System: Linux 6.1.27-gentoo-r1-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
As often happens, an akonadi resource was stuck synchronizing, blocking the
whole of akonadi. My solution for this is to restart akonadiserver in
akonadiconsole. This crash occurred when I restarted akonadiserver in such a
way.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base::operator--() (this=0x630031) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:392
#5  QAtomicOps::deref(std::atomic&) (_q_value=) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:289
#6  QBasicAtomicInteger::deref() (this=0x630031) at
/usr/include/qt5/QtCore/qbasicatomic.h:119
#7  QSharedDataPointer::~QSharedDataPointer()
(this=0x5984d1702d50, __in_chrg=) at
/usr/include/qt5/QtCore/qshareddata.h:93
#8  Akonadi::Item::~Item() (this=0x5984d1702d50, __in_chrg=) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/item.cpp:56
#9  0x7e4023707e1c in QHashData::free_helper(void (*)(QHashData::Node*))
(this=0x7e401409d9a0, node_delete=0x7e4021797cc0 ::RefCountedValue
>::deleteNode2(QHashData::Node*)>) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/tools/qhash.cpp:572
#10 0x7e402178f38f in QHash::RefCountedValue >::freeData(QHashData*)
(x=, this=) at
/usr/include/qt5/QtCore/qhash.h:617
#11 QHash::RefCountedValue >::~QHash() (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250
#12 QHash::RefCountedValue >::~QHash() (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250
#13 QHash::RefCountedValue >::operator=(QHash::RefCountedValue >&&)
(other=, this=0x5984d1bac5b8) at
/usr/include/qt5/QtCore/qhash.h:255
#14 QHash::RefCountedValue >::clear() (this=0x5984d1bac5b8)
at /usr/include/qt5/QtCore/qhash.h:625
#15 RefCountedHash::clear() (this=0x5984d1bac5b0) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/models/entitytreemodel_p.h:109
#16 Akonadi::EntityTreeModelPrivate::endResetModel() (this=0x5984d1bac5a0) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/models/entitytreemodel_p.cpp:1722
#17 0x7e40238b7b4c in doActivate(QObject*, int, void**)
(sender=0x5984d0418c60, signal_index=3, argv=0x7ffdd7c568c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3935
#18 0x7e40238b1767 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7e402182a500
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3983
#19 0x7e4021711e80 in Akonadi::ServerManager::started() (this=) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3_build/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:167
#20 0x7e4021715659 in
Akonadi::ServerManagerPrivate::setState(Akonadi::ServerManager::State)
(this=0x7e4021832560 <(anonymous
namespace)::Q_QGS_sInstance::innerFunction()::holder>,
state=Akonadi::ServerManager::Running) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/servermanager.cpp:75
#21 0x7e40238af8d4 in QObject::event(QEvent*) (this=0x5984d0418c60,
e=0x5984d84960e0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347
#22 0x7e402436344e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5984d0418c60, e=0x5984d84960e0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/src/widgets/kernel/qapplication.cpp:3640
#23 0x7e4023883f58 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5984d0418c60, event=0x5984d84960e0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1064
#24 0x7e402388414e in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1462
#25 0x7e4023887493 in QCoreApplicationPrivate::sendPostedEvents(Q

[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ

[Erik Quaeghebeur]

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

--- Comment #7 from Erik Quaeghebeur  ---
(In reply to Jan Kundrát from comment #6)
> […] Do you feel like writing that, Erik?
I've created a Todo, but likely this will not be anything that I'm going to
look at soon, due to the effort required to find out where in the code the fix
should be applied and then how to apply it. (Other things are higher priority
or more fun.)

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

[kmail2] [Bug 468801] New: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted"

[Erik Quaeghebeur]

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

Bug ID: 468801
   Summary: org.kde.pim.mimetreeparser: unknown mimetype
"text/x-moz-deleted"
Classification: Applications
   Product: kmail2
   Version: 5.22.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

In my log, I find multiple repetitions of the following warning:
---
kmail[6994]: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted"
---
Given that kmail itself produces attached with such a mimetype when an
attachment is deleted, I think it would be a good idea to support this type in
some way, so as to at least not trigger a warning.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

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

[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ

[Erik Quaeghebeur]

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

--- Comment #5 from Erik Quaeghebeur  ---
I encountered it again and I thought I had copied the full error message, but
it is not in my clipboard…

Anyway, from the logs:
---
13:25:52.852 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_WAIT_FOR_CONN
INBOX/A/B Activated
13:25:52.852 conn Waiting for another mailbox...
13:25:52.859 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING
INBOX/A/B Synchronizing mailbox
13:25:52.864 >>> y738 SELECT "INBOX/A/B" (QRESYNC (1580119498 5801022 (3,5
2142,2217)))␍␊
13:25:52.968 <<< * OK [CLOSED] Ok␍␊
13:25:52.968 <<< * 5 EXISTS␍␊
13:25:52.968 <<< * 0 RECENT␍␊
13:25:52.968 <<< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen
$X-ME-Annot-2 prive $HasAttachment $ATTACHMENT [EDITED OUT])␍␊
13:25:52.968 <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen
$X-ME-Annot-2 prive $HasAttachment $ATTACHMENT [EDITED OUT] \*)] Ok␍␊
13:25:52.968 <<< * OK [UNSEEN 5] Ok␍␊
13:25:52.968 <<< * OK [UIDVALIDITY 1580119498] Ok␍␊
13:25:52.968 <<< * OK [UIDNEXT 2218] Ok␍␊
13:25:52.968 <<< * OK [HIGHESTMODSEQ 5801022] Ok␍␊
13:25:52.968 <<< * OK [MAILBOXID (ea021f72-3f97-4cb8-8df5-9f873545481d)] Ok␍␊
13:25:52.969 <<< * OK [URLMECH INTERNAL] Ok␍␊
13:25:52.969 <<< * OK [ANNOTATIONS 65536] Ok␍␊
13:25:52.969 <<< y738 OK [READ-WRITE] Completed␍␊
13:25:52.969 conn Opening mailbox...
13:25:52.969  Warning: unhandled untagged OK with a response code
13:25:52.969  Warning: unhandled untagged OK with a response code
13:25:52.969  Warning: unhandled untagged OK with a response code
13:25:52.969  Warning: unhandled untagged OK with a response code
13:25:52.969 conn Synchronizing mailbox...
13:25:52.970 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING
INBOX/A/B First interesting message at 5 ($X-ME-Annot-2)
13:25:52.970 conn Mailbox opened.
13:25:52.970 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING
INBOX/A/B Completed
13:25:52.970 Imap::Mailbox::KeepMailboxOpenTask attached to INBOX/A/B Activated
13:25:58.789 >>> y739 IDLE␍␊
13:25:58.883 <<< + idling␍␊
13:25:58.977 <<< * STATUS INBOX/C (UIDVALIDITY 1580127289 UNSEEN 0
HIGHESTMODSEQ 5801104)␍␊
13:25:58.977 UnrecognizedResponseKind HIGHESTMODSEQ␊* STATUS INBOX/C
(UIDVALIDITY 1580127289 UNSEEN 0 HIGHESTMODSEQ 5801104)␍␊␊ 
 ^ here
13:25:58.977 conn Logged out.
13:25:58.977 *** Connection killed.
---

Trojita was in folder INBOX/A/B, but the error seems to be about folder
INBOX/C.

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

[plasmashell] [Bug 466649] [Activity Pager] Panel activity switcher text sometimes disappears

[Erik Quaeghebeur]

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

--- Comment #7 from Erik Quaeghebeur  ---
(In reply to Nate Graham from comment #6)
> ...But you say you can't reproduce it now? Is this after upgrading to a new
> Plasma version, or is it magically working now with no obvious changes to
> the system?
No Plasma update in the meantime. However, my laptop finds itself in so many
different setups (two different setups with an extra display, connecting to
projectors, etc.) that it is hard to reproduce the situations that may trigger
bugs like these.

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

[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ

[Erik Quaeghebeur]

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

--- Comment #4 from Erik Quaeghebeur  ---
(In reply to Jan Kundrát from comment #3)
> and just to double-check, this was while you had your INBOX open, right?

Likely, but not sure. I came back to the Trojita window from another virtual
desktop and the message was there. I didn't pay attention to the opened folder.

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

[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ

[Erik Quaeghebeur]

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

--- Comment #2 from Erik Quaeghebeur  ---
(In reply to Jan Kundrát from comment #1)
> Can you please provide a bit larger context, including the IMAP command to
> which Fastmail replied with this response, as well as the full error message
> as reported by Trojita?

Context from protocol log:
---
22:09:37.239 Imap::Mailbox::ExpungeMailboxTask Activated
22:09:37.239 >>> y389 EXPUNGE␍␊
22:09:37.364 <<< * VANISHED 10635:10637␍␊
22:09:37.365 <<< y389 OK [HIGHESTMODSEQ 5796805] Completed␍␊
22:09:37.367 Imap::Mailbox::ExpungeMailboxTask Completed
22:09:43.463 >>> y390 IDLE␍␊
22:09:43.571 <<< + idling␍␊
22:09:43.675 <<< * STATUS INBOX (UIDVALIDITY 1164751602 UNSEEN 0 HIGHESTMODSEQ
5796796)␍␊
22:09:43.675 UnrecognizedResponseKind HIGHESTMODSEQ␊* STATUS INBOX (UIDVALIDITY
1164751602 UNSEEN 0 HIGHESTMODSEQ 5796796)␍␊␊  
   ^ here
22:09:43.676 conn Logged out.
22:09:43.685 *** Connection killed.
---

I don't have the full error message. It was the standard one, paraphrasing,
“I've encountered an issue which is likely on the server side but may be a
Trojita bug, so report it anyway.” and then the log excerpt I gave, with the ‘^
here’ pointing at the end of the number 5796796.

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

[trojita] [Bug 468482] New: UnrecognizedResponseKind: HIGHESTMODSEQ

[Erik Quaeghebeur]

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

Bug ID: 468482
   Summary: UnrecognizedResponseKind: HIGHESTMODSEQ
Classification: Applications
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: IMAP
  Assignee: trojita-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Trojitá told me to report the following:
---
UnrecognizedResponseKind: HIGHESTMODSEQ
* STATUS INBOX (UIDVALIDITY 1164751602 UNSEEN 0 HIGHESTMODSEQ 5796796)
---
This is on a Fastmail connection.

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

[trojita] [Bug 392440] UID consistency error

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

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

[plasmashell] [Bug 466649] Panel activity switcher text disappears

[Erik Quaeghebeur]

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

--- Comment #4 from Erik Quaeghebeur  ---
(In reply to Nate Graham from comment #3)
> Similar symptoms as Bug 445828. Does the text re-appear when the panel is
> made taller? If not, then I was wrong and it's something else.

I cannot reproduce it myself. It sometimes happens. However, it was not related
to panel height changes and the text became invisible, but could still be
clicked, which is different from the other report.

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

[plasmashell] [Bug 466649] Panel activity switcher text disappears

[Erik Quaeghebeur]

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

--- Comment #2 from Erik Quaeghebeur  ---
(In reply to Nate Graham from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 445828 ***

I very much doubt this is a duplicate of the linked report. What made you
decide it is?

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

[plasmashell] [Bug 466193] Panel disappears after reboot since Frameworks 5.102.0 update

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

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

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

[kmail2] [Bug 454257] Crash on save of attachment

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

Summary|Crash on save of attachment |Crash on save of attachment
   |(tar.gz)|

--- Comment #3 from Erik Quaeghebeur  ---
(In reply to Erik Quaeghebeur from comment #2)
> *** Bug 467266 has been marked as a duplicate of this bug. ***

My encounter shows it is not limited to tar.gz, but can also occur, e.g., with
pdfs.

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

[kmail2] [Bug 454257] Crash on save of attachment (tar.gz)

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

--- Comment #2 from Erik Quaeghebeur  ---
*** Bug 467266 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 467266] KMail crashes when saving a pdf attachment

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Erik Quaeghebeur  ---


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

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

[kmail2] [Bug 467266] New: KMail crashes when saving a pdf attachment

[Erik Quaeghebeur]

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

Bug ID: 467266
   Summary: KMail crashes when saving a pdf attachment
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

Application: kmail (5.21.3 (22.08.3))
 (Compiled from sources)
Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.12-gentoo-d x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
KMail crashed when saving a pdf attachment. The crash happens after the save
file dialog has been opened and the moment the button to Save is pressed. (The
file is not saved.) This has happened before a few times now. But it also
happens that saving does work.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x70dc6574049e in
QVector::begin(QTypedArrayData::const_iterator)
const (this=) at /usr/include/qt5/QtCore/qvector.h:220
#5  KMime::Content::headerByType(char const*) const
(this=this@entry=0x630ae9dec5b0, type=0x70dc6575ca0c
"Content-Transfer-Encoding") at
/var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:617
#6  0x70dc65741a19 in
KMime::Content::header(bool)
(create=true, this=0x630ae9dec5b0) at
/var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.h:681
#7  KMime::Content::contentTransferEncoding(bool) (this=0x630ae9dec5b0,
create=) at
/var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:874
#8  0x70dc65741aa3 in KMime::Content::decodedContent()
(this=0x630ae9dec5b0) at
/var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:316
#9  0x70dc6631627e in MessageViewer::Util::saveContent(QWidget*,
KMime::Content*, QUrl const&) (parent=0x630ae4cae770, content=,
url=...) at
/var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/utils/messageviewerutil.cpp:421
#10 0x70dc66317f1e in MessageViewer::Util::saveContents(QWidget*,
QVector const&, QList&) (parent=0x630ae4cae770,
contents=..., urlList=...) at
/var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/utils/messageviewerutil.cpp:324
#11 0x70dc662d3a61 in
MessageViewer::ViewerPrivate::slotHandleAttachment(int) (this=0x630ae4d71460,
choice=) at
/var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/viewer/viewer_p.cpp:2611
#12 0x70dc672b79c4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcd657e5b0, r=0x630ae4d71460, this=0x630ae83e2890) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x630ae6cd8d80,
signal_index=4, argv=0x7ffcd657e5b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3923
#14 0x70dc672b1707 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x630ae6cd8d80, m=m@entry=0x70dc6828fd00
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffcd657e5b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3983
#15 0x70dc67d5c8b2 in QAction::triggered(bool)
(this=this@entry=0x630ae6cd8d80, _t1=) at
.moc/moc_qaction.cpp:376
#16 0x70dc67d5f64b in QAction::activate(QAction::ActionEvent)
(this=0x630ae6cd8d80, event=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qaction.cpp:1161
#17 0x70dc67eeea8a in
QMenuPrivate::activateCausedStack(QVector > const&, QAction*,
QAction::ActionEvent, bool) (this=this@entry=0x630aee197cc0, causedStack=...,
action=action@entry=0x630ae6cd8d80, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/widgets/qmenu.cpp:1384
#18 0x70dc67ef6aec in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) (this=0x630aee197cc0, action=0x630ae6cd8d80,
action_e=QAction::Trigger, self=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/widgets/qmenu.cpp:1461
#19 0x70dc67da7028 in QWidget::event(QEvent*) (this=0x7ffcd657f3c0,
event=0x7ffcd657ebc0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:9045
#20 0x70dc67d6344e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x630ae48451e0, receiv

[trojita] [Bug 391718] ASSERT: "it != ptrToInternal.constEnd()" in file trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 1488

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Status|CONFIRMED   |NEEDSINFO
 CC||bugs.kde@e3q.eu
 Resolution|--- |WORKSFORME

--- Comment #4 from Erik Quaeghebeur  ---
(In reply to Jan Kundrát from comment #3)
> 
> 1) activate threading
> 2) open a mailbox
> 3) perform a search which returns something
> 4) switch to another mailbox where that search doesn't return anything
> 5) the threading is still preserved, and trojita assert-crashes:
> 
> ASSERT: "it != ptrToInternal.constEnd()" in file
> trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 1488

I cannot reproduce this with my current Trojitá (~git master). So unless
someone can reproduce it with a recent version (from git), I suggest we close
this.

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

[trojita] [Bug 467050] Crash after mail composition

[Erik Quaeghebeur]

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

--- Comment #1 from Erik Quaeghebeur  ---
To be clear: the crash does not happen when the Sonnet plugin is not
compiled-in.

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

[trojita] [Bug 467051] Crash when typing in a recipient box when using Akonadi Contact plugin

[Erik Quaeghebeur]

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

--- Comment #1 from Erik Quaeghebeur  ---
To be clear: the crash does not happen when the Akonadi contact integration
plugin is not compiled-in.

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

[trojita] [Bug 436157] Outdated path for *.po files in «l10n-fetch-po-files.py»

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||bugs.kde@e3q.eu
 Status|REPORTED|RESOLVED

--- Comment #1 from Erik Quaeghebeur  ---
Fixed with
https://invent.kde.org/pim/trojita/-/commit/e6d5a4472fce80f4028a1125e06d5766bab73cf2

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

[trojita] [Bug 467051] New: Crash when typing in a recipient box when using Akonadi Contact plugin

[Erik Quaeghebeur]

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

Bug ID: 467051
   Summary: Crash when typing in a recipient box when using
Akonadi Contact plugin
Classification: Applications
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Other
  Assignee: trojita-b...@kde.org
  Reporter: bugs.kde@e3q.eu
CC: trojita-b...@kde.org
  Target Milestone: ---

SUMMARY
During mail composition, Trojitá crashes when typing in a recipient box (To,
Cc,…). From the stack trace (at end), I have the impression it is related to
Akonadi Contact integration. This started happening after updating Trojita to
the latest git version (was using a git checkout of a few years old before).

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

STACK TRACE
Stack trace of thread 282058:
#0  0x77c9f51079b5 _Z5qHashRK7QStringj (libQt5Core.so.5 + 0x1079b5)
#1  0x77c9e006756b n/a (trojita_plugin_AkonadiAddressbookPlugin.so +
0x756b)
#2  0x77c9e00660ad n/a (trojita_plugin_AkonadiAddressbookPlugin.so +
0x60ad)
#3  0x77c9f52b79c4 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv
(libQt5Core.so.5 + 0x2b79c4)
#4  0x77c9ef48b6b3 _ZN4KJob6resultEPS_NS_14QPrivateSignalE
(libKF5CoreAddons.so.5 + 0x6e6b3)
#5  0x77c9ef48cb8b _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6fb8b)
#6  0x77c9f52af874 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2af874)
#7  0x77c9fa76344e
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x16344e)
#8  0x77c9f5283ef8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent
(libQt5Core.so.5 + 0x283ef8)
#9  0x77c9f5287433
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
(libQt5Core.so.5 + 0x287433)
#10 0x77c9f52d6693 postEventSourceDispatch (libQt5Core.so.5 + 0x2d6693)
#11 0x77c9f3126dc8 g_main_context_dispatch (libglib-2.0.so.0 + 0x55dc8)
#12 0x77c9f3127068 n/a (libglib-2.0.so.0 + 0x56068)
#13 0x77c9f31270fc g_main_context_iteration (libglib-2.0.so.0 + 0x560fc)
#14 0x77c9f52d6196
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2d6196)
#15 0x77c9f528291b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x28291b)
#16 0x77c9f528abf6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 +
0x28abf6)
#17 0x610d7274e238 n/a (trojita + 0x93238)
#18 0x77c9f4e4f34a n/a (libc.so.6 + 0x2334a)
#19 0x77c9f4e4f3fc __libc_start_main (libc.so.6 + 0x233fc)
#20 0x610d7274fc71 n/a (trojita + 0x94c71)

Stack trace of thread 282068:
#0  0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x77c9f4ca8b03
_ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6 +
0xa8b03)
#3  0x77c9f6e9eaea
_ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl10EE
(libQt5WebKit.so.5 + 0x109eaea)
#4  0x77c9f6e9cd58 n/a (libQt5WebKit.so.5 + 0x109cd58)
#5  0x77c9f6ea1d83 n/a (libQt5WebKit.so.5 + 0x10a1d83)
#6  0x77c9f6ecae9b n/a (libQt5WebKit.so.5 + 0x10cae9b)
#7  0x77c9f4eaf36a n/a (libc.so.6 + 0x8336a)
#8  0x77c9f4f303bc n/a (libc.so.6 + 0x1043bc)

Stack trace of thread 282062:
#0  0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x77c9ed8cb7a9 n/a (radeonsi_dri.so + 0xcb7a9)
#3  0x77c9ed87d16b n/a (radeonsi_dri.so + 0x7d16b)
#4  0x77c9ed8cb6e7 n/a (radeonsi_dri.so + 0xcb6e7)
#5  0x77c9f4eaf36a n/a (libc.so.6 + 0x8336a)
#6  0x77c9f4f303bc n/a (libc.so.6 + 0x1043bc)

Stack trace of thread 282071:
#0  0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x77c9f4ca8b03
_ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6 +
0xa8b03)
#3  0x77c9f6e9eaea
_ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl10EE
(libQt5WebKit.so.5 + 0x109eaea)
#4  0x77c9f6e9cd58 n/a (libQt5WebKit.so.5 + 0x109cd58)
#5  0x77c9f6ea1d83 n/a (libQt5WebKit.so.5 + 0x10a1d83)
#6  0x77c9f6ecae9b n/a (libQt5WebKit.so.5 + 0x10cae9b)
#7  0x77c9f4eaf36a n/a (libc.so.6 + 0x8336a)
#8  0x77c9f4f303bc n/a (libc.so.6 + 0x1043bc)

Stack trace of thread 282060:
#0  0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x77c9ed8cb7a9 n/a (radeonsi_dri.so + 0xcb7a9)
#3  0x77c9ed87d16b n/a (radeonsi_dri.so + 0x7d16b)
#4  0x77c9ed8cb6e7 n/a (radeonsi_dri.so + 0xcb6e7)
#5  0x77c9f4e

[trojita] [Bug 467050] New: Crash after mail composition

[Erik Quaeghebeur]

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

Bug ID: 467050
   Summary: Crash after mail composition
Classification: Applications
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Other
  Assignee: trojita-b...@kde.org
  Reporter: bugs.kde@e3q.eu
  Target Milestone: ---

After mail composition (which itself works), Trojitá crashes. From the stack
trace (at end), I have the impression it is related to Sonnet integration. This
started happening after updating Frameworks to 5.102.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

STACK TRACE
Stack trace of thread 281971:
#0  0x72e9bb2b4cb0 _ZNKSt13__atomic_baseIiE4loadESt12memory_order
(libQt5Core.so.5 + 0x2b4cb0)
#1  0x72e98e2b9f26 _ZN6Sonnet19SpellCheckDecoratorD1Ev (libKF5SonnetUi.so.5
+ 0x21f26)
#2  0x72e98e2b9f59 _ZN6Sonnet19SpellCheckDecoratorD0Ev (libKF5SonnetUi.so.5
+ 0x21f59)
#3  0x72e9bb2af422 _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 +
0x2af422)
#4  0x72e9c07a2926 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x1a2926)
#5  0x5cf8300efef4 n/a (trojita + 0xa1ef4)
#6  0x72e9bb2af422 _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 +
0x2af422)
#7  0x72e9c07a2926 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x1a2926)
#8  0x72e9c091f089 _ZN9QSplitterD0Ev (libQt5Widgets.so.5 + 0x31f089)
#9  0x72e9bb2af422 _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 +
0x2af422)
#10 0x72e9c07a2926 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x1a2926)
#11 0x5cf8300fd109 n/a (trojita + 0xaf109)
#12 0x72e9bb2af61f _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2af61f)
#13 0x72e9c076344e
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x16344e)
#14 0x72e9bb283ef8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent
(libQt5Core.so.5 + 0x283ef8)
#15 0x72e9bb287433
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
(libQt5Core.so.5 + 0x287433)
#16 0x72e9bb2d6693 postEventSourceDispatch (libQt5Core.so.5 + 0x2d6693)
#17 0x72e9b922cdc8 g_main_context_dispatch (libglib-2.0.so.0 + 0x55dc8)
#18 0x72e9b922d068 n/a (libglib-2.0.so.0 + 0x56068)
#19 0x72e9b922d0fc g_main_context_iteration (libglib-2.0.so.0 + 0x560fc)
#20 0x72e9bb2d6196
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2d6196)
#21 0x72e9bb28291b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x28291b)
#22 0x72e9bb28abf6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 +
0x28abf6)
#23 0x5cf8300e1238 n/a (trojita + 0x93238)
#24 0x72e9bae4f34a n/a (libc.so.6 + 0x2334a)
#25 0x72e9bae4f3fc __libc_start_main (libc.so.6 + 0x233fc)
#26 0x5cf8300e2c71 n/a (trojita + 0x94c71)

Stack trace of thread 281972:
#0  0x72e9baf2268f __poll (libc.so.6 + 0xf668f)
#1  0x72e9b900ad82 n/a (libxcb.so.1 + 0xcd82)
#2  0x72e9b900d23a xcb_wait_for_event (libxcb.so.1 + 0xf23a)
#3  0x72e9b69204e8 _ZN14QXcbEventQueue3runEv (libQt5XcbQpa.so.5 + 0x664e8)
#4  0x72e9bb0cbc77 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcbc77)
#5  0x72e9baeaf36a n/a (libc.so.6 + 0x8336a)
#6  0x72e9baf303bc n/a (libc.so.6 + 0x1043bc)

Stack trace of thread 281974:
#0  0x72e9baeabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x72e9baeae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x72e9aeecb7a9 n/a (radeonsi_dri.so + 0xcb7a9)
#3  0x72e9aee7d16b n/a (radeonsi_dri.so + 0x7d16b)
#4  0x72e9aeecb6e7 n/a (radeonsi_dri.so + 0xcb6e7)
#5  0x72e9baeaf36a n/a (libc.so.6 + 0x8336a)
#6  0x72e9baf303bc n/a (libc.so.6 + 0x1043bc)

Stack trace of thread 281981:
#0  0x72e9baeabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x72e9baeae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x72e9baca8b03
_ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libs
#3  0x72e9bce9eaea
_ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl10EE
(libQt5WebKit.so.5 + 0x109eaea)
#4  0x72e9bce9cd58 n/a (libQt5WebKit.so.5 + 0x109cd58)
#5  0x72e9bcea1d83 n/a (libQt5WebKit.so.5 + 0x10a1d83)
#6  0x72e9bcecae9b n/a (libQt5WebKit.so.5 + 0x10cae9b)
#7  0x72e9baeaf36a n/a (libc.so.6 + 0x8336a)
#8  0x72e9baf303bc n/a (libc.so.6 + 0x1043bc)

Stack trace of thread 281984:
#0  0x72e9baeabef6 n/a (libc.so.6 + 0x7fef6)
#1  0x72e9baeae73f pthread_cond_wait (libc.so.6 + 0x8273f)
#2  0x72e9baca8b03
_ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6 +
0xa8b03)
#3  0x72e9bce9eaea
_ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl100