[kwin] [Bug 392076] Kwin issues illegal OpenGL calls when ALT+TABing through window list

[Clemens Eisserer]

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

--- Comment #2 from Clemens Eisserer  ---
this happens with the "Breeze" switcher theme.

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

[valgrind] [Bug 391861] Massif Assertion 'n_ips >= 1 && n_ips <= VG_(clo_backtrace_size)'

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

Summary|Massif assertion failed |Massif Assertion 'n_ips >=
   ||1 && n_ips <=
   ||VG_(clo_backtrace_size)'

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

[Heaptrack] [Bug 392085] New: Heaptrack gets all available memory and gets killed

[Anthony Fieroni]

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

Bug ID: 392085
   Summary: Heaptrack gets all available memory and gets killed
   Product: Heaptrack
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: bvb...@abv.bg
  Target Milestone: ---

1. Latest git
2. compile it
3. Navigate to bin folder in compilation directory
4. Run ./heatrack -d plasmashell
5. Click ctrl + c
6. Try to open it ./heaptrack --analyze heaptrack.plasmashell.
7. Heaptrack gets all RAM and dies

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

[kwin] [Bug 392083] Compositor, or something in kde5, causes nouveau driver to hang with video playback

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
Please report the freeze to nouveau developers. They need to fix it. Workaround
doesn't help anybody.

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

[kwin] [Bug 392076] Kwin issues illegal OpenGL calls when ALT+TABing through window list

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
Could be Qt as well. Which switcher theme are you using?

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

[Discover] [Bug 392084] New: Discover Crashed on Launch

[bugzilla_noreply]

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

Bug ID: 392084
   Summary: Discover Crashed on Launch
   Product: Discover
   Version: 5.12.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: j_...@hotmail.com
  Target Milestone: ---

Application: plasma-discover (5.12.3)

Qt Version: 5.10.0
Frameworks Version: 5.44.0
Operating System: Linux 4.13.0-37-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
New install of KDE Neon. I updated everything immediately after the install.
Now Disover crashes when I try to open it. It appears for a brief moment and
then crashes.

The crash can be reproduced every time.

-- 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 0x7f3de367a8c0 (LWP 1750))]

Thread 7 (Thread 0x7f3da520b700 (LWP 1765)):
#0  0x7ffd0cc8fb6d in clock_gettime ()
#1  0x7f3ddead6876 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f3da520aa70) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f3ddf6f7ed1 in qt_clock_gettime (ts=0x7f3da520aa70, clock=) at kernel/qelapsedtimer_unix.cpp:111
#3  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#4  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#5  0x7f3ddf6f66c9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f3d9c0018a0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f3ddf6f6c35 in QTimerInfoList::timerWait (this=0x7f3d9c0018a0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f3ddf6f896c in timerSourcePrepareHelper (timeout=0x7f3da520ab34,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  idleTimerSourcePrepare (source=, timeout=0x7f3da520ab34) at
kernel/qeventdispatcher_glib.cpp:212
#9  0x7f3dd956e91d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f3dd956f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f3dd956f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f3ddf6f85cb in QEventDispatcherGlib::processEvents
(this=0x7f3d9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f3ddf69f64a in QEventLoop::exec (this=this@entry=0x7f3da520ad00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x7f3ddf4bf554 in QThread::exec (this=) at
thread/qthread.cpp:522
#15 0x7f3ddf4c46eb in QThreadPrivate::start (arg=0x13304e0) at
thread/qthread_unix.cpp:376
#16 0x7f3ddb6676ba in start_thread (arg=0x7f3da520b700) at
pthread_create.c:333
#17 0x7f3ddeac841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f3da6c3e700 (LWP 1763)):
#0  0x7ffd0cc8fb6d in clock_gettime ()
#1  0x7f3ddead6876 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f3da6c3da70) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f3ddf6f7ed1 in qt_clock_gettime (ts=0x7f3da6c3da70, clock=) at kernel/qelapsedtimer_unix.cpp:111
#3  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#4  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#5  0x7f3ddf6f66c9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f3da00018a0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f3ddf6f6c35 in QTimerInfoList::timerWait (this=0x7f3da00018a0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f3ddf6f896c in timerSourcePrepareHelper (timeout=0x7f3da6c3db34,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  idleTimerSourcePrepare (source=, timeout=0x7f3da6c3db34) at
kernel/qeventdispatcher_glib.cpp:212
#9  0x7f3dd956e91d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f3dd956f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f3dd956f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f3ddf6f85cb in QEventDispatcherGlib::processEvents
(this=0x7f3da8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f3ddf69f64a in QEventLoop::exec (this=this@entry=0x7f3da6c3dd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x7f3ddf4bf554 in QThread::exec (this=) at
thread/qthread.cpp:522
#15 0x7f3ddf4c46eb in QThreadPrivate::start (arg=0x2444700) at
thread/qthread_unix.cpp:376
#16 0x7f3ddb6676ba in start_thread (arg=0x7f3da6c3e700) at
pthread_create.c:333
#17 0x7f3ddeac841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f3dacab2700 (LWP 1757)):
#0  0x7ffd0cc8fb6d in clock_gettime ()
#1  0x7f3ddead6876 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f3dacab1ae0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f3ddf6f7ed1 in qt_clock_gettime (ts=0x7f3dacab1ae0, 

[kwin] [Bug 392083] New: Compositor, or something in kde5, causes nouveau driver to hang with video playback

[Christopher Neufeld]

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

Bug ID: 392083
   Summary: Compositor, or something in kde5, causes nouveau
driver to hang with video playback
   Product: kwin
   Version: 5.12.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kdeb...@cneufeld.ca
  Target Milestone: ---

I'm afraid this is going to be fairly vague.  There's something in KDE5 that
causes the nouveau driver to do a hard lockup when switching back from playing
video.  I run MythTV in full-screen mode on one of my two monitors.  In KDE4,
this wasn't a problem, but in KDE5, when using OpenGL or VDPAU rendering in
MythTV, it always hangs the nouveau driver.  The screen locks up, the keyboard
is unresponsive.  I can log in remotely and reboot the box.

I have another computer whose filesystem is the same (it's copied over via
rsync for all but bits of /etc).  It runs KDE4, and it does not demonstrate
this problem.

I've tried all three rendering settings in KDE5, they all behave the same.  The
dmesg output shows:

localhost kernel: nouveau :01:00.0: mythfrontend[3151]: failed to idle
channel 19 [mythfrontend[3151]]
localhost kernel: nouveau :01:00.0: mythfrontend[3151]: failed to idle
channel 19 [mythfrontend[3151]]
localhost kernel: nouveau :01:00.0: fifo: runlist update timeout
localhost kernel: nouveau :01:00.0: fifo: INTR 0001: 000b

My video card on the non-functioning machine is NVIDIA Corporation GF106
[GeForce GTS 450] (rev a1)

The "xine" program also causes the same lockup in KDE5, but not in KDE4.  It
also uses vdpau for rendering.

Again, sorry that this is vague.  I can compile test patches and do more
investigation if somebody can direct me to interesting lines of enquiry.

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

[Discover] [Bug 392082] New: Crash at startup after uninstall flatpak package

[Dr . Chapatin]

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

Bug ID: 392082
   Summary: Crash at startup after uninstall flatpak package
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Application: plasma-discover (5.12.80)

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.13.0-37-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
- What I was doing when the application crashed:
I uninstalled discord installed from flathub, discover said "failed" despite
discord was successfully uninstalled. I closed discover and did double click on
discord .deb package 
in dolphin. So immediately plasma shown a notification about discover crash.

-- 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 0x7f51958cb8c0 (LWP 20381))]

Thread 3 (Thread 0x7f517ec76700 (LWP 20383)):
#0  0x7f5190d0827d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f518b8026f0 in read (__nbytes=16, __buf=0x7f517ec75ad0,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f51780027b0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gwakeup.c:210
#3  0x7f518b7bee74 in g_main_context_check
(context=context@entry=0x7f517990, max_priority=2147483647,
fds=fds@entry=0x7f5170003070, n_fds=n_fds@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3632
#4  0x7f518b7bf330 in g_main_context_iterate
(context=context@entry=0x7f517990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837
#5  0x7f518b7bf49c in g_main_context_iteration (context=0x7f517990,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#6  0x7f51919485cb in QEventDispatcherGlib::processEvents
(this=0x7f5178c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f51918ef64a in QEventLoop::exec (this=this@entry=0x7f517ec75ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7f519170f554 in QThread::exec (this=this@entry=0xe45c10) at
thread/qthread.cpp:522
#9  0x7f51922eaa35 in QQmlThreadPrivate::run (this=0xe45c10) at
qml/ftw/qqmlthread.cpp:147
#10 0x7f51917146eb in QThreadPrivate::start (arg=0xe45c10) at
thread/qthread_unix.cpp:376
#11 0x7f518d8b76ba in start_thread (arg=0x7f517ec76700) at
pthread_create.c:333
#12 0x7f5190d1841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f517fe87700 (LWP 20382)):
#0  0x7f5190d0827d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f518b8026f0 in read (__nbytes=16, __buf=0x7f517fe86ac0,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0xdee6c0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gwakeup.c:210
#3  0x7f518b7bee74 in g_main_context_check
(context=context@entry=0x7f5178000990, max_priority=2147483647,
fds=fds@entry=0x7f5178003220, n_fds=n_fds@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3632
#4  0x7f518b7bf330 in g_main_context_iterate
(context=context@entry=0x7f5178000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837
#5  0x7f518b7bf49c in g_main_context_iteration (context=0x7f5178000990,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#6  0x7f51919485cb in QEventDispatcherGlib::processEvents
(this=0x7f51780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f51918ef64a in QEventLoop::exec (this=this@entry=0x7f517fe86cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7f519170f554 in QThread::exec (this=this@entry=0x7f5193884d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:522
#9  0x7f51936102c5 in QDBusConnectionManager::run (this=0x7f5193884d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#10 0x7f51917146eb in QThreadPrivate::start (arg=0x7f5193884d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:376
#11 0x7f518d8b76ba in start_thread (arg=0x7f517fe87700) at
pthread_create.c:333
#12 0x7f5190d1841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f51958cb8c0 (LWP 20381)):
[KCrash Handler]
#6  QScopedPointer::data
(this=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:140
#7  

[kdeconnect] [Bug 365731] SFTP: Error while try to manage files from computer on mobile

[Andy Holmes]

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

Andy Holmes  changed:

   What|Removed |Added

 CC||andrew.g.r.hol...@gmail.com

--- Comment #2 from Andy Holmes  ---
This bug was recently reported by a user of GSConnect[1] where the incorrect IP
address was reported by the Android app. The address reported by the app was in
the Class A range (eg. 10.0.0.0), where the device's real address was in the
more reasonable Class C range (eg. 192.0.0.0).

Probably this is a regression or re-occurance of bug #337685 which was fixed[2]
by ignoring "rmnet" connections. FWIW, the reporter also seems to be using a
Xiaomi device like the user in comment 1.

I'm just going to fix this in GSConnect by pulling the address from the active
TLS connection since I'm unaware of there ever being two different IPs used to
communicate with the same device, and the IP in the packet sent by the app can
just be ignored.

[1]: https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/66
[2]:
https://github.com/KDE/kdeconnect-android/commit/c5022358de3a5c3f6bbde44915ae48702cee719d#diff-c1d48f8ae6c815183fccb4b612c5cefa

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

[yakuake] [Bug 392081] New: white line appears intervally

[zhuisui]

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

Bug ID: 392081
   Summary: white line appears intervally
   Product: yakuake
   Version: 3.0.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: zyf034...@gmail.com
  Target Milestone: ---

Created attachment 111519
  --> https://bugs.kde.org/attachment.cgi?id=111519=edit
a video to show it

Open Yakuake and then press enter all the time, you will find that three lines
with white string appear after two empty lines intervally.
When lose focus, white string disappears.
Color of string vary, and I don't know why. In below video, it is black.

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

[Falkon] [Bug 392080] New: Crashes in wayland immediately after start

[Michael D]

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

Bug ID: 392080
   Summary: Crashes in wayland immediately after start
   Product: Falkon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: nortex...@gmail.com
  Target Milestone: ---

When I try to start Falkon in a wayland session it shows the window for a split
second and then crashes. The output I get from a terminal is:

michael@michael-Lenovo-YOGA-710-15IKB:~$ falkon
Using Wayland-EGL
WebEngine compiled with X11 support, however qpa backend is not xcb. This may
fail.
[4956:4981:0319/220418.886393:ERROR:gl_implementation.cc(246)] Failed to load
/usr/bin/libGLESv2.so: /usr/bin/libGLESv2.so: cannot open shared object file:
No such file or directory
Falkon: 1 extensions loaded
Using the 'xdg-shell-v6' shell integration
[4956:4981:0319/220419.215557:ERROR:gl_surface_qt.cpp(701)] Requested OpenGL
implementation is not supported. Implementation: 0
Received signal 11 SEGV_MAPERR 
#0 0x7fc8e5e70a25 
#1 0x7fc8e4b5795b 
#2 0x7fc8e5e70dbd 
#3 0x7fc8ec70e4b0 
#4 0x7fc8e4ba1074 
#5 0x7fc8e4ba2045 
#6 0x7fc8e68e6f34 
#7 0x7fc8e68f3c04 
#8 0x7fc8e68f6822 
#9 0x7fc8e68f7a1f 
#10 0x7fc8e68f140e 
#11 0x7fc8e68f194c 
#12 0x7fc8e68f0bf6 
#13 0x7fc8e68f2ea5 
#14 0x7fc8e5ef4a49 
#15 0x7fc8e5e8d8a8 
#16 0x7fc8e5e8f01f 
#17 0x7fc8e5e8f573 
#18 0x7fc8e5e90419 
#19 0x7fc8e5eae0aa 
#20 0x7fc8e5ec8fb6 
#21 0x7fc8e5ec43dd 
#22 0x7fc8e2ed76ba start_thread
#23 0x7fc8ec7e041d clone
  r8: 7fc8eca9f770  r9: 0001 r10: 7fc86878 r11:
7fc86878
 r12:  r13: 7fc88d7f8d60 r14: 7fc88d7f8d10 r15:
7fc86800e280
  di:   si:   bp: 7fc88d7f8b00  bx:
7fc86800e280
  dx:   ax: 7fc8eb13aaa8  cx: 7fc88d7f8910  sp:
7fc88d7f8910
  ip: 7fc8e4ba1074 efl: 00010246 cgf: 002b0033 erf:
0004
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.

I see there is an error regarding the "OpenGL implementation", which might be
due to the fact that I'm running mesa from git (18.1.0, padoka), but I've no
idea really. If I recall correctly, I had Falkon running just fine from
opensuse tumbleweed in a wayland session.

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

[krita] [Bug 388495] AppImage conflicts with installed Qt libraries

[Linus Larsson]

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

--- Comment #6 from Linus Larsson  ---
(In reply to Boudewijn Rempt from comment #5)
> Can you please check with
> http://rempt.xs4all.nl/~boud/Krita-4.0.0-beta1-9f3212b-x86_64.appimage --
> that's built in a different way.

Sadly no, I had to write over that Linux partition with another OS in the hopes
of acquiring a more stable environ. to work with Krita in.

You are welcome to close this ticket as unresolved/could not reproduce.

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

[kbackup] [Bug 392042] kbackup undefined symbol

[bugzilla_noreply]

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

--- Comment #1 from kdebt45...@outlook.com ---
problem persists after update to 1.0.2-2.10

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

[Discover] [Bug 391058] Progress indicator isnt shown correctly

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #5 from Nate Graham  ---
I see a less severe version of this in Kubuntu 17.10: the progress bar always
starts at 50%, not 0%. After that though, it seems to update properly.

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

[Discover] [Bug 390319] cannot cancel flatpaks update

[Dr . Chapatin]

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

--- Comment #3 from Dr. Chapatin  ---
(In reply to Aleix Pol from comment #2)
> There's even a bug report by Dr
> Chapatin about a crash when cancelling.
crash happens when the installation of a new flatpak package is canceled.
This report is about flatpak updates.

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

[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #8 from Stefan Brüns  ---
I think the culprit is the following line in the automounter:

https://github.com/KDE/plasma-desktop/blob/master/solid-device-automounter/kded/DeviceAutomounter.cpp#L70

Solid::StorageAccess *sa = dev.as();
if (sa->isIgnored()) {
return;
}
..

if (AutomounterSettings::shouldAutomountDevice(dev.udi(), type)) {
Solid::StorageVolume *sv = dev.as();
if (!sv->isIgnored()) {
sa->setup();
}
}

The original code [1] only checked for sv->isIgnored(), see
https://github.com/KDE/kde-runtime/blame/d34c3c6cf91de9d1abd3eab73ffd0a3baf8f00e1/solid-device-automounter/kded/DeviceAutomounter.cpp

The sa->isIgnored() was added when "porting" the code to KF5.

As far as I can see the sa->isIgnored() check should be removed, and the
path.empty() check in solid should be reverted.

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

[Discover] [Bug 391933] Unreadable application names Breeze dark

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Aleix Pol  ---
I cannot reproduce, please update to a supported version of Plasma, should be
fixed there.

See the kubuntu-backports ppa for fresh KDE builds.

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

[Discover] [Bug 391760] no way to see progress of active tasks. plus a blank progress bar appears.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dis
   ||cover/1d7b96ec879eb59107b91
   ||5e52f31941d7480ef0e

--- Comment #5 from Aleix Pol  ---
Git commit 1d7b96ec879eb59107b915e52f31941d7480ef0e by Aleix Pol.
Committed on 20/03/2018 at 00:29.
Pushed by apol into branch 'Plasma/5.12'.

Simplify the tasks view

It was trying to tackle some usecases and doing so poorly. Just show
the ongoing transactions for now.

M  +45   -82   discover/qml/ProgressView.qml

https://commits.kde.org/discover/1d7b96ec879eb59107b915e52f31941d7480ef0e

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

[kdev-python] [Bug 392031] UI is regularly lagging with regular micro freezes

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

 CC||m...@flherne.uk
   Version Fixed In||5.2.2

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

[Discover] [Bug 390319] cannot cancel flatpaks update

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Aleix Pol  ---
I'm not sure what you are talking about. There's even a bug report by Dr
Chapatin about a crash when cancelling.

Also it works on my system. I need more information. Providing the terminal
output could help.

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

[neon] [Bug 391876] Discover does not update to the last version.

[RYDeN]

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

--- Comment #2 from RYDeN  ---
$ apt-cache policy plasma-discover
plasma-discover:
  Instalados: 5.12.2-0neon+16.04+xenial+build103
  Candidato:  5.12.2-0neon+16.04+xenial+build103
  Tabla de versión:
 *** 5.12.2-0neon+16.04+xenial+build103 1100
500 http://archive.neon.kde.org/user xenial/main amd64 Packages
100 /var/lib/dpkg/status
 5.12.2-0neon+16.04+xenial+build102 1100
500 http://archive.neon.kde.org/user xenial/main amd64 Packages
 5.12.2-0neon+16.04+xenial+build101 1100
500 http://archive.neon.kde.org/user xenial/main amd64 Packages
 5.12.1-0neon+16.04+xenial+build100 1100
500 http://archive.neon.kde.org/user xenial/main amd64 Packages
 5.6.2-1ubuntu1.1 500
500 http://ar.archive.ubuntu.com/ubuntu xenial-updates/universe amd64
Packages
 5.6.2-1ubuntu1 500
500 http://ar.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

---

How can I do Jonathan to get the las Discover?

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

[Discover] [Bug 390630] Only list applications for the phone when on a phone form-factor

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Summary|Feature to limit/filter |Only list applications for
   |search results and browse   |the phone when on a phone
   |lists   |form-factor

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

[kdev-python] [Bug 392031] UI is regularly lagging with regular micro freezes

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||v-python/864d2d70965e86b5b6
   ||b73ab726b88fa07d064121
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Francis Herne  ---
Git commit 864d2d70965e86b5b6b73ab726b88fa07d064121 by Francis Herne, on behalf
of Florent Viard.
Committed on 20/03/2018 at 00:03.
Pushed by flherne into branch '5.2'.

Ensure that codestyle.py always returns something on stdout to unlock m_mutex.

By returning only a "0" size on stdout, pythonstylechecking.cpp will
 see a "reply" and unlock the m_mutex.

This avoids serious UI hangs when the stylechecker is enabled but
 `pycodestyle` is not installed.
Differential Revision: https://phabricator.kde.org/D11474

M  +2-0codestyle.py
M  +2-0pythonstylechecking.cpp

https://commits.kde.org/kdev-python/864d2d70965e86b5b6b73ab726b88fa07d064121

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

[systemsettings] [Bug 392078] Accessing Removable Disk settings crashes System Settings

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
Crash is against kde4, that's unmaintained

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

[yakuake] [Bug 392079] New: Yakuake crashes every time a tab is closed

[Aleix Pol]

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

Bug ID: 392079
   Summary: Yakuake crashes every time a tab is closed
   Product: yakuake
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: aleix...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.4+)
 (Compiled from sources)
Qt Version: 5.10.1
Frameworks Version: 5.45.0
Operating System: Linux 4.15.10-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Closed a tab by Ctrl+D on bash. Used to work, happens since very recently.

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb3d6663840 (LWP 5691))]

Thread 2 (Thread 0x7fb3d3865700 (LWP 5693)):
#0  0x7fb3e097697b in poll () from /usr/lib/libc.so.6
#1  0x7fb3d9fcfff3 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb3d9fd010e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb3e181efeb in QEventDispatcherGlib::processEvents
(this=0x7fb3cc000b20, flags=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb3e17c2a8a in QEventLoop::exec (this=this@entry=0x7fb3d3864d30,
flags=..., flags@entry=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:212
#5  0x7fb3e15d867a in QThread::exec (this=this@entry=0x7fb3e340ada0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread.cpp:522
#6  0x7fb3e33966d5 in QDBusConnectionManager::run (this=0x7fb3e340ada0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/apol/devel/frameworks/qt5/qtbase/src/dbus/qdbusconnection.cpp:178
#7  0x7fb3e15dd84f in QThreadPrivate::start (arg=0x7fb3e340ada0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:376
#8  0x7fb3dea1408c in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb3e0980e7f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fb3d6663840 (LWP 5691)):
[KCrash Handler]
#6  0x7fb3c771e96d in Konsole::PlainTextDecoder::decodeLine
(this=0x7fff6b2e3550, characters=0x7fb3d0073010, count=243) at
/home/apol/devel/frameworks/konsole/src/TerminalCharacterDecoder.cpp:129
#7  0x7fb3c773274a in Konsole::TerminalDisplay::inputMethodQuery
(this=0x5562c181d9e0, query=Qt::ImSurroundingText) at
/home/apol/devel/frameworks/konsole/src/TerminalDisplay.cpp:3289
#8  0x7fb3e2178421 in QWidget::event (this=0x5562c181d9e0,
event=0x7fff6b2e3910) at
/home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:8983
#9  0x7fb3c7733485 in Konsole::TerminalDisplay::event (this=0x5562c181d9e0,
event=0x7fff6b2e3910) at
/home/apol/devel/frameworks/konsole/src/TerminalDisplay.cpp:3541
#10 0x7fb3e2138dcc in QApplicationPrivate::notify_helper
(this=this@entry=0x5562c143b230, receiver=receiver@entry=0x5562c181d9e0,
e=e@entry=0x7fff6b2e3910) at
/home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3732
#11 0x7fb3e2140554 in QApplication::notify (this=0x7fff6b2e48f8,
receiver=0x5562c181d9e0, e=0x7fff6b2e3910) at
/home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3491
#12 0x7fb3e17c43b8 in QCoreApplication::notifyInternal2
(receiver=0x5562c181d9e0, event=event@entry=0x7fff6b2e3910) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp:1050
#13 0x7fb3d6312a72 in QCoreApplication::sendEvent (event=0x7fff6b2e3910,
receiver=) at
/home/apol/build-devel/qt5/qtbase/include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/kernel/qcoreapplication.h:234
#14 QtWaylandClient::QWaylandTextInput::updateState (this=0x5562c1446f00,
queries=..., queries@entry=..., flags=flags@entry=3) at
/home/apol/devel/frameworks/qt5/qtwayland/src/client/qwaylandinputcontext.cpp:143
#15 0x7fb3d6313613 in QtWaylandClient::QWaylandInputContext::setFocusObject
(this=0x5562c1444780) at
/home/apol/devel/frameworks/qt5/qtwayland/src/client/qwaylandinputcontext.cpp:549
#16 0x7fb3e1b39858 in QGuiApplicationPrivate::_q_updateFocusObject
(this=, object=0x5562c181d9e0) at
/home/apol/devel/frameworks/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:3815
#17 0x7fb3e1b3a0d0 in QGuiApplication::qt_static_metacall (_o=, _c=, _id=, _a=) at
.moc/moc_qguiapplication.cpp:179
#18 0x7fb3e17f3f75 in QMetaObject::activate
(sender=sender@entry=0x5562c15bd200, signalOffset=,
local_signal_index=local_signal_index@entry=16, 

[systemsettings] [Bug 392078] New: Accessing Removable Disk settings crashes System Settings

[Andrew Morris]

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

Bug ID: 392078
   Summary: Accessing Removable Disk settings crashes System
Settings
   Product: systemsettings
   Version: unspecified
  Platform: Compiled Sources
OS: FreeBSD
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: morrand...@gmail.com
  Target Milestone: ---

Application: systemsettings (4.11.22)
KDE Platform Version: 4.14.30 (Compiled from sources)
Qt Version: 4.8.7
Operating System: FreeBSD 10.4-STABLE amd64
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to troubleshoot a disk mounting error. Attempted to open the
"Removable Disks" group in System Settings. I never even got the window to open
because the crash interrupted it.

- Unusual behavior I noticed:
I am having trouble mounting a CD. Opening Dolphin and selecting "CD" gives the
error: "An error occurred while accessing "CD", the system responded:
org.freedesktop.Hal.Device.PermissionDeniedByPolicy:
org.freedesktop.hal.storage.mount-removable no <-- (action, result)"

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Abort trap
[KCrash Handler]
#9  0x00080602393a in thr_kill () from /lib/libc.so.7
#10 0x000806023926 in raise () from /lib/libc.so.7
#11 0x0008060238a9 in abort () from /lib/libc.so.7
#12 0x000804e98edd in qt_message_output (msgType=QtFatalMsg,
buf=0x820c826f8 "ASSERT failure in KConfigGroup::groupImpl: \"can not have an
unnamed child group\", file
/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/config/kconfiggroup.cpp,
line 516") at global/qglobal.cpp:2423
#13 0x000804e9927a in qt_message (msgType=QtFatalMsg, msg=0x8050d2e4f
"ASSERT failure in %s: \"%s\", file %s, line %d", ap=0x7fff7910) at
global/qglobal.cpp:2469
#14 0x000804e987f7 in qFatal (msg=0x8050d2e4f "ASSERT failure in %s:
\"%s\", file %s, line %d") at global/qglobal.cpp:2652
#15 0x000804e988c8 in qt_assert_x (where=0x80469a54b
"KConfigGroup::groupImpl", what=0x80469a57e "can not have an unnamed child
group", file=0x80469a3e8
"/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/config/kconfiggroup.cpp",
line=516) at global/qglobal.cpp:2126
#16 0x0008044b9876 in KConfigGroup::groupImpl (this=0x7fff79f8,
aGroup=...) at
/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/config/kconfiggroup.cpp:516
#17 0x0008044b4317 in KConfigBase::group (this=0x7fff79f8, str=...) at
/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/config/kconfigbase.cpp:51
#18 0x0008209946f4 in AutomounterSettings::deviceSettings (udi=...) at
/usr/ports/x11/kde4-runtime/work/kde-runtime-16.12.3/solid-device-automounter/lib/AutomounterSettings.cpp:27
#19 0x0008209948a2 in AutomounterSettings::deviceAutomountIsForced
(udi=..., type=) at
/usr/ports/x11/kde4-runtime/work/kde-runtime-16.12.3/solid-device-automounter/lib/AutomounterSettings.cpp:47
#20 0x000820990faa in DeviceModel::addNewDevice (this=0x8157baa60, udi=...)
at
/usr/ports/x11/kde4-runtime/work/kde-runtime-16.12.3/solid-device-automounter/kcm/DeviceModel.cpp:93
#21 0x00082098ff2e in DeviceModel::reload (this=0x8157baa60) at
/usr/ports/x11/kde4-runtime/work/kde-runtime-16.12.3/solid-device-automounter/kcm/DeviceModel.cpp:120
#22 0x00082098fc4b in DeviceModel::DeviceModel (this=0x8157baa60,
parent=0x6) at
/usr/ports/x11/kde4-runtime/work/kde-runtime-16.12.3/solid-device-automounter/kcm/DeviceModel.cpp:16
#23 0x00082098bd34 in DeviceAutomounterKCM::DeviceAutomounterKCM
(this=0x820d58160, parent=) at
/usr/ports/x11/kde4-runtime/work/kde-runtime-16.12.3/solid-device-automounter/kcm/DeviceAutomounterKCM.cpp:58
#24 0x00082098f315 in KPluginFactory::createInstance (parentWidget=, parent=, args=...) at
/usr/local/include/kde4/KDE/../kpluginfactory.h:477
#25 0x00080467c6de in KPluginFactory::create (this=0x820c5be80,
iface=0x802853c80  "KCModule", parentWidget=0x0,
parent=0x8157b28e0, args=..., keyword=...) at
/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/util/kpluginfactory.cpp:203
#26 0x00080201cacc in QMetaObject::className (this=,
this=) at /usr/local/include/qt4/QtCore/qobjectdefs.h:492
#27 KPluginFactory::create (this=, this=, parentWidget=, parent=, keyword=...,
args=..., this=, parentWidget=, parent=, keyword=..., args=...) at
/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/util/kpluginfactory.h:531
#28 KService::createInstance (this=0x81578a340, parentWidget=0x0,
parent=0x8157b28e0, args=..., error=0x7fff7fe0) at
/usr/ports/x11/kdelibs4/work/kdelibs-4.14.30/kdecore/services/kservice.h:573
#29 0x00080201b692 in KSharedPtr::operator-> (this=, this=, this=, parent=0x8157b28e0, args=...,

[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.

[Jeremy W . Murphy]

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

Jeremy W. Murphy  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from Jeremy W. Murphy  ---
I think this is fixed; I haven't seen it happen for ages.

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

[Breeze] [Bug 392028] Incomplete refresh of selected are in menus

[Luca Carlon]

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

--- Comment #2 from Luca Carlon  ---
So you say the bug is fixed already in Qt or that I should report this there?

I have to say that I tested fusion and oxygen before reporting and I couldn't
reproduce the issue there.
Thanks!

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

[dolphin] [Bug 386460] Trashing is slow when trash size is limited

[Wyatt Childers]

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

--- Comment #7 from Wyatt Childers  ---
(In reply to Alexander Meshcheryakov from comment #4)
> I noticed this too. In my case deleting files had several seconds delay, but
> subsequent deletion was instantaneous. I suppose delay is caused by
> calculation of current trash size to decide whether it needs cleaning before
> adding new content. While trash contents listing is cached in OS, it takes
> way less time to recalculate occupied space for next deletion, but once it
> gets squeezed out of cache moving content to trash needs to reread disk
> content.
> 
> One more thing that corroborates this theory: recently calculation of
> occupied space got broken in my system (
> https://bugs.kde.org/show_bug.cgi?id=383324#c2 ), now dolphin shows free
> space of trash equal to its size limit regardless of contents. And now
> moving content to trash is always instantaneous for me.
> 
> If my assumption is correct, this bug should not be noticeable for users
> with trash on SSD. My $HOME is located on HDD, so reading thousands of
> files/dirs of trash listing from storage should take seconds.
> 
> Wyatt, Huon are your trash located on HDD or SSD?

BTRFS SSD here

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

[LabPlot2] [Bug 392077] New: Import data headers treat spaces as tab delimiter

[Justin]

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

Bug ID: 392077
   Summary: Import data headers treat spaces as tab delimiter
   Product: LabPlot2
   Version: 2.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: jr...@cornell.edu
  Target Milestone: ---

When importing ASCII data using tab/auto delimiter spaces in header are treated
as delimiters resulting in more columns than data.

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

[kwin] [Bug 377756] Restore windows to correct position and activity

[Christian Muehlhaeuser]

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

--- Comment #4 from Christian Muehlhaeuser  ---
This seems to work a lot better in the latest release! I can't reproduce it
with the bunch of common applications I use anymore, so I'd suggest to mark
this as RESOLVED. Unless someone objects?

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

[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers

[Nate Graham]

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

--- Comment #7 from Nate Graham  ---
> Did 
> https://cgit.kde.org/solid.git/commit/?id=e94ba0619477e990903abd0ea0ab584b98dbac08
>  have any effect on this?

It seems to have resolved Bug 389479, but then caused this one.

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

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

[Philippe Waroquiers]

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

--- Comment #25 from Philippe Waroquiers  ---
(In reply to Дилян Палаузов from comment #23)
> I just verified, that LLVM does not install gcc-ar and gcc-ranlib, but
> llvm-ar and llvm-ranlib .
> 
> So to make LTO work with Clang, on systems where GCC is not installed,
> either llvm-ar and llvm-ranlib shall be used, or ar and ranlib shall be used
> and it must be assumed that the system is LTO-ready (the plugins are under
> {libdir}/bfd-plugins/).
> 
> Concerning installing by default the plugins on the compiler's "make
> install" on the location where binutils will look for them I filled
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 and
> https://bugs.llvm.org/show_bug.cgi?id=36802.
Which, as I understand, does not work if you have several gcc versions
installed.

> 
> Shall I open for the assembler-review in coregrind/m_libcsetjmp.c a separate
> ticket, or can it be kept here?
Yes, that would be better, i.e. to have 2 new bugs:
* clang/lto/llvm-ar, ... (cdr comment 24)
* allow to configure valgrind using CFLAGS (a.o. to support LTO)

Thanks
Philippe

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

[plasma-pa] [Bug 352729] No obvious mute button/tick box for all devices

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||oliv...@churlaud.com

--- Comment #5 from Nicolas Fella  ---
*** Bug 354856 has been marked as a duplicate of this bug. ***

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

[plasma-pa] [Bug 354856] Disable all system sound

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||nicolas.fe...@gmx.de
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Nicolas Fella  ---


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

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

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #24 from Philippe Waroquiers  ---
(In reply to Дилян Палаузов from comment #22)
> I am against using gcc-ar or gcc-ranlib.  These are probably not available,
> when clang is used, and it can do LTO, too.
> 
> Instead of cluttering configure.ac to use gcc-ac/gcc-ranlib, it can either
> rely on the fact, that /usr/(local/)?/bfd-plugins contain the LTO plugin, or
> alternatively compile something with -flto to an object file, call "nm
> the-object-file.o" and if the latter prints "missing plugin", then configure
> shall tell the user that she has to put the linker plugin under
> {libdir}/bfd-plugins .

Using directly ar and similar is causing problems on some platforms,
(some of them that I care about). The gcc documentation (including the latest
gcc 7.3) explicitly indicates to use gcc-ar and similar
(I guess this ensures that in case you use a gcc in another path
that the 'standard' /usr/...; that the correct/associated plugins are used.
So, I do not think it is a good idea to diverge (for gcc)
from the explicitly documented way to build a static lib, even
if some advanced users might be able to fix/bypass/... using
plugins in a directory such as /usr/(local/)?/bfd-plugins 
(note that on my distro, there is no such directory. So, plugins are
somewhere else, I am guessing properly found by gcc-ar and similar).

> 
> This would help the user to adjust her system to be able to compile other
> software with LTO, even software whose authors don't know about LTO.
> 
> LTO is anyway not ready for the prime time yet.  emacs does not lTO-link
> with ld.bfd, but with ld.gold and php also doesn't work with lto.  So if the
> build process just uses ar/ranlib and it fails, then the user shall try
> without LTO or debug, debug, debug...
Or rather, configure shall do the correct thing, whenever it can, using
the way as documented in gcc manual.

> 
> I would like to know why gcc creates gcc-ar instead of puthing the linker
> plug in a place, that normal ar would auto-load it, but I do not expect an
> answer here on this.
As said above, if you have different gcc versions installed, and the plugin
differ according to gcc version, then gcc-ar and similar can
do the job properly. An 'hard-coded' path that ar would use will not
give the same. At least for some gcc, I see the plugin is part of gcc
itself.

As I understand, the real problem with gcc-ar and similar is that this
does not work with llvm, as llvm needs llvm-ar and similar.
I largely prefer to keep this bug closed, and have another one bug
discussing using clang+lto to build valgrind.
I suppose patches for this would not be too difficult, but I am not
an llvm user.

So, can you open another bug related to clang/lto/llvm-ar, ... ?

Thanks
Philippe

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

[elisa] [Bug 391495] Configure menu entry does not open any window

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/eli
   ||sa/5ffcd5c23782cad8403995c3
   ||d2c8ce6506411602
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Matthieu Gallien  ---
Git commit 5ffcd5c23782cad8403995c3d2c8ce6506411602 by Matthieu Gallien.
Committed on 19/03/2018 at 19:51.
Pushed by mgallien into branch '0.1'.

fix configuration dialog not showing properly

Summary:
fix configuration dialog not showing properly

Test Plan: configuration dialog opens correctly (depends on install path being
discovered properly)

Reviewers: #elisa

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

M  +1-1src/elisaapplication.cpp

https://commits.kde.org/elisa/5ffcd5c23782cad8403995c3d2c8ce6506411602

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

[plasmashell] [Bug 392039] Impliment "Custom command" widget

[David Edmundson]

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

--- Comment #8 from David Edmundson  ---
Or "command output": https://store.kde.org/p/1166510/ was the one I was
thinking of.

If you have any feature requests, ask those authors.

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

[krita] [Bug 392075] Program thinks I'm constantly scrolling

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #2 from Boudewijn Rempt  ---
Yes -- this is not a bug in Krita, but a problem with your system, if as you
say your browser also scrolls. A bug is something we can fix in Krita's code,
which this, obviously, isn't.

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

[konsole] [Bug 390629] Fonts not being rendered in bold in spite of removing the face name from the configuration files.

[Mike Lui]

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

--- Comment #5 from Mike Lui  ---
I'm seeing the same problem on a fresh install in ArchLinux, all default
settings.

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

[krita] [Bug 391940] [brush] [bristle-engine] Default preset "d)_Ink-8_Sumi-e" spams terminal output

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/dadc98f0fb35d48b94c4eb1b |ta/619acb0a51c4b24ddba3ebae
   |0efd7c6473c410e2|6f9864dd36cc8236

--- Comment #4 from Boudewijn Rempt  ---
Git commit 619acb0a51c4b24ddba3ebae6f9864dd36cc8236 by Boudewijn Rempt, on
behalf of Dmitry Kazakov.
Committed on 19/03/2018 at 20:30.
Pushed by rempt into branch 'krita/4.0'.

Avoid warnings in KisHairyPaintOp due to unititialized paint information
(cherry picked from commit 93b8ba3a3b207c410a50adcf0d1a7de5cc384004)

M  +9-4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/619acb0a51c4b24ddba3ebae6f9864dd36cc8236

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

[krita] [Bug 391940] [brush] [bristle-engine] Default preset "d)_Ink-8_Sumi-e" spams terminal output

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/dadc98f0fb35d48b94c4eb1b |ta/619acb0a51c4b24ddba3ebae
   |0efd7c6473c410e2|6f9864dd36cc8236
   |https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/dadc98f0fb35d48b94c4eb1b |ta/c8ffefa7e45c8944efd73c95
   |0efd7c6473c410e2|83e21198f33d83ea

--- Comment #4 from Boudewijn Rempt  ---
Git commit 619acb0a51c4b24ddba3ebae6f9864dd36cc8236 by Boudewijn Rempt, on
behalf of Dmitry Kazakov.
Committed on 19/03/2018 at 20:30.
Pushed by rempt into branch 'krita/4.0'.

Avoid warnings in KisHairyPaintOp due to unititialized paint information
(cherry picked from commit 93b8ba3a3b207c410a50adcf0d1a7de5cc384004)

M  +9-4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/619acb0a51c4b24ddba3ebae6f9864dd36cc8236

--- Comment #5 from Boudewijn Rempt  ---
Git commit c8ffefa7e45c8944efd73c9583e21198f33d83ea by Boudewijn Rempt, on
behalf of Dmitry Kazakov.
Committed on 19/03/2018 at 20:30.
Pushed by rempt into branch 'krita/4.0'.

Fix uninitialized distance info for KisHairyPaintOp
(cherry picked from commit dadc98f0fb35d48b94c4eb1b0efd7c6473c410e2)

M  +22   -4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/c8ffefa7e45c8944efd73c9583e21198f33d83ea

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

[dolphin] [Bug 226678] dolphin thumbnailer takes too much ram and makes system unresponsive

[Julian Schraner]

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

Julian Schraner  changed:

   What|Removed |Added

 CC||juliquad...@gmail.com

--- Comment #3 from Julian Schraner  ---
I don't have a lot of 8Kx8K photos (to be precise, zero) so I cannot triage
this issue properly. Can someone confirm that this problem still exists with
Dolphin 17.12.3? If yes, I'll set this bug to CONFIRMED, if not I'll close it.

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

[plasmashell] [Bug 392039] Impliment "Custom command" widget

[Zakhar]

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

--- Comment #7 from Zakhar  ---
Why isn't it provided with KDE?

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

[kmymoney] [Bug 392072] Aktualizacja do najnowszej wersji KMyMoney 5.0.1

[Jack]

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

Jack  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Jack  ---
5.0.1 was only released today, so it will be some days before the linux
distributions release packages, and it will probably be some weeks before it is
released for Windows, as there have been some issues which are still being
resolved.  You can keep watching https://kmymoney.org for an announcement.

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

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

[dolphin] [Bug 260310] Capacity bar in status bar isn't updated on changes

[Julian Schraner]

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

Julian Schraner  changed:

   What|Removed |Added

 CC||juliquad...@gmail.com

--- Comment #5 from Julian Schraner  ---
@Alexey Can you still reproduce this issue with Dolphin 17.12.3? If not, I'll
close this bug soon™.

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

[kmymoney] [Bug 391684] New Version

[Jack]

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

Jack  changed:

   What|Removed |Added

 CC||mariusz-nowi...@tlen.pl

--- Comment #4 from Jack  ---
*** Bug 392072 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 246288] dolphin does funny things when trying to view a packed file with the wrong extension

[Julian Schraner]

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

Julian Schraner  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 CC||juliquad...@gmail.com
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Julian Schraner  ---
I cannot reproduce this behavior with Dolphin 17.12.3. If I create a .rar
archive and rename the extension to .zip, then click on it, Ark will open and
try to decompress it. This also works, as Ark does not only look at the
extension but also at the file header. Closing this issue.

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

[kwin] [Bug 392076] New: Kwin issues illegal OpenGL calls when ALT+TABing through window list

[Clemens Eisserer]

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

Bug ID: 392076
   Summary: Kwin issues illegal OpenGL calls when ALT+TABing
through window list
   Product: kwin
   Version: 5.12.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: linuxhi...@gmail.com
  Target Milestone: ---

Created attachment 111518
  --> https://bugs.kde.org/attachment.cgi?id=111518=edit
screenshot of error message

When running Kwin with MESA_DEBUG=1, I get the the following output when
ALT+TABing through the window list:

Mesa: User error: GL_INVALID_OPERATION in GlTexSubImage2D(invalid texture level
0)

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

[plasmashell] [Bug 392039] Impliment "Custom command" widget

[Scott Harvey]

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

Scott Harvey  changed:

   What|Removed |Added

 CC||bund...@gmail.com

--- Comment #6 from Scott Harvey  ---
Look for a plasmoid called "Kargos". I believe it does exactly what you're
requesting.

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

[Oxygen] [Bug 383261] Tabs in Oxygen plasma5 don't look like kde4 Oxygen tabs

[bugzilla_noreply]

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

matheus4...@hotmail.com changed:

   What|Removed |Added

 CC||matheus4...@hotmail.com

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

[krita] [Bug 392075] Program thinks I'm constantly scrolling

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
that sounds like a problem with your mouse or tablet. if it happens with a web
browser, there is something going on. I would try to just test your mouse and
tablet separately.

Having two input devices connected at the same time can cause problems
sometimes too.

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

[krita] [Bug 381549] Enabled buttons appears greyed like disabled

[Rafael]

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

--- Comment #9 from Rafael  ---
I used long far away PS, then Gimp and finally Krita, and for me it's more
difficult to understand the way Krita manage this layer icons, but it's a
personal opinion, of course. 

Anyway, thank you sincerely for consider the option.

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

[krita] [Bug 392070] right click in number boxes in edit brush settings opens popup instead of allowing to type numbers.

[nikola]

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

--- Comment #2 from nikola  ---
It is hard to think of usability reasons. Numbers that users want to enter
manualy are small and faster to type than to copy and paste from clipboard via
popup menu (e.g. for rotation: 90, 180, 270; for brush size 128). Novice users
can use slider method.
Proposal
How about adding a setting (checkbox?) in preferences that omit this popup. It
could be "only beta feature" so users can test it and discuss from experience
before final decision is made.
Note
In Blender3D there is similar control that opens popup on right click. Left
click allows direct input instead of using slider. Slider responds on left
click + drag. I prefer Krita slider in Tool Options :)

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

[krita] [Bug 392075] New: Program thinks I'm constantly scrolling

[Kazumi]

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

Bug ID: 392075
   Summary: Program thinks I'm constantly scrolling
   Product: krita
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: zock...@hotmail.de
  Target Milestone: ---

The application apparently thinks I'm constantly scrolling down somehow. I even
encountered this problem with this bug-report site, but nowhere else (like in
gaming or even on other websites). My PC is running Windows 8.1. I got a Wacom
tablet and a Tecknet wireless mouse. I don't know what happend, but now,
everytime I come across a scrollbar or a dropdown-option, it just scrolls
"down" uncontrollably. I can try and scroll up, but it's just much faster than
I can scroll against it. I can't use the program like this and I've started a
little animation project in it even!

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

[krita] [Bug 391940] [brush] [bristle-engine] Default preset "d)_Ink-8_Sumi-e" spams terminal output

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/93b8ba3a3b207c410a50adcf |ta/93b8ba3a3b207c410a50adcf
   |0d1a7de5cc384004|0d1a7de5cc384004
   ||https://commits.kde.org/kri
   ||ta/dadc98f0fb35d48b94c4eb1b
   ||0efd7c6473c410e2

--- Comment #2 from Dmitry Kazakov  ---
Git commit 93b8ba3a3b207c410a50adcf0d1a7de5cc384004 by Dmitry Kazakov.
Committed on 19/03/2018 at 19:41.
Pushed by dkazakov into branch 'master'.

Avoid warnings in KisHairyPaintOp due to unititialized paint information

M  +9-4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/93b8ba3a3b207c410a50adcf0d1a7de5cc384004

--- Comment #3 from Dmitry Kazakov  ---
Git commit dadc98f0fb35d48b94c4eb1b0efd7c6473c410e2 by Dmitry Kazakov.
Committed on 19/03/2018 at 19:41.
Pushed by dkazakov into branch 'master'.

Fix uninitialized distance info for KisHairyPaintOp

M  +22   -4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/dadc98f0fb35d48b94c4eb1b0efd7c6473c410e2

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

[krita] [Bug 391940] [brush] [bristle-engine] Default preset "d)_Ink-8_Sumi-e" spams terminal output

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/93b8ba3a3b207c410a50adcf |ta/93b8ba3a3b207c410a50adcf
   |0d1a7de5cc384004|0d1a7de5cc384004
   ||https://commits.kde.org/kri
   ||ta/dadc98f0fb35d48b94c4eb1b
   ||0efd7c6473c410e2

--- Comment #2 from Dmitry Kazakov  ---
Git commit 93b8ba3a3b207c410a50adcf0d1a7de5cc384004 by Dmitry Kazakov.
Committed on 19/03/2018 at 19:41.
Pushed by dkazakov into branch 'master'.

Avoid warnings in KisHairyPaintOp due to unititialized paint information

M  +9-4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/93b8ba3a3b207c410a50adcf0d1a7de5cc384004

--- Comment #3 from Dmitry Kazakov  ---
Git commit dadc98f0fb35d48b94c4eb1b0efd7c6473c410e2 by Dmitry Kazakov.
Committed on 19/03/2018 at 19:41.
Pushed by dkazakov into branch 'master'.

Fix uninitialized distance info for KisHairyPaintOp

M  +22   -4plugins/paintops/hairy/kis_hairy_paintop.cpp

https://commits.kde.org/krita/dadc98f0fb35d48b94c4eb1b0efd7c6473c410e2

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

[kmymoney] [Bug 392072] Aktualizacja do najnowszej wersji KMyMoney 5.0.1

[Stefan Böhmann]

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

Stefan Böhmann  changed:

   What|Removed |Added

  Component|general |general
Product|knipptasch  |kmymoney
   Assignee|k...@hilefoks.org|kmymoney-de...@kde.org

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

[plasmashell] [Bug 391180] Device notifier shows "This device can now be safely removed" when a removable device is mounted

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[plasmashell] [Bug 381442] SVG starter icons not displayed in application menus/launchers

[Sefa Eyeoglu]

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

--- Comment #14 from Sefa Eyeoglu  ---
Reviving this issue. 

Could it be possible that this is an upstream issue with Qt? I have seen
multiple issues regarding svgs and Qt.

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

[ksmserver] [Bug 392071] Occasional hang on login with plasmashell being stopped

[BingMyBong]

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

--- Comment #1 from BingMyBong  ---
I forgot to list my software versions

opensuse:tumbleweed:20180316
Qt: 5.10.0 KDE Frameworks: 5.43.0 - KDE Plasma:  5.12.3 - kwin 5.12.3
kmail2 5.7.2 - akonadiserver 5.7.2 - Kernel:  4.15.9-1-default  -
xf86-video-nouveau:  1.0.15

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

[Powerdevil] [Bug 391633] Screen brightness cannot be adjusted from keyboard or UI

[bugzilla_noreply]

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

kdeb...@d3801741e.33mail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from kdeb...@d3801741e.33mail.com ---
What kind of information is required to proceed with troubleshooting this
issue?

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

[kdevelop] [Bug 392074] New: KDevelop crash while opening (and possibly removing one of the session's project dirs)

[RJVB]

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

Bug ID: 392074
   Summary: KDevelop crash while opening (and possibly removing
one of the session's project dirs)
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.2.1-62-g2d229fd94a)
 (Compiled from sources)
Qt Version: 5.9.4
Frameworks Version: 5.42.0
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS

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

I started a KDevelop session, noticed it would waste resources on an old
project and trashed that project's directory assuming KDevelop would notice its
absence and remove it from the session.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3d488b07c0 (LWP 16958))]

Thread 18 (Thread 0x7f3d2d014700 (LWP 16961)):
#0  0x7f3d40758c9d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f3d3786ab72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f3d3786c64f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3d2f876d69 in QXcbEventReader::run (this=0x11d6850) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1330
#4  0x7f3d413286e3 in QThreadPrivate::start (arg=0x11d6850) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/thread/qthread_unix.cpp:368
#5  0x7f3d3b2c9184 in start_thread (arg=0x7f3d2d014700) at
pthread_create.c:312
#6  0x7f3d4076603d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 17 (Thread 0x7f3d201ea700 (LWP 16962)):
#0  QMutex::lock (this=this@entry=0x1877d50) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/thread/qmutex.cpp:224
#1  0x7f3d41581ca5 in QMutexLocker (m=0x1877d50, this=)
at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/include/QtCore/../../src/corelib/thread/qmutex.h:200
#2  canWaitLocked (this=0x1877d20) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/include/QtCore/5.9.4/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253
#3  postEventSourcePrepare (s=0x7f3d180012d0, timeout=0x7f3d201e9c6c) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:259
#4  0x7f3d38c07996 in g_main_context_prepare () from
/opt/local/lib/libglib-2.0.so.0
#5  0x7f3d38c08713 in g_main_context_iterate.isra () from
/opt/local/lib/libglib-2.0.so.0
#6  0x7f3d38c088ec in g_main_context_iteration () from
/opt/local/lib/libglib-2.0.so.0
#7  0x7f3d41581d9b in QEventDispatcherGlib::processEvents
(this=0x7f3d180008c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#8  0x7f3d415241b3 in QEventLoop::exec (this=this@entry=0x7f3d201e9df0,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/kernel/qeventloop.cpp:212
#9  0x7f3d41322faa in QThread::exec (this=this@entry=0x7f3d44111400
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/thread/qthread.cpp:515
#10 0x7f3d43e9bdd5 in QDBusConnectionManager::run (this=0x7f3d44111400
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/dbus/qdbusconnection.cpp:178
#11 0x7f3d413286e3 in QThreadPrivate::start (arg=0x7f3d44111400 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.4/qtbase/src/corelib/thread/qthread_unix.cpp:368

[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||Qt 5.9.5

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

[Discover] [Bug 392063] [PackageKit] Update Notifier didn't update after using Discover to perform updates

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability
Summary|Update Notifier didn't  |[PackageKit] Update
   |update after using Discover |Notifier didn't update
   |to perform updates  |after using Discover to
   ||perform updates

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

[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|The number of updates   |[Flatpak] The number of
   |available shown by Discover |updates available shown by
   |and its tray icon don't |Discover and its tray icon
   |match   |don't match

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

[Discover] [Bug 392063] Update Notifier didn't update after using Discover to perform updates

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #5 from Nate Graham  ---
If Bug 385754 is tracking something Flatpak-specific, then no, this isn't a
duplicate.

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

[Discover] [Bug 392063] Update Notifier didn't update after using Discover to perform updates

[Aleix Pol]

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

--- Comment #4 from Aleix Pol  ---
Are you sure it's a duplicate? Because as described here it doesn't look like
the mismatch is coming from flatpak.

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

[Discover] [Bug 385754] The number of updates available shown by Discover and its tray icon don't match

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

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

[Discover] [Bug 392063] Update Notifier didn't update after using Discover to perform updates

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---


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

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

[Discover] [Bug 385754] The number of updates available shown by Discover and its tray icon don't match

[Nate Graham]

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

--- Comment #11 from Nate Graham  ---
*** Bug 392063 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 392061] Low resolution image for songs without covert art

[Matthijs Tijink]

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

Matthijs Tijink  changed:

   What|Removed |Added

Version|1.5 |1.8

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

[kdeconnect] [Bug 392062] Cover art now showing even if it exists in the file on the desktop

[Matthijs Tijink]

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

Matthijs Tijink  changed:

   What|Removed |Added

Version|1.5 |1.8

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

[kdeconnect] [Bug 392061] Low resolution image for songs without covert art

[Matthijs Tijink]

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

Matthijs Tijink  changed:

   What|Removed |Added

 CC||matthijstij...@gmail.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Matthijs Tijink  ---
We'll look into the blurry icons.

The notification can be disabled in the options, or can be swiped away if all
players are paused.

It should be 1.8 here too, but apparently that's not an option yet, we'll fix
that.

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

[Discover] [Bug 392063] Update Notifier didn't update after using Discover to perform updates

[Dr . Chapatin]

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

--- Comment #2 from Dr. Chapatin  ---
duplicate? bug 385754

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

[Discover] [Bug 391941] Crash when flatpak installation is canceled

[Dr . Chapatin]

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

--- Comment #5 from Dr. Chapatin  ---
info from your link was not enough for me.
However after some searches I compiled discover with debug enabled.

Thread 36 (Thread 0x7fff96ab8700 (LWP 17614)):
#0  0x7361e879 in syscall () at /usr/lib/libc.so.6
#1  0x7fffedca8dcd in g_cond_wait_until ()
at /usr/lib/libglib-2.0.so.0
#2  0x7fffedc35753 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fffedc8ac76 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fffedc8a26a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#6  0x73623e7f in clone () at /usr/lib/libc.so.6

Thread 27 (Thread 0x7fffc2b76700 (LWP 17564)):
#0  0x7361b9bc in fsync () at /usr/lib/libc.so.6
#1  0x7fffc051c6a1 in  () at /usr/lib/libostree-1.so.1
#2  0x7fffc051ee47 in ostree_repo_commit_transaction ()
at /usr/lib/libostree-1.so.1
---Type  to continue, or q  to quit---
#3  0x7fffc1a9f68a in  () at /usr/lib/libflatpak.so.0
#4  0x7fffc1aa2902 in  () at /usr/lib/libflatpak.so.0
#5  0x7fffc1a8b181 in flatpak_installation_install_full ()
at /usr/lib/libflatpak.so.0
#6  0x7fffc1a8b32b in flatpak_installation_install ()
at /usr/lib/libflatpak.so.0
#7  0x7fffc1f57dc0 in FlatpakTransactionJob::run() (this=0x565846a0)
at
/home/stalker/discover/repos/extra-x86_64/src/discover-5.12.3/libdiscover/backends/FlatpakBackend/FlatpakTransactionJob.cpp:106
installRelatedRef = 
localError = 0x0
ref = 0x0
refName = {static null = {}, d = 0x56ea7150}
kind = 1
#8  0x73d1bb4d in  () at /usr/lib/libQt5Core.so.5
---Type  to continue, or q  to quit---
#9  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#10 0x73623e7f in clone () at /usr/lib/libc.so.6

Thread 25 (Thread 0x7fffb0957700 (LWP 17562)):
#0  0x7361997b in poll () at /usr/lib/libc.so.6
#1  0x7fffedc61ff3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffedc623b2 in g_main_loop_run ()
at /usr/lib/libglib-2.0.so.0
#3  0x7fffc179a6d8 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7fffedc8a26a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#6  0x73623e7f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fffa915d700 (LWP 17295)):
#0  0x7361997b in poll () at /usr/lib/libc.so.6
#1  0x7fffedc61ff3 in  () at /usr/lib/libglib-2.0.so.0
---Type  to continue, or q  to quit---
#2  0x7fffedc6210e in g_main_context_iteration ()
at /usr/lib/libglib-2.0.so.0
#3  0x7fffedc62162 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fffedc8a26a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#6  0x73623e7f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fffabb6f700 (LWP 17292)):
#0  0x7361997b in poll () at /usr/lib/libc.so.6
#1  0x7fffedc61ff3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffedc6210e in g_main_context_iteration ()
at /usr/lib/libglib-2.0.so.0
#3  0x73f652f1 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x73f073db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
---Type  to continue, or q  to quit---
#5  0x73d167ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x73d1bb4d in  () at /usr/lib/libQt5Core.so.5
#7  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#8  0x73623e7f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fffc3377700 (LWP 17280)):
#0  0x7361997b in poll () at /usr/lib/libc.so.6
#1  0x7fffedc61ff3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffedc6210e in g_main_context_iteration ()
at /usr/lib/libglib-2.0.so.0
#3  0x73f652f1 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x73f073db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x73d167ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x73d1bb4d in  () at /usr/lib/libQt5Core.so.5
---Type  to continue, or q  to quit---
#7  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#8  0x73623e7f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fffc3fff700 (LWP 17279)):
#0  0x7361997b in poll () at /usr/lib/libc.so.6
#1  0x7fffedc61ff3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffedc6210e in g_main_context_iteration ()
at /usr/lib/libglib-2.0.so.0
#3  0x73f652f1 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x73f073db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x73d167ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x73d1bb4d in  () at /usr/lib/libQt5Core.so.5
#7  0x7fffefe9308c in start_thread () at /usr/lib/libpthread.so.0
#8 

[kdeconnect] [Bug 392062] Cover art now showing even if it exists in the file on the desktop

[Matthijs Tijink]

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

Matthijs Tijink  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Severity|normal  |wishlist
 CC||matthijstij...@gmail.com

--- Comment #1 from Matthijs Tijink  ---
That's correct, album art stored on your pc is not supported yet, only album
art stored on the internet.

It's in progress and should come in a future version of KDE Connect.

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

[krita] [Bug 392073] Segmentation fault on exit

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
I suspect that this has to do with the version of Qt you're using. It doesn't
crash with a more recent version of Qt.

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

[klipper] [Bug 352171] clipboard history in systray cannot be really disabled, security problem

[Pekka Helenius]

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

Pekka Helenius  changed:

   What|Removed |Added

 CC||fince...@hotmail.com

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

[plasmashell] [Bug 391358] Plasma crashes at login

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 CC||mrvi...@gmail.com

--- Comment #1 from Marco Martin  ---
*** Bug 389806 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 389806] Plasmashell crashed on start

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||notm...@gmail.com

--- Comment #1 from Marco Martin  ---


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

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

[Discover] [Bug 392063] Update Notifier didn't update after using Discover to perform updates

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Created attachment 111517
  --> https://bugs.kde.org/attachment.cgi?id=111517=edit
Discover and Updates Plasmoid don't agree

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

[krita] [Bug 392073] New: Segmentation fault on exit

[Aleksey Samoilov]

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

Bug ID: 392073
   Summary: Segmentation fault on exit
   Product: krita
   Version: 4.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: samoilov@gmail.com
  Target Milestone: ---

Krita crashed on exit. Debian 9, Qt 5.7.1

Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f35b888a800 (LWP 17284))]

Thread 6 (Thread 0x7f3583fff700 (LWP 17305)):
#0  0x7f35c7d9b67d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f35c0fab9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f35c0fabb0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f35c88c706b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f35c88709ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f35c869e0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3596025406 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f35c86a2da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f35c286f494 in start_thread (arg=0x7f3583fff700) at
pthread_create.c:333
#9  0x7f35c7da4acf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 (Thread 0x7f3595663700 (LWP 17302)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f35c86a3c6b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f35c869ce26 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f35c5d04a53 in KisTileDataSwapper::waitForWork (this=) at ./libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#4  0x7f35c5d04c8a in KisTileDataSwapper::run (this=0x7f35c620aea0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
./libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#5  0x7f35c86a2da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f35c286f494 in start_thread (arg=0x7f3595663700) at
pthread_create.c:333
#7  0x7f35c7da4acf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 4 (Thread 0x7f3595e64700 (LWP 17301)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f35c86a3c6b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f35c869cb33 in QSemaphore::acquire(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f35c5ce9dce in KisTileDataPooler::waitForWork (this=0x7f35c620ae60
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
./libs/image/tiles3/kis_tile_data_pooler.cc:165
#4  0x7f35c5cea6fa in KisTileDataPooler::run (this=0x7f35c620ae60
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
./libs/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x7f35c86a2da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f35c286f494 in start_thread (arg=0x7f3595e64700) at
pthread_create.c:333
#7  0x7f35c7da4acf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 3 (Thread 0x7f35aafec700 (LWP 17287)):
#0  0x7f35c0ff1104 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f35c0faafe0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f35c0fab91b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f35c0fabb0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f35c88c706b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f35c88709ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f35c869e0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f35c2a9a6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f35c86a2da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f35c286f494 in start_thread (arg=0x7f35aafec700) at
pthread_create.c:333
#10 0x7f35c7da4acf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 2 (Thread 0x7f35b667b700 (LWP 17286)):
#0  0x7f35c7d9b67d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f35c646b150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f35c646cee9 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f35b85a6b69 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f35c86a2da8 in ?? () 

[plasmashell] [Bug 385342] Segmentation fault when switching between look and feel themes

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 CC||andr...@stikonas.eu

--- Comment #3 from Marco Martin  ---
*** Bug 390092 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 390092] plasmashell crashes on boot

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||notm...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #8 from Marco Martin  ---


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

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

[plasmashell] [Bug 390105] Bug 380885 - browsing kmenu causing plasma panel crash

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

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

--- Comment #1 from Marco Martin  ---


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

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

[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 CC||forge...@freemail.hu

--- Comment #1 from Marco Martin  ---
*** Bug 390105 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 390105] Bug 380885 - browsing kmenu causing plasma panel crash

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

  Component|general |Application Menu (Kicker)
 CC||notm...@gmail.com
   Assignee|k...@davidedmundson.co.uk|h...@kde.org

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

[knipptasch] [Bug 392072] Aktualizacja do najnowszej wersji KMyMoney 5.0.1

[Mariusz Nowicki]

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

Mariusz Nowicki  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[knipptasch] [Bug 392072] New: Aktualizacja do najnowszej wersji KMyMoney 5.0.1

[Mariusz Nowicki]

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

Bug ID: 392072
   Summary: Aktualizacja do najnowszej wersji KMyMoney 5.0.1
   Product: knipptasch
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@hilefoks.org
  Reporter: mariusz-nowi...@tlen.pl
  Target Milestone: ---

Witam serdecznie.

Mam problem w aktualizacji programu KMyMoney 4.8.1 na 5.0.1.

Jak to zrobić?
Czy można gdzieś pobrać plik instalacyjny najnowszej wersji 5.0.1 na system
windows 10?

Pozdrawiam i przepraszam jeśli to nie ten dział.

Mariusz Nowicki

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

[plasmashell] [Bug 390144] crash in plasma after trying to add widgets

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE
 CC||notm...@gmail.com

--- Comment #2 from Marco Martin  ---
needs a backtrace of the crash with debug symbols installed

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

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

[Дилян Палаузов]

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

--- Comment #23 from Дилян Палаузов  ---
I just verified, that LLVM does not install gcc-ar and gcc-ranlib, but llvm-ar
and llvm-ranlib .

So to make LTO work with Clang, on systems where GCC is not installed, either
llvm-ar and llvm-ranlib shall be used, or ar and ranlib shall be used and it
must be assumed that the system is LTO-ready (the plugins are under
{libdir}/bfd-plugins/).

Concerning installing by default the plugins on the compiler's "make install"
on the location where binutils will look for them I filled
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934 and
https://bugs.llvm.org/show_bug.cgi?id=36802.

Shall I open for the assembler-review in coregrind/m_libcsetjmp.c a separate
ticket, or can it be kept here?

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

[plasmashell] [Bug 390186] Desktop crashes on adding widgets to panel

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #2 from Marco Martin  ---
pasted inline

Thread 1 (Thread 0x7fc839267800 (LWP 4082)):
[KCrash Handler]
#5  0x7fc83264d860 in raise () at /usr/lib/libc.so.6
#6  0x7fc83264eec9 in abort () at /usr/lib/libc.so.6
#7  0x7fc831608b80 in _fini () at /usr/lib/libwayland-client.so.0
#8  0x7fc831604b00 in wl_proxy_marshal_array_constructor_versioned () at
/usr/lib/libwayland-client.so.0
#9  0x7fc831604c5e in wl_proxy_marshal () at
/usr/lib/libwayland-client.so.0
#10 0x7fc837dd6c6d in  () at /usr/lib/libKF5WaylandClient.so.5
#11 0x7fc837dc1ec3 in KWayland::Client::Compositor::createRegion(QRegion
const&, QObject*) () at /usr/lib/libKF5WaylandClient.so.5
#12 0x7fc821a92350 in  () at
/usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#13 0x7fc838c53c47 in  () at /usr/lib/libKF5PlasmaQuick.so.5
#14 0x7fc838c549bc in  () at /usr/lib/libKF5PlasmaQuick.so.5
#15 0x7fc838c55043 in  () at /usr/lib/libKF5PlasmaQuick.so.5
#16 0x7fc838c56d1b in PlasmaQuick::Dialog::event(QEvent*) () at
/usr/lib/libKF5PlasmaQuick.so.5
#17 0x7fc833ff7ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#18 0x7fc833fff8a6 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#19 0x7fc832ff3850 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#20 0x7fc8337ef583 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() at /usr/lib/libQt5Gui.so.5
#21 0x7fc8337f01fe in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /usr/lib/libQt5Gui.so.5
#22 0x7fc8337c7bbc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#23 0x7fc8253eb40d in  () at /usr/lib/libQt5WaylandClient.so.5
#24 0x7fc832ff1e9b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#25 0x7fc832ffb188 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#26 0x56060fa8a743 in  ()
#27 0x7fc832639f4a in __libc_start_main () at /usr/lib/libc.so.6
#28 0x56060fa8aafa in _start ()

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

[colord-kde] [Bug 328248] colord-kde possibly assigns the profile to the wrong X atom when >1 monitor is connected

[bugzilla_noreply]

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

h...@gmx.de changed:

   What|Removed |Added

  Attachment #83836|0   |1
is obsolete||

--- Comment #4 from h...@gmx.de ---
Created attachment 111516
  --> https://bugs.kde.org/attachment.cgi?id=111516=edit
New patch

I have used a new patch for a while now. It uses a slightly different
enumeration of monitors and follows what Graeme Gill suggested on the Openicc
mailing list as an update of the specifications [0] and subsequent discussions
in different places.

[0] https://lists.freedesktop.org/archives/openicc/2016q4/005205.html

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

[systemsettings] [Bug 392050] Applications > Launch Feedback > Cursor: effect does not save when changed

[Scott Harvey]

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

--- Comment #7 from Scott Harvey  ---
Changes do take effect after logging out and back in. A simple restart of
plasmashell isn't sufficient.

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

[kdevelop] [Bug 365420] Usage of "Adapt signature" to rename argument in constructor inserts keyword "void" in its declaration

[Kevin Funk]

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

--- Comment #5 from Kevin Funk  ---
*** Bug 375277 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 375277] Some changes trigger unnecessary "update declaration" hint on constructor

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #5 from Kevin Funk  ---
Sounds sane to me. Marking as duplicate.

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

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

[trojita] [Bug 391667] Security bug

[Thomas Lübking]

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

--- Comment #4 from Thomas Lübking  ---
Jan.

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

[systemsettings] [Bug 391695] Workspace Theme/Desktop Theme KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||Qt 5.11
 Resolution|--- |UPSTREAM
URL||https://bugreports.qt.io/br
   ||owse/QTBUG-67007

--- Comment #5 from Nate Graham  ---
Fixed upstream in https://bugreports.qt.io/browse/QTBUG-67007

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

[plasma-pa] [Bug 391692] Multimedia/Audio Volume KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||Qt 5.11
URL||https://bugreports.qt.io/br
   ||owse/QTBUG-67007
 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Nate Graham  ---
Fixed upstream in https://bugreports.qt.io/browse/QTBUG-67007

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