[kwin] [Bug 381516] New: kwin_x11 started crashing each time when I log in

[Magik]

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

Bug ID: 381516
   Summary: kwin_x11 started crashing each time when I log in
   Product: kwin
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: magicznyk...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-24-lowlatency x86_64
Distribution: Ubuntu 17.04

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

I was tryint to login in into systems. It crashes each time. The problem
started after 'apt upgrade' made at 20th f June 2017.

The crash can be reproduced every time.

-- 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 0x7fe6634ec940 (LWP 4797))]

Thread 4 (Thread 0x7fe637fff700 (LWP 4974)):
#0  0x7fe65c623510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe65f94e2c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fe65f94e309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fe65c61d6da in start_thread (arg=0x7fe637fff700) at
pthread_create.c:456
#4  0x7fe662f29d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fe6411f9700 (LWP 4971)):
#0  0x7fe662f1de51 in __GI_ppoll (fds=0x7fe63ac8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fe6607e4251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fe6607e5b4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fe66079288a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fe6605bffe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fe65b38adf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fe6605c4c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fe65c61d6da in start_thread (arg=0x7fe6411f9700) at
pthread_create.c:456
#8  0x7fe662f29d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fe64b173700 (LWP 4813)):
#0  0x7fe662f1dd8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe657c23576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe657c2368c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe6607e8f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fe66079288a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fe6605bffe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fe65a5635c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fe6605c4c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fe65c61d6da in start_thread (arg=0x7fe64b173700) at
pthread_create.c:456
#9  0x7fe662f29d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fe6634ec940 (LWP 4797)):
[KCrash Handler]
#6  0x7fe635c118d4 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#7  0x7fe635c16515 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#8  0x7fe635c166eb in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#9  0x7fe635c0f986 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#10 0x7fe635914359 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#11 0x7fe635be98c4 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#12 0x7fe635be9fde in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#13 0x7fe635bea6fa in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#14 0x7fe635baa026 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#15 0x7fe65900945e in  () at /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#16 0x7fe658fdc0cc in glXMakeCurrentReadSGI () at
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#17 0x7fe6485d55c8 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#18 0x7fe6485d3987 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#19 0x7fe64a0a3451 in
QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#20 0x7fe660d15f3d in QOpenGLContext::create() () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#21 0x7fe65ba4d25b in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#22 0x7fe65ba4dc88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#23 0x7fe660ce4

[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions

[Petr Nehez]

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

--- Comment #4 from Petr Nehez  ---
Could it be related to #340548?

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

[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions

[Petr Nehez]

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

--- Comment #3 from Petr Nehez  ---
1 thing I have noticed - after restart of the system there was no primary
output set - see screenshots "monitor-1" and "monitor-0".

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

[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions

[Petr Nehez]

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

--- Comment #2 from Petr Nehez  ---
Created attachment 106223
  --> https://bugs.kde.org/attachment.cgi?id=106223&action=edit
monitor-1

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

[KScreen] [Bug 381515] New: KScreen has problem with multiple monitors with different resolutions

[Petr Nehez]

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

Bug ID: 381515
   Summary: KScreen has problem with multiple monitors with
different resolutions
   Product: KScreen
   Version: 5.10.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: petr.ne...@gmail.com
  Target Milestone: ---

I have a Dell Precision 3510 laptop which has 1920x1080 screen.
I use this laptop with 2 monitors on different places:
1) Dell U2415 with 1920x1200,
2) Eizo EV2450 with 1920x1080.

I will describe now my problem (both monitors have been already correctly set
long time ago):
* I started my laptop and then connected Dell monitor and the resolution on
this monitor was correctly set to 1920x1200.
* I disconnected Dell monitor and put a laptop into Sleep mode.
* Then I resumed the laptop and worked on it without any monitor and after 2
hours I put it into Sleep mode again.
* At home I resumed the laptop, plugged Eizo monitor but it has not been
correctly detected as Eizo but as Dell as shown on the screenshot "monitor-0".
* After restart of the system and plugging of Eizo again this monitor has been
correctly detected as Eizo as shown on "monitor-1".

These steps do not show the real problem but if we would swap usage of those
monitors in the description we would end up with Dell 1920x1200 detected as
Eizo but with the resolution set to 1920x1080 and in this case we would have to
set it manually to 1920x1200 but this would lead to changing the KScreen's
configuration for Eizo and not for Dell.

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

[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions

[Petr Nehez]

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

--- Comment #1 from Petr Nehez  ---
Created attachment 106222
  --> https://bugs.kde.org/attachment.cgi?id=106222&action=edit
monitor-0

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

[valgrind] [Bug 381514] unhandled instruction 0xD53BE002

[bugzilla_noreply]

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

--- Comment #2 from soren.brinkm...@xilinx.com ---
Created attachment 106221
  --> https://bugs.kde.org/attachment.cgi?id=106221&action=edit
Full valgrind output

This is the output from the valgrind run with the '-v' option.

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

[valgrind] [Bug 381514] unhandled instruction 0xD53BE002

[bugzilla_noreply]

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

--- Comment #1 from soren.brinkm...@xilinx.com ---
uname -a:
Linux plnx_aarch64 4.9.0 #141 SMP Wed Jun 21 15:49:29 PDT 2017 aarch64 aarch64
aarch64 GNU/Linux

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

[valgrind] [Bug 381514] New: unhandled instruction 0xD53BE002

[bugzilla_noreply]

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

Bug ID: 381514
   Summary: unhandled instruction 0xD53BE002
   Product: valgrind
   Version: 3.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: soren.brinkm...@xilinx.com
  Target Milestone: ---

I have an aarch64 Linux application that has the following instruction in its
code:
   7d48c:   d53be002mrs x2, cntfrq_el0

That causes valgrind to abort execution with
ARM64 front end: branch_etc
disInstr(arm64): unhandled instruction 0xD53BE002
disInstr(arm64): 1101'0101 0011'1011 1110' '0010
==2561== valgrind: Unrecognised instruction at address 0x48eb48c.
==2561==at 0x48EB48C: xlnkGetGlobalCounter (in
/media/card/libfilter2d_optflow.so)
==2561== Your program just tried to execute an instruction that Valgrind
==2561== did not recognise.  There are two possible reasons for this.
==2561== 1. Your program has a bug and erroneously jumped to a non-code
==2561==location.  If you are running Memcheck and you just saw a
==2561==warning about a bad jump, it's probably your program's fault.
==2561== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2561==i.e. it's Valgrind's fault.  If you think this is the case or
==2561==you are not sure, please let us know and we'll try to fix it.
==2561== Either way, Valgrind will now raise a SIGILL signal which will
==2561== probably kill your program.
==2561==
==2561== Process terminating with default action of signal 4 (SIGILL)
==2561==  Illegal opcode at address 0x48EB48C
==2561==at 0x48EB48C: xlnkGetGlobalCounter (in
/media/card/libfilter2d_optflow.so)

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

[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"

[C . Brouerius van Nidek]

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

C. Brouerius van Nidek  changed:

   What|Removed |Added

 CC||const...@indo.net.id

--- Comment #2 from C. Brouerius van Nidek  ---
Have this problem also . Just two days ago I manually moved the (old) new
emails into the cur accounts. Do this already for the last 6 month's.
It is one of the problems I face but I do not know if this behaviour has any
influence on the other more problematic kmail problems like a broken duplicate
handling etc. etc.

opensuse:tumbleweed:20170620
Qt: 5.9.0
KDE Frameworks: 5.34.0
kf5-config: 1.0
KDE Plasma: 5.10.2
plasmashell 5.10.2
Kernel: 4.11.6-1-default

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

[plasmashell] [Bug 375535] Global Menu Bar widget does not open menus on hover

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||i9i7s...@gmail.com

--- Comment #13 from Kai Uwe Broulik  ---
*** Bug 376725 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 376725] Global menu doesn't respond to mouse hover

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #8 from Kai Uwe Broulik  ---


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

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

[digikam] [Bug 381510] "open with" on multiple images only passes first image

[Peter]

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

--- Comment #2 from Peter  ---
(In reply to Maik Qualmann from comment #1)
> Problem is not reproducible here. When I select multiple images and use open
> with Gwenview, for example, the selected images are opened. It depends on
> the command line parameter %f and %u for single file or %F and %U for
> multiple files. If no command line parameter specified, the open function in
> digiKam uses single file. This behavior would be changeable.
> 
> Maik

You are correct, I wasn't using %F.  When no parameter worked I assumed that
was the way to do it.

However, when using %F I would expect one execution with all images and with %f
I would expect multiple executions with one image each.

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

[kwin] [Bug 361241] Double click to maximize does not work in some situations

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

   Version Fixed In||5.10.3
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kwi
   ||n/152be60cc04f81fb54fdbe0af
   ||ec41470aa188d54

--- Comment #14 from Martin Flöser  ---
Git commit 152be60cc04f81fb54fdbe0afec41470aa188d54 by Martin Flöser.
Committed on 22/06/2017 at 05:07.
Pushed by graesslin into branch 'Plasma/5.10'.

Fix double click on window deco if tripple clicked

Patch by Thomas Lübking which got lost in bugs.kde.org.
FIXED-IN: 5.10.3

M  +1-1abstract_client.cpp

https://commits.kde.org/kwin/152be60cc04f81fb54fdbe0afec41470aa188d54

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

[kontact] [Bug 381473] Clicking "Read Manual" in Kontact Introduction sends to 404 page

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #4 from Laurent Montel  ---
It was fixed in last version.
We moved doc in kmail2 and forgot to update url.
You need to update to last version.
Regards.

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

[marble] [Bug 381511] GeoDataLineString::setTessellate function fails to unset tessellation.

[Dennis Nienhüser]

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

Dennis Nienhüser  changed:

   What|Removed |Added

 CC||nienhue...@kde.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Dennis Nienhüser  ---
Good catch. For applying the changes it would be great if you could create a
review request in http://phabricator.kde.org (Differential) from the patch.

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

[konsole] [Bug 366368] No transparent background when compositor is enabled

[John Andrew McInnes]

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

John Andrew McInnes  changed:

   What|Removed |Added

 CC||s...@forceway.com

--- Comment #6 from John Andrew McInnes  ---
KDE Plasma 5.10.0
KDE Frameworks 5.34.0
x86_64

I have encountered this bug in Konsole version 17.04.1. Konsole is
started/restored on login as per my previous session. Transparency is not
working and I get the message on the appearance tab. If I exit and restart
Konsole it works again. Maybe Konsole is starting too soon? Kind of annoying,
but not a major bug.

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

[digikam] [Bug 381510] "open with" on multiple images only passes first image

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Problem is not reproducible here. When I select multiple images and use open
with Gwenview, for example, the selected images are opened. It depends on the
command line parameter %f and %u for single file or %F and %U for multiple
files. If no command line parameter specified, the open function in digiKam
uses single file. This behavior would be changeable.

Maik

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

[Discover] [Bug 381513] New: Discover Crashed while installing updates.

[Delfino]

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

Bug ID: 381513
   Summary: Discover Crashed while installing updates.
   Product: Discover
   Version: 5.10.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: delfino.nunez@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.8.0-56-generic x86_64
Distribution: KDE neon User Edition 5.10

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

I tried to install updates, I pressed the "Update All" button it then hang for
a little, I closed Discover and tried to install the updates again and then it
crashed.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f95ec79f8c0 (LWP 3350))]

Thread 9 (Thread 0x7f95aefdf700 (LWP 3360)):
#0  0x7f95e89d170d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f95e3dd838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f95e3dd849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f95e95faadb in QEventDispatcherGlib::processEvents
(this=0x7f959c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f95e95a430a in QEventLoop::exec (this=this@entry=0x7f95aefded00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f95e93d3af4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f95e93d8509 in QThreadPrivate::start (arg=0xdcae60) at
thread/qthread_unix.cpp:368
#7  0x7f95e5e356ba in start_thread (arg=0x7f95aefdf700) at
pthread_create.c:333
#8  0x7f95e89dd3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f95b48f7700 (LWP 3358)):
#0  0x7f95e89d170d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f95e3dd838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f95e3dd849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f95e95faadb in QEventDispatcherGlib::processEvents
(this=0x7f95a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f95e95a430a in QEventLoop::exec (this=this@entry=0x7f95b48f6d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f95e93d3af4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f95e93d8509 in QThreadPrivate::start (arg=0x18c3550) at
thread/qthread_unix.cpp:368
#7  0x7f95e5e356ba in start_thread (arg=0x7f95b48f7700) at
pthread_create.c:333
#8  0x7f95e89dd3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f95b7584700 (LWP 3357)):
#0  0x7ffe8b1fd939 in ?? ()
#1  0x7ffe8b1fdbd6 in clock_gettime ()
#2  0x7f95e89eb836 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f95b7583a60) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f95e95f9c51 in qt_clock_gettime (ts=0x7f95b7583a60, clock=) at kernel/qelapsedtimer_unix.cpp:111
#4  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#5  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#6  0x7f95e95f8449 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f95b0001470) at kernel/qtimerinfo_unix.cpp:91
#7  0x7f95e95f89b5 in QTimerInfoList::timerWait (this=0x7f95b0001470,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#8  0x7f95e95fa09e in timerSourcePrepareHelper (timeout=0x7f95b7583b34,
src=) at kernel/qeventdispatcher_glib.cpp:132
#9  timerSourcePrepare (source=, timeout=0x7f95b7583b34) at
kernel/qeventdispatcher_glib.cpp:165
#10 0x7f95e3dd791d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f95e3dd82bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f95e3dd849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f95e95faadb in QEventDispatcherGlib::processEvents
(this=0x7f95b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7f95e95a430a in QEventLoop::exec (this=this@entry=0x7f95b7583d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#15 0x7f95e93d3af4 in QThread::exec (this=) at
thread/qthread.cpp:515
#16 0x7f95e93d8509 in QThreadPrivate::start (arg=0x1dc4990) at
thread/qthread_unix.cpp:368
#17 0x7f95e5e356ba in start_thread (arg=0x7f95b7584700) at
pthread_create.c:333
#18 0x7f95e89dd3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f95c1205700 (LWP 3355)):
#0  0x7f95e3e1ca94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f95e3dd7bf9 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x

[plasmashell] [Bug 381512] New: Plasma se detuvo al configurar Gmail feed

[Gustavo]

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

Bug ID: 381512
   Summary: Plasma se detuvo al configurar Gmail feed
   Product: plasmashell
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gnv...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Estaba configurando el plasmoid Gmail feed. Se cerro el panel principal donde
esta la bandeja de sistema y el reloj; se volvió a abrir rápidamente, como si
se hubiese reiniciado.

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

Thread 10 (Thread 0x7fd1fe7fc700 (LWP 2858)):
#0  0x7fd30ac75229 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fd30ac75b2b in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fd30ac75d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fd3109e2e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fd31098921a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fd3107ab40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fd31391a645 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fd3107afcbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7fd30f978297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fd3100c425f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fd25b252700 (LWP 711)):
#0  0x7fd316976446 in _dl_update_slotinfo () at /lib64/ld-linux-x86-64.so.2
#1  0x7fd31697667c in update_get_addr () at /lib64/ld-linux-x86-64.so.2
#2  0x7fd3107aeb46 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fd3109e260a in  () at /usr/lib/libQt5Core.so.5
#4  0x7fd30ac75138 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#5  0x7fd30ac75b2b in  () at /usr/lib/libglib-2.0.so.0
#6  0x7fd30ac75d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#7  0x7fd3109e2e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#8  0x7fd31098921a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#9  0x7fd3107ab40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#10 0x7fd3107afcbd in  () at /usr/lib/libQt5Core.so.5
#11 0x7fd30f978297 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7fd3100c425f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fd260faa700 (LWP 710)):
#0  0x7fd30ac72b38 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fd30ac7506b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fd30ac75b2b in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fd30ac75d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fd3109e2e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fd31098921a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fd3107ab40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fd2601533c5 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#8  0x7fd3107afcbd in  () at /usr/lib/libQt5Core.so.5
#9  0x7fd30f978297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fd3100c425f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fd25bfff700 (LWP 708)):
#0  0x7fd3100ba2bd in poll () at /usr/lib/libc.so.6
#1  0x7fd30ac75bf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fd30ac75d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fd3109e2e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fd31098921a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fd3107ab40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fd3144d2836 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7fd3107afcbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7fd30f978297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fd3100c425f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fd2e7fff700 (LWP 679)):
#0  0x7fd30f97e39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd3161edac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fd3161edb09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fd30f978297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fd3100c425f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fd2f2772700 (LWP 678)):
#0  0x7fd3100ba2bd in poll () at /usr/lib/libc.so.6
#1  0x7fd30ac75bf

[marble] [Bug 381511] GeoDataLineString::setTessellate function fails to unset tessellation.

[Dean Adamson]

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

--- Comment #1 from Dean Adamson  ---
Happy to fix this my self if someone would pass me the instructions on how to
submit my changes.

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

[marble] [Bug 381511] New: GeoDataLineString::setTessellate function fails to unset tessellation.

[Dean Adamson]

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

Bug ID: 381511
   Summary: GeoDataLineString::setTessellate function fails to
unset tessellation.
   Product: marble
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: dadamson.dumping.gro...@gmail.com
  Target Milestone: ---

When you pass in false into the function GeoDataLineString::setTessellate in
GeoDataLineString.cpp lines 478-493, it can actually set tessellation on
instead of off. This happens because the function is using a xor operator when
it should be using an and operator. See below:

if ( tessellate ) {
p()->m_tessellationFlags |= Tessellate;
p()->m_tessellationFlags |= RespectLatitudeCircle;
} else {
p()->m_tessellationFlags ^= Tessellate;
p()->m_tessellationFlags ^= RespectLatitudeCircle;
}

The above should really be the following:

if ( tessellate ) {
p()->m_tessellationFlags |= (Tessellate | RespectLatitudeCircle);
} else {
p()->m_tessellationFlags &= ~(Tessellate | RespectLatitudeCircle);
}

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

[digikam] [Bug 381510] New: "open with" on multiple images only passes first image

[Peter]

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

Bug ID: 381510
   Summary: "open with" on multiple images only passes first image
   Product: digikam
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: ra...@batpudding.com
  Target Milestone: ---

Selecting multiple images and doing an "open with" only passes the first image
to the external program.

I would expect it to either do all images as arguments for one run or one
execution for each image.

This can be tested easily enough by making a shell script like these:

#!/bin/bash
zenity --info --text="$*"

or

#!/bin/bash
echo "$*" > /tmp/results.txt

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

[tellico] [Bug 378477] Can't see the star icon in the column view and in the entry editor

[Robby Stephenson]

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

Robby Stephenson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||3.1
  Latest Commit||https://commits.kde.org/tel
   ||lico/94376ac3c82942a26c2cf7
   ||48a5072278c57e6405

--- Comment #11 from Robby Stephenson  ---
Git commit 94376ac3c82942a26c2cf748a5072278c57e6405 by Robby Stephenson.
Committed on 22/06/2017 at 02:16.
Pushed by rstephenson into branch 'master'.

Add a QRC file for the internal icons

Use the internal resources icons when appropriate. Otherwise, check for
icons from the theme and fall back to internal ones when needed.

I can't verify this, but I expect it to fix Bug 378477.

Also scrub icons from several data sources.
FIXED-IN: 3.1

A  +51   -0icons/icons.qrc
M  +4-0src/CMakeLists.txt
M  +2-1src/borrowerdialog.cpp
M  +1-1src/configdialog.cpp
M  +2-2src/entryeditdialog.cpp
M  +1-1src/fetch/amazonfetcher.cpp
M  +1-1src/fetch/bibliosharefetcher.cpp
M  +1-1src/fetch/bibsonomyfetcher.cpp
M  +1-1src/fetch/boardgamegeekfetcher.cpp
M  +1-1src/fetch/hathitrustfetcher.cpp
M  +1-1src/fetch/ibsfetcher.cpp
M  +1-1src/fetch/imdbfetcher.cpp
M  +1-1src/fetch/moviemeterfetcher.cpp
M  +1-1src/fetch/musicbrainzfetcher.cpp
M  +1-1src/fetch/openlibraryfetcher.cpp
M  +1-1src/fetch/videogamegeekfetcher.cpp
M  +1-1src/fetch/z3950fetcher.cpp
M  +4-3src/fetchdialog.cpp
M  +4-4src/groupview.cpp
M  +2-2src/gui/collectiontypecombo.cpp
M  +2-2src/gui/ratingwidget.cpp
M  +1-1src/gui/starrating.cpp
M  +3-1src/loandialog.cpp
M  +3-1src/main.cpp
M  +34   -22   src/mainwindow.cpp
M  +1-1src/models/borrowermodel.cpp
M  +2-2src/models/entrygroupmodel.cpp
M  +3-3src/models/entrymodel.cpp
M  +1-1src/models/filtermodel.cpp
M  +2-2src/utils/tellico_utils.cpp

https://commits.kde.org/tellico/94376ac3c82942a26c2cf748a5072278c57e6405

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

[partitionmanager] [Bug 378607] virtio devices not found (vda)

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Status|VERIFIED|RESOLVED
  Latest Commit|https://commits.kde.org/kpm |https://commits.kde.org/kpm
   |core/fda1e219de430d1301839e |core/a35702e9113d655ffcc4b2
   |27790e108b12c4  |ffc06e791f256d0beb

--- Comment #12 from Andrius Štikonas  ---
Git commit a35702e9113d655ffcc4b2ffc06e791f256d0beb by Andrius Štikonas.
Committed on 22/06/2017 at 02:11.
Pushed by stikonas into branch 'master'.

Use lsblk's TYPE=disk when scanning for devices.

The previous way relied on kernel device numbers but this gets ugly, especially
in cases when device number is not assigned such as virtio disks.

M  +2-2src/backend/corebackend.cpp
M  +16   -19   src/plugins/libparted/libpartedbackend.cpp

https://commits.kde.org/kpmcore/a35702e9113d655ffcc4b2ffc06e791f256d0beb

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

[valgrind] [Bug 381509] New: Valgrind reports error: Unrecognised instruction at address 0x60f0b15

[Santosh]

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

Bug ID: 381509
   Summary: Valgrind reports error: Unrecognised instruction at
address 0x60f0b15
   Product: valgrind
   Version: 3.11.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: pleasedol...@outlook.com
  Target Milestone: ---

I was trying to incorporate valgrind to check the memory leakage in our project
in Linux, I have called the test executable along with the valgrind. But the
valgrind says Unrecognized instruction at address 0x60f0b15. Following are more
details about our environment 
1. Boost Libraries are used in the project 
2. GTest frame work is used for carrying out the testcases 
3. I also observed that the error : cannot open
/usr/bin/log/valgrind_2017-06-21 16:04:33.log file
4. There is one message for boost library saying :
boost::filesystem::create directory: permission denied : "usr/bin/log"

Program opens and terminates when run normally with out valgrind,

Could you please help me with the considerations to be taken, if any, while we
are running the valgrind along with the boost libraries and gtest framework.
Please feel free to ask if anymore details are needed. 
Appreciate your help !

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

[konsole] [Bug 381350] Regular Konsole opens to Super Root for a password instead of user bash.

[bugzilla_noreply]

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

--- Comment #18 from ja...@insiberia.net ---
Wolfgang Bauer:
> https://bugs.kde.org/show_bug.cgi?id=381350
> 
> --- Comment #17 from Wolfgang Bauer  ---
> (In reply to james from comment #16)
>> it did one thing, the screen was stuck on a white background, now it's
>> black. but still a password prompt.
> 
> Yes, black is the default background, and white the default for openSUSE's
> "Root Shell" profile.
> 
> What password prompt are you still getting?
> 
> I have to admit that I'm running out of ideas now, and I'm not really sure 
> what
> your current problem is.
> 
> But, to repeat myself:
> 
> Try a fresh user account. Does the same happen there too?
> 
> Or create a new profile in Konsole and set it as default.
> But to be sure, do it like this:
> - Go into Settings-> Manage Profiles
> - Click on an empty space to make sure that no profile is pre-selected (that
> would be taken as "template")
> - Click on "New Profile..."
> - Make sure that there's no mention of "su" in the "Command" text field (it
> should likely be "/bin/bash")
> - Click "Ok", you should get back to the previous dialog
> - Select your newly created profile, if it's not already selected
> - Click on the "Set as Default" button
> 
I've tried everything you've suggested. the password prompt is
"Password:" no prompt for my user. i'm just gonna use the
gnome-terminal. thanks for your help.

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

[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized

[John Reiser]

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

--- Comment #1 from John Reiser  ---
Using reasoning that is similar to that the NOT_EQUAL operator (not_equal in
any bit position that is initialized, implies not_equal in the whole word,
regardless of uninit bits in other positions), then the "read-only" operator
EQUAL_TO_A_CONSTANT can *change* the initialization status of bits in memory.

One version of actual code {loop(j): if (rv[j] != 0) rv[j] = 0)} for i386 is
   0xe10102 <__malloc0+27>: add$0x3,%ebx   // length in bytes
   0xe10105 <__malloc0+30>: xor%edx,%edx   // j = 0;
   0xe10107 <__malloc0+32>: shr$0x2,%ebx   // length in words
   0xe1010a <__malloc0+35>: cmp%edx,%ebx
   0xe1010c <__malloc0+37>: je 0xe1011e <__malloc0+55>  // array is
empty
   0xe1010e <__malloc0+39>: cmpl   $0x0,(%eax,%edx,4)  // if (0==rv[j])
   0xe10112 <__malloc0+43>: je 0xe1011b <__malloc0+52>  // already 0
   0xe10114 <__malloc0+45>: movl   $0x0,(%eax,%edx,4)  // rv[j] = 0;
   0xe1011b <__malloc0+52>: inc%edx  // ++j;
   0xe1011c <__malloc0+53>: jmp0xe1010a <__malloc0+35>

If the branch is taken in
   0xe1010e <__malloc0+39>: cmpl   $0x0,(%eax,%edx,4)  // if (0==rv[j])
   0xe10112 <__malloc0+43>: je 0xe1011b <__malloc0+52>  // already 0
then we know that the word in memory at address (%eax,%edx,4) is zero.  In
particular: ALL ITS BITS ARE NOW KNOWN TO BE INITIALIZED, regardless of
previous state!  So there were NO writes to memory, but the V bits must now be
all 1's (signifying initialized), even if previously some of them were 0
(signifying uninitialized).  So, EQUAL_TO_A_CONSTANT erases Uninitialized.

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

[plasmashell] [Bug 381266] Icontasks identifying Chrome apps as Chrome windows

[Ross Williams]

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

--- Comment #6 from Ross Williams  ---
(In reply to Kai Uwe Broulik from comment #5)

Thanks for the info. That approach sounds like a better solution to the regex
based approach. As you say the StartupWMClass and WM_CLASS are a match so it
should be working:

StartupWMClass=crx_gaedmjdfmmahhbjefcbgaolhhanlaolb
WM_CLASS(STRING) = "crx_gaedmjdfmmahhbjefcbgaolhhanlaolb", "Google-chrome"

One more observation for you: the correct icon shows during launch then
switches to being grouped under the chrome icon. Not sure if that indicates
anything?

I ran the searches that you suggested and nothing appeared out of place. I have
pasted the output below:

find /usr/share/applications/ -name *.desktop | xargs grep StartupWMClass

/usr/share/applications/libreoffice-draw.desktop:StartupWMClass=libreoffice-draw
/usr/share/applications/libreoffice-startcenter.desktop:StartupWMClass=libreoffice-startcenter
/usr/share/applications/libreoffice-base.desktop:StartupWMClass=libreoffice-base
/usr/share/applications/libreoffice-impress.desktop:StartupWMClass=libreoffice-impress
/usr/share/applications/libreoffice-writer.desktop:StartupWMClass=libreoffice-writer
/usr/share/applications/libreoffice-math.desktop:StartupWMClass=libreoffice-math
/usr/share/applications/google-chrome.desktop:StartupWMClass=Google-chrome
/usr/share/applications/google-chrome.desktop:StartupWMClass=Google-chrome
/usr/share/applications/google-chrome.desktop:StartupWMClass=Google-chrome
/usr/share/applications/sublime_text_3.desktop:StartupWMClass=subl3
/usr/share/applications/Discord.desktop:StartupWMClass=discord
/usr/share/applications/libreoffice-calc.desktop:StartupWMClass=libreoffice-calc

find ~/.local/share/applications -name *.desktop | xargs grep StartupWMClass 

/home/rwilliams/.local/share/applications/chrome-apdfllckaahabafndbhieahigkjlhalf-Default.desktop:StartupWMClass=crx_apdfllckaahabafndbhieahigkjlhalf
/home/rwilliams/.local/share/applications/chrome-fhbjgbiflinjbdggehcddcbncdddomop-Default.desktop:StartupWMClass=crx_fhbjgbiflinjbdggehcddcbncdddomop
/home/rwilliams/.local/share/applications/chrome-blpcfgokakmgnkcojhhkbfbldkacnbeo-Default.desktop:StartupWMClass=crx_blpcfgokakmgnkcojhhkbfbldkacnbeo
/home/rwilliams/.local/share/applications/chrome-pjkljhegncpnkpknbcohdijeoejaedia-Default.desktop:StartupWMClass=crx_pjkljhegncpnkpknbcohdijeoejaedia
/home/rwilliams/.local/share/applications/chrome-gaedmjdfmmahhbjefcbgaolhhanlaolb-Default.desktop:StartupWMClass=crx_gaedmjdfmmahhbjefcbgaolhhanlaolb
/home/rwilliams/.local/share/applications/chrome-aohghmighlieiainnegkcijnfilokake-Default.desktop:StartupWMClass=crx_aohghmighlieiainnegkcijnfilokake

I also tried clearing the ~/.local/share/applications directory of .desktop
files, deleted my Chrome profile and reinstalled Chrome just to get a fresh
environment and I am still suffering the issue on a fresh profile (not logged
in).

I'm going to have a look at the code myself when I get some time (use the ABS
in Arch to build my own copy of plasma-workspace) but I have one question from
a cursory glance at the code so far:

In terms of these two if blocks:

if (services.empty()) {
services = KServiceTypeTrader::self()->query(QStringLiteral("Application"),
QStringLiteral("exist Exec and ('%1' =~ StartupWMClass)").arg(appId));
}

if (services.empty()) {
services = KServiceTypeTrader::self()->query(QStringLiteral("Application"),
QStringLiteral("exist Exec and ('%1' =~
StartupWMClass)").arg(xWindowsWMClassName));
}

I assume xWindowsWMClassName maps to WM_CLASS but what does appId refer to?

Thanks your help. I understand it is hell trying to debug something you can't
reproduce :(

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

[dolphin] [Bug 381508] New: Make Dolphin calculate folder size in same units as file size (in KB, MB, GB, TB, etc.)

[J . B . Nicholson-Owens]

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

Bug ID: 381508
   Summary: Make Dolphin calculate folder size in same units as
file size (in KB, MB, GB, TB, etc.)
   Product: dolphin
   Version: 16.08.3
  Platform: Debian stable
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: j...@forestfield.org
  Target Milestone: ---

I noticed this on GNU/Linux but I believe this feature does not depend on the
OS.

Folders are listed with the size column showing the number of items inside the
folder. This is useless for determining which item in a folder uses up the most
space on the volume.

Instead, the size column should show the amount of storage space that folder
takes up (in KB, MB, GB, TB, etc.). As the folder's content changes, the size
is recomputed keeping this information updated.

I understand that implementing this will generate a lot of disk/network access
and that's okay. I'd like to have the option to see this information because
I'd like to have an always-updated view of which folders occupy a lot of space.
I'd like to get this information without another program (such as K4DirState)
or running:

  du --summarize --human-readable * |sort -hr |less

on the command line to get a list of items in the current working directory
sorted by their size (largest -> smallest).

This should be a togglable feature set to off by default, as it is in MacOS's
Finder. I'd like it if one could turn this on, wait while the folder sizes are
computed, and sort by size in a more meaningful way (no more using radically
different units for folders than files).

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

[ksmserver] [Bug 381507] New: ksmserver-logout-greeter shows title bar

[bugzilla_noreply]

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

Bug ID: 381507
   Summary: ksmserver-logout-greeter shows title bar
   Product: ksmserver
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ui
  Assignee: l.lu...@kde.org
  Reporter: yuval.leven...@edu.esiee.fr
  Target Milestone: ---

Created attachment 106220
  --> https://bugs.kde.org/attachment.cgi?id=106220&action=edit
Picture of ksmserver logout titlebar

Attached is a picture of how it looks like.

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

[kde-gtk-config] [Bug 378013] Honour systemwide gtk settings

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde
   |-gtk-config/34357f74ee2d981 |-gtk-config/2d417a6c9b7765c
   |28ff423b0ec6ddcbf4232c475   |79aba124aa425787435c27aea

--- Comment #5 from Aleix Pol  ---
Git commit 2d417a6c9b7765c79aba124aa425787435c27aea by Aleix Pol.
Committed on 21/06/2017 at 23:44.
Pushed by apol into branch 'netrunner'.

Make the kde-gtk-config kcm better at checking global gtk settings

Cherry-picked onto Plasma/5.10

M  +1-1CMakeLists.txt
M  +3-2src/abstractappearance.h
M  +63   -40   src/appearancegtk2.cpp
M  +12   -5src/appearancegtk2.h
M  +80   -59   src/appearancegtk3.cpp
M  +9-0src/appearancegtk3.h
M  +2-2src/appearencegtk.cpp
M  +1-1tests/CMakeLists.txt
M  +47   -28   tests/configsavetest.cpp
M  +4-4tests/configsavetest.h

https://commits.kde.org/kde-gtk-config/2d417a6c9b7765c79aba124aa425787435c27aea

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

[KSystemLog] [Bug 379933] Switching to Apache log viewing causes error

[Christoph Feck]

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

--- Comment #4 from Christoph Feck  ---
https://phabricator.kde.org/D6329

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

[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer

[avlas]

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

--- Comment #22 from avlas  ---
Excellent!

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

[KSystemLog] [Bug 379933] Switching to Apache log viewing causes error

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Attachment #105953|0   |1
is obsolete||

--- Comment #3 from Christoph Feck  ---
Created attachment 106219
  --> https://bugs.kde.org/attachment.cgi?id=106219&action=edit
Revised patch

This version handles the new '[module:level]' log level format as well as new
timestamp format (with microseconds) and added '[pid:tid]' field.

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

[kontact] [Bug 381473] Clicking "Read Manual" in Kontact Introduction sends to 404 page

[Ethan Hussong]

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

--- Comment #3 from Ethan Hussong  ---
This is going to sound crazy but after rebooting again today the interface is
different. The menu is different. The version number hasn't changed (still
5.2.3 which I think is what I opened this as last night) but now that link is
gone. Instead there's a link that now just says "KMail has many powerful
features that are described in the documentation." When you click on the
hyperlink of "documentation" it opens a popup that says "Error -- KIOExec" as
the subject and "File not found: help:/kmail/index.html" as the body.

I promise I'm not making this up! :)
I'm using English under Linux Mint 18.1 KDE version

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

[plasmashell] [Bug 380209] Speed labels and speed graph empty after showing the applet twice

[Janek Bevendorff]

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

Janek Bevendorff  changed:

   What|Removed |Added

 CC||k...@jbev.net

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

[kdevelop] [Bug 381506] New: Clicking into ":0:15:" in "Build view" opens empty file

[Piotr Mierzwinski]

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

Bug ID: 381506
   Summary: Clicking into ":0:15:" in "Build view"
opens empty file
   Product: kdevelop
   Version: 5.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Output Views
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

I met following error in compiler output ("Build view").
:0:15: error: too many decimal points in number

When I click into it new empty file is opened

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

[konsole] [Bug 381350] Regular Konsole opens to Super Root for a password instead of user bash.

[Wolfgang Bauer]

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

--- Comment #17 from Wolfgang Bauer  ---
(In reply to james from comment #16)
> it did one thing, the screen was stuck on a white background, now it's
> black. but still a password prompt.

Yes, black is the default background, and white the default for openSUSE's
"Root Shell" profile.

What password prompt are you still getting?

I have to admit that I'm running out of ideas now, and I'm not really sure what
your current problem is.

But, to repeat myself:

Try a fresh user account. Does the same happen there too?

Or create a new profile in Konsole and set it as default.
But to be sure, do it like this:
- Go into Settings-> Manage Profiles
- Click on an empty space to make sure that no profile is pre-selected (that
would be taken as "template")
- Click on "New Profile..."
- Make sure that there's no mention of "su" in the "Command" text field (it
should likely be "/bin/bash")
- Click "Ok", you should get back to the previous dialog
- Select your newly created profile, if it's not already selected
- Click on the "Set as Default" button

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

[ksshaskpass] [Bug 380085] TortoiseHG fails with Unable to extract keyFile from phrase "git@gitserver's password: "

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
https://phabricator.kde.org/D6327

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

[korganizer] [Bug 374803] How to change start of the week from Monday to Sunday?

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Allen Winter  ---
The first day of the week is now fixed by what Region you choose.
Go into systemsettings, select Regional Settings, then Formats
and from there you can change your Region.  (or "locale")

You'd have to change to a Region that has Sunday as the first day of the week.
The US has that.

In Summary: KOrganizer no longer has any control over this setting.

another option is to set your environment variable LC_TIME to en_US.UTF-8

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

[kwin] [Bug 361241] Double click to maximize does not work in some situations

[MitraX]

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

MitraX  changed:

   What|Removed |Added

 CC||mit...@gmail.com

--- Comment #13 from MitraX  ---
The issue is still here.

ENVIRONMENT:
Platform: KDE Neon
KDE Plasma Version: 5.10.2
KDE Framework Version: 5.35.0
Qt Version: 5.9.0

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

[plasmashell] [Bug 381505] New: Missing shortcut for 'Refresh Desktop' in Plasma 5 Folder View

[jwinfred]

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

Bug ID: 381505
   Summary: Missing shortcut for 'Refresh Desktop' in Plasma 5
Folder View
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: raaj.winf...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 106218
  --> https://bugs.kde.org/attachment.cgi?id=106218&action=edit
screenshot

I am missing the shortcut for 'Refresh Desktop' in Folder View settings for
Plasma 5. The issue is shown in the attached file. I looked for the 'Refresh
Desktop' shortcut settings in System Settings > Shortcuts> Standard Shortcuts
and in Global Shortcuts but couldn't find one. KDE 4 and previous versions had
F5 as shortcut for 'Refresh Desktop'. Is there a way I can assign F5 as a
shortcut for 'Refresh Desktop' ?

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

[krita] [Bug 360601] [INTEL] Various issues caused by buggy Intel drivers.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||artvlus...@gmail.com

--- Comment #44 from Boudewijn Rempt  ---
*** Bug 381504 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 381504] It's Lagging and Unresponcive

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Boudewijn Rempt  ---
Please check the faq:
https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU

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

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

[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||dvra...@kde.org,
   ||win...@kde.org

--- Comment #21 from Allen Winter  ---
this should be fixed by https://phabricator.kde.org/D6321 once it is approved
and committed.

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

[kcalc] [Bug 381418] negative results of certain magnitudes have incorrect thousands separators

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
https://phabricator.kde.org/D6326

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

[korganizer] [Bug 358265] Can't select AM while setting Start/Due time for a To-do

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #3 from Allen Winter  ---
a few comments:
 - the timezone is set in your system, not by korganizer
 - the kubuntu workaround talks about changing the way datetimes are formatted,
not about which timezone.

this looks more like a bug in the timeselection widget and not korganizer
itself.

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

[ark] [Bug 381499] Zip: executable permission not set

[Elvis Angelaccio]

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

--- Comment #1 from Elvis Angelaccio  ---
What zip plugin are you using? (You can check in Settings -> Configure Ark ->
Plugin Settings)

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

[krita] [Bug 381504] New: It's Lagging and Unresponcive

[Art Luster]

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

Bug ID: 381504
   Summary: It's Lagging and Unresponcive
   Product: krita
   Version: 3.1.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: krita sketch
  Assignee: krita-bugs-n...@kde.org
  Reporter: artvlus...@gmail.com
  Target Milestone: ---

When I try to draw, the mouse lags, and the drawings doesn't appear until after
I click the layers.

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

[digikam] [Bug 381380] Item Edit / Metadata doesn't work

[philippe weyland]

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

--- Comment #4 from philippe weyland  ---
Thanks for comments Maik.
If I understand properly the Item / Edit Metadata are data embedded in files.
Are they stored in database too ?
I understand also there is no synchronization between metadata window and
Information sidebar. 
As I've no metadata in files, these metadata are then empty. I get this.

But why when I enter a value in whatever field (like country or city), click on
Apply, the value disappears immediately ? I haven't any chance to save the data
into file...

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

[plasmashell] [Bug 368889] (Wayland) Plasma tooltips jump from last position instead of popping up.

[bugzilla_noreply]

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

tro...@free.fr changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from tro...@free.fr ---
This bug seems fixed on Plasma 5.10.

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

[Discover] [Bug 381157] picture preview image size

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Aleix Pol  ---
https://phabricator.kde.org/D6324

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

[plasmashell] [Bug 381503] New: Plasma crash on startup

[Sylvain]

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

Bug ID: 381503
   Summary: Plasma crash on startup
   Product: plasmashell
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bond.never@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Computer boot just ended, the plasma shell was starting and the desktop was
displayed for a second.
- Unusual behavior I noticed:
The desktop blink, the icons, the task bar and the second screen wallpaper
disapear. Everything was K.O. for a few seconds then the desktop loaded again
with this crash report.

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

Thread 15 (Thread 0x7fd366eb2700 (LWP 1787)):
#0  0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd455cbf8d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fd455cbfd3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fd451f1dcbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fd45183225f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fd367bff700 (LWP 1786)):
#0  0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd455cbf8d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fd455cbfd3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fd451f1dcbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fd45183225f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fd374986700 (LWP 1785)):
[KCrash Handler]
#5  0x7fd3a6fedcb5 in  () at /usr/lib/libnvidia-glcore.so.381.22
#6  0x7fd3a6fee035 in  () at /usr/lib/libnvidia-glcore.so.381.22
#7  0x7fd3a700b910 in  () at /usr/lib/libnvidia-glcore.so.381.22
#8  0x7fd3a6fd1e44 in  () at /usr/lib/libnvidia-glcore.so.381.22
#9  0x7fd452c53140 in  () at /usr/lib/libQt5Gui.so.5
#10 0x7fd452c535a6 in  () at /usr/lib/libQt5Gui.so.5
#11 0x7fd452c1ec85 in  () at /usr/lib/libQt5Gui.so.5
#12 0x7fd452c1f5f8 in QOpenGLShaderProgram::link() () at
/usr/lib/libQt5Gui.so.5
#13 0x7fd455cb2968 in
QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char
const*, char const*) () at /usr/lib/libQt5Quick.so.5
#14 0x7fd455c7f6f6 in  () at /usr/lib/libQt5Quick.so.5
#15 0x7fd455c80099 in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() at /usr/lib/libQt5Quick.so.5
#16 0x7fd455c814c5 in QSGBatchRenderer::Renderer::renderBatches() () at
/usr/lib/libQt5Quick.so.5
#17 0x7fd455c86c24 in QSGBatchRenderer::Renderer::render() () at
/usr/lib/libQt5Quick.so.5
#18 0x7fd455c775cd in QSGRenderer::renderScene(QSGBindable const&) () at
/usr/lib/libQt5Quick.so.5
#19 0x7fd455c77a8b in QSGRenderer::renderScene(unsigned int) () at
/usr/lib/libQt5Quick.so.5
#20 0x7fd455cb1d40 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at
/usr/lib/libQt5Quick.so.5
#21 0x7fd455d0e868 in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() at /usr/lib/libQt5Quick.so.5
#22 0x7fd455cbadec in  () at /usr/lib/libQt5Quick.so.5
#23 0x7fd455cbfcf8 in  () at /usr/lib/libQt5Quick.so.5
#24 0x7fd451f1dcbd in  () at /usr/lib/libQt5Core.so.5
#25 0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0
#26 0x7fd45183225f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fd375787700 (LWP 1784)):
#0  0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd455cbf8d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fd455cbfd3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fd451f1dcbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fd45183225f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fd37605b700 (LWP 1783)):
#0  0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long

[kwin] [Bug 381496] "Replacing" kwin crashes it

[Martin Flöser]

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

--- Comment #3 from Martin Flöser  ---
(In reply to Luca Weiss from comment #2)
> Just so I understand it correctly, you need information where it's "in  ()",
> right?

Yes and on Arch that's just not available. Arch is the only distribution out
there which does not provide debug packages.

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

[kde-gtk-config] [Bug 333146] Font Family is localized and hence not understood by GTK applications

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

Summary|gtk font settings has no|Font Family is localized
   |effect  |and hence not understood by
   ||GTK applications

--- Comment #5 from Aleix Pol  ---
Aleksey, if you change the name of the font then it shows properly?

Vishnu, are you sure you're facing this same issue?

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

[kde-gtk-config] [Bug 378013] Honour systemwide gtk settings

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||-gtk-config/34357f74ee2d981
   ||28ff423b0ec6ddcbf4232c475
 Resolution|--- |FIXED

--- Comment #4 from Aleix Pol  ---
Git commit 34357f74ee2d98128ff423b0ec6ddcbf4232c475 by Aleix Pol.
Committed on 21/06/2017 at 19:14.
Pushed by apol into branch 'master'.

Make the kde-gtk-config kcm better at checking global gtk settings

M  +1-1CMakeLists.txt
M  +3-2src/abstractappearance.h
M  +63   -40   src/appearancegtk2.cpp
M  +9-2src/appearancegtk2.h
M  +80   -63   src/appearancegtk3.cpp
M  +9-1src/appearancegtk3.h
M  +2-2src/appearencegtk.cpp
M  +1-1tests/CMakeLists.txt
M  +47   -28   tests/configsavetest.cpp
M  +4-4tests/configsavetest.h

https://commits.kde.org/kde-gtk-config/34357f74ee2d98128ff423b0ec6ddcbf4232c475

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

[kwin] [Bug 381496] "Replacing" kwin crashes it

[Luca Weiss]

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

--- Comment #2 from Luca Weiss  ---
Just so I understand it correctly, you need information where it's "in  ()",
right? Sidenote: DrKonqi rated the backtrace with 3 stars so that should
probably be changed then.

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

[kwin] [Bug 381502] New: System freeze on logout or sometimes at random time

[Simone Gaiarin]

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

Bug ID: 381502
   Summary: System freeze on logout or sometimes at random time
   Product: kwin
   Version: 5.10.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: simg...@gmail.com
  Target Milestone: ---

I've tried the wayland session again in Plasma 5.10.2 but unfortunately, it's
still unusable, so I'll start to report the various bugs to see if I can help
debug them.

The main bug is that the whole system freeze when I logout. At that point, I
need to turn off the notebook by pressing the power button. The freeze happened
also at other random instants when I was not doing anything in particular.

Is it there some log that I can report?

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

[kdenlive] [Bug 381223] Custom Profile handling bugs

[Evert Vorster]

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

--- Comment #12 from Evert Vorster  ---
The two bits of information you were after:

Profile:
[evert@Arch profiles]$ cat customprofile22 
description=3840x1920 29.97fps
frame_rate_num=3
frame_rate_den=1001
width=3840
height=1920
progressive=1
sample_aspect_num=1
sample_aspect_den=1
display_aspect_num=3840
display_aspect_den=1920
colorspace=709
[evert@Arch profiles]$


What is interesting is that two frame rates are detected:
29.9699
29.97


The full output of the command:
[evert@Arch Renders]$ melt Time_Lapse_01.mp4 -consumer xml


  
  
10343
pause
Time_Lapse_01.mp4
2
video
29.9699
0
3840
1920
0
29.97
yuv420p
1
709
hevc
HEVC (High Efficiency Video
Coding)
47788352
2017-06-14T12:52:25.00Z
eng
Video Media
Handler
HVC Coding
audio
fltp
48000
2
aac
AAC (Advanced Audio
Coding)
384000
2017-06-14T12:52:25.00Z
eng
Sound Media
Handler
MSNV
16786688
MSNVisommp42
2017-06-14T12:52:25.00Z
1
1
1
1
1
0
1
avformat
  
  

  
  

  


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

[Akonadi] [Bug 339576] Can't create new top level IMAP folder

[Tom Chiverton]

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

--- Comment #15 from Tom Chiverton  ---
Not fixed, sorry : https://bugs.kde.org/show_bug.cgi?id=350219#c22

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

[neon] [Bug 381501] New: qtvirtualkeyboard broken

[Martin Flöser]

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

Bug ID: 381501
   Summary: qtvirtualkeyboard broken
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: mgraess...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

With the update to Qt 5.9 the qtvirtualkeyboard is broken as it's still Qt 5.7.
This breaks e.g. virtual keyboard integration in the lock screen and KWin.

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

[plasmashell] [Bug 381500] New: Task Manger doesn't display starting indicator for some applications with pinned launchers

[MitraX]

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

Bug ID: 381500
   Summary: Task Manger doesn't display starting indicator for
some applications with pinned launchers
   Product: plasmashell
   Version: 5.10.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: mit...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

DESCRIPTION:
Task Manager displays starting indicator (spinning circle) when application
launcher is clicked, but for some applications with pinned launchers (e.g.
Kate) there’s no starting indicator.

REPRODUCIBLE: Always

STEPS TO REPRODUCE:

1) Pin the Kate editor launcher to the Task Manger widget

2) Click the Kate launcher

ACTUAL RESULTS:
Kate editor is started but spinning indicator is not displayed.

EXPECTED RESULTS:
The spinning indicator is displayed like for many other applications.

NOTE:
The starting indicator is displayed if a user runs the Kate editor using the
Application Launcher, the issue exists only for pinned icons.

ENVIRONMENT:
Platform: KDE Neon
KDE Plasma Version: 5.10.2
KDE Framework Version: 5.35.0
Qt Version: 5.9.0

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

[Discover] [Bug 380496] Discover crashes upon opening

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||ram.premn...@gmail.com

--- Comment #14 from Aleix Pol  ---
*** Bug 381497 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 381497] VirtualBox Plasma Installation Discover Crashed

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[digikam] [Bug 302527] TEMPLATE : metadata editing not possible (copyright, city, ...)

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|4.1.0   |5.6.0

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

[plasmashell] [Bug 381242] Application Launcher stops working when "Minimize All Windows" widgets is clicked

[MitraX]

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

--- Comment #5 from MitraX  ---
Additional detail: Clicking the "Minimize Windows" widget doesn't maximize
previously minimized windows in this case.

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

[plasma-pa] [Bug 380845] Plasma Crash while pluggin headphones

[Nikola Schnelle]

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

--- Comment #11 from Nikola Schnelle  ---
I can easily crash plasma with scrolling over sound/volume systray icon.
Although it does not crash every time.

I have never used valgrind and have no spare time atm to read docs, but if
there is some easy copy/paste valgrind command I would more than happy to run
it :)

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

[digikam] [Bug 302527] TEMPLATE : metadata editing not possible (copyright, city, ...)

[philippe weyland]

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

--- Comment #18 from philippe weyland  ---
Version 5.6. Still same issue. A pain.

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

[ark] [Bug 381499] New: Zip: executable permission not set

[bugzilla_noreply]

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

Bug ID: 381499
   Summary: Zip: executable permission not set
   Product: ark
   Version: 17.04.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plugins
  Assignee: rthoms...@gmail.com
  Reporter: cubob...@banit.me
CC: elvis.angelac...@kde.org
  Target Milestone: ---

When extracting zip archives the executable permissions are not set.
It works fine using unzip directly or with other archive formats (7z/tar).

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

[digikam] [Bug 381380] Item Edit / Metadata doesn't work

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
The information in the right sidebar comes from the database. The information
is only updated when the metadata is re-read (from the menu entry) or
automatically when the re-reading for modified images is activated in the
settings. The metadata editor only writes the information to the images. The
metadata information to be searched when reading image to the database (XMP ->
IPTC -> EXIF) can be defined in the extended metadata settings in the setup. It
works here without problems.

Maik

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

[plasmashell] [Bug 381242] Application Launcher stops working when "Minimize All Windows" widgets is clicked

[MitraX]

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

--- Comment #4 from MitraX  ---
Platform: KDE Neon
KDE Plasma Version: 5.10.2
KDE Framework Version: 5.35.0
Qt Version: 5.9.0

Basically, the issue exists in a couple of latest Plasma and Qt versions
(probably even before but I didn't test it).

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

[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced

[Dr . Chapatin]

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

--- Comment #13 from Dr. Chapatin  ---
I can confirm this bug under X11 session on Arch, plasma 5.10.2, qt 5.9.
Sometimes notification from dolphin about finished copy/move files appears on
top left corner.

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

[picmi] [Bug 381426] In high-score dialogue the shortcut Alt+C does not close it.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |UPSTREAM

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

[dolphin] [Bug 381494] Dolphin freezes while right clicking on folder

[Germano Massullo]

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

Germano Massullo  changed:

   What|Removed |Added

Summary|Dolphin freezes while right |Dolphin freezes while right
   |clicking on FTP folder  |clicking on folder

--- Comment #1 from Germano Massullo  ---
I edited bugreport title because it happens also on non FTP folders

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

[massif-visualizer] [Bug 381498] New: CMake fails since it does not find file 'CMakeFindDependencyMacro'

[bugzilla_noreply]

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

Bug ID: 381498
   Summary: CMake fails since it does not find file
'CMakeFindDependencyMacro'
   Product: massif-visualizer
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: massif-visuali...@kde.org
  Reporter: scie...@konze.org
  Target Milestone: 0.4

Hello there,

currently I'm trying to compile massif-visualizer from the git repository. As
stated in the INSTALL file I created a directory 'build' and executed 'cmake
..'. At first CMake complained that certain dependencies are missing. Due to
this, I installed the following packages with 'yum' (Scientific Linux 7.3):

kf5-kconfig-gui-5.33.0-1.el7.x86_64
kf5-kconfig-devel-5.33.0-1.el7.x86_64
kf5-kconfig-core-5.33.0-1.el7.x86_64
kf5-kconfig-5.33.0-1.el7.x86_64
kf5-karchive-devel-5.33.0-1.el7.x86_64
kf5-karchive-5.33.0-1.el7.x86_64
kf5-filesystem-5.33.0-1.el7.x86_64
qt5-qtxmlpatterns-devel-5.6.1-10.el7.x86_64
qt5-qtsvg-devel-5.6.1-10.el7.x86_64
qt5-qtsvg-5.6.1-10.el7.x86_64
kf5-rpm-macros-5.33.0-1.el7.noarch
extra-cmake-modules-5.33.0-1.el7.noarch

Now CMake seems to be satisfied with all dependencies, however, it now fails
with the following error message:

-- Could not set up the appstream test. appstreamcli is missing.
CMake Error at /usr/lib64/cmake/KF5Archive/KF5ArchiveConfig.cmake:37 (include):
  include could not find load file:

CMakeFindDependencyMacro
Call Stack (most recent call first):
  /usr/share/ECM/find-modules/FindKF5.cmake:74 (find_package)
  CMakeLists.txt:34 (find_package)


CMake Error at /usr/lib64/cmake/KF5Archive/KF5ArchiveConfig.cmake:38
(find_dependency):
  Unknown CMake command "find_dependency".
Call Stack (most recent call first):
  /usr/share/ECM/find-modules/FindKF5.cmake:74 (find_package)
  CMakeLists.txt:34 (find_package)


-- Configuring incomplete, errors occurred!
See also
"/local/luebeck/git/massif-visualizer/build/CMakeFiles/CMakeOutput.log".

I'm a little bit confused since I installed all KF5 dependencies and the
extra-cmake-modules (ECM). What else do I miss?

Best regards,

Konze

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

[kwin] [Bug 377171] Clicking outside of any presented windows should show desktop

[Vishnu]

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

--- Comment #7 from Vishnu  ---
(In reply to Christoph Feck from comment #6)
> You can also use the "Show Desktop" hotkey. Configure it in systemsettings5
> > Shortcuts > Global Shortcuts > KWin.

Thanks!! Didn't know this existed. My request for the feature still holds.

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

[Discover] [Bug 381497] New: VirtualBox Plasma Installation Discover Crashed

[Ram Kumar]

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

Bug ID: 381497
   Summary: VirtualBox Plasma Installation Discover Crashed
   Product: Discover
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ram.premn...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Konsole and Chromium, but they didn't affect the applcation to crash
- Unusual behavior I noticed:
Nil
- Custom settings of the application:
Nil
-Output of Kdevelop
WARNING: Cannot find style "org.kde.desktop" - fallback:
"/usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop"
error loading "flatpak-backend" "Cannot load library
/usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0: cannot open
shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"FlatpakBackendFactory","debug":false,"version":329984})
error loading "packagekit-backend" "Cannot load library
/usr/lib/qt/plugins/discover/packagekit-backend.so: (libpackagekitqt5.so.0:
cannot open shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"PackageKitBackendFactory","debug":false,"version":329984})
The file  "/home/ram/.local/share/knewstuff3/cgctheme.knsregistry"  could not
be opened.
The file  "/home/ram/.local/share/knewstuff3/emoticons.knsregistry"  could not
be opened.
The file 
"/home/ram/.local/share/knewstuff3/discover_ktexteditor_codesnippets_core.knsregistry"
 could not be opened.
The file  "/home/ram/.local/share/knewstuff3/lookandfeel.knsregistry"  could
not be opened.
The file  "/home/ram/.local/share/knewstuff3/kwineffect.knsregistry"  could not
be opened.
The file  "/home/ram/.local/share/knewstuff3/sddmtheme.knsregistry"  could not
be opened.
The file  "/home/ram/.local/share/knewstuff3/kfontinst.knsregistry"  could not
be opened.
The file  "/home/ram/.local/share/knewstuff3/icons.knsregistry"  could not be
opened.
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
The file  "/home/ram/.local/share/knewstuff3/xcursor.knsregistry"  could not be
opened.
The file  "/home/ram/.local/share/knewstuff3/kwinswitcher.knsregistry"  could
not be opened.
The file  "/home/ram/.local/share/knewstuff3/wallpaper.knsregistry"  could not
be opened.
The file  "/home/ram/.local/share/knewstuff3/comic.knsregistry"  could not be
opened.
*** Program received signal SIGSEGV (Segmentation fault) ***
The file  "/home/ram/.local/share/knewstuff3/kwinscripts.knsregistry"  could
not be opened.
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
The file  "/home/ram/.local/share/knewstuff3/colorschemes.knsregistry"  could
not be opened.
The file  "/home/ram/.local/share/knewstuff3/plasma-themes.knsregistry"  could
not be opened.
The file  "/home/ram/.local/share/knewstuff3/plasmoids.knsregistry"  could not
be opened.

The crash can be reproduced every time.

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

Thread 12 (Thread 0x7f0256c2f700 (LWP 753)):
#0  0x7f0264f833b9 in syscall () at /usr/lib/libc.so.6
#1  0x7f02652d0087 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*)
(g=0x7f0263f3bc68) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/guard.cc:302
#2  0x7f0263c8fc0c in  () at /usr/lib/libQt5Network.so.5
#3  0x7f0263c82ba3 in  () at /usr/lib/libQt5Network.so.5
#4  0x7f0265670171 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f0265673cbd in  () at /usr/lib/libQt5Core.so.5
#6  0x7f02617bc297 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f0264f8825f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f022f7fe700 (LWP 720)):
[KCrash Handler]
#5  0x7f02696af8f8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2
#6  0x7f02696b77a3 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#7  0x7f0264fc1c94 in _dl_catch_error () at /usr/lib/libc.so.6
#8  0x7f02696b70e9 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#9  0x7f025f928f26 in  () at /usr/lib/libdl.so.2
#10 0x7f0264fc1c94 in _dl_catch_error () at /usr/lib/libc.so.6
#11 0x7f025f9295f5 in  () at /usr/lib/libdl.so.2
#12 0x7f025f928fb1 in dlopen () at /usr/lib/libdl.so.2
#13 0x7f026584ab8c in  () at /usr/lib/libQt5Core.so.5
#14 0x7f0265844

[kwin] [Bug 381496] "Replacing" kwin crashes it

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Flöser  ---
As always backtraces from Arch are useless.

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

[kdevelop] [Bug 364317] Crash when executing multiple tests

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||vplatform/3ed8698f1baca73e2
   ||d7cb4400c90e6950a8ad623
   Version Fixed In||5.1.2
 Resolution|--- |FIXED

--- Comment #2 from Kevin Funk  ---
Git commit 3ed8698f1baca73e2d7cb4400c90e6950a8ad623 by Kevin Funk, on behalf of
Christoph Roick.
Committed on 21/06/2017 at 17:35.
Pushed by kfunk into branch '5.1'.

Fix crash when trying to kill a finished NativeAppJob

Summary:
- when starting the same job twice, a dialog pops up,
  asking whether to kill the running job
- if the job finished meanwhile, the running job instance
  ceases to exist and accessing its member causes a crash
- probably the same as Bug 364317

Solution:
- add a check for existence of the job after the dialog
FIXED-IN: 5.1.2

Test Plan:
- start the same job twice (a unit test for instance)
- click on "Yes" (do kill the running job), if the dialog
  pops up, after the job finished

Reviewers: #kdevelop, apol

Reviewed By: #kdevelop, apol

Subscribers: apol, kdevelop-devel

Differential Revision: https://phabricator.kde.org/D6286

M  +1-1plugins/execute/nativeappjob.cpp

https://commits.kde.org/kdevplatform/3ed8698f1baca73e2d7cb4400c90e6950a8ad623

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

[kwin] [Bug 381496] New: "Replacing" kwin crashes it

[Luca Weiss]

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

Bug ID: 381496
   Summary: "Replacing" kwin crashes it
   Product: kwin
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: l...@z3ntu.xyz
  Target Milestone: ---

Application: kwin_x11 (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I ran "kwin_x11 --replace" from the KRunner (Alt+F2) - actually saved that into
a script but I don't think that matters.
This bug doesn't break anything except that a popup with "kwin crashed"
appears. After the "restart" process is complete, everything works as expected.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fac8c96b840 (LWP 27667))]

Thread 5 (Thread 0x7fac5cacb700 (LWP 1499)):
#0  0x7fac8c3b5396 in ppoll () at /usr/lib/libc.so.6
#1  0x7fac899cf471 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7fac899d0b5e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7fac8997a21a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7fac8979c40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7fac897a0cbd in  () at /usr/lib/libQt5Core.so.5
#6  0x7fac85566297 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7fac8c3bf25f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fac53fff700 (LWP 27762)):
#0  0x7fac8556c39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fac888faac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fac888fab09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fac85566297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fac8c3bf25f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fac70c5a700 (LWP 27698)):
#0  0x7fac8c3b5396 in ppoll () at /usr/lib/libc.so.6
#1  0x7fac899cf471 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7fac899d0b5e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7fac8997a21a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7fac8979c40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7fac8342bd45 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7fac897a0cbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7fac85566297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fac8c3bf25f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fac72dd5700 (LWP 27686)):
#0  0x7fac8c3b52bd in poll () at /usr/lib/libc.so.6
#1  0x7fac8b49f8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7fac8b4a1679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7fac73eb0d49 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7fac897a0cbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fac85566297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fac8c3bf25f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fac8c96b840 (LWP 27667)):
[KCrash Handler]
#5  0x7fac8c305670 in raise () at /usr/lib/libc.so.6
#6  0x7fac8c306d00 in abort () at /usr/lib/libc.so.6
#7  0x7fac8978c807 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fac8979b77d in QThread::~QThread() () at /usr/lib/libQt5Core.so.5
#9  0x7fac8979b859 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5
#10 0x7fac899a803b in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#11 0x7fac899b19cb in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#12 0x7fac702352e9 in KWin::X11StandalonePlatform::~X11StandalonePlatform()
() at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#13 0x7fac899a803b in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#14 0x7fac899b19cb in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#15 0x7fac8997da06 in QCoreApplication::~QCoreApplication() () at
/usr/lib/libQt5Core.so.5
#16 0x7fac8a6a6ec9 in QApplication::~QApplication() () at
/usr/lib/libQt5Widgets.so.5
#17 0x7fac8c67e743 in  () at /usr/lib/libkdeinit5_kwin_x11.so
#18 0x7fac8c680029 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so
#19 0x7fac8c2f243a in __libc_start_main () at /usr/lib/libc.so.6
#20 0x0040069a in _start ()

Reported using DrKonqi

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

[plasmashell] [Bug 381495] New: Significant increase in CPU utilisation when "Show Seconds" enabled.

[Paul]

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

Bug ID: 381495
   Summary: Significant increase in CPU utilisation when "Show
Seconds" enabled.
   Product: plasmashell
   Version: 5.10.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: pip@gmx.com
  Target Milestone: 1.0

Plasma 5.10.2
KDE frameworks 5.34.0
Qt 5.9.0

When "Show Seconds" is enabled there is a significant increase in CPU
utilisation by kwin_X11

As shown by "Top" (observed when idle over approximately two minutes)

Show Seconds disabled - kwin_X11 approx 7% to 8% utilisation

Show Seconds enabled - kwin_X11 approx 13% to 22% utilisation

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

[dolphin] [Bug 381494] Dolphin freezes while right clicking on FTP folder

[Germano Massullo]

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

Germano Massullo  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[dolphin] [Bug 381494] New: Dolphin freezes while right clicking on FTP folder

[Germano Massullo]

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

Bug ID: 381494
   Summary: Dolphin freezes while right clicking on FTP folder
   Product: dolphin
   Version: 16.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: ---

I am browsing a FTP, everytime I right click on a specific file, to try copying
it, Dolphin freezes

$ gdb dolphin 16411
GNU gdb (GDB) Fedora 7.12.1-48.fc25
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from dolphin...Reading symbols from
/usr/lib/debug/usr/bin/dolphin.debug...done.
done.
Attaching to program: /usr/bin/dolphin, process 16411
[New LWP 16412]
[New LWP 16413]
[New LWP 16414]
[New LWP 16415]
[New LWP 16416]
[New LWP 16417]
[New LWP 16418]
[New LWP 16419]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x7f41037eb7cd in nanosleep () at ../sysdeps/unix/syscall-template.S:84
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
(gdb) thread apply all backtrace

Thread 9 (Thread 0x7f40d1395700 (LWP 16419)):
#0  0x7f410381af3d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f40fbe32166 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f40cc002e20, timeout=, context=0x7f40cc000990)
at gmain.c:4228
#2  0x7f40fbe32166 in g_main_context_iterate
(context=context@entry=0x7f40cc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at gmain.c:3924
#3  0x7f40fbe3227c in g_main_context_iteration (context=0x7f40cc000990,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f41046216cf in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f40cc0008c0, flags=...)
at kernel/qeventdispatcher_glib.cpp:423
#5  0x7f41045d268a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f40d1394c80, flags=..., flags@entry=...)
at kernel/qeventloop.cpp:212
#6  0x7f410442f5e3 in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7f41044339ca in QThreadPrivate::start(void*) (arg=0x55a72dea6610) at
thread/qthread_unix.cpp:368
#8  0x7f410139573a in start_thread (arg=0x7f40d1395700) at
pthread_create.c:333
#9  0x7f4103826e7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7f40d947c700 (LWP 16418)):
#0  0x7f410139b460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f40e352853b in cnd_wait (mtx=0x55a72dcdb458, cond=0x55a72dcdb480) at
../../../include/c11/threads_posix.h:159
#2  0x7f40e352853b in util_queue_thread_func
(input=input@entry=0x55a72dcdff40) at util/u_queue.c:138
#3  0x7f40e3528267 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7f410139573a in start_thread (arg=0x7f40d947c700) at
pthread_create.c:333
---Type  to continue, or q  to quit---
#5  0x7f4103826e7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 7 (Thread 0x7f40e087b700 (LWP 16417)):
#0  0x7f410139b460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f40e352853b in cnd_wait (mtx=0x55a72dcdb458, cond=0x55a72dcdb480) at
../../../include/c11/threads_posix.h:159
#2  0x7f40e352853b in util_queue_thread_func
(input=input@entry=0x55a72dce0870) at util/u_queue.c:138
#3  0x7f40e3528267 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7f410139573a in start_thread (arg=0x7f40e087b700) at
pthread_create.c:333
#5  0x7f4103826e7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f40e107c700 (LWP 16416)):
#0  0x7f410139b460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f40e352853b in cnd_wait (mtx=0x55a72dcdb458, cond=0x55a72dcdb480) at
../../../include/c11/threads_posix.h:159
#2  0x7f40e352853b in util_queue_thread_func
(input=input@entry=0x55a72dcdff00) at util/u_queue.c:138
#3  0x7f40e3528267 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7f410139573a in start_thread (arg=0x7f40e107c700) at
pthread_create.c:

[amarok] [Bug 381263] Cover art missing ocassionally

[Myriam Schweingruber]

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

--- Comment #3 from Myriam Schweingruber  ---
(In reply to Hamidreza Jafari from comment #2)
> Is it supposed to show embedded album art? Then why is it showing some but
> not all?I don't understand why you question "now"?

I have no idea why it doesn't show all embedded art, but wild guess is that
there are different file types. As for my reference to "Now": please read the
last sentence in your report, you say "Now the option is off". You talk about
actions happening in the past without being precise about the time frame and
version, and when the change happen and whether this was in the same version.

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

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

[Paul]

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

--- Comment #24 from Paul  ---
(In reply to Chris Holland from comment #22)
> So Neon now has Qt 5.9, and I can reproduce it with Plasma 5.10.2. It only
> started after yesterdays update to qt 5.9 from qt 5.7.
> 
> Anyhow. Testing cache:true didn't fix it. However, setting asynchronous:true
> to asynchronous:false DID fix it.

Not on this system I'm afraid.  Edited
"/usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml" changing
"asynchronous:true" to "asynchronous:false" and restarting plasmashell.

67% plasmashell
60% kwin_X11
39% X

Reverting back to a static image and restarting plasmashell

0.8% plasmashell
9% kwin_X11
5% X



Plasma 5.10.2
KDE frameworks 5.34.0
Qt 5.9.0

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

[kgpg] [Bug 381493] New: Displays disabled keys as trusted

[Vitaliy]

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

Bug ID: 381493
   Summary: Displays disabled keys as trusted
   Product: kgpg
   Version: 17.04
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: silverunicorn2...@yandex.ru
  Target Milestone: ---

In the key properties window, it shows “Trust: disabled” with a red rectangle,
as the key is disabled. But in the key list, it shows a green rectangle which
means “Full trust.” Moreover, these keys aren’t filtered out by selection of
the minimum trust level.

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

[picmi] [Bug 381426] In high-score dialogue the shortcut Alt+C does not close it.

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

   See Also||https://bugreports.qt.io/br
   ||owse/QTBUG-61197
 Resolution|UPSTREAM|FIXED

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

[picmi] [Bug 381426] In high-score dialogue the shortcut Alt+C does not close it.

[Jakob Gruber]

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

Jakob Gruber  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Jakob Gruber  ---
Offline discussion with Luigi: 

This seems to be a dupe of https://bugreports.qt.io/browse/QTBUG-61197.
I see the same issue e.g. in Help->About dialogs.

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

[krita] [Bug 381452] Zooming using the Intuos 4 wheel not smooth while hovering pen over tablet

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---

hm...
might be caused by Nicholas' scroll wheel patch...?
https://phabricator.kde.org/R37:9bec9bb20d9b593ed4a3194dce11bc5191c9bea5

(or maybe this actually fixes things???)

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

[picmi] [Bug 381426] In high-score dialogue the shortcut Alt+C does not close it.

[Jakob Gruber]

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

--- Comment #3 from Jakob Gruber  ---
(In reply to Luigi Toscano from comment #2)
> ksnakeduel is still Qt4 (until the next release of KDE Applications).
> 
> Which version of Qt and KDE Frameworks do you use? You can see it from the
> Help->About  menu entry, "Libraries" tab.

KDE Frameworks 5.35.0
Qt 5.9.0 (built against 5.9.0)
The xcb windowing system

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

[picmi] [Bug 381426] In high-score dialogue the shortcut Alt+C does not close it.

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #2 from Luigi Toscano  ---
ksnakeduel is still Qt4 (until the next release of KDE Applications).

Which version of Qt and KDE Frameworks do you use? You can see it from the
Help->About  menu entry, "Libraries" tab.

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

[picmi] [Bug 381426] In high-score dialogue the shortcut Alt+C does not close it.

[Jakob Gruber]

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

--- Comment #1 from Jakob Gruber  ---
Interesting. Some games (klickety, samegame, probably others) have the same
issue. Others (e.g. ksnakeduel) do not.

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

[frameworks-kwidgetsaddons] [Bug 381492] New: KSelectAction::~KSelectAction calls deleteLater() on NULL QMenu* instance

[RJVB]

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

Bug ID: 381492
   Summary: KSelectAction::~KSelectAction calls deleteLater() on
NULL QMenu* instance
   Product: frameworks-kwidgetsaddons
   Version: 5.35.0
  Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: rjvber...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

After updating to FW 5.35.0 I started seeing `QCoreApplication::postEvent:
Unexpected null receiver` errors on the calling terminal.

I traced those to the KSelectAction dtor that calls `menu()->deleteLater()`
without checking first if `menu()` returns non-null.

In turn it appears that function returns NULL because of a now-reverted change
in KXmlGui (#b5af0296cb).

Still, is it safe to assume that `KSelectAction::menu()` never returns NULL (in
the dtor and elsewhere in the file)?

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

[krita] [Bug 381453] CMYK occsionally and randomly damages images.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |LATER
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Boudewijn Rempt  ---
To this one if fine! In that case we can reopen it when we've got more data.

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

[plasmashell] [Bug 381480] Plasma desktop black screen and no widgets/taskbar after latest updates in KDE Neon

[Vangelis]

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

--- Comment #3 from Vangelis  ---
If anyone can suggest a workaround, it would be very welcome. This crash is not
transient. It is permanent.
This is my main computer at home and I can only work with krunner at the
moment.

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

[Discover] [Bug 381417] Impossible to update Firefox flatpak, discover installs the same update repeatedly

[Dr . Chapatin]

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

--- Comment #2 from Dr. Chapatin  ---
here is

Failed to install "Firefox Nightly - Wayland build" : While pulling
app/org.mozilla.FirefoxNightlyWayland/x86_64/master from remote
org.mozilla.FirefoxRepo: Need more input
Failed to install "Firefox Nightly - Wayland build" : While pulling
app/org.mozilla.FirefoxNightlyWayland/x86_64/master from remote
org.mozilla.FirefoxRepo: Need more input

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

[plasmashell] [Bug 381480] Plasma desktop black screen and no widgets/taskbar after latest updates in KDE Neon

[Vangelis]

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

--- Comment #2 from Vangelis  ---
My session manager is kwin

$ ps xau | grep -i kwin
cyber16704  0.3  2.2 3255264 182560 ?  Sl   10:49   1:33 kwin_x11
-session 10c3dbdbd800014875307720020850005_1498000455_879508


And here is the output from the gdb backtrace:
$ cat gdb.txt 
Starting program: /usr/bin/plasmashell 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe18fa700 (LWP 21645)]
[New Thread 0x7fffdbb68700 (LWP 21646)]
[New Thread 0x7fffda123700 (LWP 21647)]
[New Thread 0x7fffd3fff700 (LWP 21648)]
[New Thread 0x7fffd1c41700 (LWP 21649)]
[New Thread 0x7fff411b9700 (LWP 21650)]
[New Thread 0x7fff33438700 (LWP 21653)]
[New Thread 0x7fff32c37700 (LWP 21654)]
[New Thread 0x7fff2b092700 (LWP 21655)]
[New Thread 0x7fff2938a700 (LWP 21656)]
[New Thread 0x7fff15dc1700 (LWP 21658)]
[New Thread 0x7fff0e742700 (LWP 21678)]

Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
---[regs]
  RAX: 0x  RBX: 0x01B22540  RCX: 0x75DE5110 
RDX: 0x01B22540  o d I t s Z a P c 
  RSI: 0x01E7E2E0  RDI: 0x01B22540  RBP: 0x7FFFD480 
RSP: 0x7FFFD3E0  RIP: 0x75DE51A8
  R8 : 0x  R9 : 0x75DE6B20  R10: 0x77E06210 
R11: 0x726FC350  R12: 0x006FCFC0
  R13: 0x006F2FE0  R14: 0x7FFFD430  R15: 0x
  CS: 0033  DS:   ES:   FS:   GS:   SS: 002B
---[code]
=> 0x75de51a8 <_ZN22QQuickAnimatorProxyJob21sceneGraphInitializedEv+152>:  
movrax,QWORD PTR ds:0x38
   0x75de51b0 <_ZN22QQuickAnimatorProxyJob21sceneGraphInitializedEv+160>:  
ud2
   0x75de51b2 <_ZN22QQuickAnimatorProxyJob21sceneGraphInitializedEv+162>:  
call   0x75d800a0 <__stack_chk_fail@plt>
   0x75de51b7:  nop
   0x75de51b8:  nopDWORD PTR [rax+rax*1+0x0]
   0x75de51c0 <_ZN22QQuickAnimatorProxyJob9setWindowEP12QQuickWindow>: 
push   r12
   0x75de51c2 <_ZN22QQuickAnimatorProxyJob9setWindowEP12QQuickWindow+2>:   
push   rbp
   0x75de51c3 <_ZN22QQuickAnimatorProxyJob9setWindowEP12QQuickWindow+3>:   
push   rbx
-
0x75de51a8 in QQuickAnimatorProxyJob::sceneGraphInitialized() () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#0  0x75de51a8 in QQuickAnimatorProxyJob::sceneGraphInitialized() ()
from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#1  0x72f5a109 in QObject::event (this=0x1b22540, e=) at
kernel/qobject.cpp:1246
#2  0x738993fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x738a0e07 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x72f2d128 in QCoreApplication::notifyInternal2
(receiver=0x1b22540, event=event@entry=0x7fff080e1010) at
kernel/qcoreapplication.cpp:1018
#5  0x72f2f62b in QCoreApplication::sendEvent (event=0x7fff080e1010,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
#6  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0x0, data=0x6f2f60) at
kernel/qcoreapplication.cpp:1678
#7  0x72f2fa98 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0x0) at
kernel/qcoreapplication.cpp:1532
#8  0x72f816b3 in postEventSourceDispatch (s=0x741ed0) at
kernel/qeventdispatcher_glib.cpp:276
#9  0x7fffedd4f197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fffedd4f3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fffedd4f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x72f81abf in QEventDispatcherGlib::processEvents (this=0x750150,
flags=...) at kernel/qeventdispatcher_glib.cpp:423
#13 0x72f2b30a in QEventLoop::exec (this=this@entry=0x7fffd940,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x72f33db4 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1291
#15 0x0041ce18 in main (argc=0x1, argv=) at
/workspace/build/shell/main.cpp:166

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

[systemsettings] [Bug 378262] krdb/kcminit sets wrong font for Qt4 applications on login

[boospy]

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

boospy  changed:

   What|Removed |Added

 CC||li...@osit.cc

--- Comment #9 from boospy  ---
Same here on KDE Neon 5.10.

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

[plasmashell] [Bug 381242] Application Launcher stops working when "Minimize All Windows" widgets is clicked

[Dr . Chapatin]

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

--- Comment #3 from Dr. Chapatin  ---
qt 5.9 on my Arch.

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