[akregator] [Bug 391865] Akregator allows feeds to gather data on article reading habits

[Jaak Ristioja]

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

--- Comment #3 from Jaak Ristioja  ---
It appears this has long been fixed with the silent introduction of the "Allow
feed to load external references from the internet" setting, i.e. by the
following and other related git commits?

*
https://invent.kde.org/pim/akregator/-/commit/9170d1e43786976bc47be8135e8cadbd4cb06ffe
*
https://invent.kde.org/pim/akregator/-/commit/08fbb24d4d5529924c3ce1a1cfe468dd0bf2b28b
*
https://invent.kde.org/pim/akregator/-/commit/434fe9db7ec933929fd3bda8e0577440e9caa628

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

[kmag] [Bug 438912] No output from KMagnifier on Wayland

[Jaak Ristioja]

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

--- Comment #11 from Jaak Ristioja  ---
I have regularly used KWin to inspect individual pixels, e.g. for GUI and web
design, when things need to be pixel-perfect. The KWin zoom functionality is
insufficient for this because it blurs the pixels, making it difficult to
inspect individual pixels and their boundaries. I think KMag also drew a
hairline grid between the different pixels when zoomed in.

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

[plasmashell] [Bug 466337] New: Plasma crashed when moving files from Desktop to Pictures folder in Dolphin

[Jaak Ristioja]

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

Bug ID: 466337
   Summary: Plasma crashed when moving files from Desktop to
Pictures folder in Dolphin
Classification: Plasma
   Product: plasmashell
   Version: 5.26.5
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.26.5)
 (Compiled from sources)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.0-gentoo x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 5.27.1 [KCrashBackend]

-- Information about the crash:
Using two click-drag selections, I selected a number of picture files on the
desktop and click-drag-moved them to the Pictures folder open in a Dolphin
window, and selected the move option from the popup menu. After this plasma
crashed.

As a somewhat unrelated issue but perhaps still noteworthy is that one of the
pictures I moved was also used as the desktop wallpaper. This also caused the
wallpaper to reset after restarting plasmashell.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x7f03f78b1783 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8  0x7f03f7864516 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9  0x7f03f784e7fb in __GI_abort () at abort.c:79
#10 0x7f03f7e929cf in qt_message_fatal (message=...,
context=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffd19b65468, msg=msg@entry=0x7f03f818b968 "ASSERT: \"%s\"
in file %s, line %d") at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qlogging.cpp:893
#12 0x7f03f7e917d2 in qt_assert(char const*, char const*, int)
(assertion=assertion@entry=0x7f03f8270fea "last < rowCount(parent)",
file=file@entry=0x7f03f8270a28
"/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/itemmodels/qabstractitemmodel.cpp",
line=line@entry=2815) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qglobal.cpp:3391
#13 0x7f03f7ead64e in QAbstractItemModel::beginRemoveRows(QModelIndex
const&, int, int) (this=0x55b2f00f4500, parent=, first=120,
last=120) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/itemmodels/qabstractitemmodel.cpp:2815
#14 0x7f03bd7d7f8b in Positioner::sourceRowsAboutToBeRemoved(QModelIndex
const&, int, int) (parent=, last=14, first=,
this=0x55b2f00f4500) at
/var/tmp/portage/kde-plasma/plasma-desktop-5.26.5-r2/work/plasma-desktop-5.26.5/containments/desktop/plugins/folder/positioner.cpp:626
#15 Positioner::sourceRowsAboutToBeRemoved(QModelIndex const&, int, int)
(this=0x55b2f00f4500, parent=, first=, last=14)
at
/var/tmp/portage/kde-plasma/plasma-desktop-5.26.5-r2/work/plasma-desktop-5.26.5/containments/desktop/plugins/folder/positioner.cpp:591
#16 0x7f03f80e73ae in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd19b656c0, r=0x55b2f00f4500, this=0x55b2f00c0750) 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
#17 doActivate(QObject*, int, void**) (sender=0x55b2f025a360,
signal_index=14, argv=0x7ffd19b656c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3923
#18 0x7f03f80e0717 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55b2f025a360, m=m@entry=0x7f03f83bfcc0
,
local_signal_index=local_signal_index@entry=11, argv=argv@entry=0x7ffd19b656c0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3983
#19 0x7f03f805c8a2 in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex
const&, int, int, QAbstractItemModel::QPrivateSignal)
(this=this@entry=0x55b2f025a360, _t1=..., _t2=, _t2@entry=5,
_t3=, _t3@entry=14, _t4=...) at
.moc/moc_qabstractitemmodel.cpp:600
#20 0x7f03f8064c32 in QAbstractItemModel::beginRemoveRows(QModelIndex
const&, int, int) (this=0x55b2f025a360, parent=..., first=5, last=14) at
/var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/itemmodels/qabstractitemmodel.cpp:2818
#21 0x7f03f8086ded in

[kate] [Bug 463194] Do not like the new Kwrite. Please revert back to 22.04.3.

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[kate] [Bug 464552] KWrite configure tab looks very strange in small windows and isn't usable

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[kate] [Bug 465007] New: Revert kwrite to be a single document program again

[Jaak Ristioja]

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

Bug ID: 465007
   Summary: Revert kwrite  to be a single document program again
Classification: Applications
   Product: kate
   Version: 22.12.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Please revert kwrite to be a single document program again, or add a feature to
configure this.

The switch to MDI in kwrite has turned out to be most problematic for these two
moves in my regular workflows:

1) The default keyboard shortcut Ctrl+N changed behavior and no longer means
"new window", but instead opens a new tab. This is very confusing. It can
probably be worked around by changing the shortcuts, but it was nevertheless
not a pleasant surprise. Ctrl+N has always been more of a "new window" shortcut
for me, probably also because of familiarity with web browsers where Ctrl+T is
usually for opening a new tab and Ctrl+N is for opening a new window. I also
know that Konsole/Yakuake have Ctrl+Shift+T as the shortcut (the extra Shift
modifier is probably needed so that regular Ctrl+Letter shortcuts can be passed
to the terminal). Can these defaults please be changed with Ctrl+N reverted to
its old semantics?

2) When I have a single document open, and I try to close kwrite, the "Save
documents" dialog no longer works as before. Having been a kwrite user for a
long time, I've always used the keyboard sequence of Alt+F4 to close kwrite,
Tab to focus the "Discard" button and Space/Enter/Return to activate the
choice, so this has been in my muscle memory. This no longer works in the new
dialog. The new dialog is also needlessly complex if I only use kwrite for
single documents and it took me a long time to actually understand all its
features. So the first 30 times or so when I needed to quickly close kwrite, I
greatly struggled to figure out the dialog, the action required and to actually
perform the needed interaction. I eventually resolved to using the mouse
(instead of my keyboard) to click the right button. This takes a lot of
precious seconds. While writing this bug report I discovered, I can use
Shift+Tab instead of just Tab (which I'm used to), so this will also take a lot
of additional time getting used to. Would it please be possible to reinstate
the old "Save document" dialog in case only one document is open?

I apologize in case this sounds like a rant. I'm actually very grateful and
much all your work, but I just really miss the old behavior. I believe the
above two issues can probably be solved in the context of MDI as well, so I'm
considering filing the above these in separate issue reports. But before I do I
must really ask this one question: can I have my old n̶o̶t̶e̶p̶a̶d̶ kwrite back 
again?
:-)

KDE already has Kate for MDI, so from a UI perspective: what was the rationale
behind making kwrite MDI as well?

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

[kmag] [Bug 438912] No output from KMagnifier on Wayland

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[filelight] [Bug 449688] Filelight crash on directory scan start

[Jaak Ristioja]

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

--- Comment #24 from Jaak Ristioja  ---
I can also confirm that the committed fix solves this issue. Thank you very
much! :-)

I'm using debug builds of Qt for mostly the same reasons: it helps debugging.
More specifically, I think I turned on USE=debug for Qt on my Gentoo system
when I was hacking on BibleTime code, which also uses Qt. I guess I was dealing
with some Qt intricacies which I hoped to solve that way.

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

[filelight] [Bug 449688] Filelight crash on directory scan start

[Jaak Ristioja]

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

--- Comment #16 from Jaak Ristioja  ---
Yes, possibly.

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

[step] [Bug 311264] Crash while deleting gas during simulation

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #7 from Jaak Ristioja  ---
Yes, it has been almost 10 years now. Reopening this for the third time
already. I didn't manage to get it to crash, but valgrind does show some ugly
stuff:

$ valgrind --track-origins=yes --trace-children=yes /usr/bin/step 
==5801== Memcheck, a memory error detector
==5801== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==5801== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==5801== Command: /usr/bin/step
==5801== 
==5850== Memcheck, a memory error detector
==5850== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==5850== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==5850== Command: /bin/sh -c gnuplot\ -\ 2\>/dev/null
==5850== 
==5850== 
==5850== HEAP SUMMARY:
==5850== in use at exit: 159,342 bytes in 1,208 blocks
==5850==   total heap usage: 1,363 allocs, 155 frees, 179,636 bytes allocated
==5850== 
==5850== LEAK SUMMARY:
==5850==definitely lost: 0 bytes in 0 blocks
==5850==indirectly lost: 0 bytes in 0 blocks
==5850==  possibly lost: 0 bytes in 0 blocks
==5850==still reachable: 159,342 bytes in 1,208 blocks
==5850== suppressed: 0 bytes in 0 blocks
==5850== Rerun with --leak-check=full to see details of leaked memory
==5850== 
==5850== For lists of detected and suppressed errors, rerun with: -s
==5850== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==5801== Conditional jump or move depends on uninitialised value(s)
==5801==at 0x4A932C6: KnownVariable::set(std::__cxx11::basic_string, std::allocator >) (Variable.cc:342)
==5801==by 0x4A95479:
KnownVariable::KnownVariable(std::__cxx11::basic_string, std::allocator >,
std::__cxx11::basic_string, std::allocator
>, std::__cxx11::basic_string,
std::allocator >, std::__cxx11::basic_string, std::allocator >, bool, bool, bool)
(Variable.cc:280)
==5801==by 0x4A3B26C: Calculator::loadDefinitions(char const*, bool, bool)
(Calculator-definitions.cc:1584)
==5801==by 0x4A59595:
Calculator::loadGlobalDefinitions(std::__cxx11::basic_string, std::allocator >) (Calculator-definitions.cc:130)
==5801==by 0x4A598E9: Calculator::loadGlobalVariables()
(Calculator-definitions.cc:143)
==5801==by 0x1C0483: UnitsCalc::UnitsCalc() (unitscalc.cc:63)
==5801==by 0x1C0654: UnitsCalc::self() (unitscalc.cc:38)
==5801==by 0x16BF9E: MainWindow::MainWindow() (mainwindow.cc:73)
==5801==by 0x15412B: main (main.cc:79)
==5801==  Uninitialised value was created by a heap allocation
==5801==at 0x48460E3: operator new(unsigned long) (vg_replace_malloc.c:422)
==5801==by 0x4A3B212: Calculator::loadDefinitions(char const*, bool, bool)
(Calculator-definitions.cc:1584)
==5801==by 0x4A59595:
Calculator::loadGlobalDefinitions(std::__cxx11::basic_string, std::allocator >) (Calculator-definitions.cc:130)
==5801==by 0x4A598E9: Calculator::loadGlobalVariables()
(Calculator-definitions.cc:143)
==5801==by 0x1C0483: UnitsCalc::UnitsCalc() (unitscalc.cc:63)
==5801==by 0x1C0654: UnitsCalc::self() (unitscalc.cc:38)
==5801==by 0x16BF9E: MainWindow::MainWindow() (mainwindow.cc:73)
==5801==by 0x15412B: main (main.cc:79)
==5801== 
QTextBrowser: No document for objinfo:World
QTextBrowser: No document for objinfo:World
QTextBrowser: No document for objinfo:Disk
==5801== Conditional jump or move depends on uninitialised value(s)
==5801==at 0xB4F9086:
QtWaylandClient::QWaylandInputDevice::Keyboard::keyboard_key(unsigned int,
unsigned int, unsigned int, unsigned int) (qwaylandinputdevice.cpp:1275)
==5801==by 0xBA4667D: ffi_call_unix64 (unix64.S:105)
==5801==by 0xBA459DE: ffi_call_int (ffi64.c:672)
==5801==by 0xB5EDCA0: wl_closure_invoke (connection.c:1025)
==5801==by 0xB5E9F89: dispatch_event.isra.0 (wayland-client.c:1595)
==5801==by 0xB5EB9CB: dispatch_queue (wayland-client.c:1741)
==5801==by 0xB5EB9CB: wl_display_dispatch_queue_pending
(wayland-client.c:1983)
==5801==by 0xB4F9D69: QtWaylandClient::QWaylandDisplay::flushRequests()
(qwaylanddisplay.cpp:253)
==5801==by 0x68D8F53: QObject::event(QEvent*) (qobject.cpp:1314)
==5801==by 0x59E0AF6: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(qapplication.cpp:3637)
==5801==by 0x68A9037: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1064)
==5801==by 0x68AC83D: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1821)
==5801==by 0x6903D06: postEventSourceDispatch(_GSource*, int (*)(void*),
void*) (qeventdispatcher_glib.cpp:277)
==5801==  Uniniti

[plasmashell] [Bug 459443] KDE unusable, crashes almost on every login

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #1 from Jaak Ristioja  ---


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

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

[frameworks-kwindowsystem] [Bug 455892] plasmashell crashes in KWindowSystem::stackingOrderChanged() every 5-10 minutes

[Jaak Ristioja]

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

--- Comment #4 from Jaak Ristioja  ---
*** Bug 459443 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 459443] New: KDE unusable, crashes almost on every login

[Jaak Ristioja]

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

Bug ID: 459443
   Summary: KDE unusable, crashes almost on every login
Classification: Plasma
   Product: plasmashell
   Version: 5.25.5
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.25.5)
 (Compiled from sources)
Qt Version: 5.15.5
Frameworks Version: 5.98.0
Operating System: Linux 5.19.9-gentoo x86_64
Windowing System: X11
Distribution: "Gentoo Base System release 2.8"
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
People using this shared desktop machine are  F U R I O U S  about KDE crashing
for more than 3 months.

KDE crash handler did not find duplicate.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x7f2cd8e8e443 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8  0x7f2cd8e41386 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9  0x7f2cd8e2b7f3 in __GI_abort () at abort.c:79
#10 0x7f2cd94919af in qt_message_fatal (message=...,
context=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffca8ec25a8, msg=msg@entry=0x7f2cd978a968 "ASSERT: \"%s\"
in file %s, line %d") at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:893
#12 0x7f2cd94907b2 in qt_assert(char const*, char const*, int)
(assertion=assertion@entry=0x7f2cd9874278 "from.isValid()",
file=file@entry=0x7f2cd9873d40
"/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp",
line=line@entry=623) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qglobal.cpp:3358
#13 0x7f2cd94ad79a in
QConcatenateTablesProxyModelPrivate::_q_slotDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, from=, to=, roles=) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp:623
#14 0x7f2cd96e5c44 in doActivate(QObject*, int, void**)
(sender=0x5556388f09a0, signal_index=3, argv=0x7ffca8ec2740) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3898
#15 0x7f2cd96df047 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x5556388f09a0, m=m@entry=0x7f2cd99bdcc0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffca8ec2740)
at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3946
#16 0x7f2cd965b1b0 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=this@entry=0x5556388f09a0,
_t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:558
#17 0x7f2cd9680400 in
QIdentityProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, topLeft=...,
bottomRight=, roles=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/itemmodels/qidentityproxymodel.cpp:507
#18 0x7f2cd96e5c44 in doActivate(QObject*, int, void**)
(sender=0x5556388f0b30, signal_index=3, argv=0x7ffca8ec28c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3898
#19 0x7f2cd96df047 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x5556388f0b30, m=m@entry=0x7f2cd99bdcc0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffca8ec28c0)
at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qobject.cpp:3946
#20 0x7f2cd965b1b0 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=this@entry=0x5556388f0b30,
_t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:558
#21 0x7f2ccd999084 in operator() (__closure=) at
/var/tmp/portage/kde-plasma/plasma-workspace-5.25.5-r2/work/plasma-workspace-5.25.5/libtaskmanager/xwindowtasksmodel.cpp:193
#22 QtPrivate::FunctorCall, QtPrivate::List<>, void,
TaskManager::XWindowTasksModel::Private::init():: >::call
(arg=, f=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#23
QtPrivate::Functor,
0>::call, void> 

[plasmashell] [Bug 455892] plasmashell crashes every 5-10 minutes

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

Version|5.25.1  |5.25.2

--- Comment #2 from Jaak Ristioja  ---
Also happens with Plasma 5.25.2.

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

[plasmashell] [Bug 455892] New: plasmashell crashes every 5-10 minutes

[Jaak Ristioja]

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

Bug ID: 455892
   Summary: plasmashell crashes every 5-10 minutes
   Product: plasmashell
   Version: 5.25.1
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: 1.0

STEPS TO REPRODUCE
1. Login into a KDE session
2. Do some stuff

OBSERVED RESULT
Shell disappears.

EXPECTED RESULT
Shell does not disappear. :)

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.1 
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

BACKTRACE(S):

(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7fca6408e503 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2  0x7fca640413a6 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7fca6402b7f3 in __GI_abort () at abort.c:79
#4  0x7fca64691977 in qt_message_fatal (message=...,
context=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/global/qlogging.cpp:1914
#5  QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffd1330e3e8, msg=msg@entry=0x7fca64989968 "ASSERT: \"%s\"
in file %s, line %d") at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/global/qlogging.cpp:893
#6  0x7fca64690782 in qt_assert(char const*, char const*, int)
(assertion=assertion@entry=0x7fca64a72d18 "from.isValid()",
file=file@entry=0x7fca64a727e0
"/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp",
line=line@entry=623) at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/global/qglobal.cpp:3358
#7  0x7fca646ad4f2 in
QConcatenateTablesProxyModelPrivate::_q_slotDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, from=, to=, roles=) at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp:623
#8  0x7fca648e5304 in doActivate(QObject*, int, void**)
(sender=0x55c071e077c0, signal_index=3, argv=0x7ffd1330e580) at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/kernel/qobject.cpp:3898
#9  0x7fca648de6d7 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55c071e077c0, m=m@entry=0x7fca64bbccc0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd1330e580)
at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/kernel/qobject.cpp:3946
#10 0x7fca6485a940 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=this@entry=0x55c071e077c0,
_t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:558
#11 0x7fca6487fac0 in
QIdentityProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, topLeft=...,
bottomRight=, roles=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/itemmodels/qidentityproxymodel.cpp:507
#12 0x7fca648e5304 in doActivate(QObject*, int, void**)
(sender=0x55c071e33320, signal_index=3, argv=0x7ffd1330e700) at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/kernel/qobject.cpp:3898
#13 0x7fca648de6d7 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55c071e33320, m=m@entry=0x7fca64bbccc0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd1330e700)
at
/var/tmp/portage/dev-qt/qtcore-5.15.4-r3/work/qtbase-everywhere-src-5.15.4/src/corelib/kernel/qobject.cpp:3946
#14 0x7fca6485a940 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=this@entry=0x55c071e33320,
_t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:558
#15 0x7fca5e689fc4 in operator() (__closure=) at
/var/tmp/portage/kde-plasma/plasma-workspace-5.25.1/work/plasma-workspace-5.25.1/libtaskmanager/xwindowtasksmodel.cpp:193
#16 QtPrivate::FunctorCall, QtPrivate::List<>, void,
TaskManager::XWindowTasksModel::Private::init():: >::call
(arg=, f=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#17
QtPrivate::Functor,
0>::call, void> (arg=, f=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#18
QtPrivate::QFunctorSlotObject,
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=, r=, a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#19 0x7fca648e52be in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd1330e8a0, r=0x55c071e33320, this=0x55c071dfdec0) at

[kwin] [Bug 415008] KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()

[Jaak Ristioja]

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

--- Comment #10 from Jaak Ristioja  ---
A lot has changed since, but I don't remember seeing this issue for a very long
while now. Might have been fixed by those merge requests. Thanks! :)

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

[filelight] [Bug 449688] Filelight crash on directory scan start

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

Version|21.12.2 |22.04.0

--- Comment #5 from Jaak Ristioja  ---
Updating the product version from 21.12.2, because it still happens with
22.04.0 as well, and I forgot to note this in my previous comment.

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

[filelight] [Bug 449688] Filelight crash on directory scan start

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #4 from Jaak Ristioja  ---
(In reply to Harald Sitter from comment #3)
> Git commit e873c3bfa2e6f971e1699a5377a0e46c7e363442 by Harald Sitter.

That does not seem to fix the issue. I still get the same crash after building
the Gentoo package with `git diff v22.04.0..e873c3b` applied as a user patch.
Did you perhaps mean to resolve another bug instead?

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

[filelight] [Bug 449688] Filelight crash on directory scan start

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|FIXED   |---

--- Comment #2 from Jaak Ristioja  ---
(In reply to Martin Sandsmark from comment #1)
> That stacktrace is weird, but the crash is an assert that is removed in qt6:
> https://code.qt.io/cgit/qt/qtbase.git/commit/
> ?id=ecfda98d1f91c6a7da0d89826558d856cd88e670

Yes.

> It seems like filelight is attempting to quit at the same time (thread 1, we
> got an ICE message about saving session), were you attempting to log out
> when it happened?

No.

> If so I assume there is an issue with QThreadPool not being nice if the
> application suddenly attempts to quit, which should be better in qt6.
> 
> If not, could you try running it with the glib event loop off (it's been
> buggy before), like so: «QT_NO_GLIB=1 filelight».

It seems to make not difference whether running with QT_NO_GLIB=1 or
QT_NO_GLIB=0 in the environment, or no QT_NO_GLIB environment variable at all.
In all these cases I can reproduce the exact same crash when starting to scan.

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

[filelight] [Bug 449688] New: Filelight crash on directory scan start

[Jaak Ristioja]

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

Bug ID: 449688
   Summary: Filelight crash on directory scan start
   Product: filelight
   Version: 21.12.2
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

SUMMARY

Filelight crashes when directory scanning is initiated.

STEPS TO REPRODUCE
Start `filelight .` from home directory. Alternatively start Filelight and
choose "Scan Home Folder" from the "Scan" menu.

OBSERVED RESULT
Crash

EXPECTED RESULT
Scanning starts properly

SOFTWARE/OS VERSIONS
Linux: 5.16
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

(gdb) thread apply all bt

Thread 13 (Thread 0x7fffc67fc640 (LWP 3732527) "Thread (pooled)"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x764a9da5 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=3, op=0, addr=0x55850c78) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qfutex_p.h:116
#2  QtLinuxFutex::futexWait >
(expectedValue=0x3, futex=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qfutex_p.h:135
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal (this=0x55850c78) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qmutex_linux.cpp:159
#5  0x764adcff in QMutexLocker::QMutexLocker (m=,
this=0x7fffc67fbce8) at
../../include/QtCore/../../../qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qmutex.h:238
#6  QThreadPoolThread::run (this=0x7fffcc006e80) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qthreadpool.cpp:84
#7  0x764a99d4 in QThreadPrivate::start (arg=0x7fffcc006e80) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qthread_unix.cpp:331
#8  0x757af256 in start_thread (arg=0x7fffc67fc640) at
pthread_create.c:481
#9  0x75f1c593 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7fffc6ffd640 (LWP 3732526) "Thread (pooled)"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x764a9da5 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=3, op=0, addr=0x55850c78) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qfutex_p.h:116
#2  QtLinuxFutex::futexWait >
(expectedValue=0x3, futex=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qfutex_p.h:135
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal (this=0x55850c78) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qmutex_linux.cpp:159
#5  0x764adcff in QMutexLocker::QMutexLocker (m=,
this=0x7fffc6ffcce8) at
../../include/QtCore/../../../qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qmutex.h:238
#6  QThreadPoolThread::run (this=0x7fffcc006970) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qthreadpool.cpp:84
#7  0x764a99d4 in QThreadPrivate::start (arg=0x7fffcc006970) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qthread_unix.cpp:331
#8  0x757af256 in start_thread (arg=0x7fffc6ffd640) at
pthread_create.c:481
#9  0x75f1c593 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7fffc77fe640 (LWP 3732525) "Thread (pooled)"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x764a9da5 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=3, op=0, addr=0x55850c78) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qfutex_p.h:116
#2  QtLinuxFutex::futexWait >
(expectedValue=0x3, futex=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/thread/qfutex_p.h:135
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at

[drkonqi] [Bug 433972] drkonqi fails to submit report complaining about token errors

[Jaak Ristioja]

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

--- Comment #4 from Jaak Ristioja  ---
(In reply to Harald Sitter from comment #3)
> Please add the following to your /etc/environment
> 
> QT_LOGGING_RULES="org.kde.drkonqi.*=true;kf.kio.kio_http=true"
> KDE_FORK_SLAVES=1

I added this to /etc/environment, started a new session, modified the kcalc
sources to get a crashing kcalc binary to invoke drkonqi, tried to file a bogus
bug report and succeeded in filing bug #434155 (i.e. the original issue did not
reproduce).

While I could probably "try more" to reproduce the bug in more similar
conditions that were present while this issue occurred, I don't think spamming
bugs.kde.org with more bogus reports would be tolerated.

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

[kcalc] [Bug 434155] Test bug report for #433972

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED

--- Comment #1 from Jaak Ristioja  ---
Resolving, as this was not supposed to reach bugs.kde.org.

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

[kcalc] [Bug 434155] New: Test bug report for #433972

[Jaak Ristioja]

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

Bug ID: 434155
   Summary: Test bug report for #433972
   Product: kcalc
   Version: 20.12.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Application: kcalc (20.12.3)
 (Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.79.0
Operating System: Linux 5.11.3-gentoo x86_64
Windowing System: X11
Drkonqi Version: 5.21.2
Distribution: "Gentoo Base System release 2.7"

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

Executed a rigged kcalc to get a DrKonqi window.

- Custom settings of the application:

I modified kcalc source code for it to segfault on startup.

The crash can be reproduced every time.

-- Backtrace:
Application: KCalc (kcalc), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f7411f52b40
(LWP 2116598))]
[KCrash Handler]
#6  QButtonGroup::setExclusive (this=0x69002f00650072,
exclusive=exclusive@entry=true) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/widgets/qbuttongroup.cpp:148
#7  0x7f741736c584 in KCalculator::KCalculator (this=0x561bf6b9e7c0,
parent=, __in_chrg=, __vtt_parm=)
at /var/tmp/portage/kde-apps/kcalc-20.12.3/work/kcalc-20.12.3/kcalc.cpp:105
#8  0x7f741736d54d in kdemain (argc=, argv=)
at /var/tmp/portage/kde-apps/kcalc-20.12.3/work/kcalc-20.12.3/kcalc.cpp:2434
#9  0x7f7417197dba in __libc_start_main (main=0x561bf4cde050 ,
argc=1, argv=0x7ffd53701118, init=, fini=,
rtld_fini=, stack_end=0x7ffd53701108) at ../csu/libc-start.c:314
#10 0x561bf4cde08a in _start ()
[Inferior 1 (process 2116598) detached]

Possible duplicates by query: bug 433533, bug 423951, bug 421576, bug 420134,
bug 419798.

Reported using DrKonqi

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

[drkonqi] [Bug 433972] drkonqi fails to submit report complaining about token errors

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #2 from Jaak Ristioja  ---
Gentoo.

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

[okular] [Bug 434104] Some PDF documents only display as white

[Jaak Ristioja]

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

--- Comment #3 from Jaak Ristioja  ---
Okay, it seems that the issue was due to the fact that app-text/poppler was
compiled without support for jpeg2k on my Gentoo system. I suppose the PDF
files had embedded jpeg2k in them. Recompiling poppler with USE="jpeg2k" seems
to have fixed this.

I wonder whether it were possible to add a warning notice about missing jpeg2k
support to Okular?

Either way, I apologize for being a burden.

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

[okular] [Bug 434104] Some PDF documents only display as white

[Jaak Ristioja]

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

--- Comment #2 from Jaak Ristioja  ---
I unchecked "Enable transparency effects", changed "Memory usage" from
"Aggressive" to "Low", unchecked "Enable Text Antialias", "Enable Graphics
Antialias" and "Enable Text Hinting" under "Rendering" and clicked "OK". This
didn't help, even after restarting Okular.

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

[okular] [Bug 434104] New: Some PDF documents only display as white

[Jaak Ristioja]

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

Bug ID: 434104
   Summary: Some PDF documents only display as white
   Product: okular
   Version: 20.12.3
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Some PDF documents only display white pages. The pages are of correct size, but
always just pure white. They seem to display just fine with xpdf thou.

Example file:
https://upload.wikimedia.org/wikipedia/commons/3/37/Jewish_Encyclopedia_Volume_1.pdf
(68M)
SHA512sum of file:
13d41a6fbf4a0ecfd693c327b1eb18519a666e130275687b38de490d4e74771f629abb3f283c7e0193a9a1eca43fab6d844615fc4940d406c0fa75aeea46e67d)

Most (but not all) of the other volumes of the Jewish Encyclopedia on Wikimedia
Commons seems to produce the same issue.

I've seen similar issues with scanned documents from other sources as well.


SOFTWARE/OS VERSIONS
Okular: 20.12.3
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

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

[drkonqi] [Bug 433972] New: drkonqi fails to submit report complaining about token errors

[Jaak Ristioja]

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

Bug ID: 433972
   Summary: drkonqi fails to submit report complaining about token
errors
   Product: drkonqi
   Version: 5.21.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

SUMMARY

When trying to submit a bug report via drkonqi, it complained about token
errors, exactly as in the screenshots given in #411983. Hitting the Retry
button just kept cycling between two error messages similar to those in the
aforementioned bug.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Happened right after #433971 when trying to report #433970.

Is the token bound to an IP address? I was using Tor as the system proxy, so my
outbound IP address via Tor might have changed between "logging in" and
submitting the bug report.

When it failed I would have liked to try to login again, but there was no way
to do that, because the UI provided no login interfaces, and the "back" button
was disabled.

I don't know for sure, but since all of this happened during the crash of an
essential KDE component (plasmashell) during login, I think I might have been
fortunate to be able to access other programs via krunner (including my browser
to report this), instead of my login session terminating or ending up with no
running programs besides the non-functioning drkonqi. I also saw no button in
drkonqi to try to restart the crashing program, just one to end the wizard. I
found this to be a bit scary.

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

[drkonqi] [Bug 433971] New: Focus keeps jumping from description to title field on keypress when writing bug summary

[Jaak Ristioja]

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

Bug ID: 433971
   Summary: Focus keeps jumping from description to title field on
keypress when writing bug summary
   Product: drkonqi
   Version: 5.21.2
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

SUMMARY

Today I was unable to comfortably write bug in DrKonqi. When filling in the
details of the issue (e.g. when it occurs, other related details etc), focus
jumped out of the text edit on every keypress I tried, jumping to the
title/summary line edit. So I had to type the issue description like
this to focus back on the correct widget after every keypress.


STEPS TO REPRODUCE
1. Focus on the summary
2. Try to type stuff

OBSERVED RESULT

On keypress, letter appears in text edit, but widget focus jumps to line edit
above.

EXPECTED RESULT

On keypress, letter appears in text edit, and widget focus does not jump to
other widget, so it were easier write multiple letters in succession in order
to form more complex structures like words and sentences :)

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Happened when attempting to report #433970 when it occurred.

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

[ksysguard] [Bug 433970] Plasmashell crashed on login

[Jaak Ristioja]

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

--- Comment #2 from Jaak Ristioja  ---
Ok, I think managed to get a functional shell after doing this:

  --- ../.config/plasma-org.kde.plasma.desktop-appletsrc2021-03-05
00:36:09.449977178 +0200
  +++ ../.config/plasma-org.kde.plasma.desktop-appletsrc2021-03-05
00:40:45.383973868 +0200
  @@ -397,39 +397,6 @@
   showName=false
   showTechnicalInfo=true

  -[Containments][64][Applets][133]
  -immutability=1
  -plugin=org.kde.plasma.systemmonitor
  -
  -[Containments][64][Applets][133][Configuration]
  -PreloadWeight=0
  -
  -[Containments][64][Applets][133][Configuration][Appearance]
  -chartFace=org.kde.ksysguard.barchart
  -title=Individual Core Usage
  -
  -[Containments][64][Applets][133][Configuration][SensorColors]
  -cpu/cpu0/TotalLoad=120,136,156
  -cpu/cpu0/usage=120,136,156
  -cpu/cpu1/TotalLoad=131,120,156
  -cpu/cpu1/usage=131,120,156
  -cpu/cpu2/TotalLoad=156,120,154
  -cpu/cpu2/usage=156,120,154
  -cpu/cpu3/TotalLoad=156,120,127
  -cpu/cpu3/usage=156,120,127
  -cpu/cpu4/TotalLoad=156,140,120
  -cpu/cpu4/usage=156,140,120
  -cpu/cpu5/TotalLoad=145,156,120
  -cpu/cpu5/usage=145,156,120
  -cpu/cpu6/TotalLoad=120,156,122
  -cpu/cpu6/usage=120,156,122
  -cpu/cpu7/TotalLoad=120,156,149
  -cpu/cpu7/usage=120,156,149
  -
  -[Containments][64][Applets][133][Configuration][Sensors]
  -highPrioritySensorIds=["cpu/cpu.*/usage"]
  -totalSensors=["cpu/all/usage"]
  -
   [Containments][64][Applets][138]
   immutability=1
   plugin=org.kde.plasma.systemloadviewer
  @@ -550,7 +517,7 @@
   PreloadWeight=0

   [Containments][64][General]
  -AppletOrder=85;91;93;67;92;101;68;133;74
  +AppletOrder=85;91;93;67;92;101;68;74

   [Containments][69]
   activityId=
  @@ -819,16 +786,6 @@
   plugin=org.kde.desktopcontainment
   wallpaperplugin=org.kde.image

  -[Containments][9][Applets][133][Configuration][SensorColors]
  -cpu/cpu0/TotalLoad=120,136,156
  -cpu/cpu1/TotalLoad=131,120,156
  -cpu/cpu2/TotalLoad=156,120,154
  -cpu/cpu3/TotalLoad=156,120,127
  -cpu/cpu4/TotalLoad=156,140,120
  -cpu/cpu5/TotalLoad=145,156,120
  -cpu/cpu6/TotalLoad=120,156,122
  -cpu/cpu7/TotalLoad=120,156,149
  -
   [Containments][9][Applets][134][Configuration][Appearance]
   chartFace=org.kde.ksysguard.linechart
   title=Line Chart

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

[ksysguard] [Bug 433970] Plasmashell crashed on login

[Jaak Ristioja]

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

--- Comment #1 from Jaak Ristioja  ---
(In reply to Jaak Ristioja from comment #0)
> The reporter is unsure if this crash is reproducible.

Scrap that. It crashes with this assertion every time, so it seems I'm
currently stuck with a barely functional desktop unless I perhaps find a way to
manually disable that buggy KSysGuard widget (whatever its name was).
Fortunately apps were still autostarted and krunner seems to work.

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

[ksysguard] [Bug 433970] New: Plasmashell crashed on login

[Jaak Ristioja]

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

Bug ID: 433970
   Summary: Plasmashell crashed on login
   Product: ksysguard
   Version: 5.21.2
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Plasmoid / Applet
  Assignee: ksysguard-b...@kde.org
  Reporter: j...@ristioja.ee
CC: plasma-b...@kde.org
  Target Milestone: ---

Application: plasmashell (5.21.2)
 (Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.79.0
Operating System: Linux 5.11.3-gentoo x86_64
Windowing System: X11
Drkonqi Version: 5.21.2 <--- BUT THAT DIDN'T WORK, so reporting via web browser
Distribution: "Gentoo Base System release 2.7"

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

I just upgraded to Plasma 5.21.2, rebooted my computer and logged in from my
display manager to the X11 plasma session.

- Unusual behavior I noticed:

The wallpapers and panels seemed to appear for a second, then everything went
black and the drkonqi window appeared.

- Custom settings of the application:

Judging by the backtrace, I suppose this has something to do with one of those
standard widgets on my Plasma panel which shows system metrics via KSysGuard?

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7eff4b132c80
(LWP 3214))]
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#7  0x7eff4ec75538 in __GI_abort () at abort.c:79
#8  0x7eff4f10f703 in qt_message_fatal (message=...,
context=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/global/qlogging.cpp:1914
#9  QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffdced07d08, msg=msg@entry=0x7eff4f3c07c8 "ASSERT: \"%s\"
in file %s, line %d") at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/global/qlogging.cpp:893
#10 0x7eff4f10e614 in qt_assert(char const*, char const*, int)
(assertion=assertion@entry=0x7eff4f4a4243 "first <= columnCount(parent)",
file=file@entry=0x7eff4f4a3c28
"/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/itemmodels/qabstractitemmodel.cpp",
line=line@entry=3062) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/global/qglobal.cpp:3358
#11 0x7eff4f126186 in QAbstractItemModel::beginInsertColumns(QModelIndex
const&, int, int) (this=0x55cc25a68850, parent=..., first=4, last=4) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/itemmodels/qabstractitemmodel.cpp:3062
#12 0x7eff404ed9fa in KSysGuard::SensorDataModel::onMetaDataChanged(QString
const&, KSysGuard::SensorInfo const&) (this=0x55cc25a68850, sensorId=...,
info=...) at
/var/tmp/portage/kde-plasma/libksysguard-5.21.2/work/libksysguard-5.21.2/sensors/SensorDataModel.cpp:403
#13 0x7eff4f32b68d in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdced07f70, r=0x55cc25a68850, this=0x55cc25a67c20) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate(QObject*, int, void**) (sender=0x7eff40504060
, signal_index=3,
argv=argv@entry=0x7ffdced07f70) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3886
#15 0x7eff4f3248ec in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7eff405033c0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdced07f70)
at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3946
#16 0x7eff404e9297 in
KSysGuard::SensorDaemonInterface::metaDataChanged(QString const&,
KSysGuard::SensorInfo const&) (this=, _t1=..., _t2=...) at
sensors/Sensors_autogen/EWIEGA46WW/moc_SensorDaemonInterface_p.cpp:172
#17 0x7eff404f8792 in operator() (self=,
__closure=0x55cc1f7adaa0) at
/var/tmp/portage/kde-plasma/libksysguard-5.21.2/work/libksysguard-5.21.2/sensors/SensorDaemonInterface.cpp:87
#18 QtPrivate::FunctorCall,
QtPrivate::List, void,
KSysGuard::SensorDaemonInterface::requestMetaData(const
QStringList&):: >::call (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#19 QtPrivate::Functor,
1>::call, void> (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#20
QtPrivate::QFunctorSlotObject, 1,
QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55cc1f7ada90, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#21 0x7eff4f32b68d in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdced080f0, 

[step] [Bug 311264] Crash while deleting gas during simulation

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #5 from Jaak Ristioja  ---
(In reply to Justin Zobel from comment #4)
> As it has been a while since this was reported, can you please test and
> confirm if this issue is still occurring or if this bug report can be marked
> as resolved.

How many times do I need to confirm? :D

I now got the following crash while trying to reproduce this. It didn't crash
immediately nor flicker or scroll, but when I tried to zoom out:

Application: Step (step), signal: Floating point exception
Content of s_kcrashErrorMessage: (null)
[KCrash Handler]
#6  0x7f4745936d13 in QStyle::sliderPositionFromValue (min=,
max=, logicalValue=, span=,
upsideDown=false) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/styles/qstyle.cpp:2269
#7  0x7f474593e0e2 in QCommonStyle::subControlRect (this=0x55e159cab000,
cc=, opt=0x7ffe5a47f0e0, sc=QStyle::SC_ScrollBarFirst,
widget=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/styles/qcommonstyle.cpp:4127
#8  0x7f474594f969 in QCommonStyle::drawComplexControl
(this=this@entry=0x55e159cab000, cc=cc@entry=QStyle::CC_ScrollBar,
opt=opt@entry=0x7ffe5a47f390, p=p@entry=0x7ffe5a47f388,
widget=widget@entry=0x55e159e3c380) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/styles/qcommonstyle.cpp:3352
#9  0x7f473e0d74a8 in Breeze::Style::drawScrollBarComplexControl
(this=0x55e159cab000, option=0x7ffe5a47f390, painter=0x7ffe5a47f388,
widget=0x55e159e3c380) at
/var/tmp/portage/kde-plasma/breeze-5.20.4/work/breeze-5.20.4/kstyle/breezestyle.cpp:6583
#10 0x7f473e0d6f10 in std::function::operator()(Breeze::Style const&, QStyleOptionComplex const*,
QPainter*, QWidget const*) const (__args#3=, __args#2=, __args#1=, __args#0=..., this=0x7ffe5a47f320) at
/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include/g++-v10/bits/std_function.h:248
#11 Breeze::Style::drawComplexControl (this=0x55e159cab000,
element=QStyle::CC_ScrollBar, option=0x7ffe5a47f390, painter=0x7ffe5a47f388,
widget=0x55e159e3c380) at
/var/tmp/portage/kde-plasma/breeze-5.20.4/work/breeze-5.20.4/kstyle/breezestyle.cpp:978
#12 0x7f4745a5bdb3 in QScrollBar::paintEvent (this=0x55e159e3c380) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/widgets/qscrollbar.cpp:540
#13 0x7f4745908c68 in QWidget::event (this=0x55e159e3c380,
event=0x7ffe5a47f580) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:9019
#14 0x7f47458c910f in QApplicationPrivate::notify_helper (this=, receiver=0x55e159e3c380, e=0x7ffe5a47f580) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3632
#15 0x7f4744e7af48 in QCoreApplication::notifyInternal2
(receiver=0x55e159e3c380, event=0x7ffe5a47f580) at
/var/tmp/portage/dev-qt/qtcore-5.15.2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1063
#16 0x7f4745900ed6 in QWidgetPrivate::sendPaintEvent
(this=this@entry=0x55e15a0a6450, toBePainted=...) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:5467
#17 0x7f4745901712 in QWidgetPrivate::drawWidget (this=0x55e15a0a6450,
pdev=0x55e15a0d9e50, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:5417
#18 0x7f4745902a2f in QWidgetPrivate::paintSiblingsRecursive
(this=this@entry=0x55e159e3c1c0, pdev=pdev@entry=0x55e15a0d9e50, siblings=...,
index=, rgn=..., offset=..., flags=..., sharedPainter=0x0,
repaintManager=0x55e15a355bf0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:5598
#19 0x7f474590142b in QWidgetPrivate::drawWidget (this=0x55e159e3c1c0,
pdev=0x55e15a0d9e50, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:5458
#20 0x7f4745902a2f in QWidgetPrivate::paintSiblingsRecursive
(this=0x55e159f86e80, pdev=0x55e15a0d9e50, siblings=..., index=,
rgn=..., offset=..., flags=..., sharedPainter=0x0,
repaintManager=0x55e15a355bf0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:5598
#21 0x7f474590284d in QWidgetPrivate::paintSiblingsRecursive
(this=this@entry=0x55e159f86e80, pdev=pdev@entry=0x55e15a0d9e50, siblings=...,
index=5, rg

[plasmashell] [Bug 363333] Processes started in yakuake terminals block indefinitely some time after switching to a different VT

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #7 from Jaak Ristioja  ---
This still occurs.

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

[krdc] [Bug 282297] support for spice protocol

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[systemsettings] [Bug 417548] New: System settings crash on navigation to item

[Jaak Ristioja]

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

Bug ID: 417548
   Summary: System settings crash on navigation to item
   Product: systemsettings
   Version: 5.17.5
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Application: systemsettings5 (5.17.5)
 (Compiled from sources)
Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.5.3-gentoo x86_64
Distribution: "Gentoo Base System release 2.6"

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

Opened system settings, search for "effects", navigated to "Workspace
Behavior", switched between pages using the left pane, hit "< All Settings" to
go back, searched for "compositor", clicked on "Display And Monitor".

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

Thread 5 (Thread 0x7f1634b64700 (LWP 9295)):
#0  0x7f1656f9465c in ?? ()
#1  0x7f1656f94798 in clock_gettime ()
#2  0x7f165524eef7 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f1634b63b20) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f165587f4b1 in qt_clock_gettime (ts=0x7f1634b63b20, clock=1) at
kernel/qelapsedtimer_unix.cpp:175
#4  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#5  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#6  0x7f165587e039 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f162c003fb0) at kernel/qtimerinfo_unix.cpp:91
#7  0x7f165587e415 in QTimerInfoList::timerWait (this=0x7f162c003fb0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#8  0x7f165587f894 in timerSourcePrepareHelper (src=,
timeout=timeout@entry=0x7f1634b63bf4) at kernel/qeventdispatcher_glib.cpp:138
#9  0x7f165587f93e in timerSourcePrepare (source=,
timeout=timeout@entry=0x7f1634b63bf4) at kernel/qeventdispatcher_glib.cpp:166
#10 0x7f165356f32e in g_main_context_prepare
(context=context@entry=0x7f162c060080, priority=priority@entry=0x7f1634b63c80)
at ../glib-2.60.7/glib/gmain.c:3499
#11 0x7f165356fcd6 in g_main_context_iterate
(context=context@entry=0x7f162c060080, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.60.7/glib/gmain.c:3907
#12 0x7f165356fecf in g_main_context_iteration (context=0x7f162c060080,
may_block=may_block@entry=1) at ../glib-2.60.7/glib/gmain.c:3988
#13 0x7f165587fb2b in QEventDispatcherGlib::processEvents
(this=0x7f162c006da0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7f16558243db in QEventLoop::exec (this=this@entry=0x7f1634b63dc0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#15 0x7f1655662218 in QThread::exec (this=this@entry=0x55c3061bc450) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#16 0x7f16547ba895 in QQmlThreadPrivate::run (this=0x55c3061bc450) at
qml/ftw/qqmlthread.cpp:155
#17 0x7f16556632ac in QThreadPrivate::start (arg=0x55c3061bc450) at
thread/qthread_unix.cpp:342
#18 0x7f1653ddf497 in start_thread (arg=) at
pthread_create.c:486
#19 0x7f165523f0df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f164ceae700 (LWP 9189)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x55c2fe67f028) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55c2fe67efd8,
cond=0x55c2fe67f000) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55c2fe67f000, mutex=0x55c2fe67efd8) at
pthread_cond_wait.c:655
#3  0x7f164d5175cb in cnd_wait (mtx=0x55c2fe67efd8, cond=0x55c2fe67f000) at
../mesa-19.2.8/include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x55c2fe558bb0) at
../mesa-19.2.8/src/util/u_queue.c:272
#5  0x7f164d5171e7 in impl_thrd_routine (p=) at
../mesa-19.2.8/include/c11/threads_posix.h:87
#6  0x7f1653ddf497 in start_thread (arg=) at
pthread_create.c:486
#7  0x7f165523f0df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f164f377700 (LWP 9188)):
#0  0x7f1653540837 in g_ptr_array_set_size (array=0x55c2fe20da80,
length=length@entry=0) at ../glib-2.60.7/glib/garray.c:1205
#1  0x7f165356f21a in g_main_context_prepare
(context=context@entry=0x7f164c20, priority=priority@entry=0x7f164f376c60)
at ../glib-2.60.7/glib/gmain.c:3470
#2  0x7f165356fcd6 in g_main_context_iterate
(context=context@entry=0x7f164c20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.60.7/glib/gmain.c:3907
#3  0x7f165356fecf in g_main_context_iteration (context=0x7f164c20,
may_block=may_block@entry=1) at ../glib-2.60.7/glib/gmain.c:3988

[plasmashell] [Bug 415686] Clicking on "Digital Clock" widget to display calendar crashes Plasma shell

[Jaak Ristioja]

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

--- Comment #1 from Jaak Ristioja  ---
Output when running plasmashell from a terminal:

$ plasmashell 
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_solid_actions.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kwinrules.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kontact_akregatorplugin.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/korg_datenums.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kipiplugin_printimages.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/rawthumbnail.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kamera.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kio.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/dolphinpart.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kopete_otr.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kcm_dolphinviewmodes.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/powerdevildpmsaction_config.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/jpegthumbnail.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/plasma_runner_marble.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/miloutextplugin.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kwinoptions.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kcm_kopete_accountconfig.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/korganizerpart.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_hotkeys.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kgraphviewerpart.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kontact_todoplugin.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/powerdevilsuspendsessionaction_config.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kipiplugin_kmlexport.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_fontinst.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kopete_emailwindow.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/libaudiocd_encoder_vorbis.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kopete_privacy.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kopete_texteffect.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kcm_kget_mirrorsearchfactory.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/krunner_activities.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/krossmodulekdetranslation.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_knote.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kded_printmanager.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/krunner_datetime.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/exrthumbnail.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kontact_specialdatesplugin.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kleopatra.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_keyboard.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kritathumbnail.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kopete_privacy.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/libkcm_kdf.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kipiplugin_sendimages.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_cddb.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kipiplugin_flickr.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_opengl.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_k3blameencoder.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kopete_otr.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/krunner_services.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kontact_korganizerplugin.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/sambausershareplugin.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kcm_kopete_pluginconfig.so"
org.kde.plasma: invalid metadata
"/usr/lib64/qt5/plugins/kcm_krunner_dictionary.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_kopete_latex.so"
org.kde.plasma: invalid metadata "/usr/lib64/qt5/plugins/kcm_trash.so"
org.kde.plasma: invalid metadata "/usr/lib64

[plasmashell] [Bug 415686] New: Clicking on "Digital Clock" widget to display calendar crashes Plasma shell

[Jaak Ristioja]

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

Bug ID: 415686
   Summary: Clicking on "Digital Clock" widget to display calendar
crashes Plasma shell
   Product: plasmashell
   Version: 5.17.4
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@ristioja.ee
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.4)
 (Compiled from sources)
Qt Version: 5.14.0
Frameworks Version: 5.65.0
Operating System: Linux 5.4.6-gentoo x86_64
Distribution: "Gentoo Base System release 2.6"

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

When clicking on the "Digital Clock" widget on the bottom panel in order to
display the calendar, it crashes instead.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fecc8c38080 (LWP 2948))]

Thread 12 (Thread 0x7fec959ec700 (LWP 79957)):
#0  0x7fecce63bf55 in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55f8bfb37624) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fecce63bf55 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f8bfb375d0, cond=0x55f8bfb375f8) at pthread_cond_wait.c:502
#2  0x7fecce63bf55 in __pthread_cond_wait (cond=0x55f8bfb375f8,
mutex=0x55f8bfb375d0) at pthread_cond_wait.c:655
#3  0x7feccf8cefeb in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55f8bfb375d0) at thread/qwaitcondition_unix.cpp:146
#4  0x7feccf8cefeb in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x7fecc0017670, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7feccf8cf0c9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x7fecc0017678, mutex=mutex@entry=0x7fecc0017670,
time=time@entry=18446744073709551615) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#6  0x7fecd16b876d in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x7fecc0017668) at scenegraph/qsgthreadedrenderloop.cpp:255
#7  0x7fecd16b876d in QSGRenderThread::processEventsAndWaitForMore()
(this=0x7fecc00175d0) at scenegraph/qsgthreadedrenderloop.cpp:905
#8  0x7fecd16b8989 in QSGRenderThread::run() (this=0x7fecc00175d0) at
scenegraph/qsgthreadedrenderloop.cpp:1000
#9  0x7feccf8c8f4c in QThreadPrivate::start(void*) (arg=0x7fecc00175d0) at
thread/qthread_unix.cpp:342
#10 0x7fecce635497 in start_thread (arg=) at
pthread_create.c:486
#11 0x7feccf4a30df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7fec977fe700 (LWP 3182)):
#0  0x7fecce63bf55 in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55f8bd652d84) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fecce63bf55 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f8bd652d30, cond=0x55f8bd652d58) at pthread_cond_wait.c:502
#2  0x7fecce63bf55 in __pthread_cond_wait (cond=0x55f8bd652d58,
mutex=0x55f8bd652d30) at pthread_cond_wait.c:655
#3  0x7feccf8cefeb in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55f8bd652d30) at thread/qwaitcondition_unix.cpp:146
#4  0x7feccf8cefeb in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x55f8bd4f9570, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7feccf8cf0c9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x55f8bd4f9578, mutex=mutex@entry=0x55f8bd4f9570,
time=time@entry=18446744073709551615) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#6  0x7fecd16b876d in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x55f8bd4f9568) at scenegraph/qsgthreadedrenderloop.cpp:255
#7  0x7fecd16b876d in QSGRenderThread::processEventsAndWaitForMore()
(this=0x55f8bd4f94d0) at scenegraph/qsgthreadedrenderloop.cpp:905
#8  0x7fecd16b8989 in QSGRenderThread::run() (this=0x55f8bd4f94d0) at
scenegraph/qsgthreadedrenderloop.cpp:1000
#9  0x7feccf8c8f4c in QThreadPrivate::start(void*) (arg=0x55f8bd4f94d0) at
thread/qthread_unix.cpp:342
#10 0x7fecce635497 in start_thread (arg=) at
pthread_create.c:486
#11 0x7feccf4a30df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7fec97fff700 (LWP 3083)):
#0  0x7fecce63bf55 in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55f8bcee32b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fecce63bf55 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f8bcee3260, cond=0x55f8bcee3288) at pthread_cond_wait.c:502
#2  0x7fecce63bf55 in __pthread_cond_wait (cond=0x55f8bcee3288,
mutex=0x55f8bcee3260) at pthread_cond_wait.c:655
#3  

[kwin] [Bug 415008] KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()

[Jaak Ristioja]

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

--- Comment #2 from Jaak Ristioja  ---
(In reply to David Edmundson from comment #1)
> But it is active inside peekQueue?

When I attached to the process with GDB I got this backtrace, and ran some
number of "finish" commands, until it the command no longer returned. The stack
frame which did not return was QXcbConnection::getTimestamp() unless I
misinterpreted the output.

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

[kwin] [Bug 415008] New: KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()

[Jaak Ristioja]

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

Bug ID: 415008
   Summary: KWin-5.17.4 hangs inside loop in
QXcbConnection::getTimestamp()
   Product: kwin
   Version: 5.17.4
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-x11-standalone
  Assignee: kwin-bugs-n...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---
 Flags: X11+

SYMPTOMS

KWin hangs randomly, consuming 100% CPU.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Gentoo Linux, kde-plasma/kwin-5.17.4
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
libxcb: x11-libs/libxcb-1.13.1
X11: x11-base/xorg-server-1.20.5


ADDITIONAL INFORMATION

I've only recently started seeing this issue (3-4 times in the last 6 days), I
suspect this to be a regression introduced in -5.17.4.

Thread 1 (Thread 0x7f22ee85ce00 (LWP 203769)):
#0  0x7f22edfecd94 in
QXcbEventQueue::peek > [inline] (option=QXcbEventQueue::PeekRemoveMatch, peeker=...,
this=0x55cab6a65ab0) at qxcbconnection.cpp:783
#1  0x7f22edfecd94 in
QXcbEventQueue::peek > [inline] (peeker=..., this=0x55cab6a65ab0) at qxcbeventqueue.h:97
#2  0x7f22edfecd94 in QXcbConnection::getTimestamp() (this=0x55cab6a56390)
at qxcbconnection.cpp:782
#3  0x7f22ee00e042 in QXcbNativeInterface::getTimestamp(QXcbScreen const*)
(this=this@entry=0x55cab6a508c0, screen=screen@entry=0x55cab6a562b0) at
qxcbobject.h:53
#4  0x7f22ee00f21b in
QXcbNativeInterface::nativeResourceForScreen(QByteArray const&, QScreen*)
(this=this@entry=0x55cab6a508c0, resourceString=...,
screen=screen@entry=0x55cab6a7a110) at qxcbnativeinterface.cpp:186
#5  0x7f22f9d13be8 in QX11Info::getTimestamp() () at qx11info_x11.cpp:302
#6  0x7f22ec413d00 in KWin::X11StandalonePlatform::updateXTime()
(this=) at /usr/include/qt5/QtCore/qcoreapplication.h:116
#7  0x7f22fa056860 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
(this=0x55cab6b18f00, e=0x7f22e8003600) at
/var/tmp/portage/kde-plasma/kwin-5.17.4/work/kwin-5.17.4/events.cpp:285
#8  0x7f22f8e57334 in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=, eventType=..., message=message@entry=0x7f22e8003600,
result=result@entry=0x7fff42ca2eb8) at kernel/qabstracteventdispatcher.cpp:484
#9  0x7f22edfee3d0 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0x55cab6a56390, event=event@entry=0x7f22e8003600) at
qxcbnativeinterface.h:101
#10 0x7f22edfef136 in
QXcbConnection::processXcbEvents(QFlags)
(this=0x55cab6a56390, flags=...) at qxcbconnection.cpp:1021
#11 0x7f22ee01a36c in
QXcbUnixEventDispatcher::processEvents(QFlags)
(this=0x55cab6aad9c0, flags=...) at qxcbeventdispatcher.cpp:61
#12 0x7f22f8e58a8a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff42ca3010, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#13 0x7f22f8e614e2 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#14 0x7f22fa423b17 in kdemain(int, char**) (argc=,
argv=0x7fff42ca32a8) at
/var/tmp/portage/kde-plasma/kwin-5.17.4/work/kwin-5.17.4/main_x11.cpp:474
#15 0x7f22fa26ce3b in __libc_start_main (main=0x55cab5b2c060 ,
argc=1, argv=0x7fff42ca32a8, init=, fini=,
rtld_fini=, stack_end=0x7fff42ca3298) at ../csu/libc-start.c:308
#16 0x55cab5b2c09a in _start ()

Investigation of the hanged kwin_x11 process with GDB has shown that
QXcbConnection::getTimestamp() never returns.

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

[systemsettings] [Bug 405023] systemsettings crashes when double clicking an item in icon view

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #3 from Jaak Ristioja  ---
Kirigami has always been installed, and was at version 5.55.0 when this crash
occurred.

Since it has been a while and Gentoo is a rolling-release distribution, so I'm
already using sytemsettings 5.17.1 and Kirigami 5.63.0, and I'm now unable to
reproduce this crash.

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

[drkonqi] [Bug 410636] Crash handler crash on login in QString::size()

[Jaak Ristioja]

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

--- Comment #4 from Jaak Ristioja  ---
(In reply to Harald Sitter from comment #3)
> - install systemd-coredump

I'm not using systemd so I don't think this will be an option. However, I think
I could still use the gcore command-line utility to generate a core dump (or
attach GDB to the crashed process and use the gcore command).

> - restart and trigger the bug

...if it triggers. Because I haven't seen it lately. I also tried logging in
and out again (+ killall -u username -9) multiple times, but I couldn't
reproduce it.

> It's a long shot but the crash may be a symptom of something else. The code
> in question to do with QStringList, while involving pointers, should not
> really be able to crash, certainly not while the qapplication loop is still
> running. So, I wouldn't even begin to figure out what is wrong without
> patching Qt and seeing what happens.
> From related bugs I could find it looks like this crash appears seemingly
> randomly and then disappears again and has no discernible pattern beyond the
> top most stack frame being the QStringList contains.

I'll make sure to investigate for any other signs such if it reoccurs.

Do you have any references to similar bug reports? Do you think it is a drkonqi
issue or rather a Qt issue (e.g. perhaps something similar to QTBUG-39285)?

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

[drkonqi] [Bug 410636] Crash handler crash on login in QString::size()

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #2 from Jaak Ristioja  ---
(In reply to Harald Sitter from comment #1)
> I am guessing this isn't reproducible?

Why do you think so?

After reporting this, I've seen the crash notification for drkonqi appear after
login at least 2-3 times, but I didn't investigate any further as this was not
a blocker. Are there any other details you want me to investigate if this
happens again?

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

[drkonqi] [Bug 410636] New: Crash handler crash on login in QString::size()

[Jaak Ristioja]

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

Bug ID: 410636
   Summary: Crash handler crash on login in QString::size()
   Product: drkonqi
   Version: 5.16.4
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

SUMMARY

Crash handler crashed immediately on login.


STEPS TO REPRODUCE (didn't yet try to reproduce)
1. Enter login password in SDDM
2. Press ENTER
3. Wait a few moments for crash notification box to appear

OBSERVED RESULT

Crash notification box appears. When I click on its button I get the crash
handler dialog with the text:

  We are sorry, the KDE Crash Handler closed unexpectedly.

  As the Crash handler itself has failed, the automatic reporting process is
disabled to reduce the risks of failing again.

  Please, manually report this error to the KDE bug tracking system. Do not
forget to include the backtrace from the Developer Information tab.

  Details:
  Executable: drkonqi PID: 3237 Signal: Segmentation fault (11) Time: 06.08.19
09:24:57

Application: The KDE Crash Handler (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f14d5d0c780 (LWP 3237))]

Thread 3 (Thread 0x7f14d0a44700 (LWP 3241)):
#0  0x7f14dab5c9f6 in g_source_iter_next (iter=iter@entry=0x7f14d0a43c20,
source=source@entry=0x7f14d0a43c18) at
/var/tmp/portage/dev-libs/glib-2.58.3-r1/work/glib-2.58.3/glib/gmain.c:983
#1  0x7f14dab5f39f in g_main_context_check
(context=context@entry=0x7f14c4000bf0, max_priority=2147483647,
fds=fds@entry=0x7f14c4004db0, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.58.3-r1/work/glib-2.58.3/glib/gmain.c:944
#2  0x7f14dab5fa30 in g_main_context_iterate
(context=context@entry=0x7f14c4000bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.58.3-r1/work/glib-2.58.3/glib/gmain.c:3917
#3  0x7f14dab5fbac in g_main_context_iteration (context=0x7f14c4000bf0,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.58.3-r1/work/glib-2.58.3/glib/gmain.c:3981
#4  0x7f14dd42520b in QEventDispatcherGlib::processEvents
(this=0x7f14c4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f14dd3ccc4b in QEventLoop::exec (this=this@entry=0x7f14d0a43df0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f14dd2272d6 in QThread::exec (this=this@entry=0x7f14de334060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f14de2a3d05 in QDBusConnectionManager::run (this=0x7f14de334060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f14dd228614 in QThreadPrivate::start (arg=0x7f14de334060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
#9  0x7f14dc0c6408 in start_thread (arg=) at
pthread_create.c:486
#10 0x7f14dcc1f73f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f14d2eef700 (LWP 3239)):
#0  0x7f14dcc13473 in __GI___poll (fds=0x7f14d2eeed18, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f14da6128f7 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f14da614a1a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f14d54c0f68 in QXcbEventQueue::run (this=0x56366d4aabe0) at
qxcbeventqueue.cpp:228
#4  0x7f14dd228614 in QThreadPrivate::start (arg=0x56366d4aabe0) at
thread/qthread_unix.cpp:361
#5  0x7f14dc0c6408 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f14dcc1f73f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f14d5d0c780 (LWP 3237)):
[KCrash Handler]
#7  0x7f14dd2ba2fd in QString::size (this=0x7ffdebf4cc20) at
../../include/QtCore/../../src/corelib/tools/qstring.h:239
#8  stringList_contains (cs=cs@entry=Qt::CaseSensitive, str=...,
stringList=...) at tools/qstringlist.cpp:319
#9  QtPrivate::QStringList_contains (that=that@entry=0x7f14c4003f98, str=...,
cs=cs@entry=Qt::CaseSensitive) at tools/qstringlist.cpp:343
#10 0x7f14de2ad67a in QStringList::contains (cs=Qt::CaseSensitive, str=...,
this=0x7f14c4003f98) at
../../include/QtCore/../../src/corelib/tools/qstringlist.h:225
#11 QDBusConnectionPrivate::isServiceRegisteredByThread (serviceName=...,
this=0x7f14c4003f10) at qdbusintegrator.cpp:2593
#12 QDBusConnectionPrivate::isServiceRegisteredByThread (this=0x7f14c4003f10,
serviceName=...) at qdbusintegrator.cpp:2585
#13 0x7f14de2b6c3c in QDBusConnectionPrivate::sendWithReplyAsync
(this=0x7f14c4003f10, message=..., receiver=receiver@entry=0x0,
returnMethod=returnMethod@entry=0x0, 

[systemsettings] [Bug 405023] systemsettings crashes when double clicking an item in icon view

[Jaak Ristioja]

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

--- Comment #1 from Jaak Ristioja  ---
Created attachment 118501
  --> https://bugs.kde.org/attachment.cgi?id=118501=edit
Screenshot of transparent window

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

[systemsettings] [Bug 405023] New: systemsettings crashes when double clicking an item in icon view

[Jaak Ristioja]

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

Bug ID: 405023
   Summary: systemsettings crashes when double clicking an item in
icon view
   Product: systemsettings
   Version: 5.15.2
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Application: systemsettings5 (5.15.2)
 (Compiled from sources)
Qt Version: 5.12.1
Frameworks Version: 5.55.0
Operating System: Linux 4.20.13-gentoo x86_64
Distribution: "Gentoo Base System release 2.6"

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

I think I upgraded qt/kde/plasma before a reboot.

1) Started "systemsettings5"
2) Double clicked on "Workspace theme" or "Desktop Behavior"

- Unusual behavior I noticed:

Desktop wallpaper was missing on login, and when I right-clicked the desktop
and chose "Configure Desktop", a window titled "Desktop Settings - Plasma" with
literally no contents appears, only a border/frame. So that when something
behind that window redraws itself, e.g. when I'm typing this text, it also
appears within the border, i.e. the window is completely transparent.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f780d9ef700 (LWP 3376)):
#0  0x7f783612ab10 in __GI___libc_read (fd=15,
buf=buf@entry=0x7f780d9eeb90, nbytes=nbytes@entry=16) at
../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f782f703b40 in read (__nbytes=16, __buf=0x7f780d9eeb90,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f78180039a0) at
/var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4/glib/gwakeup.c:210
#3  0x7f782f6b3977 in g_main_context_check
(context=context@entry=0x7f7808000bf0, max_priority=2147483647,
fds=fds@entry=0x7f7808004a00, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4/glib/gmain.c:3680
#4  0x7f782f6b3e30 in g_main_context_iterate
(context=context@entry=0x7f7808000bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4/glib/gmain.c:3899
#5  0x7f782f6b3fcc in g_main_context_iteration (context=0x7f7808000bf0,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4/glib/gmain.c:3963
#6  0x7f7836acc5cb in QEventDispatcherGlib::processEvents
(this=0x7f7808000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#7  0x7f7836a7408b in QEventLoop::exec (this=this@entry=0x7f780d9eedc0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#8  0x7f78368cf546 in QThread::exec (this=this@entry=0x561f98824000) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#9  0x7f783476ec95 in QQmlThreadPrivate::run (this=0x561f98824000) at
qml/ftw/qqmlthread.cpp:148
#10 0x7f78368d0884 in QThreadPrivate::start (arg=0x561f98824000) at
thread/qthread_unix.cpp:361
#11 0x7f7831b0296a in start_thread (arg=0x7f780d9ef700) at
pthread_create.c:463
#12 0x7f783613af4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f781e38c700 (LWP 3374)):
#0  0x7f7831b094fc in futex_wait_cancelable (private=,
expected=0, futex_word=0x561f9872a928) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x561f9872a8d8,
cond=0x561f9872a900) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x561f9872a900, mutex=0x561f9872a8d8) at
pthread_cond_wait.c:655
#3  0x7f781ebb76bb in cnd_wait (mtx=0x561f9872a8d8, cond=0x561f9872a900) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x561f986a9c50) at
../mesa-18.2.8/src/util/u_queue.c:256
#5  0x7f781ebb7347 in impl_thrd_routine (p=) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:87
#6  0x7f7831b0296a in start_thread (arg=0x7f781e38c700) at
pthread_create.c:463
#7  0x7f783613af4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f7825171700 (LWP 3373)):
#0  0x7f783612ab10 in __GI___libc_read (fd=7, buf=buf@entry=0x7f7825170b80,
nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f782f703b40 in read (__nbytes=16, __buf=0x7f7825170b80,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x561f9858dfb0) at
/var/tmp/portage/dev-libs/glib-2.56.4/work/glib-2.56.4/glib/gwakeup.c:210
#3  0x7f782f6b3977 in g_main_context_check
(context=context@entry=0x7f7818000bf0, max_priority=2147483647,
fds=fds@entry=0x7f7818004db0, n_fds=n_fds@entry=1) at

[plasmashell] [Bug 363333] Processes started in yakuake terminals block indefinitely some time after switching to a different VT

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
   Target Milestone|--- |1.0
Product|yakuake |plasmashell
 Resolution|WAITINGFORINFO  |---
 CC||plasma-b...@kde.org
   Assignee|h...@kde.org|k...@davidedmundson.co.uk
  Component|general |general
Version|3.0.2   |5.14.2

--- Comment #5 from Jaak Ristioja  ---
It seems that this is not yakuake-specific after all. Now even other GUI
processes hang when left in inactive VT.

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

[knetwalk] [Bug 292032] KNetWalk 3.0.1 potential integer overflow, score cheat and division by zero crash

[Jaak Ristioja]

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

--- Comment #6 from Jaak Ristioja  ---
(In reply to Albert Astals Cid from comment #5)
> Because it's a waste of everyones time. Let's say you can click ten times
> per second, you need to be clicking at that rate during 7 years to make the
> counter wrap.

Alrighty. But how about the division-by-zero in the same place if one solves an
Easy (5x5) board in before the first second elapses (given one can also pause
the game)? It only seems to take 20 clicks or so. :D

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

[knetwalk] [Bug 292032] KNetWalk 3.0.1 potential integer overflow, score cheat and division by zero crash

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|NOT A BUG   |---

--- Comment #4 from Jaak Ristioja  ---
I agree, but if you continue clicking, and then it eventually wraps from
negative to positive again, which might yield in positive scores.

So if the program survives the undefined behavior of the integer overflow, it
is followed by ever more undefined behavior in MainWindow::gameOver(), e.g.
-NaN not being in the range of representative values values for int, and a
division by zero. :)

Why not just add guard to keep the overflow from happening and call it "game
over: too many moves"?

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

[knetwalk] [Bug 292032] KNetWalk 3.0.1 potential integer overflow, score cheat and division by zero crash

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #2 from Jaak Ristioja  ---
Yes, the bug still seems to be there:

https://cgit.kde.org/knetwalk.git/tree/src/mainwindow.cpp#n271

Although commit abe2f6ab1fb3c60d45cc8a2ce8d108ef2ae6cef5 changed the method
name to rotationStarted() instead.

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

[plasmashell] [Bug 400533] New: Plasma crash when dragging folder on desktop

[Jaak Ristioja]

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

Bug ID: 400533
   Summary: Plasma crash when dragging folder on desktop
   Product: plasmashell
   Version: 5.14.2
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@ristioja.ee
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.14.2)
 (Compiled from sources)
Qt Version: 5.11.2
Frameworks Version: 5.51.0
Operating System: Linux 4.19.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.4.1"

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

Started dragging a folder (didn't drop) on the desktop which shows the desktop
folder on top of the background picture.

- Custom settings of the application:

It seems like the desktop is configured as a folder view to show the Desktop
folder of the user.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f28f198e800 (LWP 2799))]

Thread 5 (Thread 0x7f28a8832700 (LWP 3036)):
#0  0x7f28eac03ea0 in __GI___libc_read (fd=27,
buf=buf@entry=0x7f28a8831b20, nbytes=nbytes@entry=16) at
../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f28e4ed85c0 in read (__nbytes=16, __buf=0x7f28a8831b20,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f28b4003d80) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gwakeup.c:210
#3  0x7f28e4e8927b in g_main_context_check
(context=context@entry=0x7f28a4000bf0, max_priority=2147483647,
fds=fds@entry=0x7f28a4006450, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3750
#4  0x7f28e4e89740 in g_main_context_iterate
(context=context@entry=0x7f28a4000bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3969
#5  0x7f28e4e898dc in g_main_context_iteration (context=0x7f28a4000bf0,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4033
#6  0x7f28eb5cdc5b in QEventDispatcherGlib::processEvents
(this=0x7f28a4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#7  0x7f28eb5662bb in QEventLoop::exec (this=this@entry=0x7f28a8831d60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#8  0x7f28eb38579a in QThread::exec (this=this@entry=0x56527e3d0360) at
thread/qthread.cpp:525
#9  0x7f28a9cbfbf7 in KCupsConnection::run (this=0x56527e3d0360) at
/var/tmp/portage/kde-apps/print-manager-18.08.2/work/print-manager-18.08.2/libkcups/KCupsConnection.cpp:304
#10 0x7f28eb393896 in QThreadPrivate::start (arg=0x56527e3d0360) at
thread/qthread_unix.cpp:367
#11 0x7f28e7df49aa in start_thread (arg=0x7f28a8832700) at
pthread_create.c:463
#12 0x7f28eac142ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f28c7fff700 (LWP 2970)):
#0  0x7f28e7dfb55c in futex_wait_cancelable (private=,
expected=0, futex_word=0x56527b518d44) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x56527b518cf0,
cond=0x56527b518d18) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x56527b518d18, mutex=0x56527b518cf0) at
pthread_cond_wait.c:655
#3  0x7f28d088398b in cnd_wait (mtx=0x56527b518cf0, cond=0x56527b518d18) at
/var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x56527b3bafa0) at
/var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/src/util/u_queue.c:255
#5  0x7f28d0883617 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/include/c11/threads_posix.h:87
#6  0x7f28e7df49aa in start_thread (arg=0x7f28c7fff700) at
pthread_create.c:463
#7  0x7f28eac142ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f28d37c9700 (LWP 2880)):
#0  __libc_disable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:96
#1  0x7f28eac087d7 in __GI___poll (fds=, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#2  0x7f28e4e89799 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f28c8004a00, timeout=, context=0x7f28c8000bf0)
at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4271
#3  g_main_context_iterate (context=context@entry=0x7f28c8000bf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3967
#4  0x7f28e4e898dc in g_main_context_iteration (context=0x7f28c8000bf0,
may_block=may_block@entry=1) at

[step] [Bug 311264] Crash while deleting gas during simulation

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

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

--- Comment #2 from Jaak Ristioja  ---
Still happens on Gentoo Linux with kde-apps/step-18.08.2, Qt 5.11.2, Linux
4.19.0 (sys-kernel/gentoo-sources) x86_64.

Application: Step (step), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1eebe7e800 (LWP 883))]

Thread 4 (Thread 0x7f1ebb8a1700 (LWP 887)):
#0  0x7f1edfabe4fc in futex_wait_cancelable (private=,
expected=0, futex_word=0x5639d1c393d0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5639d1c39380,
cond=0x5639d1c393a8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5639d1c393a8, mutex=0x5639d1c39380) at
pthread_cond_wait.c:655
#3  0x7f1ec05a11eb in cnd_wait (mtx=0x5639d1c39380, cond=0x5639d1c393a8) at
/var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x5639d1f925e0) at
/var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/src/util/u_queue.c:255
#5  0x7f1ec05a0e77 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-18.1.9/work/mesa-18.1.9/include/c11/threads_posix.h:87
#6  0x7f1edfab796a in start_thread (arg=0x7f1ebb8a1700) at
pthread_create.c:463
#7  0x7f1ee531cf4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f1ec21e7700 (LWP 886)):
#0  0x7f1edfabe4fc in futex_wait_cancelable (private=,
expected=0, futex_word=0x5639d1bb0080) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5639d1bb0030,
cond=0x5639d1bb0058) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5639d1bb0058, mutex=0x5639d1bb0030) at
pthread_cond_wait.c:655
#3  0x7f1ee604a043 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x5639d1bb0030) at
thread/qwaitcondition_unix.cpp:143
#4  QWaitCondition::wait (this=this@entry=0x5639d1b00770,
mutex=mutex@entry=0x5639d1b00768, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#5  0x5639d11c608a in SimulationThread::run (this=0x5639d1b00740) at
/var/tmp/portage/kde-apps/step-18.08.2/work/step-18.08.2/step/simulationthread.cc:29
#6  0x7f1ee60497f6 in QThreadPrivate::start (arg=0x5639d1b00740) at
thread/qthread_unix.cpp:367
#7  0x7f1edfab796a in start_thread (arg=0x7f1ec21e7700) at
pthread_create.c:463
#8  0x7f1ee531cf4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f1ecbfff700 (LWP 885)):
#0  0x7f1ee5311413 in __GI___poll (fds=0x7f1ec4003ce0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f1ee00aa6f6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f1ec4003ce0, timeout=, context=0x7f1ec4000bf0)
at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4271
#2  g_main_context_iterate (context=context@entry=0x7f1ec4000bf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3967
#3  0x7f1ee00aa85b in g_main_context_iteration (context=0x7f1ec4000bf0,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4033
#4  0x7f1ee627f0ab in QEventDispatcherGlib::processEvents
(this=0x7f1ec4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f1ee621851b in QEventLoop::exec (this=this@entry=0x7f1ecbffed60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7f1ee603b86a in QThread::exec (this=this@entry=0x7f1ee1e4b060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:525
#7  0x7f1ee1bb71b9 in QDBusConnectionManager::run (this=0x7f1ee1e4b060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f1ee60497f6 in QThreadPrivate::start (arg=0x7f1ee1e4b060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:367
#9  0x7f1edfab796a in start_thread (arg=0x7f1ecbfff700) at
pthread_create.c:463
#10 0x7f1ee531cf4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f1eebe7e800 (LWP 883)):
[KCrash Handler]
#6  __cxxabiv1::__dynamic_cast (src_ptr=0x5639d2178150,
src_type=src_type@entry=0x5639d147a668 ,
dst_type=dst_type@entry=0x5639d147a678 ,
src2dst=src2dst@entry=0) at
/var/tmp/portage/sys-devel/gcc-8.2.0-r4/work/gcc-8.2.0/libstdc++-v3/libsupc++/dyncast.cc:68
#7  0x5639d11747c5 in WorldModel::objectIndex (this=0x5639d1ac9d80,
obj=) at
/var/tmp/portage/kde-apps/step-18.08.2/work/step-18.08.2/step/worldmodel.c

[k3b] [Bug 399753] k3b-18.08.2 assertion on startup: "first <= rowCount(parent)" in file itemmodels/qabstractitemmodel.cpp, line 2712

[Jaak Ristioja]

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

--- Comment #1 from Jaak Ristioja  ---
The following Qt commit apparently added this assertion to
QAbstractItemModel::beginInsertRows:

https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/itemmodels/qabstractitemmodel.cpp?id=00c09e752ff7e482e1308e0e34721dc979204595

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

[k3b] [Bug 399753] New: k3b-18.08.2 assertion on startup: "first <= rowCount(parent)" in file itemmodels/qabstractitemmodel.cpp, line 2712

[Jaak Ristioja]

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

Bug ID: 399753
   Summary: k3b-18.08.2 assertion on startup: "first <=
rowCount(parent)" in file
itemmodels/qabstractitemmodel.cpp, line 2712
   Product: k3b
   Version: 18.08.1
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: j...@ristioja.ee
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

SUMMARY

Crashes on startup.


STEPS TO REPRODUCE
1.  Start K3b

OBSERVED RESULT

Doesn't start.


EXPECTED RESULT

Starts up properly.


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

[New Thread 0x7fffdf287700 (LWP 5145)]
[New Thread 0x7fffdd0b0700 (LWP 5147)]
[New Thread 0x7fffce62d700 (LWP 5148)]
21 21
ASSERT: "first <= rowCount(parent)" in file itemmodels/qabstractitemmodel.cpp,
line 2712

Thread 1 "k3b" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x71cd2f6f in __GI_abort () at abort.c:90
#2  0x724ef5c5 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1842
#3  QMessageLogger::fatal (this=this@entry=0x7fffcdc0,
msg=msg@entry=0x727cfb30 "ASSERT: \"%s\" in file %s, line %d") at
global/qlogging.cpp:880
#4  0x724eed75 in qt_assert (assertion=assertion@entry=0x72890d4d
"first <= rowCount(parent)", file=file@entry=0x72890a10
"itemmodels/qabstractitemmodel.cpp", line=line@entry=2712) at
global/qglobal.cpp:3188
#5  0x726a4e14 in QAbstractItemModel::beginInsertRows
(this=this@entry=0x55b2ffd0, parent=..., first=first@entry=1,
last=last@entry=1) at itemmodels/qabstractitemmodel.cpp:2712
#6  0x555d65e9 in K3b::MetaItemModel::addSubModel (this=0x55b2ffd0,
name=..., icon=..., model=0x55d95900, flat=) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3bmetaitemmodel.cpp:739
#7  0x555dd611 in K3b::PlacesModel::addPlace
(this=this@entry=0x55b2ffd0, name=..., icon=..., rootUrl=...) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3bplacesmodel.cpp:177
#8  0x555dd8ae in K3b::PlacesModel::PlacesModel (this=0x55b2ffd0,
parent=) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3bplacesmodel.cpp:62
#9  0x555df493 in K3b::FileTreeView::FileTreeView (this=0x55c63d40,
parent=) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3bfiletreeview.cpp:72
#10 0x555ea8f1 in K3b::MainWindow::initView
(this=this@entry=0x559e48b0) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3b.cpp:522
#11 0x555eb410 in K3b::MainWindow::MainWindow (this=0x559e48b0,
__in_chrg=, __vtt_parm=) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3b.cpp:237
#12 0x555ce4b4 in K3b::Application::init (this=0x7fffd250,
commandLineParser=) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/k3bapplication.cpp:84
#13 0x555ca0a3 in main (argc=, argv=) at
/var/tmp/portage/kde-apps/k3b-18.08.2/work/k3b-18.08.2/src/main.cpp:141
(gdb) bt full
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {0, 140737488342048, 140737488342048, 140737258876986,
272, 8, 0, 17650251434217378048, 88, 140737488342048, 140737488342048,
17650251434217378048, 140737488342048, 140737253893344, 140737253893792,
93824998375376}}
pid = 
tid = 
ret = 
#1  0x71cd2f6f in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x55d97f80, sa_sigaction
= 0x55d97f80}, sa_mask = {__val = {17650251434217378048, 140737488342464,
140737488342232, 3, 140737258754524, 93825000967152, 17650251434217378048, 0,
17650251434217378048, 140737488342464, 140737488342232, 3, 140737488342464,
93824998375376, 140737258755016, 140737431774131}}, sa_flags = 349901056,
sa_restorer = 0x7fffccd8}
sigs = {__val = {32, 0 }}
#2  0x724ef5c5 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1842
No locals.
#3  QMessageLogger::fatal (this=this@entry=0x7fffcdc0,
msg=msg@entry=0x727cfb30 "ASSERT: \"%s\" in file %s, line %d") at
global/qlogging.cpp:880
message = 
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffcdc0, reg_save_area = 0x7fffcd00}}
#4  0x724eed75 in qt_assert (assertion=assertion@entry=0x72890d4d
"first <= rowCount(parent)", file=file@entry=0x72890a10
"itemmodels/qabstractitemmodel.cpp", 

[kleopatra] [Bug 395601] New: kleopatra v18.04.2 ASSERT: "!"QSortFilterProxyModel: index from wrong model passed to mapToSource"" in file itemmodels/qsortfilterproxymodel.cpp, line 381

[Jaak Ristioja]

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

Bug ID: 395601
   Summary: kleopatra v18.04.2 ASSERT: "!"QSortFilterProxyModel:
index from wrong model passed to mapToSource"" in file
itemmodels/qsortfilterproxymodel.cpp, line 381
   Product: kleopatra
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: j...@ristioja.ee
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

How to reproduce:
1) Start kleopatra
2) Click column header "Valid until" to sort the certificates based on the
values of that column.
3) Uncheck "Hierarchical Certificate List" from the "view menu"

QSortFilterProxyModel: index from wrong model passed to mapToSource
ASSERT: "!"QSortFilterProxyModel: index from wrong model passed to
mapToSource"" in file itemmodels/qsortfilterproxymodel.cpp, line 381

Kleopatra 18.04.2
KDE Frameworks 5.47.0
KDE Plasma 5.12.5
Qt 5.9.6
Gentoo Linux x86_64

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7238af6f in __GI_abort () at abort.c:90
#2  0x72dd9c17 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1690
#3  QMessageLogger::fatal (this=this@entry=0x7fffbf70,
msg=msg@entry=0x73091ec0 "ASSERT: \"%s\" in file %s, line %d") at
global/qlogging.cpp:796
#4  0x72dd1dc6 in qt_assert (assertion=assertion@entry=0x73152848
"!\"QSortFilterProxyModel: index from wrong model passed to mapToSource\"",
file=file@entry=0x731527b0 "itemmodels/qsortfilterproxymodel.cpp",
line=line@entry=381) at global/qglobal.cpp:3080
#5  0x72f97ff1 in QSortFilterProxyModelPrivate::proxy_to_source
(this=0x55fc7190, proxy_index=...) at
itemmodels/qsortfilterproxymodel.cpp:381
#6  0x72f98021 in QSortFilterProxyModel::mapToSource (this=, proxyIndex=...) at itemmodels/qsortfilterproxymodel.cpp:2673
#7  0x778fd1c6 in Kleo::AbstractKeyListSortFilterProxyModel::key
(this=this@entry=0x55fc6840, idx=...) at
/var/tmp/portage/kde-apps/libkleo-18.04.2/work/libkleo-18.04.2/src/models/keylistsortfilterproxymodel.cpp:77
#8  0x55622414 in Kleo::KeyTreeView::setHierarchicalView
(this=0x55fc6f10, on=on@entry=false) at
/var/tmp/portage/kde-apps/kleopatra-18.04.2/work/kleopatra-18.04.2/src/view/keytreeview.cpp:324
#9  0x556407d5 in (anonymous namespace)::Page::setHierarchicalView
(on=false, this=) at
/var/tmp/portage/kde-apps/kleopatra-18.04.2/work/kleopatra-18.04.2/src/view/tabwidget.cpp:298
#10 Kleo::TabWidget::Private::toggleHierarchicalView (on=false, page=, this=) at
/var/tmp/portage/kde-apps/kleopatra-18.04.2/work/kleopatra-18.04.2/src/view/tabwidget.cpp:642
#11 Kleo::TabWidget::Private::slotToggleHierarchicalView (on=false,
this=) at
/var/tmp/portage/kde-apps/kleopatra-18.04.2/work/kleopatra-18.04.2/src/view/tabwidget.cpp:359
#12 Kleo::TabWidget::qt_static_metacall (_o=, _c=, _id=, _a=) at
/var/tmp/portage/kde-apps/kleopatra-18.04.2/work/kleopatra-18.04.2_build/src/kleopatra_bin_autogen/include/moc_tabwidget.cpp:182
#13 0x7300a57e in QMetaObject::activate
(sender=sender@entry=0x55d834d0, signalOffset=,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fffc2c0)
at kernel/qobject.cpp:3767
#14 0x7300a94f in QMetaObject::activate
(sender=sender@entry=0x55d834d0, m=m@entry=0x74458960
, local_signal_index=local_signal_index@entry=4,
argv=argv@entry=0x7fffc2c0) at kernel/qobject.cpp:3629
#15 0x73d18382 in QAction::toggled (this=this@entry=0x55d834d0,
_t1=, _t1@entry=false) at .moc/moc_qaction.cpp:386
#16 0x73d1b119 in QAction::setChecked (this=this@entry=0x55d834d0,
b=) at kernel/qaction.cpp:981
#17 0x73d1b280 in QAction::activate (this=this@entry=0x55d834d0,
event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1162
#18 0x73ec03ac in QMenuPrivate::activateCausedStack
(this=this@entry=0x55c2b5d0, causedStack=...,
action=action@entry=0x55d834d0, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at widgets/qmenu.cpp:1323
#19 0x73ec80eb in QMenuPrivate::activateAction
(this=this@entry=0x55c2b5d0, action=action@entry=0x55d834d0,
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at
widgets/qmenu.cpp:1400
#20 0x73ec8f83 in QMenu::mouseReleaseEvent (this=,
e=0x7fffc940) at widgets/qmenu.cpp:2888
#21 0x73d660d8 in QWidget::event (this=this@entry=0x55d9a430,
event=event@entry=0x7fffc940) at kernel/qwidget.cpp:9280
#22 0x73ecb2bb in QMenu::event (this=0x55d9a430, e=0x7fffc940)
at widgets/qmenu.cpp:3010
#23 0x73d2009c in QApplicationPrivate::notify_helper
(this=this@entry=0x55b21aa0, 

[kmail2] [Bug 395310] New: Check mail interval less than 5 minutes / support for IMAP IDLE (RFC 2177)

[Jaak Ristioja]

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

Bug ID: 395310
   Summary: Check mail interval less than 5 minutes / support for
IMAP IDLE (RFC 2177)
   Product: kmail2
   Version: unspecified
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

The "Check mail interval" input field in the "IMAP account settings" dialog
does not allow intervals shorter than 5 minutes. I require an interval of 1
minute or even shorter.

Ideally, KMail would use the IMAP IDLE extension (RFC 2177) for instant
notifications. Although there seem to be some bugs related to KMail and IMAP
IDLE in this bugzilla, but I found no option to toggle it in KMail, nor any
information about whether/when it is enabled or not.

Please allow users to specify intervals shorter than 5 minutes as well.

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

[korganizer] [Bug 344679] Korganizer no alerts no reminders

[Jaak Ristioja]

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

--- Comment #7 from Jaak Ristioja  ---
Same here on Gentoo Linux with a fresh install of KOrganizer 18.04.1.

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

[korganizer] [Bug 344679] Korganizer no alerts no reminders

[Jaak Ristioja]

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

Jaak Ristioja  changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[akregator] [Bug 229989] Akregator allows feeds to gather data on article reading habits

[Jaak Ristioja]

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

--- Comment #4 from Jaak Ristioja <j...@ristioja.ee> ---
(In reply to Denis Kurz from comment #3)
> Just as announced in my last comment, I close this bug. If you encounter it
> again in a recent version (at least 5.0 aka 15.08), please open a new one
> unless it already exists. Thank you for all your input.

Since this still happens with at least version 5.5.3, I now filed a new bug:
https://bugs.kde.org/show_bug.cgi?id=391865

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

[akregator] [Bug 391865] New: Akregator allows feeds to gather data on article reading habits

[Jaak Ristioja]

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

Bug ID: 391865
   Summary: Akregator allows feeds to gather data on article
reading habits
   Product: akregator
   Version: 5.5.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Created attachment 111403
  --> https://bugs.kde.org/attachment.cgi?id=111403=edit
Screenshot of (an unbranded version of) Mozilla Thunderbird handling a similar
situation.

I'm filing a new bug as instructed in
https://bugs.kde.org/show_bug.cgi?id=229989#c2 and
https://bugs.kde.org/show_bug.cgi?id=229989#c3 since this still occurs in
recent versions of Akregator.

When opening an article, Akregator automatically downloads all requisites found
in the  (e.g. if images etc are specified in HTML; perhaps even
flash or AJAX?). Generally this generates extra HTTP(S) requests to remote
server(s), leaking information about the users activities, i.e. which articles
they browse, and possibly info about how long they read an article before
switching to another article, etc.

The man in the middle, even when the user is using HTTPS, has quite good
chances to figure out the exact articles being read (given he can determine the
endpoint of the HTTPS connection), which are probabilistically among those new
articles which the user has not previously read.

Hopefully it will be configurable per-feed, whether such requisites are
downloaded or not, and with an action somewhere to force download of requisites
of the article currently open.

Please fix these privacy leaks!

Mozilla Thunderbird, for example, handles such e-mails with remote content much
better, by prompting the user about whether to download remote content or not
(see attached screenshot). This is also what Akregator could do on a per-feed
basis. An "always show remote content" checkbox could also be added to the feed
properties dialog.

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

[plasmashell] [Bug 388223] Plasma crash while hovering cursor

[Jaak Ristioja]

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

--- Comment #1 from Jaak Ristioja <j...@ristioja.ee> ---
Created attachment 111401
  --> https://bugs.kde.org/attachment.cgi?id=111401=edit
New crash information added by DrKonqi

plasmashell (5.12.3) using Qt 5.9.4

- What I was doing when the application crashed:

I had the "Application Menu" widget open and was hovering over its root-level
menu items when it crashed.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7f90dc983045 in __GI_abort () at abort.c:90
#8  0x7f90dd1ecccb in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1690
#9  QMessageLogger::fatal (this=this@entry=0x7ffd5524b930,
msg=msg@entry=0x7f90dd4c53e8 "ASSERT failure in %s: \"%s\", file %s, line %d")
at global/qlogging.cpp:796
#10 0x7f90dd1e66b9 in qt_assert_x (where=where@entry=0x7f90e05469ff
"QList::at", what=what@entry=0x7f90e059dc2f "index out of range",
file=file@entry=0x7f90e0546aa8 "/usr/include/qt5/QtCore/qlist.h",
line=line@entry=541) at global/qglobal.cpp:3088

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

[plasmashell] [Bug 388223] Plasma crash while hovering cursor

[Jaak Ristioja]

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

Jaak Ristioja <j...@ristioja.ee> changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[konsole] [Bug 365893] Clear scrollback and reset leaves the terminal screen completely blank.

[Jaak Ristioja]

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

Jaak Ristioja <j...@ristioja.ee> changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[kdenlive] [Bug 378469] 17.04 - Crash on Exit

[Jaak Ristioja]

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

--- Comment #13 from Jaak Ristioja <j...@ristioja.ee> ---
(In reply to Jean-Baptiste Mardelle from comment #1)
> Thanks for your report. This was fixed in a recent MLT commit:
> https://github.com/mltframework/mlt/commit/
> a3188e301b5a9a1f25dbb98a510e366363348e64
> 
> Using MLT from git or the next MLT version to be released will solve the
> crash

What is the use if upstream won't release a new version? According to
https://github.com/mltframework/mlt/releases their last release was 6.4.1 on
Nov 16, 2016.

Dear Kdenlive! Whatever reasons upstream has, it hurts Your users! Isn't there
something You could do to work around this?

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

[kdenlive] [Bug 388252] New: kdenlive 17.12.0 crash on exit

[Jaak Ristioja]

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

Bug ID: 388252
   Summary: kdenlive 17.12.0 crash on exit
   Product: kdenlive
   Version: 17.12.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Application: kdenlive (17.12.0)
 (Compiled from sources)
Qt Version: 5.9.3
Frameworks Version: 5.41.0
Operating System: Linux 4.14.7-gentoo x86_64
Distribution: "NAME=Gentoo"

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

Give-or-take some extra random moves (since I'm almost a first-time-user) I
opened kdenlive, added a video clip to the untitled/unsaved project, removed
all tracks except one video track, moved the clip to the video track, perhaps
moved it back and forth a bit. Browsed some effects menu items for search of
something. Finally, I closed the application using the [X] button on the window
decoration. I don't remember whether there was a dialog asking to save the
project, but eventually the crash reporting assistant popped up in the system
tray, and now I'm writing this crash report in the assistant.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f63b07637c0 (LWP 6695))]

Thread 9 (Thread 0x7f636c34d700 (LWP 6846)):
#0  0x7f63a833246b in futex_reltimed_wait_cancelable (private=, reltime=0x7f636c34cca0, expected=0, futex_word=0x7f637002df30) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f636c34cd50, mutex=0x7f637002dee0,
cond=0x7f637002df08) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f637002df08, mutex=0x7f637002dee0,
abstime=0x7f636c34cd50) at pthread_cond_wait.c:667
#3  0x7f63aaa518f8 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f637002dee0) at thread/qwaitcondition_unix.cpp:133
#4  QWaitConditionPrivate::wait (time=3, this=0x7f637002dee0) at
thread/qwaitcondition_unix.cpp:141
#5  QWaitCondition::wait (this=this@entry=0x7f6370092980,
mutex=mutex@entry=0x55c7b2e4b650, time=3) at
thread/qwaitcondition_unix.cpp:215
#6  0x7f63aaa4bfa8 in QThreadPoolThread::run (this=0x7f6370092970) at
thread/qthreadpool.cpp:144
#7  0x7f63aaa51071 in QThreadPrivate::start (arg=0x7f6370092970) at
thread/qthread_unix.cpp:368
#8  0x7f63a832aac6 in start_thread (arg=0x7f636c34d700) at
pthread_create.c:465
#9  0x7f63a9f4555f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f636b247700 (LWP 6839)):
#0  0x7f63a833246b in futex_reltimed_wait_cancelable (private=, reltime=0x7f636b246ca0, expected=0, futex_word=0x55c7b29084c4) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f636b246d50, mutex=0x55c7b2908470,
cond=0x55c7b2908498) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x55c7b2908498, mutex=0x55c7b2908470,
abstime=0x7f636b246d50) at pthread_cond_wait.c:667
#3  0x7f63aaa518f8 in QWaitConditionPrivate::wait_relative (time=3,
this=0x55c7b2908470) at thread/qwaitcondition_unix.cpp:133
#4  QWaitConditionPrivate::wait (time=3, this=0x55c7b2908470) at
thread/qwaitcondition_unix.cpp:141
#5  QWaitCondition::wait (this=this@entry=0x55c7b29381f0,
mutex=mutex@entry=0x55c7b2e4b650, time=3) at
thread/qwaitcondition_unix.cpp:215
#6  0x7f63aaa4bfa8 in QThreadPoolThread::run (this=0x55c7b29381e0) at
thread/qthreadpool.cpp:144
#7  0x7f63aaa51071 in QThreadPrivate::start (arg=0x55c7b29381e0) at
thread/qthread_unix.cpp:368
#8  0x7f63a832aac6 in start_thread (arg=0x7f636b247700) at
pthread_create.c:465
#9  0x7f63a9f4555f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f636d34f700 (LWP 6710)):
#0  0x7f63a9f34549 in __GI___libc_read (fd=26,
buf=buf@entry=0x7f636d34eba0, nbytes=nbytes@entry=16) at
../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f63a4d6fe50 in read (__nbytes=16, __buf=0x7f636d34eba0,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f6360003d50) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gwakeup.c:210
#3  0x7f63a4d1b95e in g_main_context_check
(context=context@entry=0x7f6354000be0, max_priority=2147483647,
fds=fds@entry=0x7f6354002de0, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3707
#4  0x7f63a4d1be48 in g_main_context_iterate
(context=context@entry=0x7f6354000be0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3926
#5  0x7f63a4d1c00b in g_main_context_iteration (context=0x7f6354000be0,
may_block=may_block@entry=1) at

[plasmashell] [Bug 388223] New: Plasma crash while hovering cursor

[Jaak Ristioja]

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

Bug ID: 388223
   Summary: Plasma crash while hovering cursor
   Product: plasmashell
   Version: 5.11.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@ristioja.ee
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.4)
 (Compiled from sources)
Qt Version: 5.9.3
Frameworks Version: 5.41.0
Operating System: Linux 4.14.7-gentoo x86_64
Distribution: "NAME=Gentoo"

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

Afaict nothing special. I didn't interact directly with any Plasma components,
perhaps if only hovered over something with my cursor.

- Unusual behavior I noticed:

A Plasma panel at the bottom of my screen disappeared, then re-appeared with
some sliding effect.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbf54588c40 (LWP 3066))]

Thread 7 (Thread 0x7fbf1f4aa700 (LWP 3187)):
#0  0x7fbf4a075691 in g_main_context_query
(context=context@entry=0x7fbf10003400, max_priority=2147483647,
timeout=timeout@entry=0x7fbf1f4a9c44, fds=fds@entry=0x7fbf10003f00,
n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3659
#1  0x7fbf4a075e1f in g_main_context_iterate
(context=context@entry=0x7fbf10003400, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3911
#2  0x7fbf4a07600b in g_main_context_iteration (context=0x7fbf10003400,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990
#3  0x7fbf4f2d617b in QEventDispatcherGlib::processEvents
(this=0x7fbf10018b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fbf4f26c102 in QEventLoop::exec (this=this@entry=0x7fbf1f4a9da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fbf4f06ef4e in QThread::exec (this=this@entry=0x55899127a6c0) at
thread/qthread.cpp:515
#6  0x7fbf0ab0e2c6 in KCupsConnection::run (this=0x55899127a6c0) at
/var/tmp/portage/kde-apps/print-manager-17.12.0/work/print-manager-17.12.0/libkcups/KCupsConnection.cpp:305
#7  0x7fbf4f076071 in QThreadPrivate::start (arg=0x55899127a6c0) at
thread/qthread_unix.cpp:368
#8  0x7fbf4de00ac6 in start_thread (arg=0x7fbf1f4aa700) at
pthread_create.c:465
#9  0x7fbf4e8be55f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fbf204ab700 (LWP 3181)):
#0  0x7fbf4e8ad549 in __GI___libc_read (fd=16,
buf=buf@entry=0x7fbf204aab30, nbytes=nbytes@entry=16) at
../sysdeps/unix/sysv/linux/read.c:26
#1  0x7fbf4a0c9e50 in read (__nbytes=16, __buf=0x7fbf204aab30,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7fbf24003dc0) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gwakeup.c:210
#3  0x7fbf4a07595e in g_main_context_check
(context=context@entry=0x7fbf18022240, max_priority=2147483647,
fds=fds@entry=0x7fbf180221c0, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3707
#4  0x7fbf4a075e48 in g_main_context_iterate
(context=context@entry=0x7fbf18022240, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3926
#5  0x7fbf4a07600b in g_main_context_iteration (context=0x7fbf18022240,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990
#6  0x7fbf4f2d617b in QEventDispatcherGlib::processEvents
(this=0x7fbf1800d150, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fbf4f26c102 in QEventLoop::exec (this=this@entry=0x7fbf204aad70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7fbf4f06ef4e in QThread::exec (this=this@entry=0x55898ed87b90) at
thread/qthread.cpp:515
#9  0x7fbf522b1045 in QQuickPixmapReader::run (this=0x55898ed87b90) at
util/qquickpixmapcache.cpp:868
#10 0x7fbf4f076071 in QThreadPrivate::start (arg=0x55898ed87b90) at
thread/qthread_unix.cpp:368
#11 0x7fbf4de00ac6 in start_thread (arg=0x7fbf204ab700) at
pthread_create.c:465
#12 0x7fbf4e8be55f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fbf363a1700 (LWP 3159)):
#0  0x7fbf4e8b1f84 in __GI___poll (fds=0x7fbf24002de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fbf4a075ea4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fbf24002de0, timeout=, context=0x7fbf24000be0) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:4228
#2  

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Jaak Ristioja]

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

Jaak Ristioja <j...@ristioja.ee> changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[okular] [Bug 185636] More printing options for page control

[Jaak Ristioja]

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

--- Comment #8 from Jaak Ristioja <j...@ristioja.ee> ---
(In reply to Manuel López-Ibáñez from comment #7)
> It seems there is some way to enable a page ranges interface: 
> https://bugs.kde.org/show_bug.cgi?id=208736#c6 but it is not enabled by
> default.

Nothing in that bug report seems to indicate that one can work around this as a
user.

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

[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back

[Jaak Ristioja]

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

Jaak Ristioja <j...@ristioja.ee> changed:

   What|Removed |Added

 CC|j...@ristioja.ee|

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

[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back

[Jaak Ristioja]

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

Jaak Ristioja <j...@ristioja.ee> changed:

   What|Removed |Added

 CC||j...@ristioja.ee

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

[plasmashell] [Bug 375941] Unable to switch users with plasma-workspace-5.9.0

[Jaak Ristioja]

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

--- Comment #2 from Jaak Ristioja <j...@ristioja.ee> ---
I can confirm that the following workarounds help me as the user:

1) Disabling "Lock screen automatically after:" in "System Settings" ->
"Desktop Behavior" -> "Screen Locking" makes the [Switch] button work again.

2) Using "Switch user" from the lock screen.

PS: Bah, I hit a segfault when clicking the back button in systemsettings after
doing workaround #1.

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

[plasmashell] [Bug 375941] New: Unable to switch users with plasma-workspace-5.9.0

[Jaak Ristioja]

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

Bug ID: 375941
   Summary: Unable to switch users with plasma-workspace-5.9.0
   Product: plasmashell
   Version: 5.9.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: j...@ristioja.ee
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Switching from plasma-workspace 5.8.5 to 5.9 I'm unable to switch users.
Nothing seems to happen if I click the [Switch] button in
ksmserver-switchuser-greeter.

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

[plasmashell] [Bug 374586] New: Plasma panel crash when hovering over task manager items

[Jaak Ristioja]

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

Bug ID: 374586
   Summary: Plasma panel crash when hovering over task manager
items
   Product: plasmashell
   Version: 5.8.5
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@ristioja.ee
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.15-hardened-r1 x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
I was hovering the mouse over the task manager, perhaps clicking on some items
to bring the respective windows to the foreground focus.

- Unusual behavior I noticed:
The panel disappeared, maximized windows were resized to fill the resulting
void until the panel reappeared, resulting in the maximized windows to be
resized to their original proportions. Almost immediately, the crash reporting
assistant window appeared.

- Other information:
I've see frequent crashes with the same symptoms on a Kubuntu 16.04 machine as
well, but the crash assistant couldn't find a duplicate thou.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x37bb90ea780 (LWP 2266))]

Thread 7 (Thread 0x37b86c7b700 (LWP 2409)):
#0  0x037bb3c78e68 in
std::__atomic_base::compare_exchange_strong (__m2=,
__m1=std::memory_order_acquire, __p2=, __p1=@0x37b86c7ab68: 0x0,
this=0x7ce7cea970) at
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/bits/atomic_base.h:752
#1  std::atomic::compare_exchange_strong
(__m=std::memory_order_acquire, __p2=, __p1=@0x37b86c7ab68: 0x0,
this=0x7ce7cea970) at
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/atomic:475
#2  QAtomicOps::testAndSetAcquire
(currentValue=, newValue=, expectedValue=0x0,
_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:290
#3  QBasicAtomicPointer::testAndSetAcquire (currentValue=: , newValue=, expectedValue=0x0,
this=0x7ce7cea970) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:259
#4  QBasicMutex::fastTryLock (current=: ,
this=0x7ce7cea970) at thread/qmutex.h:89
#5  QMutex::lock (this=this@entry=0x7ce7cea970) at thread/qmutex.cpp:225
#6  0x037bb3ede447 in QMutexLocker::QMutexLocker (m=0x7ce7cea970,
this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:137
#7  QThreadData::canWaitLocked (this=0x7ce7cea940) at
../../include/QtCore/5.7.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253
#8  postEventSourcePrepare (s=0x37b800091b0,
timeout=timeout@entry=0x37b86c7ac04) at kernel/qeventdispatcher_glib.cpp:259
#9  0x037baf40439d in g_main_context_prepare
(context=context@entry=0x37b8000a5b0, priority=priority@entry=0x37b86c7ac90) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3442
#10 0x037baf404d93 in g_main_context_iterate
(context=context@entry=0x37b8000a5b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3820
#11 0x037baf404fcb in g_main_context_iteration (context=0x37b8000a5b0,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901
#12 0x037bb3ede94b in QEventDispatcherGlib::processEvents
(this=0x37b8001f360, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x037bb3e77a1a in QEventLoop::exec (this=this@entry=0x37b86c7adf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x037bb3c7dd93 in QThread::exec (this=this@entry=0x7ce7cea7c0) at
thread/qthread.cpp:507
#15 0x037b77795886 in KCupsConnection::run (this=0x7ce7cea7c0) at
/var/tmp/portage/kde-apps/print-manager-16.12.0/work/print-manager-16.12.0/libkcups/KCupsConnection.cpp:304
#16 0x037bb3c849bc in QThreadPrivate::start (arg=0x7ce7cea7c0) at
thread/qthread_unix.cpp:368
#17 0x037bb2cd264c in start_thread (arg=0x37b86c7b700) at
pthread_create.c:334
#18 0x037bb34e183d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x37b86398700 (LWP 2385)):
#0  0x037bb34d35b9 in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x037baf457450 in read (__nbytes=16, __buf=0x37b86397b90,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x37b80002570) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gwakeup.c:210
#3  0x037baf404934 in g_main_context_check
(context=context@entry=0x37b78000990, max_priority=2147483647,
fds=fds@entry=0x37b780013e0, n_fds=n_fds@entry=1) at

[kgpg] [Bug 373910] New: kgpg crash when changing key trust

[Jaak Ristioja]

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

Bug ID: 373910
   Summary: kgpg crash when changing key trust
   Product: kgpg
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: j...@ristioja.ee
  Target Milestone: ---

Application: kgpg (16.12.0)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.15-hardened x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
1. Opened key properties dialog for a key imported earlier
2. Changed owner trust to "Ultimate"
3. Clicked the "OK" button

- Unusual behavior I noticed:
1. The mouse cursor changed to some spinning thing
2. Nothing happened for a while (key properties dialog was still displayed on
screen)
3. Crash

Gentoo Linux, x86_64, hardened-sources-4.8.15. These kernel messages are
probably related:

[13671.860748] PAX: execution attempt in: (null), - 
[13671.860750] PAX: terminating task: /usr/bin/kgpg(kgpg):13799, uid/euid:
1001/1001, PC: 0201, SP: 03e22099c3d8
[13671.860751] PAX: bytes at PC: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
?? ?? ?? ?? ?? 
[13671.860764] PAX: bytes at SP-8: 03e22099c4d0 03b3ac001d2e
001f3907b730 3dd6033e0ed41f00 03b3aa9e5bd8 03b3aa9e5bd8
 03b3ac002b2c 03e22099c4d0 3dd6033e0ed41f00
03e22099c770 
[13671.860821] grsec: denied resource overstep by requesting 4096 for
RLIMIT_CORE against limit 0 for /usr/bin/kgpg[kgpg:13799] uid/euid:1001/1001
gid/egid:100/100, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0

The crash can be reproduced every time.

-- Backtrace:
Application: KGpg (kgpg), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x3a3ab4d4780 (LWP 13855))]

Thread 3 (Thread 0x3a3997eb700 (LWP 13865)):
#0  0x03a3bf8032ec in g_mutex_lock (mutex=mutex@entry=0x3a394000990) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gthread-posix.c:1335
#1  0x03a3bf7aee26 in g_main_context_iterate
(context=context@entry=0x3a394000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3844
#2  0x03a3bf7aefcb in g_main_context_iteration (context=0x3a394000990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901
#3  0x03a3c644894b in QEventDispatcherGlib::processEvents
(this=0x3a3940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x03a3c63e1a1a in QEventLoop::exec (this=this@entry=0x3a3997eae30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x03a3c61e7d93 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x03a3c61ee9bc in QThreadPrivate::start (arg=0x4cdd364910) at
thread/qthread_unix.cpp:368
#7  0x03a3c204464c in start_thread (arg=0x3a3997eb700) at
pthread_create.c:334
#8  0x03a3c583483d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x3a3a1629700 (LWP 13860)):
#0  0x03a3c582aa4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x03a3bf7aee64 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x3a39c003020, timeout=, context=0x3a39c000990) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x3a39c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3835
#3  0x03a3bf7aefcb in g_main_context_iteration (context=0x3a39c000990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901
#4  0x03a3c644894b in QEventDispatcherGlib::processEvents
(this=0x3a39c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x03a3c63e1a1a in QEventLoop::exec (this=this@entry=0x3a3a1628df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x03a3c61e7d93 in QThread::exec (this=this@entry=0x3a3cb32bb20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x03a3cb29bdb3 in QDBusConnectionManager::run (this=0x3a3cb32bb20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x03a3c61ee9bc in QThreadPrivate::start (arg=0x3a3cb32bb20 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#9  0x03a3c204464c in start_thread (arg=0x3a3a1629700) at
pthread_create.c:334
#10 0x03a3c583483d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x3a3ab4d4780 (LWP 13855)):
[KCrash Handler]
#6  

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

[Jaak Ristioja via KDE Bugzilla]

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

--- Comment #22 from Jaak Ristioja <j...@ristioja.ee> ---
(In reply to Mirek Mieszczak from comment #21)
> Same in gentoo until 16.04.2

Is it fixed in 16.04.2 or you just haven't tested that version yet?

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

[yakuake] [Bug 363333] Processes started in yakuake terminals block indefinitely some time after switching to a different VT

[Jaak Ristioja via KDE Bugzilla]

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

Jaak Ristioja <j...@ristioja.ee> changed:

   What|Removed |Added

Summary|Processes started in|Processes started in
   |yakuake terminals block |yakuake terminals block
   |indefinitely ~45s after |indefinitely some time
   |switching to a different VT |after switching to a
   ||different VT

--- Comment #2 from Jaak Ristioja <j...@ristioja.ee> ---
I think the ~45s period might be mplayer specific. Probably some OS buffer gets
full because the other end (Yakuake) is not reading.

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

[yakuake] [Bug 363333] Processes started in yakuake terminals block indefinitely ~45s after switching to a different VT

[Jaak Ristioja via KDE Bugzilla]

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

--- Comment #1 from Jaak Ristioja <j...@ristioja.ee> ---
More information:
* Only happens when Yakuake is left visible (i.e. "dropped down") when leaving
the VT.
* Switching back to the VT with Yakuake immediately resumes the blocked
process, even if VT is locked.
* Bug does not occur when process is launched in Konsole instead of Yakuake.

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

[yakuake] [Bug 363333] New: Processes started in yakuake terminals block indefinitely ~45s after switching to a different VT

[Jaak Ristioja via KDE Bugzilla]

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

Bug ID: 36
   Summary: Processes started in yakuake terminals block
indefinitely ~45s after switching to a different VT
   Product: yakuake
   Version: 3.0.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: j...@ristioja.ee

This seems to be a regression after upgrading from kde-misc/yakuake-2.9.9-r3 to
kde-misc/yakuake-3.0.2 together with the upgrade from KDE4 to KF5.

Reproducible: Always

Steps to Reproduce:
1. Open two KDE sessions with yakuake
2. Run mplayer somemusicfile.mp3
3. Switch to another VT using Ctrl+Alt+F1, for example.
4. Wait ~45s

Actual Results:  
The application wanting to write something to stdout blocks:

  gdb:
#0  0x688bef0b3610 in __write_nocancel () at
../sysdeps/unix/syscall-template.S:84
  strace:
write(1, "A: 245.1 (04:05.1) of 346.8 (05:"..., 48
  # ls /proc/`pidof mplayer`/fd/1 -lhd
lrwx-- 1 myser mygroup 64 mai   20 19:13 /proc/4550/fd/1 -> /dev/pts/4

Expected Results:  
Process does not block.

Backtrace of yakuake during block:

(gdb) thread apply all bt full

Thread 2 (Thread 0x78c72a55f700 (LWP 3354)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
No locals.
#1  0x78c7346f0f09 in _xcb_conn_wait (c=c@entry=0x69552506800,
cond=cond@entry=0x69552506840, vector=vector@entry=0x0, count=count@entry=0x0)
at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:427
ret = 
fd = {fd = 603994464, events = 30919, revents = 0}
#2  0x78c7346f30df in xcb_wait_for_event (c=0x69552506800) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
ret = 0x0
#3  0x78c72bd26899 in QXcbEventReader::run (this=0x69552510e90) at
qxcbconnection.cpp:1229
event = 
#4  0x78c7368ffc1c in QThreadPrivate::start (arg=0x69552510e90) at
thread/qthread_unix.cpp:331
__clframe = {__cancel_routine = 0x78c7368fe8e0
, __cancel_arg = 0x69552510e90, __do_it = 1,
__cancel_type = }
thr = 0x69552510e90
data = 0x695525111f0
objectName = {static null = {}, d = 0x78c736bd9660
}
#5  0x78c732f5464c in start_thread (arg=0x78c72a55f700) at
pthread_create.c:334
__res = 
pd = 0x78c72a55f700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {132796804101888,
7985632438364207210, 135822295332368, 135822295332127, 0, 132796804101888,
7985632438318069866, 7985615675874539626}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#6  0x78c7361e183d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
No locals.

Thread 1 (Thread 0x78c72bfed780 (LWP 3352)):
#0  0x78c7361d7a4d in poll () at ../sysdeps/unix/syscall-template.S:84
No locals.
#1  0x78c7346f0c6a in poll (__timeout=-1, __nfds=1, __fds=0x7b8797aa7090)
at /usr/include/bits/poll2.h:46
No locals.
#2  _xcb_conn_wait (c=c@entry=0x69552506800, cond=cond@entry=0x7b8797aa71c0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
ret = 
fd = {fd = 3, events = 1, revents = 0}
#3  0x78c7346f2d5f in wait_for_reply (c=c@entry=0x69552506800,
request=4247, e=e@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:516
cond = {__data = {__lock = 0, __futex = 2, __total_seq = 1,
__wakeup_seq = 1, __woken_seq = 1, __mutex = 0x69552506818, __nwaiters = 0,
__broadcast_seq = 0}, __size =
"\000\000\000\000\002\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\030hPR\225\006\000\000\000\000\000\000\000\000\000",
__align = 8589934592}
reader = {request = 4247, data = 0x7b8797aa71c0, next = 0x0}
ret = 0x0
#4  0x78c7346f2e98 in xcb_wait_for_reply (c=0x69552506800, request=4247,
e=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:546
ret = 
#5  0x78c72bd1f8b0 in QXcbConnection::sync (this=0x69552505210) at
qxcbconnection.cpp:1839
cookie = 
#6  0x78c72bd46705 in QXcbShmImage::preparePaint (this=0x69552524810,
region=...) at qxcbbackingstore.cpp:286
region = 
this = 0x69552524810
#7  0x78c72bd46ae8 in QXcbBackingStore::beginPaint (this=0x695526307d0,
region=...) at qxcbbackingstore.cpp:324
dpr = 
windowDpr = 
#8  0x78c737466c25 in QWidgetBackingStore::beginPaint
(toCleanIsInTopLevelCoordinates=true, returnInfo=,
backingStore=, widget=, toClean=...,
this=0x69552747090) at 

[kgpg] [Bug 357362] Provide key expiration notifications

[Jaak Ristioja via KDE Bugzilla]

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

--- Comment #2 from Jaak Ristioja <j...@ristioja.ee> ---
I think it is needed.

Personally, I only need notifications for keys I'm responsible for and need to
update or keep track of. For example, I would not care much when another
person's key is about to expire, unless I want to manually update that key from
a keyserver.

PS: Is kgpg also missing a "refresh all keys" feature? Should I file a separate
bug for this?

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

[kgpg] [Bug 357362] New: Provide key expiration notifications

[Jaak Ristioja via KDE Bugzilla]

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

Bug ID: 357362
   Summary: Provide key expiration notifications
   Product: kgpg
   Version: unspecified
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: j...@ristioja.ee

I often fail to remember when my GPG keys expire, so when it happens I have
created new keys, and temporarily rolled back the computer time/date to sign
the new keys with the expired keys.

It were proactively nice to be able to get notifications before selected keys
expire (and dismiss/postpone these notifications).

Per key, this probably requires a notification time and a boolean whether the
notification is active. Changes to the expiration time of monitored keys also
need to be handled. It were also nice if KGPG would also ask to enable the
notifications after (or during) key generation or import.

Reproducible: Always

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