[kdevelop] [Bug 393789] New: Crash Opening Session

[John Schneiderman]

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

Bug ID: 393789
   Summary: Crash Opening Session
   Product: kdevelop
   Version: 5.1.1
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: joh...@member.fsf.org
  Target Milestone: ---

Application: kdevelop (5.1.1)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.14.30-desktop-3.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
I have a plasmoid which opens the KDevelop sessions directly. This is how I
normally opening KDevelop. I clicked on the session this morning and it
crashed. Clicking it a second time, opened it without issue.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8452b67840 (LWP 19789))]

Thread 14 (Thread 0x7f840da56700 (LWP 20029)):
#0  0x7f8466019c4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f846c754dfb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f84617f02f7 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f84617f3fe8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f84617ef579 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f84617f1ddf in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f846c753ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f846601466d in start_thread () at /lib64/libpthread.so.0
#8  0x7f846c06ce0d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f840e257700 (LWP 20028)):
#0  0x7f8466019c4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f846c754dfb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f84617f02f7 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f84617f3fe8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f84617ef579 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f84617f1ddf in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f846c753ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f846601466d in start_thread () at /lib64/libpthread.so.0
#8  0x7f846c06ce0d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f840ea58700 (LWP 20027)):
#0  0x7f846c066f69 in syscall () at /lib64/libc.so.6
#1  0x7f846c74c400 in QBasicMutex::lockInternal() () at
/lib64/libQt5Core.so.5
#2  0x7f846c74c4fa in QMutex::lock() () at /lib64/libQt5Core.so.5
#3  0x7f8437114dd7 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /lib64/libKDevClangPrivate.so.27
#4  0x7f8437114bad in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /lib64/libKDevClangPrivate.so.27
#5  0x7f8437114bad in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /lib64/libKDevClangPrivate.so.27
#6  0x7f8437114bad in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /lib64/libKDevClangPrivate.so.27
#7  0x7f8437114bad in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /lib64/libKDevClangPrivate.so.27
#8  0x7f8437114bad in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /lib64/libKDevClangPrivate.so.27
#9  0x7f8437378ba1 in
ClangParseJob::run(QSharedPointer,

[kwin] [Bug 393788] New: Window rules editing broken

[Duncan]

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

Bug ID: 393788
   Summary: Window rules editing broken
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: 1i5t5.dun...@cox.net
  Target Milestone: ---

The window rules kcm GUI won't save changes.  It will load existing rules from
kwinrulesrc (as does kwin itself) and changes will appear to save -- hitting
the apply button causes it to go inactive, but:
1) kwin doesn't actually act on them (even after hitting apply).
2) switching to another kcm (say kwin scripts) and back to window rules, the
changes were not saved and I get the same rule as when I loaded it the first
time.
3) kwinrulesrc isn't actually changed (yes, it's appropriate 0600 perms).

Running gentoo/kde's live-git of frameworks and plasma as well.  Currently
running qt-5.11.0_beta4 as plasma-live-git is now requiring > 5.10, and gentoo
doesn't have 5.10 in-tree, only 5.11_beta4.  However, this bug triggered before
that upgrade.

This has apparently been broken in kwin on X at least for months, as when I
unmerged superkaramba (my last kde4 app, so I could unmerge kde4/qt4, still
nothing with superkaramba's full set of features for plasma5 that I can find,
but this bug isn't about that...) and setup ksysguard graphing to replace what
I could of superkaramba, I ended up having to manually edit kwinrulesrc in
ordered to get a working rule for ksysguard, and that was a couple months ago
or so.  I have a somewhat large but reasonably stable set of kwin window rules
and hadn't needed to edit any of them for some time before that, so I've no
idea how long it has actually been broken.

Fortunately, I can still edit the kwinrulesrc file manually and the changes do
take (after restarting kde/plasma, and I think after simply running kwin_x11
--replace, tho I'd have to check that again to be sure), but it'd sure be nice
to have a working GUI editor back again!

(The current trigger to file the bug was full-screening a game that changed the
resolution and left the desktop a mess.  I quit and restarted kde/plasma/X, and
got the desktop back, but firefox restarted at 0,15 which on my multi-monitor
setup is offscreen.  I tried to edit an existing window rule for it to
reposition it onscreen, but found the GUI editor still not saving changes, so
that didn't work.  Fortunately I have wmctrl installed, and a wmctrl -R firefox
did the trick!)

I suppose none of the devs have seen it due to running wayland these days.

(BTW, is plasma-wayland usable now, and can you point me at a good article
describing how to configure it analogous to xorg.conf.d?  Or is the only way to
configure plasma-wayland via the plasma-wayland GUI?  I haven't had much luck
with multi-monitor config GUIs such as kscreen on X/kde/plasma -- while they do
work sometimes, they're often broken bad enough to be unusable (leaving me with
a sufficiently broken desktop that I must restart X/kde/plasma, I had to
studiously avoid that kcm for awhile, as even opening it would screw things
up!), so I tend to avoid them, and while xrandr has at least worked more
consistently, simply configuring the layout in xorg.conf.d and not touching it
from the GUI has been most reliable.  So you can see why I'm hoping there's a
wayland analog to xorg.conf.d, despite my not seeing /anything/ about it in the
various Linux-related news feeds I follow.  So a link to a good article on the
topic would be extremely useful!)

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

[kwin] [Bug 393639] Mouse cursor flicker when passing window borders

[Martin Flöser]

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

--- Comment #18 from Martin Flöser  ---
Does it neither work for the panel nor for the deco issue? I would have assumed
it fixes for the panel and maybe for the deco.

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

[kwin] [Bug 393778] Kwin crashed on user login (fedora27)

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
Unfortunately the backtrace is lacking debug symbols. If you are able to
reproduce please install debug packages and attach a new backtrace.

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

[plasmashell] [Bug 393787] Icons only task manager gets confused between Native Steam app and Wine Steam

[Benjamin Xiao]

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

--- Comment #1 from Benjamin Xiao  ---
For reference this is Wine Steam's desktop file:

[Desktop Entry]
Name=Steam
Exec=env WINEPREFIX="/home/benxiao/.wine" wine
C:windowscommandstart.exe /Unix
/home/benxiao/.wine/dosdevices/c:/ProgramData/Microsoft/Windows/Start\\
Menu/Programs/Steam/Steam.lnk
Type=Application
StartupNotify=true
Path=/home/benxiao/.wine/dosdevices/c:/Program Files (x86)/Steam
Icon=10B4_steam.0
StartupWMClass=steam.exe

Here's the info from Window Rules for Wine Steam:
Class: Wine (steam.exe Wine)
Role:
Type: Normal Window
Title: Steam
Machine: 



Likewise here's native Steam's .desktop file:
[Desktop Entry]
Name=Steam
Comment=Application for managing and playing games on Steam
Exec=/usr/bin/steam %U
Icon=steam
Terminal=false
Type=Application
Categories=Network;FileTransfer;Game;
MimeType=x-scheme-handler/steam;
Actions=Store;Community;Library;Servers;Screenshots;News;Settings;BigPicture;Friends;

And native Steam's window info:
Class: Steam (Steam Steam)
Role:
Type: Unknown - will be treated as Normal Window
Title: Steam
Machine:


What I am a bit confused over is why native Steam would match with Wine Steam's
.desktop file when it specifies StartupWMClass=steam.exe?

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

[plasmashell] [Bug 393787] New: Icons only task manager gets confused between Native Steam app and Wine Steam

[Benjamin Xiao]

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

Bug ID: 393787
   Summary: Icons only task manager gets confused between Native
Steam app and Wine Steam
   Product: plasmashell
   Version: 5.12.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: ben.r.x...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

I have Steam installed natively on my Fedora 27 KDE system as well as Steam
installed via Wine. Both will create desktop shortcuts. However, now whenever I
launch native Steam, the icons only task manager thinks the application is Wine
Steam and will use the wrong icon.

This does not happen in GNOME or Unity.

I can work around this by setting StartupWMClass to Steam for the native Steam
.desktop file, but this gets overriden every time Steam updates.


Seems like there needs to be more logic to the mapping to be able to
differentiate the two apps.

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

[i18n] [Bug 393786] Typo in volume applet

[Simon Depiets]

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

Simon Depiets  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||sdepi...@gmail.com

--- Comment #1 from Simon Depiets  ---
Hello and thank you for the bug report.

This sentence is now fixed :

https://phabricator.kde.org/R883:1515011

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

[i18n] [Bug 393786] New: Typo in volume applet

[bugzilla_noreply]

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

Bug ID: 393786
   Summary: Typo in volume applet
   Product: i18n
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: fr
  Assignee: kde-francoph...@kde.org
  Reporter: grouchomarx...@gmail.com
CC: an...@kde.org
  Target Milestone: ---

Hello,
there is an extra " :" at the end of this line.

file: kde-workspace/plasma_applet_org.kde.plasma.volume.po

"Raise maximum volume"
"Augmenter le volume maximum :" -> "Augmenter le volume maximum"

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

[ktorrent] [Bug 393785] New: Everytime KTorrent is closing, it crash

[Paul Ladouceur]

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

Bug ID: 393785
   Summary: Everytime KTorrent is closing, it crash
   Product: ktorrent
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: tipaul2...@hotmail.com
  Target Milestone: ---

Application: ktorrent (5.1.0)

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

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

Torrent download finished, removed the torrent from the list, quit application
from the file menu OR the close button of the window.
Always reproduce, never got a clean close of KTorrent.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f67b0fe58c0 (LWP 1546))]

Thread 6 (Thread 0x7f67157fa700 (LWP 1766)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f67abe9367b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x23c1d40) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x2504930,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f67b08cfd13 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6
#4  0x7f67abe926eb in QThreadPrivate::start (arg=0x2504920) at
thread/qthread_unix.cpp:376
#5  0x7f67a6e5f6ba in start_thread (arg=0x7f67157fa700) at
pthread_create.c:333
#6  0x7f67ab28041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f67743c9700 (LWP 1630)):
#0  0x7f67ab27027d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f679e41cf61 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7f67a37ffa2e in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f67a38004a0 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f67a3800560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f67a380e7a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f679e44b078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#7  0x7f67a6e5f6ba in start_thread (arg=0x7f67743c9700) at
pthread_create.c:333
#8  0x7f67ab28041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f6792955700 (LWP 1603)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f677f68548b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#2  0x7f677f685397 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#3  0x7f67a6e5f6ba in start_thread (arg=0x7f6792955700) at
pthread_create.c:333
#4  0x7f67ab28041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f6792154700 (LWP 1570)):
#0  0x7fffc9d3ab6d in clock_gettime ()
#1  0x7f67ab28e876 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f6792153ae0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f67ac0c5ed1 in qt_clock_gettime (ts=0x7f6792153ae0, 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  0x7f67ac0c46c9 in QTimerInfoList::updateCurrentTime
(this=0x7f6788002ed0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f67ac0c6d25 in timerSourceCheckHelper (src=) at
kernel/qeventdispatcher_glib.cpp:146
#7  timerSourceCheck (source=) at
kernel/qeventdispatcher_glib.cpp:173
#8  0x7f67a5185dc1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f67a5186330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f67a518649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f67ac0c65cb in QEventDispatcherGlib::processEvents
(this=0x7f67880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7f67ac06d64a in QEventLoop::exec (this=this@entry=0x7f6792153d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#13 0x7f67abe8d554 in QThread::exec (this=) at
thread/qthread.cpp:522
#14 0x7f67abe926eb in QThreadPrivate::start (arg=0x19f51f0) at
thread/qthread_unix.cpp:376
#15 0x7f67a6e5f6ba in start_thread (arg=0x7f6792154700) at
pthread_create.c:333
#16 0x7f67ab28041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f6793b66700 (LWP 1558)):
#0  0x7fffc9d3ab6d in clock_gettime ()
#1  0x7f67ab28e876 in __GI___clock_gettime 

[konsole] [Bug 393644] Regression: Bi-Directional rendering doesn't work after this commit

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kon
   ||sole/bdd98f8561ec92098794e4
   ||11517f630c87a1dc02

--- Comment #6 from Kurt Hindenburg  ---
Git commit bdd98f8561ec92098794e411517f630c87a1dc02 by Kurt Hindenburg, on
behalf of Mariusz Glebocki.
Committed on 03/05/2018 at 00:46.
Pushed by hindenburg into branch 'master'.

Restore Bi-Directional text support

Summary:
Fix regression introduced by commit a565bc9 (Clip character drawing
to its own cell). When the first character in a text fragment is
classified as RTL, rest of the fragment is also considered to be RTL
and is passed to `drawText()` as one string. The rendering is not
perfect (especially when RTL and LTR characters are mixed), but it
works as before.

{F5830191}

Test Plan:
* Display example sentences using a program which prints text directly
  to terminal (e.g. `echo`, `cat`):
```
حروف به هم پیوسته

کِی‌دی‌ئی (به انگلیسی: KDE) پروژه‌ای برای توسعه یک
میزکار آزاد و متن باز است.
```
* Display the sentences in Konsole built before
  commit a565bc97337a3bfc3a027f46aa2dec3e9a6f8618
* Compare visually

Reviewers: #konsole, sassanh, hindenburg

Reviewed By: #konsole, sassanh, hindenburg

Subscribers: hindenburg, #konsole

Tags: #konsole

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

M  +28   -2src/TerminalDisplay.cpp

https://commits.kde.org/konsole/bdd98f8561ec92098794e411517f630c87a1dc02

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

[dolphin] [Bug 393784] New: Dolphin crashed when emptying trash

[Balthasar]

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

Bug ID: 393784
   Summary: Dolphin crashed when emptying trash
   Product: dolphin
   Version: 18.04.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: balthasar.b...@gmx.de
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (18.04.0)

Qt Version: 5.10.1
Frameworks Version: 5.45.0
Operating System: Linux 4.16.6-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
Archlinux, KDE 5.12.5

- What I was doing when the application crashed:
emptying the trash

- Custom settings of the application:
just changed a few seconds before, max age for files 14 days, no size limit
because baloo ate all my cpu and I thought it might be related to the trash. I
deleted my config folder (.config und .kde4) today because of the updates.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe6b8872800 (LWP 3480))]

Thread 10 (Thread 0x7fe653fff700 (LWP 3939)):
#0  0x7fe6b812df09 in syscall () at /usr/lib/libc.so.6
#1  0x7fe6aab1c411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fe683d6f707 in  () at /usr/lib/libgstreamer-1.0.so.0
#3  0x7fe6aaafe463 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe6aaafda2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fe6ad1660bc in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe6b81332ff in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fe674deb700 (LWP 3938)):
#0  0x7fe6b812df09 in syscall () at /usr/lib/libc.so.6
#1  0x7fe6aab1c411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fe683d6f707 in  () at /usr/lib/libgstreamer-1.0.so.0
#3  0x7fe6aaafe463 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe6aaafda2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fe6ad1660bc in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe6b81332ff in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fe676def700 (LWP 3936)):
#0  0x7fe6b812df09 in syscall () at /usr/lib/libc.so.6
#1  0x7fe6aab1c411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fe683d6f707 in  () at /usr/lib/libgstreamer-1.0.so.0
#3  0x7fe6aaafe463 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe6aaafda2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fe6ad1660bc in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe6b81332ff in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fe6777fe700 (LWP 3934)):
#0  0x7fe6b812df09 in syscall () at /usr/lib/libc.so.6
#1  0x7fe6aab1c411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fe6828afdec in  () at /usr/lib/libgstbase-1.0.so.0
#3  0x7fe6828b1198 in gst_data_queue_pop () at /usr/lib/libgstbase-1.0.so.0
#4  0x7fe67d7ee1d8 in  () at /usr/lib/gstreamer-1.0/libgstcoreelements.so
#5  0x7fe683d6f513 in  () at /usr/lib/libgstreamer-1.0.so.0
#6  0x7fe6aaafe463 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7fe6aaafda2a in  () at /usr/lib/libglib-2.0.so.0
#8  0x7fe6ad1660bc in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe6b81332ff in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fe67cf20700 (LWP 3933)):
#0  0x7fe6b812df09 in syscall () at /usr/lib/libc.so.6
#1  0x7fe6aab1c411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fe683d6f707 in  () at /usr/lib/libgstreamer-1.0.so.0
#3  0x7fe6aaafe463 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe6aaafda2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fe6ad1660bc in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe6b81332ff in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fe6755ec700 (LWP 3923)):
#0  0x7fe6b812df09 in syscall () at /usr/lib/libc.so.6
#1  0x7fe6aab1c411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fe683d6f707 in  () at /usr/lib/libgstreamer-1.0.so.0
#3  0x7fe6aaafe463 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe6aaafda2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fe6ad1660bc in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe6b81332ff in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fe6927e6700 (LWP 3484)):
#0  0x7fe6aaad44f9 in g_main_context_release () at
/usr/lib/libglib-2.0.so.0
#1  0x7fe6aaad54dd in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe6aaad563e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe6b2330254 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe6b22d231b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe6b20e171e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe6b20e6abd in  () at /usr/lib/libQt5Core.so.5
#7  

[kdevelop] [Bug 393779] Code parsing is totally broken

[Eugene Shalygin]

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

--- Comment #10 from Eugene Shalygin  
---
Correcting the path in the config file does not solve the problem. It might be
important that my clang is installed without libcxx.

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

[kmail2] [Bug 393783] New: Kmail crashes instead of starting

[bugzilla_noreply]

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

Bug ID: 393783
   Summary: Kmail crashes instead of starting
   Product: kmail2
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: paul.leopa...@iinet.net.au
  Target Milestone: ---

Application: kmail (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-20-generic x86_64
Distribution: Ubuntu 18.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Launched kmail via search in launcher. It did not display a window, just a
crash notification. Kubuntu 18.04 upgraded from Kubuntu 17.10. Could a
configuration item be interfering with startup?

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f01d0f71b80 (LWP 11482))]

Thread 9 (Thread 0x7f016ccdd700 (LWP 11497)):
#0  0x7f01c39619f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x559b85533580) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f01c39619f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x559b85533530, cond=0x559b85533558) at pthread_cond_wait.c:502
#2  0x7f01c39619f3 in __pthread_cond_wait (cond=0x559b85533558,
mutex=0x559b85533530) at pthread_cond_wait.c:655
#3  0x7f01ce77659b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f01ce76ec0b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f016dccb80c in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so
#6  0x7f01ce77516d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f01c395b6db in start_thread (arg=0x7f016ccdd700) at
pthread_create.c:463
#8  0x7f01ce06b88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f0184833700 (LWP 11489)):
#0  0x7f01c1d4bcd9 in g_mutex_lock () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f01c1d05805 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f01c1d0636b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f01c1d0654c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f01ce9ac90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f01ce9519ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f01ce77022a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f01ce77516d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f01c395b6db in start_thread (arg=0x7f0184833700) at
pthread_create.c:463
#9  0x7f01ce06b88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f0185034700 (LWP 11488)):
#0  0x7f01ce05a0b4 in __GI___libc_read (fd=14, buf=0x7f0185033810,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f01c1d4a960 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f01c1d05f27 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f01c1d063e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f01c1d0654c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f01ce9ac90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f01ce9519ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f01ce77022a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f01ce77516d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f01c395b6db in start_thread (arg=0x7f0185034700) at
pthread_create.c:463
#10 0x7f01ce06b88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f0185ed3700 (LWP 11487)):
#0  0x7f01ce05ebf9 in __GI___poll (fds=0x7f017c004a10, nfds=1,
timeout=9576) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f01c1d06439 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f01c1d0654c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f01ce9ac90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f01ce9519ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f01ce77022a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f01ce77516d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f01c395b6db in start_thread (arg=0x7f0185ed3700) at
pthread_create.c:463
#8  

[kdeconnect] [Bug 387532] Conflicting device IDs cause paired devices to become unpaired

[Damodara Dec Calvin]

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

Damodara Dec Calvin  changed:

   What|Removed |Added

 CC||calvinsupo...@gmail.com

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

[plasmashell] [Bug 393782] New: Changing system tray entry visibility to shown crash

[bugzilla_noreply]

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

Bug ID: 393782
   Summary: Changing system tray entry visibility to shown crash
   Product: plasmashell
   Version: 5.12.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: crazylego...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.4)

Qt Version: 5.10.1
Frameworks Version: 5.45.0
Operating System: Linux 4.16.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I changed the visibility of the seafile entry to "shown" instead of "auto"

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

Thread 25 (Thread 0x7f4b3e7fc700 (LWP 17887)):
#0  0x7f4c6003007c in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4c60e75f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4b91c7552f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4b91c79719 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f4b91c79772 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f4b91c77583 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4c60e74abd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4c6002a0bc in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4c6077a2ff in clone () at /usr/lib/libc.so.6

Thread 24 (Thread 0x7f4b3effd700 (LWP 17886)):
#0  0x7f4c6003007c in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4c60e75f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4b91c7552f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4b91c79719 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f4b91c79772 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f4b91c77583 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4c60e74abd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4c6002a0bc in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4c6077a2ff in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7f4b3f7fe700 (LWP 17885)):
#0  0x7f4c6003007c in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4c60e75f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4b91c7552f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4b91c79719 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f4b91c79772 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f4b91c77583 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4c60e74abd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4c6002a0bc in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4c6077a2ff in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7f4b3700 (LWP 17884)):
#0  0x7f4c6003007c in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4c60e75f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4b91c7552f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4b91c79719 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4b91c746fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f4b91c79772 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4b91c746fd in

[kdevelop] [Bug 393779] Code parsing is totally broken

[Eugene Shalygin]

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

--- Comment #9 from Eugene Shalygin  ---
Gentoo packages allow parallel installation of several major LLVM/CLang
version, ad each one can be 64 bit or 32, or both in parallel. 

Why don't you parse clang++ -v output to get the list of default include
directories?

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

[krita] [Bug 393302] Not saved layer-mask animation

[bugzilla_noreply]

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

ofteek...@dayrep.com changed:

   What|Removed |Added

 CC||ofteek...@dayrep.com

--- Comment #2 from ofteek...@dayrep.com ---
I also can confirm the bug.

Just ran into the same issue on Ubuntu 16.4 with Latest Krita Nightly Build #78
(https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/78/)

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

[kwin] [Bug 393639] Mouse cursor flicker when passing window borders

[Piotr Kloc]

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

--- Comment #17 from Piotr Kloc  ---
Patched both 5.12.5 and master. No changes unfortunately. I will switch my
desktop to nouveau to see if it's also affected.

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Sven Brauch]

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

--- Comment #8 from Sven Brauch  ---
Hm. On my system,

> llvm-config --includedir
/usr/include

and

> llvm-config --libdir
/usr/lib

Both is definitely not what we want to put here. I don't know why this returns
a path of a completely different kind on your system.

Specifically, for you, --libdir includes an extra "llvm/6/lib64" suffix, which
seems just ... different from what the utility gives here. I don't see how one
would compute the correct path such that it works for both outputs. Hm.

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Eugene Shalygin]

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

--- Comment #7 from Eugene Shalygin  ---
CLANG_LIBRARY_DIRS is "/usr/lib64/llvm/6/lib64" and this path is correct, as I
wrote above; the path is the same as returned by llvm-config --libdir.

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

[Breeze] [Bug 393318] Request: better, more universal "sort options" icon

[Nate Graham]

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

--- Comment #6 from Nate Graham  ---
Another idea: https://image.flaticon.com/icons/png/512/644/644070.png
I'll leave it to icon folks now.

We'd really like to get this in for Frameworks 5.47, as it's required for us to
land https://phabricator.kde.org/D12337

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Sven Brauch]

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

--- Comment #6 from Sven Brauch  ---
What is the output of llvm-config --libdir? That is what is used by cmake to
find this directory as far as I can see.

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Sven Brauch]

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

--- Comment #5 from Sven Brauch  ---
... CLANG_LIBRARY_DIRS this was meant to read, of course

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #4 from Sven Brauch  ---
It almost looks a bit like there are two directories in CMAKE_LIBRARY_DIRS in
cmake and they are concatenated ...?

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

[plasmashell] [Bug 393781] New: wallpaper cannot span multiple screens

[Chris Cheney]

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

Bug ID: 393781
   Summary: wallpaper cannot span multiple screens
   Product: plasmashell
   Version: master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: chris.che...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Most other DE's and even just regular WM's when used with feh can use a single
large wallpaper spanning multiple screens, eg 5760x1080 for triple head. KDE 5
however can not do this and it also blocks feh from working as well. This used
to work with KDE 3 and earlier but appears to have broken since then with the
rewrite.

I wasn't sure which component was the better fit, Image Wallpaper or
Multi-screen support so put it under Image Wallpaper since that is likely where
it needs to be fixed.

https://feh.finalrewind.org/

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

[kmail2] [Bug 387876] Check mail stops working, must restart akonadi to fix

[Raúl]

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

Raúl  changed:

   What|Removed |Added

 CC||rasas...@gmail.com

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

[kmail2] [Bug 380979] Kmail hangs on "Retrieving folder content"

[Raúl]

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

Raúl  changed:

   What|Removed |Added

 CC||rasas...@gmail.com

--- Comment #1 from Raúl  ---
Looking into similar issues, I came accross #377877. Could this be a duplicate
of #377877?

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

[kmail2] [Bug 377877] kmail stuck with retrieving folders 0%

[Raúl]

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

Raúl  changed:

   What|Removed |Added

 CC||rasas...@gmail.com

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

[k3b] [Bug 390081] Icons look pixelated when I increase display scale

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/k3b
   ||/683aee875d173c3183252e2b00
   ||2648239bc3193a

--- Comment #5 from Henrik Fehlauer  ---
Git commit 683aee875d173c3183252e2b002648239bc3193a by Henrik Fehlauer, on
behalf of Andrew Crouthamel.
Committed on 02/05/2018 at 21:10.
Pushed by rkflx into branch 'Applications/18.04'.

Fix pixmap scaling on HiDPI screens

Summary:
This fixes the pixelation seen when using display scaling on HiDPI screens.
This fixes the main screen as well as the settings and other areas.

Before:
{F5765495}

After:
{F5765496}

Test Plan: Browse file structure in project, open settings and change values,
ensuring functionality.

Reviewers: aacid, lesliezhai, rkflx

Reviewed By: rkflx

Subscribers: rkflx, ngraham

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

M  +2-0src/main.cpp

https://commits.kde.org/k3b/683aee875d173c3183252e2b002648239bc3193a

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

[Powerdevil] [Bug 345618] Powerdevil crash from idle desktop.

[Dennis Schridde]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Eugene Shalygin]

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

--- Comment #3 from Eugene Shalygin  ---
And the last piece:
$ clang++ -c file.cc -v
clang version 6.0.0 (tags/RELEASE_600/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/6/bin
Selected GCC installation: /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64
 "/usr/lib64/llvm/6/bin/clang-6.0" -cc1 -triple x86_64-pc-linux-gnu -emit-obj
-mrelax-all -disable-free -disable-llvm-verifier -discard-value-names
-main-file-name file.cc -mrelocation-model static -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info
-debugger-tuning=gdb -v -coverage-notes-file /tmp/file.gcno -resource-dir
/usr/lib64/llvm/6/bin/../../../../lib/clang/6.0.0 -internal-isystem
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7 -internal-isystem
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/x86_64-pc-linux-gnu
-internal-isystem
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/backward
-internal-isystem /usr/local/include -internal-isystem
/usr/lib64/llvm/6/bin/../../../../lib/clang/6.0.0/include
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-fdeprecated-macro -fdebug-compilation-dir /tmp -ferror-limit 19
-fmessage-length 171 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -fcolor-diagnostics -o file.o -x c++ file.cc
clang -cc1 version 6.0.0 based upon LLVM 6.0.0 default target
x86_64-pc-linux-gnu
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/x86_64-pc-linux-gnu
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/backward
 /usr/lib64/llvm/6/bin/../../../../lib/clang/6.0.0/include
 /usr/include
End of search list.

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Eugene Shalygin]

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

--- Comment #2 from Eugene Shalygin  ---
And yes, /usr/lib64/llvm/6/lib64 is the correct path for the clang libraries

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

[kdevelop] [Bug 393779] Code parsing is totally broken

[Eugene Shalygin]

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

--- Comment #1 from Eugene Shalygin  ---
#define KDEV_CLANG_BUILTIN_DIR "/usr/lib64/llvm/6/lib64/clang/6.0.0/include" in
the generated file; the path is wrong. FYI, 
$ llvm-config --includedir
/usr/lib64/llvm/6/include

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

[kdeconnect] [Bug 364571] Can't mount android filesystem on Dolphin

[bugzilla_noreply]

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

mathwiz2...@gmail.com changed:

   What|Removed |Added

  Component|plasmoid|common

--- Comment #5 from mathwiz2...@gmail.com ---
Same problem here, trying to browse remote device returns error, screenshot
posted as attachment. Running plasma on arch. Phone is a samsung note 5.

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

[kdeconnect] [Bug 364571] Can't mount android filesystem on Dolphin

[bugzilla_noreply]

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

mathwiz2...@gmail.com changed:

   What|Removed |Added

 CC||mathwiz2...@gmail.com

--- Comment #4 from mathwiz2...@gmail.com ---
Created attachment 112381
  --> https://bugs.kde.org/attachment.cgi?id=112381=edit
Screenshot of error

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

[kstars] [Bug 393780] New: Execute session is showing the wrong object in kstars

[Sebastien]

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

Bug ID: 393780
   Summary: Execute session is showing the wrong object in kstars
   Product: kstars
   Version: 2.9.5
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: sebastien.lecler...@gmail.com
  Target Milestone: ---

Created attachment 112380
  --> https://bugs.kde.org/attachment.cgi?id=112380=edit
Screenshot of the bug

Create a list of objects (3 in my case). Then, execute the session and click on
step 2 to see the list of objects.

Click on the first one. Kstars is centering on the next item in the list.

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

[okular] [Bug 333844] (wish) configurable default for printing

[Michael Weghorn]

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

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #3 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #2)
> 
> The actual problem is not in Okular but in the underlying Qt library.
> There is currently quite some work with regard to the print dialog going on
> in Qt and this problem will most probably be fixed very soon. The user
> default value for the printer should be preselected then (which in my
> opinion is the most reasonable way to deal with this, since it works across
> applications and allows a per printer default).

This is now implemented in Qt's development version (which will become Qt
5.12), s. https://codereview.qt-project.org/#/c/226881/

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

[kdelibs] [Bug 198795] printer settings in KDE not consistent with CUPS settings

[Michael Weghorn]

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

Michael Weghorn  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #7 from Michael Weghorn  ---
The Qt print dialog has been improved and options are now properly initialized
with their default values. Most of this work will already be contained in Qt
version 5.11, but some of it will only be in Qt 5.12.

(Options are still reset to their default values when a print job has been
done, but this does not seem to be the main focus of this bug and I'd rather
recommend opening an issue in Qt's upstream issue tracker in case a different
behaviour is wanted.)

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

[kdevelop] [Bug 393779] New: Code parsing is totally broken

[Eugene Shalygin]

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

Bug ID: 393779
   Summary: Code parsing is totally broken
   Product: kdevelop
   Version: git master
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: eugene.shalygin+bugzilla@gmail.com
  Target Milestone: ---

KDevelop shows an error on each identifier in each project. Hint says that
identifier is not found in the std:: namespace. Reverting   
c791359763cd862f93ad9f91fa628d20e1e630f2 helps.

$ locate varargs.h | grep lib64
/usr/lib64/clang/6.0.0/include/varargs.h
/usr/lib64/gcc/x86_64-pc-linux-gnu/7.3.0/include/varargs.h

Will be happy to provide any further information.

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

[digikam] [Bug 393728] Reread metadata from Video uses sidecar only

[Maik Qualmann]

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

--- Comment #4 from Maik Qualmann  ---
(In reply to meku from comment #2)
> It seems if "Read from sidecar" is enabled then the Metadata viewer still
> does not show certain metadata such as dimensions or GPS, even when this is
> in the sidecar.

GPS information from the sidecar are only available in the XMP tab from
metadata viewer. I think we can now close the bug, it is now possible to
re-scan the files and keep the old information in the database.

Maik

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

[digikam] [Bug 393777] Item Tool Tips are unreadable in Windows 10 (white on yellow)

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #2 from Maik Qualmann  ---


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

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

[digikam] [Bug 391521] "Tool-tip" box difficult to read due to default color scheme

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||l5dewswo...@temp.mailbox.or
   ||g

--- Comment #7 from Maik Qualmann  ---
*** Bug 393777 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 393728] Reread metadata from Video uses sidecar only

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
Git commit a45a706a0f9b97c2ad1a57c93bf2a0d3d54bd7bc by Maik Qualmann.
Committed on 02/05/2018 at 18:57.
Pushed by mqualmann into branch 'master'.

add delete the metadata from the database as option in the setup

M  +0-15   core/libs/database/coredb/coredb.cpp
M  +2-1core/libs/database/item/imagescanner.cpp
M  +3-0core/libs/dmetadata/metadatasettingscontainer.cpp
M  +1-0core/libs/dmetadata/metadatasettingscontainer.h
M  +78   -42   core/utilities/setup/metadata/setupmetadata.cpp
M  +1-0core/utilities/setup/metadata/setupmetadata.h

https://commits.kde.org/digikam/a45a706a0f9b97c2ad1a57c93bf2a0d3d54bd7bc

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

[kwin] [Bug 392754] After I wake up a touch screen via double tap, its power management stops working until some input device is used

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Flags||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D12668

--- Comment #1 from Martin Flöser  ---
Possible patch at https://phabricator.kde.org/D12668

Any chance to test? The issue and the fix look straight forward to me.

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

[kwin] [Bug 392754] After I wake up a touch screen via double tap, its power management stops working until some input device is used

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Component|input   |platform-drm

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

[digikam] [Bug 393777] Item Tool Tips are unreadable in Windows 10 (white on yellow)

[bugzilla_noreply]

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

--- Comment #1 from l5dewswo...@temp.mailbox.org ---
Just noticed that tooltips are best readable in "Color Contrast" design.
Standard is what the screenshots are showing. High Key is worse, Low Key is
better readable. In all of the other designs except these three, tooltips are
almost unreadable.

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

[kwin] [Bug 393778] New: Kwin crashed on user login (fedora27)

[Brajmohan]

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

Bug ID: 393778
   Summary: Kwin crashed on user login (fedora27)
   Product: kwin
   Version: 5.12.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kumar.brajmo...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.12.4)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.16.5-200.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
- What I was doing when the application crashed:
kwin crashed when I was logging-into my system. It is a Fedora 27(64bit)
machine on intel i5/8th gen Lenovo laptop.
Tried to restart kwin, but no success.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdd4a8e7940 (LWP 3476))]

Thread 3 (Thread 0x7fdd264d6700 (LWP 3588)):
#0  0x7fdd3f3f5d66 in ppoll () from /lib64/libc.so.6
#1  0x7fdd40247ec5 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#2  0x7fdd4024916d in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fdd401f996a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fdd4004a8ca in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fdd45820449 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#6  0x7fdd4004ede2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fdd42c3950b in start_thread () from /lib64/libpthread.so.0
#8  0x7fdd3f40016f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fdd2872c700 (LWP 3576)):
#0  0x7fdd3f3f5c6b in poll () from /lib64/libc.so.6
#1  0x7fdd4213afe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fdd4213cdda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fdd29409bf9 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7fdd4004ede2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fdd42c3950b in start_thread () from /lib64/libpthread.so.0
#6  0x7fdd3f40016f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fdd4a8e7940 (LWP 3476)):
[KCrash Handler]
#6  0x7fdd4a12bffc in KWin::Atoms::Atoms() () from /lib64/libkwin.so.5
#7  0x7fdd4a135526 in KWin::Application::createAtoms() () from
/lib64/libkwin.so.5
#8  0x7fdd4a52db6d in KWin::ApplicationX11::performStartup() () from
/lib64/libkdeinit5_kwin_x11.so
#9  0x7fdd4a135aa8 in KWin::Application::start() () from
/lib64/libkwin.so.5
#10 0x7fdd4a52e16e in kdemain () from /lib64/libkdeinit5_kwin_x11.so
#11 0x7fdd3f32bf2a in __libc_start_main () from /lib64/libc.so.6
#12 0x56106301fc1a in _start ()

Reported using DrKonqi

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

[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland

[Urs Wolfer]

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

--- Comment #9 from Urs Wolfer  ---
> Do you work on KRDC on Wayland support?

No, I do not work on it. I'm happy to review such a change though. Feel free to
create one and push it to reviewboard: https://git.reviewboard.kde.org/r/

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

[digikam] [Bug 393777] Item Tool Tips are unreadable in Windows 10 (white on yellow)

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Usability-Themes
 CC||caulier.gil...@gmail.com

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

[Phonon] [Bug 393772] cartella su disco locale scsi

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|digikam-bugs-n...@kde.org   |sit...@kde.org
  Component|general |general
Product|digikam |Phonon
Version|5.9.0   |unspecified
 CC||caulier.gil...@gmail.com,
   ||myr...@kde.org,
   ||romain.per...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
It crash in Phonon, not digiKam, while desktop sound notification.

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

[digikam] [Bug 393777] Item Tool Tips are unreadable in Windows 10 (white on yellow)

[bugzilla_noreply]

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

l5dewswo...@temp.mailbox.org changed:

   What|Removed |Added

Version|unspecified |5.9.0

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

[digikam] [Bug 393777] New: Item Tool Tips are unreadable in Windows 10 (white on yellow)

[bugzilla_noreply]

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

Bug ID: 393777
   Summary: Item Tool Tips are unreadable in Windows 10 (white on
yellow)
   Product: digikam
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: l5dewswo...@temp.mailbox.org
  Target Milestone: ---

Created attachment 112379
  --> https://bugs.kde.org/attachment.cgi?id=112379=edit
White text on yellow background for files as well as for albums

Tool Tips are unreadable - see screenshots (white text on yellow background for
files as well as for albums. Changing the icon theme does not seem to help.

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

[kwin] [Bug 382698] wayland windows react wrongly to middle/right clicks on maximise button

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

Summary|xwayland windows react  |wayland windows react
   |wrongly to middle/right |wrongly to middle/right
   |clicks on maximise button   |clicks on maximise button

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

[okular] [Bug 306818] Okular cannot close instructions overlay in PDF

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[okular] [Bug 307304] Javascript in forms not working correctly

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[krusader] [Bug 393766] "Open terminal here" action opens shell in home directory

[Toni Asensi Esteve]

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

Toni Asensi Esteve  changed:

   What|Removed |Added

 CC||toni.ase...@kdemail.net

--- Comment #1 from Toni Asensi Esteve  ---
Hi, Kornel:

I've tried it using the latest git version of Krusader, with a clean profile,
under Kubuntu 18.04, and I didn't see the problem. 

Can you use the latest git version of Krusader? The "compile Krusader from
source" instructions can be seen in:
https://commits.kde.org/krusader?path=INSTALL

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

[Discover] [Bug 393776] left bar disappears when I click in "Updates".

[bugzilla_noreply]

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

paninomaninod...@gmail.com changed:

   What|Removed |Added

Summary|left bar dissapears |left bar disappears when I
   ||click in "Updates".

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

[Discover] [Bug 393776] New: left bar dissapears

[bugzilla_noreply]

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

Bug ID: 393776
   Summary: left bar dissapears
   Product: Discover
   Version: 5.12.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: paninomaninod...@gmail.com
  Target Milestone: ---

Sometimes I open Discover to search and install updates.
Discover opens, I can see in the left bar at the bottom the program searching
for updates and when I click there the whole bar disappears.
I thought that this bug could be prevented if I clicked after it finished
searching for updates or when I was doing nothing, but it also happened in
those instances.

Sometimes I click um "Atualizar" (Updates, or check for updates) and that whole
side of the program contracts and disappears.

I'll add an image if this happens again.

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

[kstars] [Bug 393775] New: Problem connecting Maxdome II since KSatrs v. 2.9.4

[Jean-Claude]

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

Bug ID: 393775
   Summary: Problem connecting Maxdome II since KSatrs v. 2.9.4
   Product: kstars
   Version: 2.9.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: jcjes...@free.fr
  Target Milestone: ---

Created attachment 112378
  --> https://bugs.kde.org/attachment.cgi?id=112378=edit
Maxdome II not recognized

I spent a long time trying to find out why it was impossible to connect my
Maxdome II observatory to KSatrs v. 2.9.5.
Finally I tested older versions of KStars I had saved.
I found the same difficulties with KStars v. 2.9.4 as with KSatrs v. 2.9.5.
However there was no problem with KStars v. 2.9.3 !
See attached log

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

[plasmashell] [Bug 393774] New: Unable to group by program without popup option

[Brian Cohen]

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

Bug ID: 393774
   Summary: Unable to group by program without popup option
   Product: plasmashell
   Version: 5.12.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: br...@intercarve.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

What I did: Right-clicked on the Task Manager, click Task Manager Settings,
under Grouping and Sorting choose Grouping "By Program Name". Leave "Open
Groups in Popups" unchecked. Click 'Apply'.

What I expected to happen: I would expect the windows to be grouped by program
(eg. all my Atom windows appear as one item in the Task Manager) and clicking
on that item would raise just one window of the group.

What actually happens: The windows do not group at all. They only group if I
check "Open Groups in Popups". This is not desirable behavior because I do not
like interacting with the popup menu of windows.


Additional info: in addition to making grouping function in the case that 'Open
Groups in Popups" is unchecked, it would be ideal if Task Manager had an option
here that would make it so that upon clicking a group, the most recently used
window in that group would be raised.  See:
https://bugs.kde.org/show_bug.cgi?id=390400).

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

[plasmashell] [Bug 379259] Add option to activate last window in grouped icon task

[Brian Cohen]

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

Brian Cohen  changed:

   What|Removed |Added

 CC||br...@intercarve.net

--- Comment #3 from Brian Cohen  ---
I would also like to see this behavior made an option in both Task Manager and
Icons-Only Task Manager.

Before I switched to KDE, I was using the default 'Ubuntu' desktop in Ubuntu
17.10 and higher, which includes Canonical's fork of the GNOME dash-to-dock
plugin. That plugin can be configured to implement the behavior described by
this bug.  As this bug notes, by default Unity behaves this way.

As a consultant programmer, I usually have between 5 and 8 separate Atom
windows open because I switch projects throughout the day. But, I only work on
one project at a time. So if I want to switch quickly between my code (Atom)
and my browser (Chrome), my expectation is that when I raise Atom, I'm raising
the most recently used window.  I'm able to achieve this in the Task Switcher
(System Settings > Task Switcher > Main > Content > Sort Order: Recently Used,
[X] Only one window per application. So it would be great if I could achieve
the same behavior by interacting with Task Manager with my mouse.

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

[ksysguard] [Bug 304145] Ridiculously high peaks in CPU usage graph

[Ville Aakko]

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

Ville Aakko  changed:

   What|Removed |Added

 CC||ville.aa...@gmail.com

--- Comment #10 from Ville Aakko  ---
Created attachment 112377
  --> https://bugs.kde.org/attachment.cgi?id=112377=edit
Another example of erroneously high CPU usage spikes

Hi,

This is still an issue on KSysguard 5.12.5 (Arch, Plasma 5.12).

Just a guess, but maybe this is related to Bug #238331 ? Including I/O wait
time might confuse the computing somemtimes? I tried a few quick test by making
my hard disks sleep and then making some file system operations to wake them
up, but that didn't reproduce this. So maybe this hypothesis is just a red
herring, unless someone knows otherwise just ignore it :-). 

All I know this still happends but I have no idea how to reproduce at will
(which would make it easier to debug this).

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

[Falkon] [Bug 392805] Loading an URL from another application does not raise Falkon window to the top

[Achim Bohnet]

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

--- Comment #6 from Achim Bohnet  ---
Houston? We have a problem!  :-)

I think the user does not know or care about focus steeling and X11/wayland.
The user has a problem if she/he clicks in an app on a http URL and it looks
like
nothing happens (just because falkon is hidden by other windows).  User
compares it to PDFs that pop up a window all the time.  (User does not know
that everytime a new okular instance is startet.)

Problem is that a uniq app acts in unexpected ways, compared to a single
document app. 

Question is: where can one report this 'usability' bug?

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

[Falkon] [Bug 392805] Loading an URL from another application does not raise Falkon window to the top

[David Rosca]

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

--- Comment #7 from David Rosca  ---
> it looks like nothing happens
It's not like "nothing happens", you get the Falkon icon higlighted in task
manager.

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

[kde] [Bug 393773] New: showfoto crashes when geotagging

[Richard Lucking]

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

Bug ID: 393773
   Summary: showfoto crashes when geotagging
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: kdeb...@lucking.org
  Target Milestone: ---

Application: showfoto (5.9.0)

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.4.126-48-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
attempting to "geotag" a jpeg. Every time, either clicking on the little
"globe" icon, or pressing ctrl-shift-g and it crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Showfoto (showfoto), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0759de7a00 (LWP 12715))]

Thread 13 (Thread 0x7f06f9016700 (LWP 12736)):
#0  0x7f074ad198b4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f074acd7950 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f074acd8230 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f074acd842c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f0756585fbb in QEventDispatcherGlib::processEvents
(this=0x7f06d40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f0756531a4b in QEventLoop::exec (this=this@entry=0x7f06f9015bc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f075636f14a in QThread::exec (this=) at
thread/qthread.cpp:522
#7  0x7f0756373e0f in QThreadPrivate::start (arg=0x1b952b0) at
thread/qthread_unix.cpp:376
#8  0x7f0755514724 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0755a62e8d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f06f981f700 (LWP 12735)):
#0  0x7f07555190ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0756374e8b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x19cd290) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, readWriteLock=0x194aa38,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239
#3  0x7f075181744b in QtAV::BlockingQueue::take() ()
from /usr/lib64/libQtAV.so.1
#4  0x7f07518870cb in QtAV::ExtractThread::run() () from
/usr/lib64/libQtAV.so.1
#5  0x7f0756373e0f in QThreadPrivate::start (arg=0x194aa00) at
thread/qthread_unix.cpp:376
#6  0x7f0755514724 in start_thread () from /lib64/libpthread.so.0
#7  0x7f0755a62e8d in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f06fa0b5700 (LWP 12729)):
#0  0x7f07555194a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0756374bc8 in QWaitConditionPrivate::wait_relative (time=3,
this=0x193b5f0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x193b5f0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x1929610,
mutex=mutex@entry=0x136d010, time=3) at thread/qwaitcondition_unix.cpp:215
#4  0x7f07563713ae in QThreadPoolThread::run (this=0x1929600) at
thread/qthreadpool.cpp:146
#5  0x7f0756373e0f in QThreadPrivate::start (arg=0x1929600) at
thread/qthread_unix.cpp:376
#6  0x7f0755514724 in start_thread () from /lib64/libpthread.so.0
#7  0x7f0755a62e8d in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f06fa8b6700 (LWP 12728)):
#0  0x7f07555194a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0756374bc8 in QWaitConditionPrivate::wait_relative (time=3,
this=0x1939bd0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x1939bd0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x1929050,
mutex=mutex@entry=0x136d010, time=3) at thread/qwaitcondition_unix.cpp:215
#4  0x7f07563713ae in QThreadPoolThread::run (this=0x1929040) at
thread/qthreadpool.cpp:146
#5  0x7f0756373e0f in QThreadPrivate::start (arg=0x1929040) at
thread/qthread_unix.cpp:376
#6  0x7f0755514724 in start_thread () from /lib64/libpthread.so.0
#7  0x7f0755a62e8d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f06fb7fe700 (LWP 12725)):
#0  0x7f07555190ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0756374e8b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x11a9240) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, readWriteLock=0x11aad38,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239
#3  0x7f075181744b in QtAV::BlockingQueue::take() ()
from /usr/lib64/libQtAV.so.1
#4  0x7f07518870cb in QtAV::ExtractThread::run() () from

[elisa] [Bug 393486] Elisa not picking covers for songs

[Matthieu Gallien]

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

--- Comment #1 from Matthieu Gallien  ---
Could you please test with the latest version ? For example, you can easily get
it from the flatpak KDE repository.

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

[kwin] [Bug 382698] xwayland windows react wrongly to middle/right clicks on maximise button

[Martin Flöser]

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

--- Comment #4 from Martin Flöser  ---
The thing is: Wayland doesn't have a horizontal/vertical maximize mode.

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

[digikam] [Bug 393772] New: cartella su disco locale scsi

[umberto valentinotti]

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

Bug ID: 393772
   Summary: cartella su disco locale scsi
   Product: digikam
   Version: 5.9.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: umv...@gmail.com
  Target Milestone: ---

Application: digikam (5.9.0)

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.4.126-48-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
ricaricaricare cartella su disco locale, con solo parziaole visualizzazione

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8a7abbaa00 (LWP 17521))]

Thread 43 (Thread 0x7f895e121700 (LWP 13086)):
#0  0x7f8a729b90ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8a76d04e8b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x228c5e0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, readWriteLock=0x2bc7fa8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239
#3  0x7f8a6ed0e44b in QtAV::BlockingQueue::take() ()
from /usr/lib64/libQtAV.so.1
#4  0x7f8a6ed7e0cb in QtAV::ExtractThread::run() () from
/usr/lib64/libQtAV.so.1
#5  0x7f8a76d03e0f in QThreadPrivate::start (arg=0x2bc7f70) at
thread/qthread_unix.cpp:376
#6  0x7f8a729b4724 in start_thread () from /lib64/libpthread.so.0
#7  0x7f8a76013e8d in clone () from /lib64/libc.so.6

Thread 42 (Thread 0x7f8998f7d700 (LWP 17786)):
#0  0x7f8a729b90ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8a76d04c7b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2280f00) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x2280ed0,
mutex=mutex@entry=0x2280ec8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f8a79356fde in Digikam::VideoThumbnailerJob::run (this=0x2280a80) at
/usr/src/debug/digikam-5.9.0/core/libs/threadimageio/videothumbnailerjob.cpp:165
#4  0x7f8a76d03e0f in QThreadPrivate::start (arg=0x2280a80) at
thread/qthread_unix.cpp:376
#5  0x7f8a729b4724 in start_thread () from /lib64/libpthread.so.0
#6  0x7f8a76013e8d in clone () from /lib64/libc.so.6

Thread 41 (Thread 0x7f88b47f8700 (LWP 17626)):
#0  0x7f8a729b90ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8a76d04e8b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x62bb6b0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, readWriteLock=0x62bb238,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239
#3  0x7f8a6ed0e44b in QtAV::BlockingQueue::take() ()
from /usr/lib64/libQtAV.so.1
#4  0x7f8a6ed7e0cb in QtAV::ExtractThread::run() () from
/usr/lib64/libQtAV.so.1
#5  0x7f8a76d03e0f in QThreadPrivate::start (arg=0x62bb200) at
thread/qthread_unix.cpp:376
#6  0x7f8a729b4724 in start_thread () from /lib64/libpthread.so.0
#7  0x7f8a76013e8d in clone () from /lib64/libc.so.6

Thread 40 (Thread 0x7f88b4ff9700 (LWP 17625)):
#0  0x7f8a729b90ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8a76d04e8b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x611aea0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, readWriteLock=0x6152eb8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239
#3  0x7f8a6ed0e44b in QtAV::BlockingQueue::take() ()
from /usr/lib64/libQtAV.so.1
#4  0x7f8a6ed7e0cb in QtAV::ExtractThread::run() () from
/usr/lib64/libQtAV.so.1
#5  0x7f8a76d03e0f in QThreadPrivate::start (arg=0x6152e80) at
thread/qthread_unix.cpp:376
#6  0x7f8a729b4724 in start_thread () from /lib64/libpthread.so.0
#7  0x7f8a76013e8d in clone () from /lib64/libc.so.6

Thread 39 (Thread 0x7f88b57fa700 (LWP 17624)):
#0  0x7f8a729b90ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8a76d04e8b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x6151e70) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, readWriteLock=0x61519b8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239
#3  0x7f8a6ed0e44b in QtAV::BlockingQueue::take() ()
from /usr/lib64/libQtAV.so.1
#4  0x7f8a6ed7e0cb in QtAV::ExtractThread::run() () from
/usr/lib64/libQtAV.so.1
#5  0x7f8a76d03e0f in QThreadPrivate::start (arg=0x6151980) at
thread/qthread_unix.cpp:376
#6  0x7f8a729b4724 in start_thread () 

[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it

[Dr . Chapatin]

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

--- Comment #51 from Dr. Chapatin  ---
Patch was already applied on Arch Linux and the problem is really fixed.

Thank you all.

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

[krita] [Bug 393771] Bug: EXR files coming from Nuke or Maya have wrong channel orders.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Assignee|krita-bugs-n...@kde.org |b...@valdyas.org
 Ever confirmed|0   |1
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Thanks!

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

[krita] [Bug 393771] New: Bug: EXR files coming from Nuke or Maya have wrong channel orders.

[Jeroen Hoolmans]

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

Bug ID: 393771
   Summary: Bug: EXR files coming from Nuke or Maya have wrong
channel orders.
   Product: krita
   Version: 4.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: jhoolm...@gmail.com
  Target Milestone: ---

Created attachment 112376
  --> https://bugs.kde.org/attachment.cgi?id=112376=edit
Example EXR

Nuke writes out extra layer channels as 'layer.red' instead of 'layer.R'.
I have attached an EXR showing the behaviour.

The main layer is written as R G B A, but additional layers are red green blue.

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

[frameworks-solid] [Bug 389479] Plasma not mount disk

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #58 from Wolfgang Bauer  ---
Maybe
https://cgit.kde.org/solid.git/commit/?id=d735708ff11c40ee6b9bee64544250d55067403f
would help with the remaining errors?

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

[frameworks-kholidays] [Bug 393770] New: Update holiday_th_en-gb to the year 2018

[Andy Great]

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

Bug ID: 393770
   Summary: Update holiday_th_en-gb to the year 2018
   Product: frameworks-kholidays
   Version: 5.45.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: andythe_gr...@pm.me
  Target Milestone: ---

holiday_th_en-gb is not accurate for 2018, seems like it is outdated.

Updated Version here.
Jan 1   Monday  New Year's Day  National holiday
Jan 2   Tuesday Bridge Public Holiday   National holiday
Jan 13  SaturdayNational Children's Day Observance
Jan 16  Tuesday Teachers' Day   Observance
Feb 14  Wednesday   Valentine's Day Observance
Feb 16  Friday  Chinese Lunar New Year's DayObservance
Feb 17  SaturdaySecond day of Chinese Lunar New YearObservance
Feb 18  Sunday  Third day of Chinese Lunar New Year Observance
Mar 1   ThursdayMakha Bucha National holiday
Mar 20  Tuesday March equinox   Season
Apr 6   Friday  Chakri Day  National holiday
Apr 12  ThursdaySongkran observed   National holiday
Apr 13  Friday  SongkranNational holiday
Apr 14  SaturdaySongkranNational holiday
Apr 15  Sunday  SongkranNational holiday
Apr 16  Monday  Songkran observed   National holiday
May 1   Tuesday Labor Day   National holiday
May 14  Monday  Royal Ploughing Ceremony DayNational holiday
May 29  Tuesday Visakha Bucha   National holiday
Jul 27  Friday  Asalha BuchaNational holiday
Jul 28  Saturday His Majesty King Vajiralongkorn's Birthday National
holiday
Jul 28  SaturdayBuddhist Lent Day   National holiday
Jul 30  Monday  King's Birthday holiday National holiday
Aug 12  Sunday  Her Majesty the Queen's BirthdayNational holiday
Aug 12  Sunday  Mother's DayNational holiday
Aug 13  Monday  The Queen's Birthday observed   National holiday
Aug 13  Monday  Mother's Day observed   National holiday
Oct 13  Saturday His Majesty the late King Bhumibol Adulyadej Memorial Day 
National holiday
Oct 15  Monday  Anniversary of the Death of King Bhumibol observed 
National holiday
Oct 23  Tuesday King Chulalongkorn Memorial Day National holiday
Oct 31  Wednesday   Halloween   Observance
Nov 22  ThursdayLoy KrathongObservance
Dec 5   Wednesday   Father's DayNational holiday
Dec 10  Monday  Constitution DayNational holiday
Dec 24  Monday  Christmas Eve   Observance
Dec 25  Tuesday Christmas Day   Observance
Dec 31  Monday  New Year's Eve  National holiday

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

[krita] [Bug 393431] Some bugs found by PVS-Studio

[Dmitry Kazakov]

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

--- Comment #45 from Dmitry Kazakov  ---
Git commit e443b1a7191157dae1f6234c82704e075bc63213 by Dmitry Kazakov.
Committed on 02/05/2018 at 15:34.
Pushed by dkazakov into branch 'master'.

Fix PVS-Studio warning: overwriting the parameter

The real bug was actually not in the fact that the variable was unused,
but that its usage was different in two (scalar and vector) implementations
of alphadarken compositor.

M  +7-0libs/pigment/compositeops/KoOptimizedCompositeOpAlphaDarken128.h
M  +7-0libs/pigment/compositeops/KoOptimizedCompositeOpAlphaDarken32.h

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

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

[elisa] [Bug 387772] Stuck at configuring

[now-im]

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

--- Comment #20 from now-im  ---
Yes, I visited the development thread and found some other work is going on.
KDE needed a decent music player. Your project fills the hole. Good luck!

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

[elisa] [Bug 387772] Stuck at configuring

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

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

--- Comment #19 from Matthieu Gallien  ---
Thanks for your report. For your information, I am optimizing refresh scan of
your music after the first start. I hope this will improve your usecase.

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

[dolphin] [Bug 392882] Trash icon in info panel does not match icon in Places panel

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
Summary|Trash icon in info panel is |Trash icon in info panel
   |still red when I empty  |does not match icon in
   |trash   |Places panel
 Ever confirmed|0   |1
 CC||n...@kde.org

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

[plasmashell] [Bug 392756] Can't change time zone && ktimezonedrc gets overwritten at log-in

[bugzilla_noreply]

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

spiolli...@googlemail.com changed:

   What|Removed |Added

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

--- Comment #8 from spiolli...@googlemail.com ---
I managed to solve the issue by deleting /etc/timezone

The funny thing is that I never created or edited that file myself as Gentoo
manages time with /etc/localtime symlinks.
It'd be interesting to find out how /etc/timezone was ever created, but as I
can't reproduce that behaviour I'll close this as fixed.

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

[Discover] [Bug 389108] number of updates available and selected don't match

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/dis |https://commits.kde.org/dis
   |cover/1305ba643f6c50cc54049 |cover/2fc8f0c31e764693396d2
   |14c0a7cfb63f24e70b4 |fe4e764e4b8c7c14cd1
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #9 from Aleix Pol  ---
Git commit 2fc8f0c31e764693396d2fe4e764e4b8c7c14cd1 by Aleix Pol.
Committed on 02/05/2018 at 14:56.
Pushed by apol into branch 'Plasma/5.12'.

De-duplicate redundant updates

Count packages, not resources.

M  +0-1libdiscover/UpdateModel/UpdateModel.cpp
M  +11   -1libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp

https://commits.kde.org/discover/2fc8f0c31e764693396d2fe4e764e4b8c7c14cd1

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

[systemsettings] [Bug 393460] [Visual] "Appearance" title is non-bolded in translations

[bugzilla_noreply]

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

yst...@posteo.net changed:

   What|Removed |Added

   Version Fixed In||5.12.5

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

[systemsettings] [Bug 393460] [Visual] "Appearance" title is non-bolded in translations

[bugzilla_noreply]

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

yst...@posteo.net changed:

   What|Removed |Added

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

--- Comment #3 from yst...@posteo.net ---
Fixed for me with the upgrade to 5.12.5; marking as fixed. Feel free to reopen
if you still see this.

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

[plasmashell] [Bug 369327] User photo/avatar doesn't support antialias

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/pla
   ||sma-desktop/9da4da7ea7f71dc
   ||f6da2b6b263f7a636029c4a25

--- Comment #11 from David Edmundson  ---
Git commit 9da4da7ea7f71dcf6da2b6b263f7a636029c4a25 by David Edmundson, on
behalf of Kirill Tatunov.
Committed on 02/05/2018 at 14:43.
Pushed by davidedmundson into branch 'Plasma/5.12'.

Fix avatar picture aliasing and stretching in kickoff

Summary:
QML Image element has some smoothing when scaling an image by default but it's
not enough and the picture still looks a bit pixelated. This patch fixes that.
Also while I was at it, I added keeping the aspect ratio, because no one likes
their avatars stretched.

Test Plan:
Before: {F5819424} {F5819425}
After: {F5819429} {F5819430}

Reviewers: #plasma, mart

Reviewed By: #plasma, mart

Subscribers: davidedmundson, plasma-devel

Tags: #plasma

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

M  +5-0applets/kickoff/package/contents/ui/Header.qml

https://commits.kde.org/plasma-desktop/9da4da7ea7f71dcf6da2b6b263f7a636029c4a25

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

[elisa] [Bug 387772] Stuck at configuring

[now-im]

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

--- Comment #18 from now-im  ---
I think for me the problem is fixed. After the latest update, the error
vanished. Thanks for your hard work. You can close the issue. Have a nice day.

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

[digikam] [Bug 393728] Reread metadata from Video uses sidecar only

[meku]

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

--- Comment #2 from meku  ---
(In reply to Maik Qualmann from comment #1)
> DigiKam-6.0.0 cleans up the database on a re-read metadata when all 8
> metadata write options are enabled. As a workaround, you could disable a
> write option. Reading from image and sidecar I see not as a good option. We
> will come up with something.
> 
> Maik

Thanks that workaround appears to work for the purpose of updating the sidecar
files.

It seems if "Read from sidecar" is enabled then the Metadata viewer still does
not show certain metadata such as dimensions or GPS, even when this is in the
sidecar.

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

[Breeze] [Bug 393318] Request: better, more universal "sort options" icon

[Andres Betts]

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

Andres Betts  changed:

   What|Removed |Added

 CC||anditosan1...@gmail.com

--- Comment #5 from Andres Betts  ---
The first two options are my favorite. It is as simple as the concept gets.

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

[Breeze] [Bug 393318] Request: better, more universal "sort options" icon

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
Options I like:

- https://image.flaticon.com/icons/svg/159/159799.svg
- https://image.flaticon.com/icons/svg/565/565620.svg
- https://image.flaticon.com/icons/svg/219/219380.svg
- https://image.flaticon.com/icons/svg/690/690319.svg

If the icon has arrows, we need them to be pointing in both directions to avoid
suggesting descending or ascending order (it has to work for either one)

I'd also like to avoid numbers or letters, as that would imply that the current
sort order is alphabetical or by size or something, when, again, the icon needs
to work for either one.

Basically it needs to suggest the *concept* of sorting without seeming to imply
a specific sorting mode.

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

[valgrind] [Bug 393769] New: Building 3.13.0 on MacOS High Sierra

[Alex]

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

Bug ID: 393769
   Summary: Building 3.13.0 on MacOS High Sierra
   Product: valgrind
   Version: 3.13.0
  Platform: unspecified
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: ascolw...@verizon.net
  Target Milestone: ---

Created attachment 112375
  --> https://bugs.kde.org/attachment.cgi?id=112375=edit
Differences of the modifications on

I attached difference file that I modified in my local copy of 3.13.0 running
on MacOS High Sierra 10.13.4 using Xcode 9.3.

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

[frameworks-kio] [Bug 393653] Trash is shown in Open dialog

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Powerdevil] [Bug 345618] Powerdevil crash from idle desktop.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[konqueror] [Bug 393768] New: konqueror crashs on exit

[Markus Rathgeb]

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

Bug ID: 393768
   Summary: konqueror crashs on exit
   Product: konqueror
   Version: 5.0.97
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: maggu2...@web.de
  Target Milestone: ---

Application: konqueror (5.0.97)
 (Compiled from sources)
Qt Version: 5.9.5
Frameworks Version: 5.45.0
Operating System: Linux 4.16.3-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

I closed Konqueror

If you need further debug symbols, please comment.
I will recompile the relevant packages with debug symbols and try to reproduce.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
29return SYSCALL_CANCEL (wait4, pid, stat_loc, options, NULL);
[Current thread is 1 (Thread 0x7f2174468880 (LWP 8715))]

Thread 22 (Thread 0x7f20c6ffd700 (LWP 8754)):
#0  0x7f21699cd7cd in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f20fc003708) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f20fc0036b8,
cond=0x7f20fc0036e0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f20fc0036e0, mutex=0x7f20fc0036b8) at
pthread_cond_wait.c:655
#3  0x7f21403952f5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f21403957d7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f2140396571 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f2140392c4b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f21699c68ea in start_thread (arg=0x7f20c6ffd700) at
pthread_create.c:465
#8  0x7f2173cf068f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 21 (Thread 0x7f20c77fe700 (LWP 8746)):
#0  0x7f21699cd7cd in futex_wait_cancelable (private=,
expected=0, futex_word=0x5643c470811c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5643c47080c8,
cond=0x5643c47080f0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5643c47080f0, mutex=0x5643c47080c8) at
pthread_cond_wait.c:655
#3  0x7f21403952f5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f21403957d7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f2140396571 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f2140392c4b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f21699c68ea in start_thread (arg=0x7f20c77fe700) at
pthread_create.c:465
#8  0x7f2173cf068f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 20 (Thread 0x7f20c7fff700 (LWP 8745)):
#0  __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7f2173d0157c in ___fprintf_chk (fp=0x7f2173fae890
<_IO_stdfile_2_lock>, flag=1, format=0x7f213e53cdc8 "[%s] %s\n") at
fprintf_chk.c:30
#2  0x7f213e525eae in ?? () from /usr/lib64/libevent-2.1.so.6
#3  0x7f213e5260bc in event_warn () from /usr/lib64/libevent-2.1.so.6
#4  0x7f213e5277d8 in ?? () from /usr/lib64/libevent-2.1.so.6
#5  0x7f213e51d6d9 in event_base_loop () from /usr/lib64/libevent-2.1.so.6
#6  0x7f2140366309 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f21403625f8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f214037efcb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f2140396b36 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f2140392c4b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#11 0x7f21699c68ea in start_thread (arg=0x7f20c7fff700) at
pthread_create.c:465
#12 0x7f2173cf068f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7f20f4ff9700 (LWP 8744)):
#0  0x7f21699cd7cd in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f20f4ff8a38) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f20f4ff89e8,
cond=0x7f20f4ff8a10) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f20f4ff8a10, mutex=0x7f20f4ff89e8) at
pthread_cond_wait.c:655
#3  0x7f214038ad89 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f214038adb7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f2140365d2b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f21403625f8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f214037efcb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f2140396b36 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f2140392c4b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f21699c68ea in start_thread (arg=0x7f20f4ff9700) at
pthread_create.c:465
#11 

[konqueror] [Bug 393768] konqueror crashs on exit

[Markus Rathgeb]

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

Markus Rathgeb  changed:

   What|Removed |Added

 CC||maggu2...@web.de

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

[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.46

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

[kdeplasma-addons] [Bug 381173] Wrong countdown speed in timer plasmoid's window.

[Peter Mühlenpfordt]

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

Peter Mühlenpfordt  changed:

   What|Removed |Added

 CC||de...@ukn8.de

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

[plasmashell] [Bug 391646] When applet history contains several entries, I need to scroll up to show latest entry on top

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

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

--- Comment #8 from Dr. Chapatin  ---
Unfortunately it's not fixed in plasma 5.12.5, Arch Linux

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

[plasmashell] [Bug 391918] Make the default colors more contrasted

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||plasma-addons/6e753e6653ace
   ||887daceea2d05cf35661a7d0422
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from David Edmundson  ---
Git commit 6e753e6653ace887daceea2d05cf35661a7d0422 by David Edmundson.
Committed on 02/05/2018 at 13:27.
Pushed by davidedmundson into branch 'master'.

Sync systemloadviewer showed items to ksysguard/system monitor

Summary:
We currently show how much cache is used. It's a completely useless value to
know vs how much memory is free and leaves this applet out of sync with all the
other memory monitors.

It's problematic because the bar is inconsistent with the tooltip, and
by default the system load viewer chooses a colour very similar to the
application used memory making the UI actually worse.

Test Plan:
Ran it
(there's some unrelated bugs/warnings in this applet that need fixing)
Bar showed a sensible value that matched tooltip, rather than
looking 100% full all the time

Reviewers: #plasma, broulik

Reviewed By: #plasma, broulik

Subscribers: rkflx, plasma-devel

Tags: #plasma

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

M  +0-3applets/systemloadviewer/package/contents/config/main.xml
M  +0-10   applets/systemloadviewer/package/contents/ui/ColorSettings.qml
M  +4-11  
applets/systemloadviewer/package/contents/ui/SystemLoadViewer.qml

https://commits.kde.org/kdeplasma-addons/6e753e6653ace887daceea2d05cf35661a7d0422

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

[Discover] [Bug 391931] "Update" view says "nothing found" when selected after an app to be installed

[Dr . Chapatin]

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

--- Comment #4 from Dr. Chapatin  ---
https://www.youtube.com/watch?v=_9UVD_X5Pk8

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

[gwenview] [Bug 393735] Opening an image from a local folder via Dolphin with a large recent files list is slow

[Don Curtis]

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

--- Comment #14 from Don Curtis  ---
(In reply to Henrik Fehlauer from comment #12)
> And what about your recent files list? From which locations did it contain
> entries from?
I suspect (believe) that, the recent files list had only local files listed in
it but, I could be mistaken.

Thinking about my previous comment, it could be that, due to a DSL issue I
experienced earlier this week -- DSL Router power off and then on -- the NAS
"brick" didn't re-establish the LAN cable connection.

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

[krita] [Bug 393753] Krita Crash when trying to merge a Layer with a Colorize Mask

[sebastian labi]

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

--- Comment #3 from sebastian labi  ---
Created attachment 112374
  --> https://bugs.kde.org/attachment.cgi?id=112374=edit
crash step by step

i hope i can explain with this image

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

[gwenview] [Bug 393735] Opening an image from a local folder via Dolphin with a large recent files list is slow

[Don Curtis]

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

--- Comment #13 from Don Curtis  ---
(In reply to Henrik Fehlauer from comment #9)
> 1. If you have an Autofs mounted NFS share, the Places panel will try to
> access it, which takes a while due to how the automounting works. I'm lost
> with the recent bugs reorganization and don't know anymore which bug is
> _really_ about this exact problem, but starting to browse from Bug 335498
> should get you started in the maze of duplicates.
Thanks for the tip -- the »expletive deleted« NAS "brick" has removed itself
from the LAN.
After shutting it down via the power button and then powering it back on again,
guess what?
 ** Gwenview restored to the "normal" «perfect» behaviour!

Many thanks and cheers!!

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

[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache

[Pascal d'Hermilly]

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

--- Comment #4 from Pascal d'Hermilly  ---
> The disk cache is included in used memory.
To clarify my point: misrepresented in the visualization of used memory.

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