[dolphin] [Bug 398337] Trying to overwrite a file with a corrupted file deletes the former

[Safa Alfulaij]

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

--- Comment #2 from Safa Alfulaij  ---
(In reply to Andrew Crouthamel from comment #1)
> If you were using copy + paste, the source file is untouched. I would not
> attribute the loss of the file from CHKDSK on Windows, to Dolphin.

The idea is that I'm overwriting the original file, with a corrupted file. At
the end of the copy process, the original file is deleted and the corrupted
(new) file couldn't be copied. I will try again and check to see if the source
file is really untouched in this case.

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

[Discover] [Bug 398347] discover gets stuck on updates and corrupts the OS if I quit the process

[bugzilla_noreply]

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

--- Comment #1 from bionic...@gmail.com ---
Created attachment 114819
  --> https://bugs.kde.org/attachment.cgi?id=114819=edit
Task Window at 0%

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

[Discover] [Bug 398347] New: discover gets stuck on updates and corrupts the OS if I quit the process

[bugzilla_noreply]

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

Bug ID: 398347
   Summary: discover gets stuck on updates and corrupts the OS if
I quit the process
   Product: Discover
   Version: 5.12.6
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: bionic...@gmail.com
  Target Milestone: ---

Created attachment 114818
  --> https://bugs.kde.org/attachment.cgi?id=114818=edit
View of Update Window as well as exit message

I click the "update" button in the notification for discover and it opens up
the update window to update. The "Tasks" stay at "0%" and if I try to close the
window it tells me "Could not close the application, there are tasks that need
to be done". If I force restart the machine the operating system corrupts and I
lose all my data. The usual "sudo apt-get update" and "sudo apt-get upgrade" do
not have issues. My "Update" window stays stuck with the application and system
updates, letting me know how many updates are selected and the size of the
updates but with all options grayed out.

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

[kdeplasma-addons] [Bug 398346] New: System Load Viewer is not working at all with X399 motherboard

[wolfyrion]

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

Bug ID: 398346
   Summary: System Load Viewer is not working at all with X399
motherboard
   Product: kdeplasma-addons
   Version: 5.13.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: systemloadviewer
  Assignee: plasma-b...@kde.org
  Reporter: kyria...@mypcrevolution.com
  Target Milestone: ---

Hi , 

I am using Asrock Fatal1ty X399 Professional Gaming motherboard with an AMD
Threadripper 1950X and I dont get any indications of the CPU or memory using
system load viewer. (motherboard web site:
https://www.asrock.com/mb/AMD/Fatal1ty%20X399%20Professional%20Gaming/index.asp
)

However other addons like CPU Load monitor is working fine and also Thermal
Monitor addon is displaying the temperatures correctly.
Also Psensor is working fine and is displaying all the values correctly so I
guess is something with the System Load Viewer addon.

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

[kmail2] [Bug 383279] Kmail unnecessarily prompts for passwords

[bugzilla_noreply]

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

abyss.and...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Platform|openSUSE RPMs   |Neon Packages
 Ever confirmed|0   |1

--- Comment #6 from abyss.and...@gmail.com ---
It is still valid in 18.08.1
kdepim-runtime/xenial,now 4:18.08.1-0xneon+16.04+xenial+build64 amd64

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

[Discover] [Bug 398312] Close to panel feature

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Nate Graham  ---
Thanks for the idea! However, that's not really how most of our apps work. The
behavior of "close to system tray" can be problematic and non-obvious. If you
want to get rid of the Discover window during updates, just minimize it.

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

[kscreenlocker] [Bug 398317] lock screen text has no shadows when using software plasma renderer

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[dolphin] [Bug 398316] Time to move files into another tab is pretty long

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||n...@kde.org
 Resolution|--- |FIXED

--- Comment #1 from Nate Graham  ---
According to your video, by "pretty long" it seems like you mean "about half a
second". Is that correct?

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

[frameworks-ktexteditor] [Bug 382075] Solarized light color schema is outdated or uses wrong colors

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

  Component|general |general
Product|kate|frameworks-ktexteditor
 Status|UNCONFIRMED |CONFIRMED
   Priority|NOR |LO
   Severity|normal  |minor
Version|17.04.2 |5.49.0
 CC||andrew.crouthamel@kdemail.n
   ||et
   Assignee|kwrite-bugs-n...@kde.org|andrew.crouthamel@kdemail.n
   ||et
 Ever confirmed|0   |1

--- Comment #1 from Andrew Crouthamel  ---
I'm working on this now. The colors need a full rework in my opinion so they
follow Solarized rules and match the default Vim template.

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

[Discover] [Bug 398321] proxy config script not recognized/used

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[dolphin] [Bug 398324] Dophin has ambiguous shortcuts

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[dolphin] [Bug 398309] Use icon or the word 'Edit' instead of 'Change' for editing tags and comments

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et
   Severity|normal  |wishlist

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

[kwin] [Bug 398345] New: Black screen

[MH2]

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

Bug ID: 398345
   Summary: Black screen
   Product: kwin
   Version: 5.13.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: haa...@zoho.com
  Target Milestone: ---

Presented with a black screen after system loads. Creating file
/etc/X11/xorg.conf with specified resolution using nvidia-xconfig results in
the SDDM login screen appearing correctly. However, after logging in I'm again
presented with a black screen. Plasma-desktop is active, since it will respond
to keyboard events. The problem has something to do with "handshaking" to
obtain correct screen resolution.

I'm now running Debian Stretch with an earlier version of KDE, but the problem
is the same when running Debian Buster. My PC is connected to an AVR via HDMI
that is limited to 1920x1080 resolution. The AVR is then connected via HDMI to
a 4k TV.

If I connect the system directly to the TV via HDMI, all is well, but I no
longer have surround sound. My NVidia card, GT 710 correctly detects the TV as
2-channel and  will not output multi-channel.

I did not have any display issues with earlier NVidia cards/drivers on this
system. Also, everything did work at one time running Buster, meaning the AVR
resolution was correctly detected and the nvidia-driver passed multi-channel
audio. However, subsequent updates to nvidia-driver, Xserver, and KDE libraries
resulted in the above behavior.

I reported this bug under KWIN because I can get everything to work with a
manual configuration of xorg.conf, i.e. working SDDM display with correct
resolution. KWIN seems to be re-acquiring the EDID from the TV and switching to
a 4k resolution which my AVR is incapable of handling.

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

[kwin] [Bug 398344] New: Crash when returning from full screen.

[bugzilla_noreply]

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

Bug ID: 398344
   Summary: Crash when returning from full screen.
   Product: kwin
   Version: 5.13.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alstjr7...@daum.net
  Target Milestone: ---

Application: kwin_x11 (5.13.4)

Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.17.0-9-generic x86_64
Distribution: Ubuntu Cosmic Cuttlefish (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
When I full window browsing(Firefox),  press use 'F11' button for returning
from full screen.
Then crash alarm notification is on.

The crash can be reproduced sometimes.

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

Thread 10 (Thread 0x7f31928f2700 (LWP 11484)):
#0  0x7f325a0e42eb in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ce070a2e34) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f325a0e42eb in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55ce070a2de0, cond=0x55ce070a2e08) at pthread_cond_wait.c:502
#2  0x7f325a0e42eb in __pthread_cond_wait (cond=0x55ce070a2e08,
mutex=0x55ce070a2de0) at pthread_cond_wait.c:655
#3  0x7f325b4ad43b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3259a7b279 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f3259a7b4da in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f325b4acc87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f325a0de164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f325cb0edef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f3193cdd700 (LWP 11392)):
#0  0x7f325cb027d6 in __GI_ppoll (fds=0x7f3234000d68, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f325b6a3141 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f325b6a45b9 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f325b65416b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f325b4a30b6 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3259745c75 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f325b4acc87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f325a0de164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f325cb0edef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f324e18c700 (LWP 7350)):
#0  0x7f325a0e42eb in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ce06e033f4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f325a0e42eb in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55ce06e033a0, cond=0x55ce06e033c8) at pthread_cond_wait.c:502
#2  0x7f325a0e42eb in __pthread_cond_wait (cond=0x55ce06e033c8,
mutex=0x55ce06e033a0) at pthread_cond_wait.c:655
#3  0x7f325b4ad43b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3259a7b279 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f3259a7b4da in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f325b4acc87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f325a0de164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f325cb0edef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f3233fff700 (LWP 6680)):
#0  0x7f325a0e42eb in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ce06a64f80) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f325a0e42eb in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55ce06a64f30, cond=0x55ce06a64f58) at pthread_cond_wait.c:502
#2  0x7f325a0e42eb in __pthread_cond_wait (cond=0x55ce06a64f58,
mutex=0x55ce06a64f30) at pthread_cond_wait.c:655
#3  0x7f325b4ad43b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3259a7b279 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f3259a7b4da in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f325b4acc87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f325a0de164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f325cb0edef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f32317bc700 (LWP 3700)):
#0  0x7f325a0e42eb in futex_wait_cancelable (private=,

[lokalize] [Bug 398185] Column Last Translator became not visible after latest update

[Simon Depiets]

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

Simon Depiets  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 CC||sdepi...@gmail.com
 Ever confirmed|0   |1
   Assignee|sha...@ukr.net  |sdepi...@gmail.com

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

[lokalize] [Bug 395119] Open multiple files at once from project view

[Simon Depiets]

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

Simon Depiets  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://commits.kde.org/lok
   ||alize/a6688209a3737bc1e26c3
   ||54a07e0df80c27557d9
 Resolution|--- |FIXED

--- Comment #3 from Simon Depiets  ---
Git commit a6688209a3737bc1e26c354a07e0df80c27557d9 by Simon Depiets.
Committed on 07/09/2018 at 01:52.
Pushed by sdepiets into branch 'master'.

Allow multiple and background file opening

Summary:
This revision addresses the following feature :
Open multiple files at once from project view
https://bugs.kde.org/show_bug.cgi?id=395119

Three features added :
* Opening multiple selected files (Open selected files menu entry)
{F6236568}
* Opening all files in one/many folder(s) (Open selected files menu entry)
* Open a file in the background (Ctrl+DblClick)

Reviewers: #localization, aacid, ltoscano, adrianchavesfernandez, huftis

Tags: #localization

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

M  +1-1src/editortab.h
M  +3-4src/filesearch/filesearchtab.cpp
M  +3-3src/filesearch/filesearchtab.h
M  +17   -15   src/lokalizemainwindow.cpp
M  +4-4src/lokalizemainwindow.h
M  +8-8src/nokde-stubs/prefs.cpp
M  +2-2src/nokde-stubs/projectbase.h
M  +1-1src/project/project.cpp
M  +1-1src/project/project.h
M  +12   -2src/project/projecttab.cpp
M  +1-1src/project/projecttab.h
M  +2-1src/project/projectwidget.cpp
M  +1-1src/project/projectwidget.h
M  +2-1src/tm/tmtab.cpp
M  +1-1src/tm/tmtab.h
M  +1-1src/tm/tmview.cpp
M  +1-1src/tm/tmview.h

https://commits.kde.org/lokalize/a6688209a3737bc1e26c354a07e0df80c27557d9

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

[krita] [Bug 398343] New: Krita doesn't recognize stylus when moved outside of hover distance

[Alexander Gray]

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

Bug ID: 398343
   Summary: Krita doesn't recognize stylus when moved outside of
hover distance
   Product: krita
   Version: 4.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: mistersandman...@gmail.com
  Target Milestone: ---

I'm using Windows 10 (x86_64) with a Wacom Cintiq 22HD and my stylus loses
connectivity if the pen goes more than a half inch away from my tablet, and it
doesn't recognize the stylus when it comes back into range to move the cursor
or when the stylus is making contact with the tablet. The only way that the
stylus will reconnect is if I hover the stylus over anything other than the
canvas (Tools, Brushes, Colors, Etc) and I keep the stylus in that half inch
range onto the canvas. The stylus acts correctly in every other program I have
as well as on my browser. 

Reproducible: Always

Steps to Reproduce:
1: Open Krita
2: Open/Load file
3: Use stylus
4: Lift stylus away from canvas

Actual Results: Stylus isn't recognized when it leaves drawing/hover range

Expected Results: Stylus should reconnect no matter how far it is taken from
the tablet

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

[kate] [Bug 387262] Kate ignores the setting "Default schema for Kate" under the Fonts & Colors Configuration

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Andrew Crouthamel  ---
Hi from the Bugsquad!

I tested this on Kate 18.08 and am unable to reproduce your issue. Could you
please retest on the latest version? If you still have an issue, let us know.

KDE Plasma Version: 5.13.4
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

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

[kate] [Bug 368182] Cursor disappears when adding more spaces at the end of a LTR line

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||andrew.crouthamel@kdemail.n
   ||et
   Severity|normal  |minor
 Ever confirmed|0   |1

--- Comment #1 from Andrew Crouthamel  ---
Hi from the Bugsquad!

I can confirm this with Kate 18.08. I presume you would like the LTR behavior
to keep the cursor in-screen, but still allow spaces to be entered (as happens
with RTL)?

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

[kate] [Bug 347329] Problems with remote hidden files (dot-files) on Samba share

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED
 CC||andrew.crouthamel@kdemail.n
   ||et

--- Comment #1 from Andrew Crouthamel  ---
Hi from the Bugsquad!

I tested this on Kate 18.08 and am unable to reproduce your issue. Could you
please retest? If you still have an issue, let us know.

KDE Plasma Version: 5.13.4
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

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

[kate] [Bug 351362] Warn kate user of opening large files

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 CC||andrew.crouthamel@kdemail.n
   ||et

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

[kate] [Bug 268913] Load a default session that can be saved on application closure, so session saving is automatic like a web browser

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et
   Severity|normal  |wishlist
Summary|Sessions are not resumed|Load a default session that
   |when closing and reopening  |can be saved on application
   |the window  |closure, so session saving
   ||is automatic like a web
   ||browser

--- Comment #8 from Andrew Crouthamel  ---
Hi from the Bugsquad!

I am going to change this severity to wishlist since the reporter can make this
function, but has to create a session first. I can confirm the session loading
works, but agree it is confusing.

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

[kate] [Bug 348205] Kate does not open last used session after login

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Andrew Crouthamel  ---
Hi there from the Bugsquad!

I just tested this on Kate 18.08 successfully. Could you test again and let me
know if you still have an issue?

KDE Plasma Veresion: 5.13.4
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

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

[LabPlot2] [Bug 398342] New: ProjectImportTest segfaults while loading Excel file

[awilfox]

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

Bug ID: 398342
   Summary: ProjectImportTest segfaults while loading Excel file
   Product: LabPlot2
   Version: latest
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Building LabPlot 2.5.0 on Adélie Linux 1.0-beta1-exp with musl libc 1.1.20,
there was a segmentation fault during the automated tests:


awilcox on gwyn [pts/16 Thu 6 22:54] labplot-2.5.0:
tests/import_export/project/projectimporttest
* Start testing of ProjectImportTest *
Config: Using QtTest library 5.9.6, Qt 5.9.6 (power64-big_endian-lp64 shared
(dynamic) debug build; by GCC 6.4.0)
PASS   : ProjectImportTest::initTestCase()
QDEBUG : ProjectImportTest::testOrigin01() "Starting the import of
/usr/src/packages/user/labplot/src/labplot-2.5.0/tests/import_export/project/data/origin8_test_tree_import.opj"
OriginProjectParser::load()

= Received signal, dumping stack ==
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64-foxkit-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 57000
[New LWP 57001]
[New LWP 57002]
__cp_end () at src/thread/powerpc64/syscall_cp.s:32
(gdb) 
Thread 3 (LWP 57002):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffa2ed22e4 in __syscall_cp_c (nr=128, u=2, v=70367082657680, w=0,
x=0, y=0, z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffa2ed10d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffa2ed11f4 in __timedwait_cp (addr=0x3fff9cf73804, val=, clk=, at=, priv=128) at
src/thread/__timedwait.c:31
r = 
to = {tv_sec = 299, tv_nsec = 99232}
top = 
#4  0x3fffa2e7b028 in __pthread_cond_timedwait (c=0x3fffa0761c28,
m=0x3fffa0761c00, ts=0x3fff9cf738d8) at src/thread/pthread_cond_timedwait.c:105
node = {prev = 0x0, next = 0x0, state = 0, barrier = 2, notify = 0x0}
e = 
seq = 2
clock = 1
cs = 0
shared = 0
oldstate = 
tmp = 
fut = 0x3fff9cf73804
#5  0x3fffa0bef6f8 in QWaitConditionPrivate::wait_relative (time=30,
this=0x3fffa0761c00) at thread/qwaitcondition_unix.cpp:133
ti = {tv_sec = 5699834, tv_nsec = 684002528}
ti = 
#6  QWaitConditionPrivate::wait (time=30, this=0x3fffa0761c00) at
thread/qwaitcondition_unix.cpp:141
code = 
code = 
#7  QWaitCondition::wait (this=, mutex=0x3fffa07614f8,
time=30) at thread/qwaitcondition_unix.cpp:215
__PRETTY_FUNCTION__ = "bool QWaitCondition::wait(QMutex*, long unsigned
int)"
returnValue = 
#8  0x3fffa2d914d0 in QTest::WatchDog::run (this=0x3fffa07614e0) at
qtestcase.cpp:988
t = 
locker = {val = 70367141303545}
__PRETTY_FUNCTION__ = "virtual void QTest::WatchDog::run()"
#9  0x3fffa0beec88 in QThreadPrivate::start (arg=0x3fffa07614e0) at
thread/qthread_unix.cpp:368
__cb = {__f = 0x3fffa0bed04c , __x =
0x3fffa07614e0, __next = 0x0}
thr = 0x3fffa07614e0
data = 
#10 0x3fffa2ed283c in start (p=0x3fff9cf73a88) at
src/thread/pthread_create.c:147
self = 0x3fff9cf73a88
#11 0x3fffa2ede5a8 in __clone () at src/thread/powerpc64/clone.s:43
No locals.

Thread 2 (LWP 57001):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffa2ed2374 in __syscall_cp_c (nr=167, u=-1, v=0, w=0, x=0, y=0,
z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffa2ed10d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffa2ec00b4 in poll (fds=, n=,
timeout=) at src/select/poll.c:10
No locals.
#4  0x3fff9f35a6e0 in _xcb_conn_wait (c=0x122e6fec0, cond=,
vector=0x0, count=0x0) at xcb_conn.c:479
ret = 
fd = {fd = 3, events = 1, revents = 0}
#5  0x3fff9f35d074 in xcb_wait_for_event (c=) at
xcb_in.c:697
ret = 0x0
#6  0x3fff9d327a98 in QXcbEventReader::run (this=0x3fffa2d75a60) at
qxcbconnection.cpp:1330
event = 0x0
#7  

[systemsettings] [Bug 398341] New: Allow copying of text from About System

[Andrew Crouthamel]

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

Bug ID: 398341
   Summary: Allow copying of text from About System
   Product: systemsettings
   Version: 5.13.4
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: andrew.croutha...@kdemail.net
  Target Milestone: ---

It would be great if I could copy text off of the About System window.

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

[frameworks-krunner] [Bug 398305] FF Bookmarks KRunner does not work with database created with FF 58 or later

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/pla
   ||sma-workspace/cb99ab735c813
   ||b250f4cd5031b4b078fe0b6c250
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Stefan Brüns  ---
Git commit cb99ab735c813b250f4cd5031b4b078fe0b6c250 by Stefan Brüns.
Committed on 06/09/2018 at 22:55.
Pushed by bruns into branch 'master'.

KRunner: remove no longer existant and unused column from SQL query

Summary:
The favicon_id is not used in the query results, and may not even exist
when the places db has been created with FF 58 or later. In case the
column does not exist the query fails completely.

Test Plan:
1. Create a new FF profile
2. Add some bookmarks
3. Do some queries

Reviewers: #plasma, davidedmundson

Reviewed By: #plasma, davidedmundson

Subscribers: broulik, plasma-devel

Tags: #plasma

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

M  +4-4runners/bookmarks/browsers/firefox.cpp

https://commits.kde.org/plasma-workspace/cb99ab735c813b250f4cd5031b4b078fe0b6c250

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

[kwin] [Bug 398340] New: VirtualBOX, VMware Player - hot corners don't work, hot edges work as intended

[Tomasz Feliksiak]

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

Bug ID: 398340
   Summary: VirtualBOX, VMware Player - hot corners don't work,
hot edges work as intended
   Product: kwin
   Version: 5.12.6
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: vo...@webtrunki.pl
  Target Milestone: ---

In work I use Kubuntu 18.04.1 LTS as my main system and there everything works
fine. I use top left corner for windows presentation and bottom right for
desktop grid.

In home I have Windows 10 and VMware Player 14 (14.1.3 build-9474260) with
exact the same Kubuntu 18.04.1 LTS. Earlier I used VirtualBOX (5.2.18 r124319
(Qt5.6.2)).

No mater on which VM software I run Kubuntu, hot corners doesn't work.

Inspired by bugs https://bugs.kde.org/show_bug.cgi?id=290887 and
https://bugs.kde.org/show_bug.cgi?id=321259 I started testing this a bit, and
noticed that hot edges are working normally.

Reproducible: Always

Steps to Reproduce:
1. Install Kubuntu 18.04.1 on VMware Player (with open-vm-tools) or VirtualBox
(with vboxguestadditions) and go fullscreen (in window it's the same but harder
to hit corner/edge of screen)
2. Bind any effect to the corners and edges
3. Throw your mouse in the corners and edges

Actual Results:
Hot corners doesn't work, hot edges are working

Expected Results:
Working hot corners and edges

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

[krita] [Bug 398241] Assert when saving CMYK to PNG with force sRGB unchecked

[Antti Savolainen]

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

Antti Savolainen  changed:

   What|Removed |Added

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

--- Comment #1 from Antti Savolainen  ---
Confirming
https://youtu.be/GpaVDsqY0PU


Thread 36 "Thread (pooled)" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff9effd700 (LWP 19281)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x73ee3e97 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x73ee5801 in __GI_abort () at abort.c:79
#2  0x748d2fa7 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x748ce476 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x770656c9 in KisPNGConverter::buildFile(QIODevice*, QRect const&,
double, double, KisSharedPtr,
QTypedArrayData >::iterator,
QTypedArrayData >::iterator, KisPNGOptions,
KisMetaData::Store*) (this=0x7fff9effc8e0, iodevice=0x7fff9effca40,
imageRect=..., xRes=4.167, yRes=4.167, device=...,
annotationsStart=..., annotationsEnd=..., options=..., metaData=0x0) at
/home/managor/Sourcebuilding/krita/libs/ui/kis_png_converter.cpp:968
#5  0x7fff8f11c39c in KisPNGExport::convert(KisDocument*, QIODevice*,
KisPinnedSharedPtr) (this=0x66f19550,
document=0x66bdb4e0, io=0x7fff9effca40, configuration=...)
at
/home/managor/Sourcebuilding/krita/plugins/impex/png/kis_png_export.cc:93
#6  0x7730c2e5 in KisImportExportManager::doExportImpl(QString const&,
QSharedPointer,
KisPinnedSharedPtr) (this=0x66bdc3e0,
location=..., filter=..., exportConfiguration=...)
at
/home/managor/Sourcebuilding/krita/libs/ui/KisImportExportManager.cpp:638
#7  0x7730beb6 in KisImportExportManager::doExport(QString const&,
QSharedPointer,
KisPinnedSharedPtr, bool) (this=0x66bdc3e0,
location=..., filter=..., exportConfiguration=..., alsoAsKra=false)
at
/home/managor/Sourcebuilding/krita/libs/ui/KisImportExportManager.cpp:586
#8  0x77310fa7 in
std::__invoke_impl,
KisPinnedSharedPtr, bool),
KisImportExportManager*&, QString&, QSharedPointer&,
KisPinnedSharedPtr&,
bool&>(std::__invoke_memfun_deref, KisImportExportFilter::ConversionStatus
(KisImportExportManager::*&)(QString const&,
QSharedPointer,
KisPinnedSharedPtr, bool),
KisImportExportManager*&, QString&, QSharedPointer&,
KisPinnedSharedPtr&, bool&) (__f=
@0x66f37430: (KisImportExportFilter::ConversionStatus
(KisImportExportManager::*)(KisImportExportManager * const, const QString &,
QSharedPointer,
KisPinnedSharedPtr, bool)) 0x7730be38
,
KisPinnedSharedPtr, bool)>, __t=@0x66f37468:
0x66bdc3e0, __args#0=..., __args#1=..., __args#2=...,
__args#3=@0x66f37440: false)
at /usr/include/c++/7/bits/invoke.h:73
#9  0x77310d13 in std::__invoke,
KisPinnedSharedPtr, bool),
KisImportExportManager*&, QString&, QSharedPointer&,
KisPinnedSharedPtr&,
bool&>(KisImportExportFilter::ConversionStatus
(KisImportExportManager::*&)(QString const&,
QSharedPointer,
KisPinnedSharedPtr, bool),
KisImportExportManager*&, QString&, QSharedPointer&,
KisPinnedSharedPtr&, bool&) (__fn=
@0x66f37430: (KisImportExportFilter::ConversionStatus
(KisImportExportManager::*)(KisImportExportManager * const, const QString &,
QSharedPointer,
KisPinnedSharedPtr, bool)) 0x7730be38
,
KisPinnedSharedPtr, bool)>,
__args#0=@0x66f37468: 0x66bdc3e0, __args#1=..., __args#2=...,
__args#3=..., __args#4=@0x66f37440: false)
at /usr/include/c++/7/bits/invoke.h:96
#10 0x773107af in std::_Bind,
KisPinnedSharedPtr, bool))(QString const&,
QSharedPointer,
KisPinnedSharedPtr,
bool)>::__call(std::tuple<>&&, std::_Index_tuple<0ul, 1ul, 2ul, 3ul, 4ul>)
(this=0x66f37430, __args=...)
at /usr/include/c++/7/functional:469
#11 0x77310033 in std::_Bind,
KisPinnedSharedPtr, bool))(QString const&,
QSharedPointer,
KisPinnedSharedPtr, bool)>::operator()<,
KisImportExportFilter::ConversionStatus>() (this=0x66f37430) at
/usr/include/c++/7/functional:551
#12 0x7731130e in
QtConcurrent::StoredFunctorCall0,
KisPinnedSharedPtr, bool))(QString const&,
QSharedPointer,
KisPinnedSharedPtr, bool)> >::runFunctor()
(this=0x66f37410) at
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:60
#13 0x773111f9 in
QtConcurrent::RunFunctionTask::run()
(this=0x66f37410) at
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:108
#14 0x748e52a2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x748e816d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fffed9056db in start_thread (arg=0x7fff9effd700) at

[skrooge] [Bug 397611] [ERR-5]: Format de date non pris en charge importation boobank

[bugzilla_noreply]

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

--- Comment #10 from chos...@laposte.net ---
J'ai ouvert un signalement d'erreur su le git de Weboob.

https://git.weboob.org/weboob/devel/issues/162

Apparemment c'est la banque postale qui ne donne plus cette donnée rdate. 
Pour Boobank ils ne veulent pas peupler artificiellement un champ s'il n'existe
pas sur le site.

Peut-être qu'il vous serait possible de paramétrer la ligne 
#This parameter is not MANDATORY but if not used then getbulk must be used
X-SKROOGE-getoperations=a="%parameter2" && b="%4" && m=$( [[ ${a} > ${b} ]] &&
echo "$a" || echo "$b" ) && PYTHONIOENCODING=utf_8 boobank -q -f csv history
"%1" -s rdate,type,raw,label,amount --condition "rdate>$m OR date>$m OR
rdate>$m 00:00:00 OR date>$m 00:00:00" -n 9 %parameter3 2>/dev/null

dans le script org.kde.skrooge-import-backend-weboob.desktop en fonction de la
présence de rdate ou non et de remplacer rdate par date ?

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

[valgrind] [Bug 396290] [PATCH] Possible tool - failgrind

[bugzilla_noreply]

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

--- Comment #23 from roger.li...@cedalo.com ---
Created attachment 114817
  --> https://bugs.kde.org/attachment.cgi?id=114817=edit
Patch with function enter/leave detection code from callgrind.

This patch is the same as 114630, but with code borrowed from callgrind for
tracking the callstack for detecting function entering/leaving. I've minimised
the code from callgrind as much as I think is sensible, but it may be possible
to remove more with some thought. It is still 3800 lines of text from callgrind
compared to 1100 for the rest of failgrind.

There's effectively a lot of duplicate code here, so I'll be interested to hear
your comments.

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

[partitionmanager] [Bug 398306] Window hang and crash after move and resize ntfs partition

[Andrius Štikonas]

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

--- Comment #1 from Andrius Štikonas  ---
Hard to tell from crash report what happened (especially since there are no
debug symbols).

Whether data is alright depends only on when crash occurred.

If crash occurred during resize stage, it's much more likely that your data is
alright, I would still try to run fsck. If it happened during move state, it's
very tricky to recover data... In principle it's still there, but there will be
an empty gap in your partition.

Btw, I think at the moment rollback does not happen if you click cancel. I
think running job has to finish... Rollback only happens if copying data
function tells that copying failed.

Also, note that in the next version of KPM, GUI crashes will not affect
currently running job. I.e. even if GUI crashes, the job will successfully
finish in the background.

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

[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs

[Emre]

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

--- Comment #12 from Emre  ---
Dears, any development on this? KMail added EWS resource and it seems to work
good, but without solving this bug, we can't use Kmail in Corporate Office 365
environment.

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

[okular] [Bug 398326] Letter ž is displayed as š instead

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

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

--- Comment #5 from Luigi Toscano  ---
When you don't have Tahoma, what are the fonts used for the replacement?
(File->Properties->Fonts)

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

[dolphin] [Bug 295526] Turn off frames for SVGs

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||18.12.0
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dol
   ||phin/cf0052c2968a7c3e110e24
   ||134dbe7ef13c835995

--- Comment #33 from Nate Graham  ---
Git commit cf0052c2968a7c3e110e24134dbe7ef13c835995 by Nathaniel Graham.
Committed on 06/09/2018 at 20:47.
Pushed by ngraham into branch 'master'.

Make thumbnail frame-and-shadow drawing criteria match those of the file dialog

Summary:
KIO's file dialog already has logic to avoid drawing frames around images
detected as likely to be icons, which is improved with D15071. Since Dolphin
doesn't use KIO for any of this (boo) we have to pull it over here too; this
patch brings the same feature to Dolphin, as well as the feature to disable
frames and shadows for all thumbnails at very small sizes, which improves
clarity.

With this patch, Dolphin's frame drawing behavior becomes consistent with that
of the file dialog (as of D15071).
FIXED-IN: 18.12.0

Test Plan:
Icons no longer have frames:
{F6214279}

Images without transparency still have frames:
{F6214280}

Nicer presentation for folders with mixed image types (images without
transparency get frames; images without it don't):
{F6214278}

At small sizes, thumbnail clarity is improved by omitting the frame and shadow.
Before:
{F6214296}

After:
{F6214294}

Reviewers: #dolphin, broulik, elvisangelaccio

Reviewed By: #dolphin, broulik, elvisangelaccio

Subscribers: markg, anthonyfieroni, elvisangelaccio, kfm-devel

Tags: #dolphin

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

M  +3-8src/kitemviews/kfileitemmodelrolesupdater.cpp

https://commits.kde.org/dolphin/cf0052c2968a7c3e110e24134dbe7ef13c835995

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

[krita] [Bug 398339] New: Gamut mask does not update

[brusheco]

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

Bug ID: 398339
   Summary: Gamut mask does not update
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: ngmstu...@yahoo.co.uk
  Target Milestone: ---

When editing a gamut mask, the image in the gamut mask docker updates, but it
doesn't update in the artistic color selector, it just shows the original.

1. Click edit gamut mask in gamut mask docker.
2. Transform or rotate the mask
3. save new mask with different name
4. you should see that the mask has not updated in the artistic colour selector
docker.

Using windows 7 64bit
Krita git fb16dc5

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

[plasmashell] [Bug 397779] Navigating search result for apps require double-pressing of arrow buttons

[Rik Mills]

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

Rik Mills  changed:

   What|Removed |Added

 CC||rikmi...@kubuntu.org

--- Comment #8 from Rik Mills  ---
(In reply to Eike Hein from comment #6)
> These fixes will be in the next 5.12.x, 5.13.x and the 5.14 releases.

5.13 has had its final point release, but maybe this is worth cherry picking?

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

[kwin] [Bug 398058] Effect to slide notifications

[Vlad Zagorodniy]

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

--- Comment #8 from Vlad Zagorodniy  ---
https://www.youtube.com/watch?v=B3Y45z0Eb2A

@Kai

Not sure whether that's a bug in KWin, but effects receive signals in the
following order:

  windowAdded / Notification 0
  windowAdded / Notification 1
  windowAdded / Notification 2

  windowGeometryShapeChanged
  windowGeometryShapeChanged
  windowClosed / Notification 0

  windowGeometryShapeChanged
  windowGeometryShapeChanged
  windowClosed / Notification 1

  ...

  windowGeometryShapeChanged
  windowGeometryShapeChanged
  windowClosed / Notification 10

With this sequence of emitted signals, it's really hard to implement proper
version of this effect (or any other that wants to correctly animate
notifications).

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

[okular] [Bug 398338] New: Compilation failure on Musl due to use of vasprintf

[Bart Ribbers]

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

Bug ID: 398338
   Summary: Compilation failure on Musl due to use of vasprintf
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: bribb...@disroot.org
  Target Milestone: ---

If building Okular on a Musl based system (like Alpine Linux or postmarketOS),
compilation will fail:

okular-18.08.1/core/synctex/synctex_parser.c:8202:13: error: implicit
declaration of function 'vasprintf' [-Werror=implicit-function-declaration]
 if (vasprintf(, format, va) < 0) {
 ^


This is due to the use of "vasprintf()" which is not part of POSIX
(https://linux.die.net/man/3/vasprintf). It can be quite easily resolved by
using "vsprintf()" instead, but I'm guessing this will cause problems during
runtime due to missing the terminating null byte.

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

[plasmashell] [Bug 395647] No action proposed by notifier for encrypted removable devices (dmcrypt LUKS)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #1 from Christoph Feck  ---
I am using zuluCrypt GUI to mount encrypted volumes, but would indeed be nice
if it was possible directly from Plasma device list.

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

[Falkon] [Bug 396024] Allow per-site configuration of JavaScript

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
I tried it, but it doesn't allow the reverse. If I have JavaScript disabled,
the button doesn't allow me to temporarily enable it. Starting with enabled,
then later disabling it defeats the purpose; any malformed site will have
already executed its scripts before I get the chance to disable it.

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

[dolphin] [Bug 398337] New: Trying to overwrite a file with a corrupted file deletes the former

[Safa Alfulaij]

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

Bug ID: 398337
   Summary: Trying to overwrite a file with a corrupted file
deletes the former
   Product: dolphin
   Version: 18.08.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: safa1996alful...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

I was trying to copy-past several files from my fat32 USB stick. One file had a
problem and Dolhpin told me (by a dialog) that it can't be copied. Do you want
to skip or skip all etc. etc.
I chose Skip and then found that I don't that file in the destination location.
I tried copying it again from the USB stick and it was the same. I took the
stick to Windows and it refused to copy/open it asking to check the stick for
errors. I've done that and the file was gone too. (The file was really
corrupted)

The issue here is that Dolphin should make sure 100% that the destination file
is not corrupted before deleting the current file, or to just keep it as backup
if anything goes wrong.

Now I have to rewrite that ~300-lines main tex file again :)

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

[Akonadi] [Bug 397239] crash when searching with kmail

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

--- Comment #5 from Wolfgang Bauer  ---
*** Bug 398282 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 398282] Akonadi crashes frequently since upgrade to 5.9.0

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

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

--- Comment #2 from Wolfgang Bauer  ---
As bug#398191 has the very same backtrace and is confirmed to be fixed in
5.9.1, I assume the same is true here.

Feel free to reopen if you still experience the crash.

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

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

[Akonadi] [Bug 397239] crash when searching with kmail

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||pieter.da...@gmail.com

--- Comment #4 from Wolfgang Bauer  ---
*** Bug 398191 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 398191] akonadiserver crashes from time to time since upgrading to 18.08

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #5 from Wolfgang Bauer  ---
(In reply to Pieter David from comment #4)
> Indeed, after updating to 5.9.1 (applications 18.08.1) the crashes are gone.

Thank you very much for the confirmation.

But let's better mark it as duplicate then...

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

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

[plasmashell] [Bug 398336] New: Plasma menu crashes while searching applications

[Giulio]

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

Bug ID: 398336
   Summary: Plasma menu crashes while searching applications
   Product: plasmashell
   Version: 5.13.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: giu...@glgprograms.it
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.13.4)

Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.14.67-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
The issue shows up systematically when searching certain applications.
I noticed more frequently when I search for Thunderbird.
Only plasma crashes and opens again after a few seconds

The crash can be reproduced every time.

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

Thread 15 (Thread 0x7f762effd700 (LWP 2981)):
#0  0x7f7704d8eafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f77054007bc in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f765de8c469 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f765de90339 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7f765de8e389 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#18 0x7f770545 in  () at /usr/lib/libQt5Core.so.5
#19 0x7f7704d88a9d in start_thread () at /usr/lib/libpthread.so.0
#20 0x7f77050e4a43 in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f762f7fe700 (LWP 2980)):
#0  0x7f7704d8eafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f77054007bc in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f765de8c469 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f765de90339 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f765de8e389 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f770545 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f7704d88a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f77050e4a43 in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f762700 (LWP 2979)):
#0  0x7f7704d8eafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f77054007bc in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f765de8c469 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f765de90339 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f765de8b52d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f765de90392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f765de8b52d in

[plasmashell] [Bug 398335] New: Plasma crashes after using bleachbit

[Paolo]

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

Bug ID: 398335
   Summary: Plasma crashes after using bleachbit
   Product: plasmashell
   Version: 5.13.4
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pa...@benso1968.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.13.4)

Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.17.0-3-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
I was closing bleachbit (after job completion)
- Unusual behavior I noticed:

- Custom settings of the application:
I've just ticked some options of the application (Bleachbit), NOT overwrite,
NOT deep cleaning...

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa1c2666100 (LWP 822))]

Thread 25 (Thread 0x7fa0d17fa700 (LWP 8306)):
#0  0x7fa1ca7d2e6c in futex_wait_cancelable (private=,
expected=0, futex_word=0x555eeae73cf0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fa1ca7d2e6c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x555eeae73ca0, cond=0x555eeae73cc8) at pthread_cond_wait.c:502
#2  0x7fa1ca7d2e6c in __pthread_cond_wait (cond=0x555eeae73cc8,
mutex=0x555eeae73ca0) at pthread_cond_wait.c:655
#3  0x7fa1cac334fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa1280e3d30 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fa1280e7ae8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#15 0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#16 0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#17 0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#18 0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#19 0x7fa1280e7b42 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#20 0x7fa1280e2e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#21 0x7fa1280e5bb9 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#22 0x7fa1cac32d47 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fa1ca7ccf2a in start_thread (arg=0x7fa0d17fa700) at
pthread_create.c:463
#24 0x7fa1ca927edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7fa0d1ffb700 (LWP 8305)):
#0  0x7fa1ca7d2e6c in futex_wait_cancelable (private=,
expected=0, futex_word=0x555eeae73cf0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fa1ca7d2e6c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x555eeae73ca0, cond=0x555eeae73cc8) at pthread_cond_wait.c:502
#2  0x7fa1ca7d2e6c in __pthread_cond_wait (cond=0x555eeae73cc8,
mutex=0x555eeae73ca0) at pthread_cond_wait.c:655
#3  0x7fa1cac334fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa1280e3d30 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fa1280e7ae8 in  () at

[digikam] [Bug 398331] xmp sidecar files are not reloaded on change

[Daniel Laidig]

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

--- Comment #2 from Daniel Laidig  ---
Sorry, I tried to search for duplicates, but apparently not using the right
terms. Is there are reason you didn't mark this bug as a duplicate?

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

[Akonadi] [Bug 398191] akonadiserver crashes from time to time since upgrading to 18.08

[Pieter David]

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

Pieter David  changed:

   What|Removed |Added

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

--- Comment #4 from Pieter David  ---
Indeed, after updating to 5.9.1 (applications 18.08.1) the crashes are gone.

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

[plasma-nm] [Bug 398332] Plasma (plasmashell), signal: Segmentation fault: QQmlDelegateModel::_q_layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint)

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|general |general
Product|plasmashell |plasma-nm
   Target Milestone|1.0 |---
   Assignee|k...@davidedmundson.co.uk|jgrul...@redhat.com

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

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

[Shawn Sörbom]

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

--- Comment #16 from Shawn Sörbom  ---
Bug Still exists in Plasma 5.13.5, Applications 18.08.1

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

[okular] [Bug 398334] Okular crashes while un/re highlighting PDF file

[T . Zack Crawford]

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

T. Zack Crawford  changed:

   What|Removed |Added

Summary|Okular crashes while|Okular crashes while un/re
   |highlighting PDF file   |highlighting PDF file

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

[kopete] [Bug 393662] Kopete Crashes on Program exit

[Shawn Sörbom]

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

--- Comment #2 from Shawn Sörbom  ---
Bug still exists in kopete version 18.08.1, Plasma 5.13.5. No change in
behavior.

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

[okular] [Bug 398334] New: Okular crashes while highlighting PDF file

[T . Zack Crawford]

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

Bug ID: 398334
   Summary: Okular crashes while highlighting PDF file
   Product: okular
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: t.z.crawf...@hotmail.com
  Target Milestone: ---

--Software Versions

Application: okular (1.5.1)
KDE Frameworks 5.49.0
Qt 5.11.1 (built against 5.11.1)
Operating System: 4.18.5-arch1-1-ARCH (Linux kernel 4.18.5)
Distribution: Arch Linux
Window manager: i3 (if that matters)
PDF Backend 0.6.5

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

An arbitrary highlightable pdf file was opened with okular (have tried opening
from both Okular>File>Open as well as from thunar and launching from zotero) 
The F6 button was pressed to open the review tool with the highlighter option
At least two separate sections of text were highlighted with the default yellow
highlighter. Doing this after highlighting only one section does not produce a
crash (at least not consistently).
CTRL+Z was pressed to undo the last highlighted text
Another section of text was then highlighted
Okular immediately crashes

- Custom settings of the application:

I have added a few extra colored highlighters to the review tool, but I can
make the crash occur using the default yellow highlighter only. Seems not
relevant to the bug.

-- Backtrace:

Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efbf7a52800 (LWP 12111))]

Thread 9 (Thread 0x7efbdaffd700 (LWP 12123)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7efbdb7fe700 (LWP 12122)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7efbdbfff700 (LWP 12121)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7efbe0f53700 (LWP 12120)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7efbe1754700 (LWP 12119)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7efbe1f55700 (LWP 12118)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7efbe2897700 (LWP 12117)):
#0  0x7efbfca8aafc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7efbe77c9404 in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7efbe77c90f8 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7efbfca84a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7efbfdb1fa43 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7efbefde4700 (LWP 12116)):
#0  0x7efbfdb14bb1 in poll () from /usr/lib/libc.so.6
#1  0x7efbfb67dec0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7efbfb67dfee in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7efbfe03e4a9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7efbfdfe9dac in
QEventLoop::exec(QFlags) () from

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Jeff Hodd]

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

--- Comment #31 from Jeff Hodd  ---
Will do.

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Eike Hein]

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

--- Comment #30 from Eike Hein  ---
That seems to be another misunderstanding then. I want you to open a new ticket
on bugs.kde.org.

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

[Plasma Vault] [Bug 398323] Add gocryptfs support

[Ivan Čukić]

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

Ivan Čukić  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Ivan Čukić  ---
gocrypt almost became the (future) default backend when we had some problems
with cryfs.

Nowadays, cryfs is well maintained, and I'm in contact with its main developer
/ maintainer. And cryfs got quite a few neat features for GUIs like Plasma
Vault to use.

gocrypt (the last time I checked it out) did not seem to have been designed to
be used from a wrapper. One thing I remember is that depending on how it was
compiled, it sometimes reported its version and sometimes not.

I'm not going to close this report because I think gocrypt backend should be
implemented at some point, but it is not a very low priority task at the
moment.

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Jeff Hodd]

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

--- Comment #29 from Jeff Hodd  ---
Yeah, but I don;t think it's a thunderbird bug, either, since the same
behaviour crops up in other apps. That was kinda my response to your comment.

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

[krita] [Bug 398333] New: Selection mode cursors not updating when using shortcuts

[mvowada]

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

Bug ID: 398333
   Summary: Selection mode cursors not updating when using
shortcuts
   Product: krita
   Version: git master
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it
  Target Milestone: ---

Created attachment 114816
  --> https://bugs.kde.org/attachment.cgi?id=114816=edit
Video

(Ubuntu 14.04, Unity - Krita Appimage 4.2.0-pre-alpha (git 65a1598))

Hi and thanks for this useful feature :)
It seems that the cursor icons (+/-) are not updating when using the key
shortcuts:

1. add to a selection
2. press the "ALT" key (subtract)

Actual Results: the cursor is "+"
Expected Results: cursor "-"? 

(original wishbug: Bug 385861)

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

[digikam] [Bug 398331] xmp sidecar files are not reloaded on change

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This is a duplicate of bug 397340 and bug 339342. Yes, the sidecar file is not
stored in the database, we can not know if it has changed.

Maik

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Eike Hein]

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

--- Comment #28 from Eike Hein  ---
And that's why I wrote comment #21 earlier ...

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Jeff Hodd]

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

--- Comment #27 from Jeff Hodd  ---
OK. I understand. Thunderbird and QTransmission do conform to expected
behaviour then.

However, both also display the same odd launcher behaviour Michail describes,
and they do not appear to fall into the same category as the gimp bug.

Do we have yet a 3rd class of bug here then?

I inserted myself into this thread after emailing Michail about the annoying
thunderbird behaviour, which is made more annoying since I run it at all times
throughout all my sessions. He pointed me in this direction, but apparently we
have a case of same strange behaviour, different bug.

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

[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off

[Andrew Crouthamel]

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

--- Comment #37 from Andrew Crouthamel  ---
(In reply to Nate Graham from comment #34)
> Created attachment 114800 [details]
> Network KCM looks fine to me now
> 
> I'm attaching an image of what `kcmshell5 kcm_networkmanagement` shows at 1x
> scaling for me now. Looks fine to me. Andrew and bugseforuns, can you
> confirm that this is what it looks like for you at 1x? If it looks bad at >
> 1x, that's a separate bug, or an issue with the patch that we didn't catch
> (oops), in which case we should track that with a new bug.

I confirm it looks OK at 1x. 2x I get scrollbars.

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

[plasmashell] [Bug 398332] New: Plasma (plasmashell), signal: Segmentation fault: QQmlDelegateModel::_q_layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint)

[Don Curtis]

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

Bug ID: 398332
   Summary: Plasma (plasmashell), signal: Segmentation fault:
QQmlDelegateModel::_q_layoutChanged(QList const&,
QAbstractItemModel::LayoutChangeHint)
   Product: plasmashell
   Version: 5.12.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugrprt21...@online.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.6)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.12.14-lp150.12.16-default x86_64
Distribution: "openSUSE Leap 15.0"

-- Information about the crash:
- What I was doing when the application crashed:
Renewing the Network Manager WLAN entries -- the Plasma crash doesn't seem to
have affected the interaction with KWallet …

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

Thread 9 (Thread 0x7f70a1fea700 (LWP 13241)):
#0  0x7f716b90065d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f716b90103b in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f716b90121c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f71719c4c0b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f709c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f717196d09a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f70a1fe9c50, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f717179c4da in QThread::exec() (this=) at
thread/qthread.cpp:515
#6  0x7f70a4903f67 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f71717a10ce in QThreadPrivate::start(void*) (arg=0x55c7f6528fb0) at
thread/qthread_unix.cpp:368
#8  0x7f717093a559 in start_thread () at /lib64/libpthread.so.0
#9  0x7f717109382f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f70c1db1700 (LWP 13227)):
#0  0x7f717094089d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f70c67f3ceb in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f70c67f3a17 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f717093a559 in start_thread () at /lib64/libpthread.so.0
#4  0x7f717109382f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f70c25b2700 (LWP 13226)):
#0  0x7f717094089d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f70c67f3ceb in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f70c67f3a17 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f717093a559 in start_thread () at /lib64/libpthread.so.0
#4  0x7f717109382f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f7151562700 (LWP 13214)):
#0  0x7f717094089d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f71774165e4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f7177416629 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f717093a559 in start_thread () at /lib64/libpthread.so.0
#4  0x7f717109382f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f71533b2700 (LWP 13185)):
#0  0x7f717108908b in poll () at /lib64/libc.so.6
#1  0x7f716b901109 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f716b90121c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f71719c4c0b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f7148000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f717196d09a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f71533b1c70, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f717179c4da in QThread::exec() (this=) at
thread/qthread.cpp:515
#6  0x7f7175081cb5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f71717a10ce in QThreadPrivate::start(void*) (arg=0x55c7f4e2ccf0) at
thread/qthread_unix.cpp:368
#8  0x7f717093a559 in start_thread () at /lib64/libpthread.so.0
#9  0x7f717109382f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f7158fea700 (LWP 13168)):
#0  0x7f716b946759 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f716b9010ce in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f716b90121c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f71719c4c0b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f714c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f717196d09a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f7158fe9c70, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f717179c4da in QThread::exec() (this=) at
thread/qthread.cpp:515
#6  0x7f7175081cb5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f71717a10ce in QThreadPrivate::start(void*) (arg=0x55c7f503b730) at

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Eike Hein]

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

--- Comment #26 from Eike Hein  ---
It's quite OK and expected for the two components of WM_CLASS to be
substantially different. In general the relevant one for identification
purposes is only the second string, which should match a .desktop file name or
the value of a .desktop file's StartupWMClass key (the Task Manager also tries
many other things to identify apps beyond that, if apps get this wrong). The
issue with LO6 is that this second string changes during startup from something
generic no .desktop file exists for (and that doesn't match the launcher) to
the eventual one that does.

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Jeff Hodd]

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

--- Comment #25 from Jeff Hodd  ---
I understand that wm_class contains 2 strings, but, for example, "caprine" and
"Caprine" are a different difference than "Mail" and "Thunderbird", or
"transmission-qt" and "transmission". I've been using Michail's software for
quite some time and I'm seeing fairly consistently that the odd launcher
behaviour he describes occurs with apps that have fundamentally differently
wm_class strings. Perhaps I'm not fully understanding the issue, but I am
contributing my observations.

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

[digikam] [Bug 398331] xmp sidecar files are not reloaded on change

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Metadata-Engine |Metadata-Sidecar
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 398331] New: xmp sidecar files are not reloaded on change

[Daniel Laidig]

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

Bug ID: 398331
   Summary: xmp sidecar files are not reloaded on change
   Product: digikam
   Version: 6.0.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: lai...@kde.org
  Target Milestone: ---

I set up digikam to write metadata only to xmp sidecar files and also checked
"Rescan file when files are modified". However, changes in xmp sidecar files
are not detected (not when digiKam is running and also not when restarting it).

Reloading metadata works when the actual image is changed:
exiv2 -M"set Xmp.xmp.Rating 3" IMG.JPG
-> Rating is instantly updated in digiKam.

When setting a rating in digikam and then using a text editor to change
xmp:Rating in the xmp sidecar, the rating is not updated automatically. When
triggering "Reread Metadata From File" manually or running "touch IMG.JPG", the
rating is updated.

Due to the last observation I would guess that the mtime of the xmp file is
currently not stored in the database.

Fixing this would make interoperability with other applications so much better.

(tested using the 6.0.0-beta1 AppImage, but also previously observed with
5.9.0)

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

[Discover] [Bug 398330] New: Discover Crashed immidiately after opening it

[Thunder]

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

Bug ID: 398330
   Summary: Discover Crashed immidiately after opening it
   Product: Discover
   Version: 5.12.6
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: thunderb...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.12.6)

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

-- Information about the crash:
- What I was doing when the application crashed:The update notifier applet
informed me I had updates available so I Clicked the update button in the
applet. I had just installed the nvidia proprietary drivers but not restarted
my computer yet.

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7fe3cd5da700 (LWP 20514)):
#0  0x7fe40bb479f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fe3c80376a0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe40bb479f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fe3c8037650, cond=0x7fe3c8037678) at pthread_cond_wait.c:502
#2  0x7fe40bb479f3 in __pthread_cond_wait (cond=0x7fe3c8037678,
mutex=0x7fe3c8037650) at pthread_cond_wait.c:655
#3  0x7fe40f93959b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fe40f931c0b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fe40fb458c8 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fe40d10ce1b in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#7  0x7fe40d1a2c9d in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#8  0x7fe40fb455b5 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fe40d102f41 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#10 0x7fe40d1036f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#11 0x7fe40fb455b5 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fe40d19ca2f in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#13 0x7fe40d19a690 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#14 0x7fe40d19aa3a in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#15 0x7fe40d17f381 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#16 0x7fe40fb455b5 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fe40d1497c3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#18 0x7fe40d149874 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#19 0x7fe40d15d721 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#20 0x7fe411dea82c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7fe411df20f4 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7fe40fb169a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fe40fb7054d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fe409a14287 in g_main_context_dispatch () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fe409a144c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7fe409a1454c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fe40fb6f90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fe40fb149ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7fe40f93322a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7fe40f93816d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7fe40bb416db in start_thread (arg=0x7fe3cd5da700) at
pthread_create.c:463
#32 0x7fe40f22e88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fe3dc864700 (LWP 20512)):
#0  0x7fe40bb47ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fe3dc863c40, expected=0, futex_word=0x7fe3d0006df4) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fe40bb47ed9 in __pthread_cond_wait_common (abstime=0x7fe3dc863d00,
mutex=0x7fe3d0006da0, cond=0x7fe3d0006dc8) at pthread_cond_wait.c:533
#2  0x7fe40bb47ed9 in __pthread_cond_timedwait (cond=0x7fe3d0006dc8,
mutex=0x7fe3d0006da0, abstime=0x7fe3dc863d00) at 

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Eike Hein]

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

--- Comment #24 from Eike Hein  ---
BTW, re-reading your comments on the ticket I think you're confused about the
xprop outout. WM_CLASS consists of two strings. I think you thought seeing two
strings means it changed. That is not the case. Thunderbird and qTransmission
(I use both myself) don't do what LO6 does.

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Eike Hein]

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

--- Comment #23 from Eike Hein  ---
There aren't any "dozens of apps" that do this.

What it comes down to is that this is neither a bug in the app nor is it a bug
in the Task Manager. Everything is in fact working correctly, it's just that
this application behavior is a very bad idea to implement if you want your app
to work nicely on a Task Manager.

Let's analyze:

- LO6 (I can't reproduce this with Thunderbird 60+ on my system BTW) changes
WM_CLASS on a window after initially showing it.

- We handle this WM_CLASS change just fine. We notice it and react to it and
take the appropriate steps.

- However: The decision "let's sort this window in where a matching launcher
was previously" is only done at the time a new window appears. It's not done
when the WM_CLASS changes later.


There's good reasos for this:

- Even if we decided to re-sort on the WM_CLASS change, the visual result would
still be poor (the icon would briefly show at the wrong location, before moving
to the right location).

- A WM_CLASS change can occur at any time, not just during early startup.
Clearly, randomly resorting the Task Manager at any time would not be a very
nice thing to for the user. Implementing generic behavior like "do change
sorting on the user, but only in the first second" starts to be a brittle
system.


There's exactly one hacky work-around that's sort of acceptable to implement,
and probably what we implement: Extend our rules system to allow writing a rule
like "if a new window matches this WM_CLASS, pretend the window doesn't exist
until it either changes WM_CLASS for the first time, or a timeout condition is
met". The visual result will then be that the launcher spins a little longer
until LO6 changes WM_CLASS, making it appear to launch a bit slower (although
the window is of course unaffected).

But make no mistake, that's yet another concession towars poorly-coded
applications that do something that they shouldn't be doing. And it requires
whitelisting and therefore manual curation and that makes us sad (at least it's
forward-compatible - when LO6 is fixed, the rule doesn't match anymore and the
TM can use the usual immediate mode).

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

[kate] [Bug 398289] Set "Open Terminal" by default to F4

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
+1 for enabling the plugin by default.

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

[kalzium] [Bug 398293] kalzium interface is missing parts

[Matt Fagnani]

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

Matt Fagnani  changed:

   What|Removed |Added

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

--- Comment #1 from Matt Fagnani  ---
I just had the thought that some file in my home directory might be affecting
kalzium's behaviour. So I ran sudo kalzium and all of kalzium's interface parts
showed up normally. I found ~/.config/kalziumrc which contained

[HTML Settings]
AutomaticDetectionLanguage=1

[KFileDialog Settings]
Recent
Files[$e]=porphyrin.cml,file:///usr/share/kalzium/data/molecules/porphyrin.cml
Recent URLs[$e]=file:///usr/share/kalzium/data/molecules/
Window-Maximized 768x1024=true

[MainWindow]
Height 768=341
MenuBar=Disabled
State=/wD9AgD6AAACJvwCAfseAGsAYQBsAHoAaQB1AG0ALQBzAGkAZABlAGIAYQByAEImrgEAAAMDAAAEAFH8AQL7IgBrAGEAbAB6AGkAdQBtAC0AdABhAGIAbABlAGkAbgBmAG8AAP8AAACHAQAAA/scAGsAYQBsAHoAaQB1AG0ALQBsAGUAZwBlAG4AZAAEAGABAAADAAAB/UIEBAgI/AECAQAAABYAbQBhAGkAbgBUAG8AbwBsAEIAYQByAAD/AAA=
StatusBar=Disabled
ToolBarsMovable=Disabled
Width 1024=508
Window-Maximized 768x1024=true

I'm guessing the MenuBar=Disabled, StatusBar=Disabled, and maybe State were
behind the missing menu and other parts. After I renamed that file to
~/.config/kalziumrc.backup and ran kalzium as my user all the parts showed up
normally. I'm not sure how the kalziumrc config file got into that state, but
it was last modified on August 31 when I tested kalzium related to the
avogadro2-1.91.0 update issue. I'm sorry about the mixup. The problem is
resolved.

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

[frameworks-kirigami] [Bug 398303] GridViewKCM: double-clicking on a delegate should select it and then apply

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
My thought was that this could just be a hidden accelerator, and wouldn't need
explicit documentation. I found myself instinctively double-clicking delegates
in these KCMs to insta-apply and was slightly disappointed when it didn't work.
It's particularly useful when you want to rapidly iterate through visual
options to see what they look like. In practice, I don't think it would be a
big problem to apply other un-applied changes (in most case there wouldn't be
any), though. If you feel differently, maybe it could throw away other
un-applied changes if that's feasible?

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

[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager

[Jeff Hodd]

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

--- Comment #22 from Jeff Hodd  ---
I'm not convinced this is a thunderbird bug or a libre-office bug, or, for that
matter, a bug in the dozens of other apps where this issue manifests. This is
far more likely to be an issue with plasmashell:taskmanager or some other DE
component (windowmanager?) that's not providing the ability to reconcile
changes to wm_class - it was indeed pointed out that apps can and do change
wm_class, so I doubt this will be viewed as a bug at the app level.

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

[plasmashell] [Bug 397779] Navigating search result for apps require double-pressing of arrow buttons

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.12.7

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

[plasmashell] [Bug 397779] Navigating search result for apps require double-pressing of arrow buttons

[Øystein Steffensen-Alværvik]

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

--- Comment #7 from Øystein Steffensen-Alværvik  ---
Cheers!

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

[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off

[Dr . Chapatin]

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

--- Comment #36 from Dr. Chapatin  ---
Created attachment 114815
  --> https://bugs.kde.org/attachment.cgi?id=114815=edit
Network kcm on neon dev unstable. Hidden buttons on bottom.

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

[okular] [Bug 398326] Letter ž is displayed as š instead

[David Hurka]

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

--- Comment #4 from David Hurka  ---
Well, I’ve just installed Tahoma and now it’s displayed fine.

My Okular action “About Backends” doesn’t work, but in aptitude I have
libpoppler 0.41.

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

[okular] [Bug 398326] Letter ž is displayed as š instead

[bugzilla_noreply]

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

--- Comment #3 from gal...@gmail.com ---
I didn't have Tahoma and I've just installed it and now I've got the same
situation as David https://bugsfiles.kde.org/attachment.cgi?id=114814

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

[okular] [Bug 398326] Letter ž is displayed as š instead

[Yuri Chornoivan]

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

Yuri Chornoivan  changed:

   What|Removed |Added

 CC||yurc...@ukr.net

--- Comment #2 from Yuri Chornoivan  ---
Works fine here ("Žiro račun:" is shown correctly, Okular 1.5.70, poppler
0.52).

Do you have Tahoma fonts installed?

Thanks in advance for your answer.

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

[okular] [Bug 398326] Letter ž is displayed as š instead

[David Hurka]

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

David Hurka  changed:

   What|Removed |Added

 CC||david.hu...@mailbox.org

--- Comment #1 from David Hurka  ---
Created attachment 114814
  --> https://bugs.kde.org/attachment.cgi?id=114814=edit
Letters displayed differently than expected in Okular

In my Okular (1.5.0 on KDE Neon 5.13), several capital letters are displayed
wrong.

Does it happen in other PDF files too? It’s possible to change the
appearance/meaning of letters in PDF files, so that copying produces other
letters.

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

[krita] [Bug 396199] Workspaces are slightly distorted when the program is first turned on.

[Creta Park]

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

--- Comment #6 from Creta Park  ---
How about loading Workspace after Krita is run? I think might be possible.

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

[Akonadi] [Bug 397979] akonadi,permanently, disk write, a mean of 1.2 Mb

[Philippe ROUBACH]

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

--- Comment #4 from Philippe ROUBACH  ---
akonadi consumes 25 % cpu power during several hours for example from five pm
to 12 pm

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

[Akonadi] [Bug 397979] akonadi,permanently, disk write, a mean of 1.2 Mb

[Philippe ROUBACH]

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

--- Comment #3 from Philippe ROUBACH  ---
Created attachment 114813
  --> https://bugs.kde.org/attachment.cgi?id=114813=edit
akonadi consumes 25 % cpu power

when akonadi stops making numerous disk accesses after several days
then
akonadi consumes 25 % cpu power

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

[krita] [Bug 318340] Brush options docker to access more sliders

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|CONFIRMED   |RESOLVED

--- Comment #8 from Boudewijn Rempt  ---
We put the sliders in the popup, not in a docker. Closing this wish.

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

[frameworks-kio] [Bug 397742] Silent data loss when using a program that deletes and re-creates the document after every save operation when the document is located on a samba share accessed with KIO/

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Silent data loss when using |Silent data loss when using
   |a program that deletes and  |a program that deletes and
   |re-creates the document |re-creates the document
   |after every save operation  |after every save operation
   |when the document is|when the document is
   |located on a samba share|located on a samba share
   |mounted with GNOME's gvfs   |accessed with KIO/Dolphin

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

[krita] [Bug 360454] Load reference images over the network

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UNMAINTAINED

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

[krita] [Bug 374674] Fill to selected layer

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|Dockers |Tools
 CC||b...@valdyas.org

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

[krita] [Bug 397400] Masking reference pictures

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|Dockers |Tools/Reference Images
 CC||b...@valdyas.org

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

[frameworks-kio] [Bug 397742] Silent data loss when using a program that deletes and re-creates the document after every save operation when the document is located on a samba share mounted with GNOME

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.51

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

[marble] [Bug 398329] New: Build fails without Qt 5.5, due to QItemSelectionModel.setModel, cmake tests for 5.3

[John Drinkwater]

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

Bug ID: 398329
   Summary: Build fails without Qt 5.5, due to
QItemSelectionModel.setModel, cmake tests for 5.3
   Product: marble
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: j...@nextraweb.com
  Target Milestone: ---

Check’d out the master branch, and it failed to build:

```
[  2%] Building CXX object
src/lib/marble/CMakeFiles/marblewidget.dir/MarbleModel.cpp.o
/home/john/code/marble/src/lib/marble/MarbleModel.cpp: In constructor
‘Marble::MarbleModelPrivate::MarbleModelPrivate()’:
/home/john/code/marble/src/lib/marble/MarbleModel.cpp:111:35: error: ‘class
QItemSelectionModel’ has no member named ‘setModel’
 m_placemarkSelectionModel.setModel(_placemarkProxyModel);
   ^
src/lib/marble/CMakeFiles/marblewidget.dir/build.make:10527: recipe for target
'src/lib/marble/CMakeFiles/marblewidget.dir/MarbleModel.cpp.o' failed
make[2]: *** [src/lib/marble/CMakeFiles/marblewidget.dir/MarbleModel.cpp.o]
Error 1
CMakeFiles/Makefile2:1200: recipe for target
'src/lib/marble/CMakeFiles/marblewidget.dir/all' failed
```

This is because my installed Qt5 is 5.4.2, and apparently this method was added
in 5.5 according to docs.

CMakeLists.txt tests for 5.3.0, which is why cmake didn’t fail:

set(REQUIRED_QT_VERSION 5.3.0)

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

[krita] [Bug 347799] The color sampler rotates with the canvas

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|General |Tools

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

[krita] [Bug 386488] Subwindow mode: minimizing/restoring or maximizing/unmaximizing file with unsaved changes makes titlebar asterisk (*) disappear

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|General |Usability

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

[krita] [Bug 384110] Shift-drag brush size change doesn't work for inpaint

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
  Component|General |Tool/Smart Patch

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

[krita] [Bug 397853] Window Background color setting decreases each time settings are opened and saved

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
  Component|General |Usability

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

[krita] [Bug 347874] Drawing area flashes random section of the alpha layer

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|General |Layer Stack

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

[krita] [Bug 352205] shortcut ctrl+w cannot be reassigned from default action

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|shortcuc ctrl+w cannot be   |shortcut ctrl+w cannot be
   |reassigned from default |reassigned from default
   |action  |action

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

[krita] [Bug 352205] shortcut ctrl+w cannot be reassigned from default action

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|General |Shortcuts and Canvas Input
   ||Settings

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

[krita] [Bug 356153] Tool Options Drop-Down locked into top left corner of the screen when detached on Windows 8.1

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|General |Usability

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