[ksmserver] [Bug 380500] New: ksmserver-logout-greeter aborted

[Valter Mura]

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

Bug ID: 380500
   Summary: ksmserver-logout-greeter aborted
   Product: ksmserver
   Version: 5.7.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ui
  Assignee: l.lu...@kde.org
  Reporter: valterm...@gmail.com
  Target Milestone: ---

The ksmserver crashes, both restarting and shutting down. Note that I'm coming
form a "suspend to ram" state and the system made an update regarding Nvidia
driver (no restart made).

Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal:
Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd445a19d80 (LWP 1180))]

Thread 4 (Thread 0x7fd42d75e700 (LWP 1208)):
#0  0x7fd44166dcad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd43a393b30 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd43a34f042 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd43a34f514 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fd43a34f68c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fd441f95f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd441f3f88a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fd441d6cfe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd443d27df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fd441d71c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fd43c0a56da in start_thread (arg=0x7fd42d75e700) at
pthread_create.c:456
#11 0x7fd44167e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fd42e4a2700 (LWP 1198)):
#0  0x7fd44167218d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd43a34f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd43a34f68c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd441f95f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd441f3f88a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd441d6cfe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd442ade5c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fd441d71c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd43c0a56da in start_thread (arg=0x7fd42e4a2700) at
pthread_create.c:456
#9  0x7fd44167e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fd42ffe0700 (LWP 1188)):
#0  0x7fd44167218d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd43c905c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fd43c9078d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fd432543ed9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fd441d71c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd43c0a56da in start_thread (arg=0x7fd42ffe0700) at
pthread_create.c:456
#6  0x7fd44167e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fd445a19d80 (LWP 1180)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x7fd4415ad37a in __GI_abort () at abort.c:89
#8  0x7fd441d58451 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fd4443e90e3 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7fd4443f0b12 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7fd4443f0efb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7fd442491475 in QWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7fd27245 in QQuickWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x55a882e518c1 in ?? ()
#15 0x7fd442ea435c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fd442eabb11 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7fd441f418a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fd44248670d in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x7fd44248731d in

[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

 CC||fab...@ritter-vogt.de

--- Comment #13 from Fabian Vogt  ---
(In reply to Kurt Hindenburg from comment #12)
> Git commit 9a3e18816e66aecbb5f79cc243a6e1d5c5723d6f by Kurt Hindenburg.
> Committed on 02/06/2017 at 02:24.
> Pushed by hindenburg into branch 'master'.
> 
> Fix 'Manage Profiles' option from KonsolePart
> 
> Allow the menu option to work again.  Code copied from MainWindow.
> Keeping the bug report open for now as I think this still need some
> work.
> 
> M  +3-2src/CMakeLists.txt
> M  +22   -1src/Part.cpp
> M  +2-1src/Part.h
> 
> https://commits.kde.org/konsole/9a3e18816e66aecbb5f79cc243a6e1d5c5723d6f

While this patch works (on top of konsole 17.04.1) with yakuake, there seems to
be a conflict with the KConfigDialog.

Depending whether "Manage Profiles" or "Configure Yakuake" is selected first,
the actions done by both are identical. Example:

- Click on "Manage Profiles"
-> Manage Profiles dialog opens
- Click on "Configure Yakuake"
-> Manage Profiles dialog opens (!)

Or the other way around:

- Click on "Configure Yakuake"
-> Configuration dialog opens
- Click on "Manage Profiles"
-> Configuration dialog opens (!)

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

[kontact] [Bug 380499] New: Kontact crashes if opening a contact group after recreating the akonadi database

[Christoph Drexler]

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

Bug ID: 380499
   Summary: Kontact crashes if opening a contact group after
recreating the akonadi database
   Product: kontact
   Version: 5.5.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ch...@gmx.at
  Target Milestone: ---

Application: kontact (5.5.1)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

2 or 3 years ago I created a "personal contacts" folder with some contact
groups. When I had to recreate my akonadi database some months ago, I did not
re-establish the corresponding akonadi resource any more because then I had no
use for those contacts.

Now I wanted to use these contacts again and recreated the corresponding
akonadi resource. I can see, use, and modify the contacts in that address book
as expected, but whenever I open a contact group, kontact crashes. When I start
kontact on the cli, the last output is as follows:

org.kde.pim.akonadicontact: Contact for Akonadi item 23267 does not exist
anymore!
org.kde.pim.akonadicontact: Contact for Akonadi item 23268 does not exist
anymore!
org.kde.pim.akonadicontact: Contact for Akonadi item 23269 does not exist
anymore!
org.kde.pim.akonadicontact: Contact for Akonadi item 23262 does not exist
anymore!
org.kde.pim.akonadicontact: Contact for Akonadi item 23238 does not exist
anymore!
org.kde.pim.akonadicontact: Contact for Akonadi item 23253 does not exist
anymore!
org.kde.pim.akonadicontact: Contact for Akonadi item 23260 does not exist
anymore!
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: Wrong payload type (requested:
sp(0); present: sp(2)
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
KCrash: Application 'kontact' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

Thus, the reason for the crash seems to be that the payload type is different,
which is probably a consequence of the fact that the IDs of the pimitems have
been reassigned, so that the pimitems that are referenced by the contact group,
are not valid any more.

IMHO the issue might be solved as follows:
(1) the program should not crash in case of a wrong payload type;
(2) the contact group xml files should not use the akonadi pimitem IDs as a
reference, but the contact's UID.

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

Thread 29 (Thread 0x7fbd9a4dc700 (LWP 16277)):
#0  0x7fbeeecfd2bd in poll () from /usr/lib/libc.so.6
#1  0x7fbee896a9b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fbee896aacc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fbeef847f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fbeef7ef3aa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fbeef60744a in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fbeef60be9c in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fbeeab89297 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fbeeed0725f in clone () from /usr/lib/libc.so.6

Thread 28 (Thread 0x7fbda9b96700 (LWP 16261)):
#0  0x7fbeeecfd2bd in poll () from /usr/lib/libc.so.6
#1  0x7fbee896a9b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fbee896aacc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fbeef847f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fbeef7ef3aa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fbeef60744a in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fbeef60be9c in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fbeeab89297 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fbeeed0725f in clone () from /usr/lib/libc.so.6

Thread 27 (Thread 0x7fbdaa397700 (LWP 16239)):
#0  0x7fbeeab8f39d in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fbee16bd169 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fbee16bd799 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fbee16bd950 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fbee16ba4d2 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fbeeab89297 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fbeeed0725f in clone () from 

[kscreenlocker] [Bug 380491] kscreenlocker_greet incorrect behaviour after pressing enter key with empty password

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
I noticed some odd behavior in screen locker indeed but I never figured out why
that happens - thanks for the hint with submitting empty breaking it.

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

[Discover] [Bug 380496] Discover crashes upon opening

[Antonio Rojas]

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

--- Comment #4 from Antonio Rojas  ---
@Aleix I've gotten a few reports of this one, though I can't reproduce it
myself. It happens when flatpak is not installed but packagekit is, not when
both are installed or both aren't. See
https://bbs.archlinux.org/viewtopic.php?id=226752 for more details including a
BT with debug symbols

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

[Discover] [Bug 380496] Discover crashes upon opening

[Llaurator]

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

--- Comment #3 from Llaurator  ---
(In reply to Antonio Rojas from comment #1)
> does it work if you install flatpak?

Yes, it works when installing flatpak, Thanks

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

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

[David Faure]

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

David Faure  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kio
   ||/e10f44d87270ca6f8e509a99f6
   ||df17c8a31fbfa8
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.35
 Resolution|--- |FIXED

--- Comment #18 from David Faure  ---
Git commit e10f44d87270ca6f8e509a99f6df17c8a31fbfa8 by David Faure, on behalf
of Kai Uwe Broulik.
Committed on 03/06/2017 at 09:54.
Pushed by dfaure into branch 'master'.

Workaround for QTBUG-59017

CHANGELOG: Addressed an issue where certain elements in applications (e.g.
Dolphin's file view) would become inaccessible in high-dpi multi-screen setup
FIXED-IN: 5.35
Differential Revision: https://phabricator.kde.org/D6063

M  +11   -3src/widgets/krun.cpp

https://commits.kde.org/kio/e10f44d87270ca6f8e509a99f6df17c8a31fbfa8

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

[Discover] [Bug 380496] Discover crashes upon opening

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||llaura...@gmail.com

--- Comment #2 from Antonio Rojas  ---
*** Bug 380498 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 380498] Discover crashes upon opening

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||aro...@archlinux.org

--- Comment #1 from Antonio Rojas  ---


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

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

[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar

[Martin Pagh Goodwin]

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

--- Comment #11 from Martin Pagh Goodwin  ---
Using Kubuntu 17.04.

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

[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar

[Martin Pagh Goodwin]

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

--- Comment #10 from Martin Pagh Goodwin  ---
I guess this should no longer be in UNCONFIRMED, as it seems several users have
seen this problem (myself included). The 'akonadictl restart' command does the
trick with respect to getting stuff working again. I have attached the output
of said command, just in case it reveals anything interesting

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

[Discover] [Bug 380498] New: Discover crashes upon opening

[bugzilla_noreply]

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

Bug ID: 380498
   Summary: Discover crashes upon opening
   Product: Discover
   Version: 5.10.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: llaura...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.0)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed: After 5.10 Plasma update, just
opening discover crashes the application.

The crash can be reproduced every time.

-- Backtrace:
Application: Descubrir (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3c4cee4800 (LWP 1205))]

Thread 5 (Thread 0x7f3c24bf1700 (LWP 1209)):
#0  0x7f3c42f291e0 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f3c42ee31b9 in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#2  0x7f3c42ee3928 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f3c42ee3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f3c48fd2f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f3c48f7a3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f3c48d9244a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f3c4c233fd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f3c48d96e9c in  () at /usr/lib/libQt5Core.so.5
#9  0x7f3c44eec297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f3c486a925f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f3c2700 (LWP 1208)):
#0  0x7f3c4869f2bd in poll () at /usr/lib/libc.so.6
#1  0x7f3c42ee39b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f3c42ee3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f3c48fd2f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f3c48f7a3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f3c48d9244a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f3c4994a085 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f3c48d96e9c in  () at /usr/lib/libQt5Core.so.5
#8  0x7f3c44eec297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f3c486a925f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3c2efee700 (LWP 1207)):
#0  0x7f3c4869f2bd in poll () at /usr/lib/libc.so.6
#1  0x7f3c42ee39b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f3c42ee3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f3c48fd2f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f3c48f7a3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f3c48d9244a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f3c4b0eec45 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f3c48d96e9c in  () at /usr/lib/libQt5Core.so.5
#8  0x7f3c44eec297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f3c486a925f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f3c379f2700 (LWP 1206)):
#0  0x7f3c4869f2bd in poll () at /usr/lib/libc.so.6
#1  0x7f3c42c7c8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f3c42c7e679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f3c3a5891d9 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f3c48d96e9c in  () at /usr/lib/libQt5Core.so.5
#5  0x7f3c44eec297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f3c486a925f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3c4cee4800 (LWP 1205)):
[KCrash Handler]
#6  0x7f3c4cdbe10d in do_lookup_x () at /lib64/ld-linux-x86-64.so.2
#7  0x7f3c4cdbecbf in _dl_lookup_symbol_x () at /lib64/ld-linux-x86-64.so.2
#8  0x7f3c4cdc0769 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2
#9  0x7f3c4cdc85e3 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#10 0x7f3c486e2c94 in _dl_catch_error () at /usr/lib/libc.so.6
#11 0x7f3c4cdc7f29 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#12 0x7f3c4361ef26 in  () at /usr/lib/libdl.so.2
#13 0x7f3c486e2c94 in _dl_catch_error () at /usr/lib/libc.so.6
#14 0x7f3c4361f5f5 in  () at /usr/lib/libdl.so.2
#15 0x7f3c4361efb1 in dlopen () at /usr/lib/libdl.so.2
#16 0x7f3c48f77d01 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f3c48f71165 in  () at /usr/lib/libQt5Core.so.5
#18 0x7f3c48f5f2a8 in QPluginLoader::instance() () at
/usr/lib/libQt5Core.so.5
#19 0x7f3c4bee446f in DiscoverBackendsFactory::backendForFile(QString
const&, QString const&) const () at
/usr/lib/plasma-discover/libDiscoverCommon.so
#20 0x7f3c4bee4b4b in 

[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar

[Martin Pagh Goodwin]

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

Martin Pagh Goodwin  changed:

   What|Removed |Added

 CC||mpg...@goodwin.dk

--- Comment #9 from Martin Pagh Goodwin  ---
Created attachment 105863
  --> https://bugs.kde.org/attachment.cgi?id=105863=edit
Output of akonadictrl restart

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

[yakuake] [Bug 380497] New: Yakuake KeepOpen=false doesn't work with Wayland

[leo_rockway]

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

Bug ID: 380497
   Summary: Yakuake KeepOpen=false doesn't work with Wayland
   Product: yakuake
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: lgdeluc...@gmail.com
  Target Milestone: ---

The option KeepOpen=false makes the window hide and show up once and again in
Wayland.

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

[Discover] [Bug 380496] Discover crashes upon opening

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #1 from Antonio Rojas  ---
does it work if you install flatpak?

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

[Discover] [Bug 380496] New: Discover crashes upon opening

[CDK]

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

Bug ID: 380496
   Summary: Discover crashes upon opening
   Product: Discover
   Version: 5.10.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: cdk...@gmx.de
  Target Milestone: ---

Application: plasma-discover (5.10.0)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-MANJARO x86_64
Distribution: "NAME="Netrunner Rolling""

-- Information about the crash:
- What I was doing when the application crashed:
After 5.10 Plasma update, just opening discover crashes the application.

The crash can be reproduced every time.

-- Backtrace:
Application: Entdecken (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0289d297c0 (LWP 2153))]

Thread 39 (Thread 0x7f01e57fa700 (LWP 2191)):
#0  0x7f027fe3e1c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f027fdf7d67 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f027fdf88db in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f027fdf8acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f0285e26f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f0285dce3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f0285be644a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f0285beae9c in  () at /usr/lib/libQt5Core.so.5
#8  0x7f0281d40297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f02854fd25f in clone () at /usr/lib/libc.so.6

Thread 38 (Thread 0x7f01e5ffb700 (LWP 2190)):
#0  0x7f027fdf83f1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#1  0x7f027fdf8954 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f027fdf8acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f0285e26f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f0285dce3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f0285be644a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f0285beae9c in  () at /usr/lib/libQt5Core.so.5
#7  0x7f0281d40297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f02854fd25f in clone () at /usr/lib/libc.so.6

Thread 37 (Thread 0x7f01e67fc700 (LWP 2189)):
#0  0x7f027fe3e1e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f027fdf83b1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f027fdf8954 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f027fdf8acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f0285e26f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f0285dce3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f0285be644a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f0285beae9c in  () at /usr/lib/libQt5Core.so.5
#8  0x7f0281d40297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f02854fd25f in clone () at /usr/lib/libc.so.6

Thread 36 (Thread 0x7f01e6ffd700 (LWP 2188)):
#0  0x7f02854f32bd in poll () at /usr/lib/libc.so.6
#1  0x7f027fdf89b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f027fdf8acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f0285e26f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f0285dce3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f0285be644a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f0285beae9c in  () at /usr/lib/libQt5Core.so.5
#7  0x7f0281d40297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f02854fd25f in clone () at /usr/lib/libc.so.6

Thread 35 (Thread 0x7f01e77fe700 (LWP 2187)):
#0  0x7f02854ef02d in read () at /usr/lib/libc.so.6
#1  0x7f027fe3ce20 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f027fdf847e in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f027fdf8954 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f027fdf8acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f0285e26f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f0285dce3aa in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f0285be644a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f0285beae9c in  () at /usr/lib/libQt5Core.so.5
#9  0x7f0281d40297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f02854fd25f in clone () at /usr/lib/libc.so.6

Thread 34 (Thread 0x7f01e7fff700 (LWP 2186)):
#0  0x7f02854f32bd in poll () at /usr/lib/libc.so.6
#1  0x7f027fdf89b6 in  () at /usr/lib/libglib-2.0.so.0
#2  

[kio-extras] [Bug 379817] Behaviour change: JPEG image preview scaled to widget size

[Alexander Volkov]

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

--- Comment #5 from Alexander Volkov  ---
Try it now https://git.reviewboard.kde.org/r/130129/diff

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

[kio-extras] [Bug 379817] Behaviour change: JPEG image preview scaled to widget size

[Alexander Volkov]

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

--- Comment #4 from Alexander Volkov  ---
Sorry, I didn't publish it.

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

[krita] [Bug 380486] No default favorite brushes selected

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Summary|Brushs Greyed out and not   |No default favorite brushes
   |selectable  |selected
 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Boudewijn Rempt  ---
I'll rename this bug and confirm it; the problem is that after the tags got
reordered, we no longer have a favorite tag, and that leaves the popup palette
empty by default.

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

[plasmashell] [Bug 380495] New: Freezes during login process

[Nobuhiro Iwamatsu]

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

Bug ID: 380495
   Summary: Freezes during login process
   Product: plasmashell
   Version: 5.8.6
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: iwama...@nigauri.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 105862
  --> https://bugs.kde.org/attachment.cgi?id=105862=edit
a patch

Login processing stops with ksplashqml.
This causes problems in the uim Japanese input environment of Debian stretch
(Debian 9).

When Mr.Yoshino investigated this problem, he and I thought that this is
ksplashqml's problem, not uim and other software.

An upstream commit
https://cgit.kde.org/plasma-workspace.git/commit/?id=56d2c15b9acb9c4b57398b281685807c3191f622
has caused this problem.

x-session-manag,133,kdetest /usr/bin/x-session-manager
  ├─(ksplashqml,232)
  ├─ssh-agent,191 /usr/bin/im-launch x-session-manager
  ├─uim-toolbar,220
  │   ├─{llvmpipe-0},235
  │   ├─{llvmpipe-1},236
  │   ├─{llvmpipe-2},237
  │   └─{llvmpipe-3},238
  └─uim-xim,219
ksplashqml,233,kdetest Breeze --pid
  ├─mozc_server,239
  │   ├─{IPCServer},244
  │   ├─{QueueTimer},240
  │   ├─{QueueTimer},243
  │   └─{WatchDog},242
  ├─uim-candwin-qt5,245 -v
  │   ├─{QDBusConnection},249
  │   └─{QXcbEventReader},248
  ├─{QDBusConnection},255
  ├─{QQmlThread},254
  ├─{QXcbEventReader},234
  ├─{llvmpipe-0},250
  ├─{llvmpipe-1},251
  ├─{llvmpipe-2},252
  └─{llvmpipe-3},253

# strace -f -p 133
strace: Process 133 attached
read(3, ^Cstrace: Process 133 detached
 

It looks like the parent process (133), x-session-manager (startkde
script), is waiting for the stdout of the ksplashqml process (232),
but which is now defunct. Its child process(es) may be writing to the
same fd.

# ls -l /proc/133/fd/3
lr-x-- 1 kdetest kdetest 64 May 31 05:13 /proc/133/fd/3 -> pipe:[88694]

The direct child of the ksplashqml process (233), the splash screen daemon,
closes the file descriptor at ksplash/ksplashqml/main.cpp:97.

# ls -l /proc/233/fd/1
ls: cannot access '/proc/233/fd/1': No such file or directory

One of the children of the process (239), mozc_server, is holding the fd:

# ls -l /proc/239/fd/1
l-wx-- 1 kdetest kdetest 64 May 31 05:14 /proc/239/fd/1 -> pipe:[88694]

So the startkde process has finished reading the pid number string from
the now-defunct process, but is still waiting for another write(s) until
the (shared) fd has been closed.

This mozc_server process has been started during uim-qt5
(a QPlatformInputContext) startup in the SplashApp
initialization phase at ksplash/ksplashqml/main.cpp:92.

Due to the upstream commit the splash screen daemon does not close file
descriptors before the SplashApp initialization, thus its subprocess
shares the fds.

The commit log states Wayland initialization of this daemon needs the
channels. While it may require open file descriptors 0, 1 or 2,
no one should expect the process to talk to the parent through the
descriptors, since the splash screen is a daemon.

An attached patch reverts the commit and redirects the file descriptors
to /dev/null.

MR.Yoshino created a patch which revise this problem.
Could you check this patch?

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

[kde] [Bug 380494] New: Akonadi baloo crash

[Jens Mander]

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

Bug ID: 380494
   Summary: Akonadi baloo crash
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jem...@mailmaxe.de
  Target Milestone: ---

Application: akonadi_baloo_indexer (4.14)
KDE Platform Version: 4.14.30
Qt Version: 4.8.7
Operating System: Linux 4.10.0-22-lowlatency x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
several prblems starting akonadi:

org.kde.pim.akonadi_search_xapian: Could not obtain lock for Xapian Database.
This is bad
org.kde.pim.akonadicontrol: Agent instance "akonadi_baloo_indexer" has no
interface!
org.kde.pim.akonadicontrol: Agent instance "akonadi_baloo_indexer" has no
interface!
akonadi_baloo_indexer(9079): Could not obtain lock for Xapian Database. This is
bad 
akonadi_baloo_indexer(9079): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/werner/.local/share/baloo/notes/: already locked" 
akonadi_baloo_indexer(9079): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/werner/.local/share/baloo/calendars/: already locked" 
akonadi_baloo_indexer(9079)/libakonadi: Unable to register service
"org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" 
KCrash: Application 'akonadi_baloo_indexer' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/werner/.kde/socket-mobiLX/kdeinit4__0
org.kde.pim.akonadicontrol: ProcessControl: Application
"/usr/bin/akonadi_baloo_indexer" stopped unexpectedly ( "Der Prozess ist
abgestürzt" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_baloo_indexer'
crashed! 1 restarts left.
QProcess: Destroyed while process ("/usr/bin/akonadi_baloo_indexer") is still
running.
org.kde.pim.akonadicontrol: ProcessControl: Application
"/usr/bin/akonadi_baloo_indexer" stopped unexpectedly ( "Der Prozess ist
abgestürzt" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_baloo_indexer'
crashed! 0 restarts left.
akonadi_baloo_indexer(9197): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/werner/.local/share/baloo/email/: already locked" 
akonadi_baloo_indexer(9197): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/werner/.local/share/baloo/emailContacts/: already
locked" 
akonadi_baloo_indexer(9197): Could not obtain lock for Xapian Database. This is
bad 
akonadi_baloo_indexer(9197): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/werner/.local/share/baloo/notes/: already locked" 
akonadi_baloo_indexer(9197): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/werner/.local/share/baloo/calendars/: already locked" 
akonadi_baloo_indexer(9197)/libakonadi: Unable to register service
"org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" 
KCrash: Application 'akonadi_baloo_indexer' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/werner/.kde/socket-mobiLX/kdeinit4__0

The crash can be reproduced every time.

-- Backtrace:
Application:  (akonadi_baloo_indexer), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f4311fc377f in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:58
#7  0x7f4311fc537a in __GI_abort () at abort.c:89
#8  0x7f4315ba6f15 in qt_message_output(QtMsgType, char const*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f43146d9cc7 in  () at /usr/lib/libakonadi-kde.so.4
#10 0x7f43146d918a in  () at /usr/lib/libakonadi-kde.so.4
#11 0x7f4315cdbd11 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x7f431321a03c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7f4313220f76 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x7f4313f7ef5a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkdeui.so.5
#15 0x7f4315cc18ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x7f4315cc5366 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x7f4315cf209e in  () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7f4311686377 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f43116865e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f431168668c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f4315cf220e in

[krita] [Bug 380436] Adding a shape crashes the program

[mvowada]

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

--- Comment #3 from mvowada  ---
( maybe similar to Bug 378328  )

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

[kate] [Bug 310314] Opening two fish:// files with same name but different URL make the full path in window title to fail

[Darren Lissimore]

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

Darren Lissimore  changed:

   What|Removed |Added

 CC||darren.lissim...@gmail.com

--- Comment #1 from Darren Lissimore  ---
Just tried reproducing this one following the steps described and can't
reproduce.
Used kate from git build from commit e4f135bddb2f894f0f776b7f75384e8ef3cb661a.

Think that bug is not an issue anymore. Would recommend closing.

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

[krita] [Bug 380436] Adding a shape crashes the program

[mvowada]

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

--- Comment #2 from mvowada  ---
Created attachment 105861
  --> https://bugs.kde.org/attachment.cgi?id=105861=edit
Video example

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

[krita] [Bug 380436] Adding a shape crashes the program

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from mvowada  ---
Created attachment 105860
  --> https://bugs.kde.org/attachment.cgi?id=105860=edit
GDB report

I think I can confirm this behaviour on Ubuntu 14.04 with Krita 3.1.4 appimage.
Please, see the video example and the gdb report.

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

[krita] [Bug 380437] Save does not work when I only change layer name

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[krita] [Bug 380437] Save does not work when I only change layer name

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from mvowada  ---
(This is on Ubuntu 14.04 with Krita 3.1.4 appimage). I think I can confirm this
behaviour with *.kra files too, in my case it happens whenever I change the
layer name without accessing the layer Property dialog (important).

Steps to reproduce:

- open an existing *.ora or *.kra file,
- change a layer name on the "Layers" docker just by double clicking on the
name (important)
- save the file (either by doing "CTRL+S" or by going to menu "File > Save")
- close and reopen.

Actual results: the file has not been saved, the layer name has not been saved.
Expected results: save the file even after changing the layer name without
accessing the Property dialog?

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

[kwin] [Bug 380493] New: KWin crashes when title of a window changes

[VaryHeavy]

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

Bug ID: 380493
   Summary: KWin crashes when title of a window changes
   Product: kwin
   Version: 5.8.7
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: anvar...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.7)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.4.0-79-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

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

I am writing a text note in Kate, and when I saved the note (and window title
changed), KWin crashed.
In addition, I had some other applications opened, like Firefox, Dolphin,
Telegram Desktop or Avidemux.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8675559900 (LWP 1809))]

Thread 8 (Thread 0x7f8654b8c700 (LWP 21752)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8672d1c9fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1d8e5e0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x228d988,
mutex=mutex@entry=0x228d980, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f866e3b547d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x228d978) at scenegraph/qsgthreadedrenderloop.cpp:242
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x228d900) at
scenegraph/qsgthreadedrenderloop.cpp:690
#5  0x7f866e3b5d55 in QSGRenderThread::run (this=0x228d900) at
scenegraph/qsgthreadedrenderloop.cpp:719
#6  0x7f8672d1bb48 in QThreadPrivate::start (arg=0x228d900) at
thread/qthread_unix.cpp:368
#7  0x7f866ed8c6ba in start_thread (arg=0x7f8654b8c700) at
pthread_create.c:333
#8  0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f86569d0700 (LWP 21751)):
#0  0x7f867504fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8672f37aaa in poll (__timeout=, __nfds=1,
__fds=0x7f8648012898) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f8648012898) at
kernel/qcore_unix.cpp:83
#3  qt_safe_poll (fds=0x7f8648012898, nfds=1, timeout_ts=timeout_ts@entry=0x0)
at kernel/qcore_unix.cpp:102
#4  0x7f8672f39392 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f8672ee70ba in QEventLoop::exec (this=this@entry=0x7f86569cfca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8672d16f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f866dee9bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f8672d1bb48 in QThreadPrivate::start (arg=0x226cdf0) at
thread/qthread_unix.cpp:368
#9  0x7f866ed8c6ba in start_thread (arg=0x7f86569d0700) at
pthread_create.c:333
#10 0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f86456ad700 (LWP 1992)):
#0  0x7f867504fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8672f37aaa in poll (__timeout=, __nfds=1,
__fds=0x7f863c000a58) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f863c000a58) at
kernel/qcore_unix.cpp:83
#3  qt_safe_poll (fds=0x7f863c000a58, nfds=1, timeout_ts=timeout_ts@entry=0x0)
at kernel/qcore_unix.cpp:102
#4  0x7f8672f39392 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f8672ee70ba in QEventLoop::exec (this=this@entry=0x7f86456acca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8672d16f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f866dee9bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f8672d1bb48 in QThreadPrivate::start (arg=0x17a23b0) at
thread/qthread_unix.cpp:368
#9  0x7f866ed8c6ba in start_thread (arg=0x7f86456ad700) at
pthread_create.c:333
#10 0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f863bfff700 (LWP 1920)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f86720b36f4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f86720b3739 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f866ed8c6ba in start_thread (arg=0x7f863bfff700) at
pthread_create.c:333
#4  0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f8655c21700 (LWP 

[digikam] [Bug 374783] Window location is not restored correctly after restart

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #4 from caulier.gil...@gmail.com ---
This problem is reproducible with current 5.6.0 pre release installer for
Windows ?

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[krita] [Bug 380486] Brushs Greyed out and not selectable

[mvowada]

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

--- Comment #2 from mvowada  ---
(maybe you already know, a couple of links about tags and the pop-up palette)
- https://docs.krita.org/Tag_System
- https://docs.krita.org/Special:MyLanguage/Navigation#Pop-up_Palette

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

[digikam] [Bug 380434] 5.6.0-pre pkg does not detect filesystem changes

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
I cannot reproduce the dysfunction on my Macbook pro 2012 with last Sierra
10.12.5

Did you already seen this dysfunction with older digiKam versions ?

In last 5.6.0 PKG, nothing has changed. Same Qt version is used (5.7.1) and we
use Qt to handle file changes notifications. The PKG has KF5 update, Exiv2, and
QtAV.

It will help to see want DK print as debug statements in the console at run
time while disk changes. To run it from a console, look the "Freezes and Other
Issues" section here :

https://www.digikam.org/contribute/

Gilles Caulier

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

[kwin] [Bug 380492] Touch Screen edge action "grabs" mouse clicks on fullscreen games

[Yannick]

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

--- Comment #1 from Yannick  ---
Sorry, I forgot to mention that I use the X11 Plasma session, with xorg-server
1.19.3 and nvidia 381.22 drivers.

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

[kwin] [Bug 380492] New: Touch Screen edge action "grabs" mouse clicks on fullscreen games

[Yannick]

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

Bug ID: 380492
   Summary: Touch Screen edge action "grabs" mouse clicks on
fullscreen games
   Product: kwin
   Version: 5.10.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: leguen.yann...@gmail.com
  Target Milestone: ---

With Plasma 5.10.0 from ArchLinux repositories, I noticed some unresponsive
clicks on fullscreen video games, such as Xonotic 0.8.2 (SDL executable).

By default, one touchscreen left edge action was configured.
After disabling this action and restarting kwin, the issue is gone, no more
mouse issues with fullscreen games.

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

[krita] [Bug 380486] Brushs Greyed out and not selectable

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from mvowada  ---
(In reply to Nicole from comment #0)
> Created attachment 105856 [details]
> Krita brush bug
> 
> I don't have a tablet (yet) so all I use is a mouse.  I have not downloaded
> nor created any brushes as of yet, so I am using the default brushes.  So
> now the real problem. Every time I right click so that I can select a
> different brush, all the brushes are grey and are not selectable.  I am
> stuck using only a single brush.  I have uninstalled and reinstalled Krita
> and it has not fixed the problem.  I will provide a screenshot of the
> problem.

Hi Nicole, have you tried by pressing the wrench icon on the pop-up palette (at
the bottom right)? That should allow you to populate the slots with the presets
of any tags you have set.

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

[Discover] [Bug 380488] Discover locks up after a keyword search and then going back.

[Gopal]

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

--- Comment #2 from Gopal  ---
Maybe related to problem is that my display DPI is set to 66 to reduce all font
sizes. Discover alone is unique in rendering unreadable "greek" text before the
first window change (update).

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

[kscreenlocker] [Bug 380491] kscreenlocker_greet incorrect behaviour after pressing enter key with empty password

[Bhargavi H R]

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

Bhargavi H R  changed:

   What|Removed |Added

 CC||hrbharg...@gmail.com

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

[kscreenlocker] [Bug 380491] New: kscreenlocker_greet incorrect behaviour after pressing enter key with empty password

[Bhargavi H R]

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

Bug ID: 380491
   Summary: kscreenlocker_greet incorrect behaviour after pressing
enter key with empty password
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: hrbharg...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

Version: 5.10.0

In locked screen of KDE plasma 5.10, if you press enter/return key without
entering any password, then after that even if you enter correct password it
says 'Unlocking failed'.

Please fix it soon.

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

[Discover] [Bug 380488] Discover locks up after a keyword search and then going back.

[Gopal]

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

--- Comment #1 from Gopal  ---
Created attachment 105859
  --> https://bugs.kde.org/attachment.cgi?id=105859=edit
valgrind log, crash comes when exiting Discover

Discover was run as root, with valgrind prefix.

Middle part of the log file is absent (nothing new there).

A few applications were successfully installed, crash comes when exiting
Discover (this is typical).

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