[okular] [Bug 415340] Crash when closing print preview dialog on Linux

[Oliver Sander]

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

Oliver Sander  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||oliver.san...@tu-dresden.de
 Ever confirmed|0   |1

--- Comment #4 from Oliver Sander  ---
Indeed.  For me it even crashes when *opening* the print preview.

A fix for this should be accompagnied by a unit test.

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

[dolphin] [Bug 415281] Dlophin shows full remote path in side panel for NFS shares instead of local name

[Méven Car]

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

--- Comment #3 from Méven Car  ---
The issue is that in the place view we currently display

/which/folder/is/mount on ipfrom

But the bug reporter would like either by default or with a setting to it as:

/mounted/on

This is perfectly doable, but I wonder about the opportunity.
An opinion Nate ?

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

[kmail2] [Bug 415254] [regression] HTML viewer complains about "external references to images etc." when there are no images

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit|https://commits.kde.org/mes |https://commits.kde.org/mes
   |sagelib/56f1d42f68ed2f597fc |sagelib/b551d400afe823b4357
   |599e4952ee81e579cd355   |b9e3a0ed7ba233e27a77e
 Status|REOPENED|RESOLVED

--- Comment #7 from Laurent Montel  ---
Git commit b551d400afe823b4357b9e3a0ed7ba233e27a77e by Laurent Montel.
Committed on 19/12/2019 at 07:22.
Pushed by mlaurent into branch 'release/19.12'.

Fix Bug 415254 - [regression] HTML viewer complains about "external references
to images etc." when there are no images

FIXED-IN: 5.13.1

M  +0-3messageviewer/src/utils/autotests/messageviewerutilstest.cpp
M  +23   -4messageviewer/src/utils/messageviewerutil.cpp

https://commits.kde.org/messagelib/b551d400afe823b4357b9e3a0ed7ba233e27a77e

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

[okular] [Bug 415332] Okular does not show the dialogue to let me load a file

[bugzilla_noreply]

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

--- Comment #3 from adalbert.hans...@gmx.de ---
(In reply to Albert Astals Cid from comment #2)
> Are you saying that you did some crazy copying of snap stuff by hand, things
> don't work and now you're opening a bug?

If you call this crazy: yes, I did so. This method worked well before (with
~/.kde/share/config/okularpartrc) and I only noticed that this is a snap
install after it did not work. First I tried to copy the whole directory
~/.kde/share/config/ to my place (followed by chowning it) and after that did
not work, I changed one pen and looked for files that had changed in the last
minutes. Then I found out that this is a snap install and that the proper place
must have been ~/snap/okular/63/.config/okularrc. Since I had copied the whole
surrounding, I did so with the whole directory ~/snap/okular/63/.config/.

The presence of ~/.kde/share/config/okularpartrc despite the snap installation
now was a leftover from before, when okular was running under Xubuntu 16.03.
/home lives on a separate partition, so upgrading the operating system
maintained all my files and the settings of all programs - if they were not
destroyed in the new installation of my application programs. Most of them kept
 existing settings untouched.

By the way: copying the whole set of annotation pen definitions worked well, it
is just the strange thing with the file>open file command which is missing its
dialogue.

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

[krita] [Bug 414890] Palette Docker does not show swatches 9 Version: 4.3.0-prealpha (git 818c841)

[vanyossi]

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

vanyossi  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://invent.kde.org/kde/
   ||krita/commit/ef55574a4af751
   ||34a2a9be03fcd70e8b16aaf614
 Resolution|--- |FIXED

--- Comment #2 from vanyossi  ---
Git commit ef55574a4af75134a2a9be03fcd70e8b16aaf614 by Ivan Yossi.
Committed on 19/12/2019 at 07:05.
Pushed by ivany into branch 'master'.

Fix PaletteDocker not showing palettes

Reverts 97c03e0f3314dae5520deb901dda73d1cf8df201

 "-1" is a QMap key to signal "root group"

Changed Q_ASSERT to KIS_ASSERT_RECOVER_RETURN_VALUE to
try and avoid crashing if Qt is compiled in debug mode.

M  +2-5libs/widgets/KisPaletteModel.cpp

https://invent.kde.org/kde/krita/commit/ef55574a4af75134a2a9be03fcd70e8b16aaf614

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

[dolphin] [Bug 415281] Dlophin shows full remote path in side panel for NFS shares instead of local name

[Méven Car]

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

Méven Car  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Méven Car  ---
I reproduce it.

It is not related to my recent NFS share fix :
https://phabricator.kde.org/D21204

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

[plasmashell] [Bug 414935] Pager widget with dual monitors only shows outline of apps for left monitor

[Markus]

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

Markus  changed:

   What|Removed |Added

 CC||m4rkus...@web.de

--- Comment #3 from Markus  ---
It was solved by recent update of frameworks 5.65 for me. How about you?

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

[plasmashell] [Bug 413224] plasma - control bar - desktop switcher - resized font when moving window

[Markus]

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

--- Comment #2 from Markus  ---
Still valid for plasma 5.17.4 / frameworks 5.65 / qt 5.13.2.

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

[plasmashell] [Bug 414907] [regression] plasma - control bar - desktop switcher - only shows windows of secondary screen

[Markus]

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

--- Comment #2 from Markus  ---
Updated to frameworks 5.65 yesterday. Now it works again for me.

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

[okular] [Bug 415340] Crash when closing print preview dialog on Linux

[jimbo1qaz]

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

--- Comment #3 from jimbo1qaz  ---
PageView::capability() did not call methods on d->ptr until commit
bd25d17e704ed4bfed8e0db1dd233fe584fa96ef, which I think introduced the crash.

>Save view information per file
>
>Adds the functionality to save the view mode (single page, facing...),
>continuous scrolling, and margin trimming  to the document information,
>as it is already done with the zoom information.

https://cgit.kde.org/okular.git/commit/?id=bd25d17e704ed4bfed8e0db1dd233fe584fa96ef
https://github.com/KDE/okular/commit/bd25d17e704ed4bfed8e0db1dd233fe584fa96ef

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

[okular] [Bug 415340] Crash when closing print preview dialog on Linux

[jimbo1qaz]

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

--- Comment #2 from jimbo1qaz  ---
The crash occurs after ~FilePrinterPreview finishes, while unwinding
FilePrinterPreview's Qt child widgets (via QObjectPrivate::deleteChildren).

Okular::Part::~Part calls Okular::Document::closeDocument calls
d->saveDocumentInfo().

void DocumentPrivate::saveDocumentInfo() const
{
...
for ( View *view : qAsConst(m_views) )
{
QDomElement viewEntry = doc.createElement( QStringLiteral("view") );
viewEntry.setAttribute( QStringLiteral("name"), view->name() );
viewsNode.appendChild( viewEntry );
saveViewsInfo( view, viewEntry );
}


void DocumentPrivate::saveViewsInfo( View *view, QDomElement  ) const
{
...
const bool mode = view->capability( View::Continuous ).toBool();

QVariant PageView::capability( ViewCapability capability ) const
{
switch ( capability )
{
...
case Continuous:
return d->aViewContinuous->isChecked();

## Null pointers

The problem is that PageView::d's member pointers are mostly nullptr (assigned
by the constructor). This is what causes the crash.

Is the PageViewPrivate of a print preview document supposed to contain many
nullptr, or should the pointers be initialized through
PageView::setupViewerActions()? (This method constructs QAction and whatnot.
Maybe it makes no sense to initialize them to QAction/etc, since the print
preview dialog has no buttons.)

## Operating on null pointers.

I'm suspicious that Okular::Document::closeDocument unconditionally calls
DocumentPrivate::saveDocumentInfo() (which leads to the crash). Is it necessary
to save the info of a print-preview document? (It crashes if
PageView::setupViewerActions() has not been called.)

The hacky workaround is to patch PageView::capability() to return some dummy
value instead of dereferencing null pointers.

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

[krita] [Bug 414890] Palette Docker does not show swatches 9 Version: 4.3.0-prealpha (git 818c841)

[vanyossi]

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

vanyossi  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com
 CC||ghe...@gmail.com

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

[konsole] [Bug 415249] Tab goes unresponsive if copying in tmux copy mode

[bugzilla_noreply]

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

adorkablue1...@outlook.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||adorkablue1...@outlook.com
 Status|REPORTED|CONFIRMED

--- Comment #1 from adorkablue1...@outlook.com ---
Confirmed.

SOFTWARE/OS VERSIONS (Archlinux packages)
Linux: 5.4.4-zen1-1-zen / Arch Linux
KDE Plasma Version: 5.17.4-2
KDE Frameworks Version: 5.64.0-1
Qt Version: 5.13.2-3

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

[okular] [Bug 415340] Crash when closing print preview dialog on Linux

[jimbo1qaz]

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

--- Comment #1 from jimbo1qaz  ---
Okular 78cf6bd910aa2dfeb55ea110a1d0423fc54f58a5 via AUR okular-git.

Running with valgrind causes okular to crash as soon as I open a document. Is
this a false positive?

I managed to build Okular with `-fsanitize=address,undefined
-fno-sanitize=vptr`. (Omitting -fno-sanitize results in a nondescript linking
error like `undefined reference to `typeinfo for MyObject'`. I eventually found
https://stackoverflow.com/a/48322000 which mentions that the vptr sanitizer is
incompatible with RTTI off.)

The resulting asan Okular does not crash as soon as I open a document, nor when
I open print preview. It prints the following message when I close print
preview:

/home/nyanpasu64/aur/okular-git/src/okular/ui/pageview.cpp:1595:49: runtime
error: member access within null pointer of type 'struct KToggleAction'
/home/nyanpasu64/aur/okular-git/src/okular/ui/pageview.cpp:1595:49: runtime
error: member call on null pointer of type 'struct QAction'

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

[krita] [Bug 414274] Frame by Frame and Onion Skin Fault

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #6 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 414810] Bug in selection tool

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kate] [Bug 414235] "Defocus Terminal" does not work

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 414691] Wrong image selected when dragging and dropping reference images

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[systemsettings] [Bug 414188] System Settings Application Style Adwaita-Dark crash Colors (choose colors scheme).

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[print-manager] [Bug 414658] KDE does no longer print except text files with Kate since Plasma 5.17.3

[Bug Janitor Service]

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

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 414622] Canvas Only and Toolbar Visibility - Visibility toggle Bug

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[KScreen] [Bug 413995] Display Bug

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 414583] growing selection often results in rotating canvas also

[Bug Janitor Service]

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

--- Comment #3 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[ktimetracker] [Bug 344516] Fictional time on records

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #9 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 414165] Compilation error with sizeInBytes()

[Vincent PINON]

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

Vincent PINON  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|FIXED   |---

--- Comment #3 from Vincent PINON  ---
Would you share your patch if you still have it?
Maybe other users would like to take that "risk" (I'm OK to publish it in the
PPA...)

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

[kwin] [Bug 414626] kwin_wayland on DisplayLink/udl turns screen off, and back on every frame

[bugzilla_noreply]

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

--- Comment #1 from bluescreenaven...@gmail.com ---
I am willing to test with adding debug lines in places, trying workarounds,
etc.
It happens every time a frame changes. I can open say, Konsole, and the screen
will flash every time I move the cursor, or every time I type a letter into
Konsole

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

[okular] [Bug 415340] New: Crash when closing print preview dialog on Linux

[jimbo1qaz]

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

Bug ID: 415340
   Summary: Crash when closing print preview dialog on Linux
   Product: okular
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: jimbo1...@protonmail.com
  Target Milestone: ---

Application: okular (1.9.70)

Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 5.4.3-1-MANJARO x86_64
Distribution: Manjaro Linux

-- Information about the crash:
- Open any file (.pdf or .md).
- Under File menu, open print preview dialog.
- Close print preview dialog.

Okular segfaults.

The crash can be reproduced every time.

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

Thread 18 (Thread 0x7fac48c93700 (LWP 141635)):
#0  0x7fac899e6e9d in syscall () from /usr/lib/libc.so.6
#1  0x7fac89d648f2 in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#2  0x7fac480d77c2 in GSRendererThread::run (this=0x564b8a87c580) at
/home/nyanpasu64/aur/okular-git/src/okular/generators/spectre/rendererthread.cpp:50
#3  0x7fac89d62530 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 17 (Thread 0x7fac497fa700 (LWP 141623)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 16 (Thread 0x7fac49ffb700 (LWP 141622)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 15 (Thread 0x7fac4a7fc700 (LWP 141621)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 14 (Thread 0x7fac4affd700 (LWP 141620)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7fac4b7fe700 (LWP 141619)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7fac4bfff700 (LWP 141618)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 11 (Thread 0x7fac68ff9700 (LWP 141617)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7fac697fa700 (LWP 141616)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from /usr/lib/dri/radeonsi_dri.so
#2  0x7fac76dd4088 in ?? () from /usr/lib/dri/radeonsi_dri.so
#3  0x7fac88f2e4cf in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fac899ec2d3 in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7fac69ffb700 (LWP 141615)):
#0  0x7fac88f34c45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fac76dd448c in ?? () from 

[Akonadi] [Bug 415339] Akonadi IMAP crashed on waking up from sleep

[Bedouin]

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

Bedouin  changed:

   What|Removed |Added

Version|unspecified |5.13.0

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

[Akonadi] [Bug 415339] New: Akonadi IMAP crashed on waking up from sleep

[Bedouin]

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

Bug ID: 415339
   Summary: Akonadi IMAP crashed on waking up from sleep
   Product: Akonadi
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-b...@kde.org
  Reporter: slamet.ba...@gmail.com
  Target Milestone: ---

Application: akonadi_imap_resource (5.13.0 (19.12.0))
 (Compiled from sources)
Qt Version: 5.12.5
Frameworks Version: 5.65.0
Operating System: Linux 5.3.16-300.fc31.x86_64 x86_64
Distribution: "Fedora release 31 (Thirty One)"

-- Information about the crash:
- What I was doing when the application crashed:
Wake up from sleep state, it showed a DrKonqi notification about the crash.

- Unusual behavior I noticed:
There was another notification about selinux-policy that prevents "tlp" to
search for "snapd" (this info may not related though)

- Custom settings of the application:
Kmail was set to Enable system tray icon to be enabled

-- Backtrace:
Application: badwi.my.id (boku) (akonadi_imap_resource), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc98ce38940 (LWP 1565))]

Thread 7 (Thread 0x7fc95bfff700 (LWP 626426)):
#0  0x7fc997baaa08 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fc997b5dd0d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7fc997b5e6cb in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fc997b5e8d3 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fcc1da3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fc6bcfb in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fc9997c43a5 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fc9997c54f6 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fc9989584e2 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc99942c693 in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc975d29700 (LWP 1693)):
#0  0x7fc999421a6f in poll () at /lib64/libc.so.6
#1  0x7fc997b5e79e in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc997b5e8d3 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fcc1da3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fc6bcfb in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fc9997c43a5 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fc9997c54f6 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fc9989584e2 in start_thread () at /lib64/libpthread.so.0
#8  0x7fc99942c693 in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc976f3a700 (LWP 1651)):
#0  0x7fc99b6adfed in __tls_get_addr_slow () at /lib64/ld-linux-x86-64.so.2
#1  0x7fc99b6b2fbc in __tls_get_addr () at /lib64/ld-linux-x86-64.so.2
#2  0x7fc9997c4a9a in QThreadData::current(bool) () at
/lib64/libQt5Core.so.5
#3  0x7fcc1c5e in postEventSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#4  0x7fc997b5dd1a in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#5  0x7fc997b5e6cb in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#6  0x7fc997b5e8d3 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#7  0x7fcc1da3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#8  0x7fc6bcfb in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#9  0x7fc9997c43a5 in QThread::exec() () at /lib64/libQt5Core.so.5
#10 0x7fc9997c54f6 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#11 0x7fc9989584e2 in start_thread () at /lib64/libpthread.so.0
#12 0x7fc99942c693 in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc97c923700 (LWP 1648)):
#0  0x7fc999421a6f in poll () at /lib64/libc.so.6
#1  0x7fc997b5e79e in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc997b5e8d3 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fcc1da3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fc6bcfb in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fc9997c43a5 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fc99aa2cf4a in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fc9997c54f6 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fc9989584e2 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc99942c693 in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc97d4df700 (LWP 1637)):
#0  0x7fc99895ed45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc97e37014b in util_queue_thread_func () at

[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update

[Ralf]

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

--- Comment #15 from Ralf  ---
System: Apple Macbook 12” (2017)
OS: macOS Mojave 10.14.6
VM software: VMware Fusion 11.5.1

More testing. I have an existing Manjaro KDE VM:

KDE Plasma: 5.17.4
KDE Frameworks: 5.64.0
Qt Version: 5.13.2
Kernel Version: 5.4.2-1-MANJARO
OS Type: 64-bit

that ehibits this (800x600) on every boot. My notes from this summer indicate a
workaround. To fix in-session, do:

systemctl stop vmtoolsd.service
systemctl start vmtoolsd.service

To fix it "for good," edit:

/usr/lib/systemd/system/vmtoolsd.service

adding:

After=display-manager.service

At the end of the [Unit] section.

Then resolutions (including HiDPI) can be set as usual. The in-session fix
still works and could probably be scripted, but the “permanent” fix above only
works sometimes! It failed all today day and then when I rebooted just now it
worked again. Sigh.

The above workarounds and “fixes” are from a discussion of the bug in the
Manjaro forums:
https://forum.manjaro.org/t/vmware-cant-change-screen-resolution/89090

This would seem to be a bug at the intersection of Plasma, VMware and Open VM
Tools. Hope these data points help in some way.

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

[plasmashell] [Bug 415338] New: In Application Launcher (start menu), moving mouse along bottom of menu when you start typing causes search results to disappear

[jimbo1qaz]

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

Bug ID: 415338
   Summary: In Application Launcher (start menu), moving mouse
along bottom of menu when you start typing causes
search results to disappear
   Product: plasmashell
   Version: 5.17.4
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: jimbo1...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
if i move my mouse over the bottom tabs while typing into the search bar, it
doesn't show the search results

STEPS TO REPRODUCE
1. Press Super or click on the application launcher icon, to open the "start
menu".
2. Move your mouse over the bottom tabs, then start typing into the Search...
field. (The exact order doesn't matter. Your mouse needs to be moving right
after the first keystroke.)

OBSERVED RESULT
The first keystroke causes Application Launcher to switch to search results,
and start hiding the bottom tabs. However, at first, the bottom tabs still
respond to mouse movement (which causes it to switch from search results to
tabs). After half a second or so, the bottom tabs disappear, and you're stuck
on one tab which doesn't respond to the search bar.

This appears to be a race condition between "switch to search tab and hide
tabs", but tabs still respond to mouse input.

EXPECTED RESULT
Typing while the mouse is moving over the bottom tabs does not switch to a
different tab and ignore the contents of the search field. Perhaps the first
keystroke into the search bar should cause the bottom tabs to *immediately*
ignore mouse-hover events, or maybe lock the menu to the search tab regardless
of mouse events to the bottom tabs.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

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

[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update

[Ralf]

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

Ralf  changed:

   What|Removed |Added

 CC||ralfdash199...@gmail.com

--- Comment #14 from Ralf  ---
System: Apple Macbook 12” (2017)
OS: macOS Mojave 10.14.6
VM software: VMware Fusion 11.5.1

Doing some Kubuntu testing, test case #1: Kubuntu 19.10 - “Try Kubuntu” (live
disk)

It is in 800x600 and the resolution can’t be changed via System Settings (it
snaps back to 800x600 after a second as previously described). 

Fixed by: sudo apt install open-vm-tools

which sets the VM to a usable 1280x800 resolution. However, the bug still
exists as the resolution still can’t be changed by System Settings: it will now
snap back to 1280x800 if you try to change it.

-

Test case #2: Kubuntu 19.10 - “Install Kubuntu”

The installer starts in 800x600 which makes selections difficult, but as soon
as installer gets past the “Updates and Other Software" screen and Kubuntu's
under-the-covers open-vm-tools kick in the screen becomes a usable resolution
and this is “permanent” as the installed VM stays at this resolution even
through reboots.

I can even enable “Use full resolution for Retina display” in VMware Fusion and
get a 2560x1600 resolution in the VM. I then set the scaling in System Settings
to 2 for a beautiful, usable HiDPI VM.

Still, the 2560x1600 can’t be altered via system settings, but since this is an
optimal resolution I don’t really want to change it!

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

[okular] [Bug 415332] Okular does not show the dialogue to let me load a file

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #2 from Albert Astals Cid  ---
Are you saying that you did some crazy copying of snap stuff by hand, things
don't work and now you're opening a bug?

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

[k3b] [Bug 415292] K3b crashes after opening ISO file

[Albert Astals Cid]

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

--- Comment #7 from Albert Astals Cid  ---
> strangely, it does not crash on small images

It doesn't work either, right?

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

[dolphin] [Bug 358038] KDE service for dolphin to change wallaper on the one was clicked with RMB

[bugzilla_noreply]

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

hoperidesal...@protonmail.ch changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from hoperidesal...@protonmail.ch ---
*** This bug has been confirmed by popular vote. ***

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

[dolphin] [Bug 415337] New: Cant copy files into discord

[Adrian]

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

Bug ID: 415337
   Summary: Cant copy files into discord
   Product: dolphin
   Version: 19.08.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: zetabite.horz...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 124580
  --> https://bugs.kde.org/attachment.cgi?id=124580=edit
File path is copied and pasted

SUMMARY
When trying to copy a file from dolphin into discord, dolphin copies the file
path instead of the actual file.

STEPS TO REPRODUCE
1. Copy a picture in dolphin
2. Paste it into discord

OBSERVED RESULT
File path is pasted

EXPECTED RESULT
File is pasted

SOFTWARE/OS VERSIONS
Linux: 5.3.15-1-Manjaro
(available in About System)
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2

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

[dolphin] [Bug 415336] New: Cant drag and drop pictures into discord

[Adrian]

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

Bug ID: 415336
   Summary: Cant drag and drop pictures into discord
   Product: dolphin
   Version: 19.08.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: zetabite.horz...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 124579
  --> https://bugs.kde.org/attachment.cgi?id=124579=edit
Action is forbidden

SUMMARY
When trying to drag and drop files into discord, the forbidden marker appears
(see attachment).

STEPS TO REPRODUCE
1. Drag picture
2. Drag it to discord window
3. Drop it

OBSERVED RESULT
Action is forbidden

EXPECTED RESULT
Sending picture in discord

SOFTWARE/OS VERSIONS
Linux: 5.3.15-1-Manjaro
(available in About System)
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2

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

[plasmashell] [Bug 415335] New: Right Clicking in applications menu (Wayland)

[Jason]

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

Bug ID: 415335
   Summary: Right Clicking in applications menu (Wayland)
   Product: plasmashell
   Version: 5.17.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jas.ga...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.4)

Qt Version: 5.13.2
Frameworks Version: 5.65.0
Operating System: Linux 5.0.0-37-generic x86_64
Distribution: KDE neon User Edition 5.17

-- Information about the crash:
- Unusual behavior I noticed:
When right clicking an application in the "start" applications menu, plasma
crashed. I tried it again when it reapeared and it also crashed again, and now
it completely disapeared. Everything works still that is open, but bottom panel
is gone.

The crash can be reproduced every time.

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

Thread 49 (Thread 0x7f098e019700 (LWP 20647)):
#0  0x7f0a6ce5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x560c925d0e34) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x560c925d0de0,
cond=0x560c925d0e08) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x560c925d0e08, mutex=0x560c925d0de0) at
pthread_cond_wait.c:655
#3  0x7f0a6ff2daeb in QWaitConditionPrivate::wait (deadline=...,
this=0x560c925d0de0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x560c927aa670,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f0a6ff2ddf9 in QWaitCondition::wait (this=0x560c9324be18,
mutex=0x560c927aa670, time=) at
thread/qwaitcondition_unix.cpp:208
#6  0x7f09f8dfc845 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f09f8e006f8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f09f8dfbb0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f09f8dfe5bb in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f0a6ff26b52 in QThreadPrivate::start (arg=0x7f09d800a6d0) at
thread/qthread_unix.cpp:360
#11 0x7f0a6ce576db in start_thread (arg=0x7f098e019700) at
pthread_create.c:463
#12 0x7f0a6f82388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 48 (Thread 0x7f098e81a700 (LWP 20646)):
#0  0x7f0a6ce5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x560c925d0e34) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x560c925d0de0,
cond=0x560c925d0e08) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x560c925d0e08, mutex=0x560c925d0de0) at
pthread_cond_wait.c:655
#3  0x7f0a6ff2daeb in QWaitConditionPrivate::wait (deadline=...,
this=0x560c925d0de0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x560c927aa670,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f0a6ff2ddf9 in QWaitCondition::wait (this=0x560c9324be18,
mutex=0x560c927aa670, time=) at
thread/qwaitcondition_unix.cpp:208
#6  0x7f09f8dfc845 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f09f8e006f8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f09f8dfbb0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f09f8dfe5bb in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f0a6ff26b52 in QThreadPrivate::start (arg=0x560c92ae7f90) at
thread/qthread_unix.cpp:360
#11 0x7f0a6ce576db in start_thread (arg=0x7f098e81a700) at
pthread_create.c:463
#12 0x7f0a6f82388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 47 (Thread 0x7f098f01b700 (LWP 20645)):
#0  0x7f0a6ce5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x560c925d0e34) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x560c925d0de0,
cond=0x560c925d0e08) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x560c925d0e08, mutex=0x560c925d0de0) at
pthread_cond_wait.c:655
#3  0x7f0a6ff2daeb in QWaitConditionPrivate::wait (deadline=...,
this=0x560c925d0de0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x560c927aa670,

[dolphin] [Bug 415334] Scaling and/or Anti-Anilising of Pixel Art in preview looks blurry

[Adrian]

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

Adrian  changed:

   What|Removed |Added

 CC||zetabite.horz...@gmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Adrian  ---


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

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

[dolphin] [Bug 364527] Unnecessary scaling of small SVG and PNG icons leads to blurry thumbnails

[Adrian]

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

Adrian  changed:

   What|Removed |Added

 CC||zetabite.horz...@gmail.com

--- Comment #12 from Adrian  ---
*** Bug 415334 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 415334] New: Scaling and/or Anti-Anilising of Pixel Art in preview looks blurry

[Adrian]

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

Bug ID: 415334
   Summary: Scaling and/or Anti-Anilising of Pixel Art in preview
looks blurry
   Product: dolphin
   Version: 19.08.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: zetabite.horz...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 124578
  --> https://bugs.kde.org/attachment.cgi?id=124578=edit
Example for blur on pixel art

SUMMARY
Scaling and/or Anti-Anilising of Pixel Art in preview looks blurry in preview
mode.

STEPS TO REPRODUCE
1. Choose folder with pixel art (for example working on 16x16 MC texurepacks)
2. Set image size to something bigger than the actual pixel art size
3. Enable preview

OBSERVED RESULT
Blurry scaling

EXPECTED RESULT
Sharp looking pixel art without blur

SOFTWARE/OS VERSIONS
Linux: 5.3.15-1-Manjaro
(available in About System)
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2

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

[konversation] [Bug 372493] right click to ignore does not work

[Rabid Raven]

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

Rabid Raven  changed:

   What|Removed |Added

 CC||ra...@posteo.net

--- Comment #4 from Rabid Raven  ---
/ignore actually works but it doesn't record in Konversation's settings so the
next time you open the application, you have to do it all over again.

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

[digikam] [Bug 350350] Moving images notifies me moving finished when it did not finish yet

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||metzping...@gmail.com
 Resolution|--- |FIXED
   Version Fixed In||7.0.0

--- Comment #3 from Maik Qualmann  ---
This problem can no longer be reproduced with the newly introduced code for
copying and moving files. I close the bug.

Maik

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

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

[Roman Gilg]

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

Roman Gilg  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Roman Gilg  ---
Thanks for your report. I just tried on Intel and AMD graphics and was not able
to reproduce the issue with Wobbly Windows or Zoom.

Can you give me a step-by-step rundown on how to reproduce it? Do I need to
have a certain load on the CPU or GPU?

I have a single 4K monitor connected. Do you experience the issue only when
both your 4K monitors are connected or also with only one connected?

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

[plasmashell] [Bug 414823] Plasma crash on clicking widget

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
All duplicates use Qt 5.13.2, could be a Qt regression.

Please install debug symbols for libQt5*.so, and add an updated backtrace.

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

[plasmashell] [Bug 415043] plasmashell crashed after resume and click on system tray

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Christoph Feck  ---


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

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

[plasmashell] [Bug 414823] Plasma crash on clicking widget

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||scott.ashf...@gmail.com

--- Comment #1 from Christoph Feck  ---
*** Bug 414840 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 414840] plasmashell crashed after clicking on widget

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Christoph Feck  ---


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

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

[plasmashell] [Bug 414823] Plasma crash on clicking widget

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||w...@wian.co.za

--- Comment #2 from Christoph Feck  ---
*** Bug 415043 has been marked as a duplicate of this bug. ***

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

[neon] [Bug 414964] Touchpad stopped working after kernel update to 4.15.0-72

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #2 from Christoph Feck  ---
Thanks for the update. Users there confirmed it is a kernel regression;
changing status.

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

[lattedock] [Bug 415333] Long pressing on Latte dock icon makes it unusable

[Michail Vourlakos]

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

--- Comment #1 from Michail Vourlakos  ---
This is the dragging functionality, I suppose Qt 5.14 broke it...

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

[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul

[bugzilla_noreply]

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

--- Comment #9 from tempel.jul...@gmail.com ---
(In reply to Roman Gilg from comment #8)
> I have cleaned up / reformulated the patch. Could you test this patch one
> more time if it works for you like the previous poc one? Thanks!
> 
> https://phabricator.kde.org/D26090

Issue is still gone, afaict till now.

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

[digikam] [Bug 377127] Wrong item count on years in Dates View

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||7.0.0
  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/4aa4b52189e4
   ||36d6488d14d122e33543672ac94
   ||5

--- Comment #2 from Maik Qualmann  ---
Git commit 4aa4b52189e436d6488d14d122e33543672ac945 by Maik Qualmann.
Committed on 18/12/2019 at 21:16.
Pushed by mqualmann into branch 'master'.

fix wrong display of item counting in the date view
FIXED-IN: 7.0.0

M  +2-1NEWS
M  +21   -6core/libs/album/treeview/abstractalbumtreeview.h
M  +8-5core/libs/album/treeview/abstractcountingalbumtreeview.cpp
M  +1-8core/libs/album/treeview/datetreeview.cpp

https://invent.kde.org/kde/digikam/commit/4aa4b52189e436d6488d14d122e33543672ac945

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

[kscreenlocker] [Bug 415329] [>] button does not take keyboard input

[Achim Bohnet]

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

--- Comment #3 from Achim Bohnet  ---
I don't think that these are duplicates. I was aware of the other bug 415130

My bug report is about behavior of the [>] Button
Bug report 415130 is about keybindings of the password text field.

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

[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[lattedock] [Bug 415333] New: Long pressing on Latte dock icon makes it unusable

[Yaohan Chen]

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

Bug ID: 415333
   Summary: Long pressing on Latte dock icon makes it unusable
   Product: lattedock
   Version: 0.9.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: yaohan.c...@gmail.com
  Target Milestone: ---

SUMMARY
After long-pressing with mouse on a Latte dock icon, a blue border appears
around the icon, and the icon can no longer be used to switch window or launch
the application.

STEPS TO REPRODUCE
1. Have a Latte dock open
2. Move the mouse cursor over an icon in the dock
3. Hold the mouse down for about a second
4. Try to click on the icon to bring the application to the front or launch it

OBSERVED RESULT
A blue border appears around the icon, and the icon can no longer be used to
switch window or launch the application. It still responds to mouse over and
shows the context menu on right click. The icon is usable again if Latte dock
is restarted.

EXPECTED RESULT
The icon should be usable like normal

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0

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

[kmymoney] [Bug 415322] Flathub

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

   Severity|normal  |wishlist

--- Comment #1 from Thomas Baumgart  ---
Any volunteer who sets it up and takes care of it?

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

[kscreenlocker] [Bug 415329] [>] button does not take keyboard input

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Patrick Silva  ---


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

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

[plasmashell] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password

[Patrick Silva]

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

--- Comment #9 from Patrick Silva  ---
*** Bug 415329 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul

[Roman Gilg]

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

--- Comment #8 from Roman Gilg  ---
I have cleaned up / reformulated the patch. Could you test this patch one more
time if it works for you like the previous poc one? Thanks!

https://phabricator.kde.org/D26090

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

[okular] [Bug 415332] Okular does not show the dialogue to let me load a file

[bugzilla_noreply]

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

--- Comment #1 from adalbert.hans...@gmx.de ---
Created attachment 124577
  --> https://bugs.kde.org/attachment.cgi?id=124577=edit
Messages in a terminal window when starting Okular with a command

When I start okular in a terminal adding the file to load, I see these messages
in the terminal after closing okular. Maybe this plays a role in the error or
not, I don't know.

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

[krunner] [Bug 414941] krunner crashes when clicking configure

[Eugene]

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

Eugene  changed:

   What|Removed |Added

 CC||ken20...@ukr.net

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

[krita] [Bug 415320] Conversion from openraster to png gives different results unpredictably

[bugzilla_noreply]

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

--- Comment #3 from inklab...@gmail.com ---
Ok, I just ran the same analysis but instead of saving as png I save as ora
using the script call and then extract the mergedimage.png with zipfile. The
results are the same, there are two possible png files with close to even
distribution of occurrence. (In this case it was 52 vs 48) Very strange.

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

[okular] [Bug 415332] New: Okular does not show the dialogue to let me load a file

[bugzilla_noreply]

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

Bug ID: 415332
   Summary: Okular does not show the dialogue to let me load a
file
   Product: okular
   Version: 1.7.2
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: adalbert.hans...@gmx.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. With Okular started, I do Datei>Öffnen (file>open) or Ctl-O
2. 
3. 

OBSERVED RESULT no dialogue box which lets me input the file to load.


EXPECTED RESULT
a dialogue box which lets me input the file to load.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Frameworks 5.61.0
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: Qt 5.12.3 (kompiliert gegen 5.12.3)
Das xcb Fenstersystem

ADDITIONAL INFORMATION

To avoid having to make all mark pen definitions a second time, I just copied
all those settings from another user: copy /home/user/snap/okular to
~/snap/okular and then I did a chown -R to it for the current user.

I can open a file with okular when I give it the filename as a command line
argument.

The bug happens in Xubuntu 18.04.3 LTS.

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

[i18n] [Bug 404286] Absurd "cancel" polish translation

[bugzilla_noreply]

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

--- Comment #34 from r.ro...@outlook.com ---
(In reply to NSLW from comment #33)
> (In reply to r.rozne from comment #30)
> > I stumbled over here after seeing angry comments from people on Nate's blog
> > and feel I have a couple things to say.
> > 
> > One, as a native Polish speaker (and sorta a purist like our translator
> > here) who only actually tried using KDE in Polish after the change to
> > "Zaniechaj" (my day-to-day machine is set to English), my reaction to seeing
> > this for the first time was: "Oh, how cute. I like it."
> 
> You used Polish translation in KDE before the change to "Zaniechaj" and
> after the change 
> you tried (struggled) to use it?

No, I had never used KDE *in Polish* before the change occurred is what I
meant. I had only tried KDE in English before. I'm a person learned in both
linguistics and computers, so I didn't have any problems. But here's the thing,
I, like you, am a learned person. In my experience, the typical user gets
confused a *lot* when presented with different wording than they've been seeing
for years (Windows, Android, modern Apple platforms).
> 
> > On the other hand, I
> > don't think idiosyncrasies like this one are exactly good, for example when
> > someone unfamiliar with KDE tries supporting a user over the phone… Has
> > anyone considered this? In software translation, you don't want "cute" or
> > "where's the 'Anuluj' button" to be the first reaction.
> 
> I want to get you right: an expert unfamiliar with KDE tries to help a novice
> also unfamiliar with KDE on how to achieve something in KDE. He does so by
> phone conversation.
> The key here should be presence of "Anuluj" button otherwise there would be
> searching for it.

In this scenario, neither the expert, nor the user are even aware they're
running KDE. The user is agitated and puts pressure on the "so-called expert"
to solve their problem at all costs. The expert may assume things because of
that.

> Here is how I consider the situation, I understood:
> First, I think that "Zaniechaj" equals "Anuluj" so that's not like the
> meaning has changed. In English 
> you could also say "Dove" and "Pigeon" and AFAIK that would mean exactly the
> same. No confusion here.

Well, on paper it hasn't. However, some people don't know the formal definition
of "Anuluj". I don't have a real-life example for that, but I do have one for
the word "Edycja" (Edit). My grandmother was recently confused by this word,
because she was used to seeing it in a web app, where clicking it opened a
separate screen that showed more details about something than could be seen
normally, in addition to making them editable. So, she told, she thought it
means something like "show more details". Then, she encountered it in a
situation, where tapping the "Edytuj" button didn't show more stuff, leaving
her tapping over and over, looking for more stuff.
Encountering the same word in a different place, where the *apparent effect*
(to them) is different, may leave them confused.
Likewise, users may not associate "Anuluj" and "Zaniechaj" with the same
concept. Is Microsoft to blame for this?

> Second, I think that the expert has much bigger challenges in helping than
> to find "Anuluj" button, because he is in general unfamiliar with KDE .
> 
> Third, If the expert asks "where's 'Anuluj' button" then he could also ask
> "where's 'Start' button" which is equally important. Should we then
> instantiate Start button in KDE as well? I think not.
> 
Given that the Start button hasn't been labeled since Vista, I think the
average user calls any button in the bottom-left corner of the screen a "Start"
button. Even then, there's the resort of "the button in the bottom-left corner"
(and if that fails, try the upper-left and the upper-right - that can happen on
Windows, too). Not so much with our "Anuluj" button, given that different OS'
put "OK" and "Anuluj" in different order.
> 
> > Two, Apple had not commissioned a Polish translation of Mac OS before
> > Leopard. However, "Polonizator" fan translations did exist. Hence, it wasn't
> > that Apple 'softened', it was that fan translators were purists, too. At
> > least *they* could argue that there was no existing translation and no
> > prevailing standard (unless you count Windows 95, which was still fairly new
> > at the time these translations started - the oldest one I could find was for
> > Mac OS 9), either. 
> 
> MacOS was translated since 1986.
> Please read and interview with translators
> https://www.computerworld.pl/wywiad/Kwasne-jablka-do-szarlotki,320100.html
> Their opinion on Window translation is that it was: ugly, illogic,
> inconsistent.
> That might be the same time at which someone made decision to be
> incompatible with 
> MacOS and choose "Anuluj" instead of "Poniechaj".
> 
Huh, that's the first time I've heard of this… Have you ever seen it? Where?
Only other trace I've found was an archived Allegro listing. I think I 

[kdeconnect] [Bug 415331] New: "Share file" option shows squeezed to 0 file name (first) column in "Open File" dialog

[Piotr Mierzwinski]

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

Bug ID: 415331
   Summary: "Share file" option shows squeezed to 0 file name
(first) column in "Open File" dialog
   Product: kdeconnect
   Version: 1.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

Created attachment 124575
  --> https://bugs.kde.org/attachment.cgi?id=124575=edit
KDE Connect - Please choose a file

SUMMARY
In case of very first using option described in subject is displaying "Open
File" dialog with incorrect (too tiny) size (mostly width) and squeezed to 0
file name column (only icons are visible). Other columns seems to be fine.
After second use this option, File Selector dialog gets normal (bigger) size
with correct width of file name column (and also other columns).

STEPS TO REPRODUCE
1. Login into KDE/Plasma
2. Click left button into "KDE Connect" icon placed in taskbar
3. Click into three vertical dots
4. Choose "Share file" option

OBSERVED RESULT
Tiny "Open File" dialog with squeezed to 0 file name column (only icons are
visible).

EXPECTED RESULT
Should be shown "normal" (bigger) "Open File" dialog with "normal" (wider) file
name column.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: YES
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64
Qt Version: 5.13.2

ADDITIONAL INFORMATION
Screenshot in attachment.

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

[lattedock] [Bug 415315] latte-dock freezes for 1 or 2 seconds on various situations iff Visual Studio Code is open

[bugzilla_noreply]

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

--- Comment #6 from ruben.be...@gmail.com ---
(In reply to ruben.bejar from comment #4)
> (In reply to Michail Vourlakos from comment #1)
> > 1. Latte v0.8 is not the current stable version and is not getting any more
> > updates
> > 2. Use plasma panel and taskmanager, don't you have the same issue?
> 
> - I have updated latte-dock to testing with this PPA
>  (after
> updating, version is 0.9.85) and the problem is still there.
> - Plank, Docky, the Icon-only task manager on a plasma panel and other
> Plasma launchers work normally. The only problematic configuration in my
> computer is Plank with Visual Studio Code.

Of course, the last sentence should be "The only problematic configuration in
my computer is **Latte** with Visual Studio Code."

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

[gwenview] [Bug 411196] gwenview very slow to launch

[Torsten Römer]

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

--- Comment #7 from Torsten Römer  ---
I have the same problem for quite a while now, since kubuntu 19.04 I think.
Even Dolphin was slow displaying contents of folders with somewhat the same
delay as Gwenview showing up.
Just did a clean new install of 19.10 including fresh home directory - still
the same problem with Gwenview, Dolphin however seems to work fine again.

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

[kate] [Bug 415323] Allow tabs to be displayed horizontally.

[Kåre Särs]

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

Kåre Särs  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||kare.s...@iki.fi
 Status|REPORTED|RESOLVED

--- Comment #1 from Kåre Särs  ---
For that we already have the Documents tool-view that gives you a tree-view of
all your open documents. I will close this bug. If you think you actually want
real tab widgets you can reopen.

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

[k3b] [Bug 415292] K3b crashes after opening ISO file

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---

--- Comment #6 from Albert Astals Cid  ---
yep, thanks :)

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

[krita] [Bug 415320] Conversion from openraster to png gives different results unpredictably

[bugzilla_noreply]

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

--- Comment #2 from inklab...@gmail.com ---
Yes, that is an interesting suggestion. I am actually trying to get Krita to
compose two layers with the specified blending or compositing effect,
programmatically. So I generate the ORA first, and then feed to Krita to do the
rendering. (in general)

However, for this test case, I did actually make the ORA with Krita instead of
manually creating it, just to verify it was not some fault of mine in creating
the ORA. 

If I extract mergedimage.png from the ora file, it does not actually match
either of the other two possible pngs produced from the bug report...

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

[frameworks-kfilemetadata] [Bug 415330] Songs aren't shown if id3v1 is used

[Squeaky Pancakes]

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

Squeaky Pancakes  changed:

   What|Removed |Added

Summary|Songs aren't shown if   |Songs aren't shown if id3v1
   |metadata|is used

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

[i18n] [Bug 404286] Absurd "cancel" polish translation

[NSLW]

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

--- Comment #33 from NSLW  ---
(In reply to r.rozne from comment #30)
> I stumbled over here after seeing angry comments from people on Nate's blog
> and feel I have a couple things to say.
> 
> One, as a native Polish speaker (and sorta a purist like our translator
> here) who only actually tried using KDE in Polish after the change to
> "Zaniechaj" (my day-to-day machine is set to English), my reaction to seeing
> this for the first time was: "Oh, how cute. I like it."

You used Polish translation in KDE before the change to "Zaniechaj" and after
the change 
you tried (struggled) to use it?


> On the other hand, I
> don't think idiosyncrasies like this one are exactly good, for example when
> someone unfamiliar with KDE tries supporting a user over the phone… Has
> anyone considered this? In software translation, you don't want "cute" or
> "where's the 'Anuluj' button" to be the first reaction.

I want to get you right: an expert unfamiliar with KDE tries to help a novice
also unfamiliar with KDE on how to achieve something in KDE. He does so by
phone conversation.
The key here should be presence of "Anuluj" button otherwise there would be
searching for it.

Here is how I consider the situation, I understood:
First, I think that "Zaniechaj" equals "Anuluj" so that's not like the meaning
has changed. In English 
you could also say "Dove" and "Pigeon" and AFAIK that would mean exactly the
same. No confusion here.

Second, I think that the expert has much bigger challenges in helping than to
find "Anuluj" button, because he is in general unfamiliar with KDE .

Third, If the expert asks "where's 'Anuluj' button" then he could also ask
"where's 'Start' button" which is equally important. Should we then instantiate
Start button in KDE as well? I think not.


> Two, Apple had not commissioned a Polish translation of Mac OS before
> Leopard. However, "Polonizator" fan translations did exist. Hence, it wasn't
> that Apple 'softened', it was that fan translators were purists, too. At
> least *they* could argue that there was no existing translation and no
> prevailing standard (unless you count Windows 95, which was still fairly new
> at the time these translations started - the oldest one I could find was for
> Mac OS 9), either. 

MacOS was translated since 1986.
Please read and interview with translators
https://www.computerworld.pl/wywiad/Kwasne-jablka-do-szarlotki,320100.html
Their opinion on Window translation is that it was: ugly, illogic,
inconsistent.
That might be the same time at which someone made decision to be incompatible
with 
MacOS and choose "Anuluj" instead of "Poniechaj".

> In this case, we have both a long history of KDE using
> "Anuluj" *and* others using *Anuluj* virtually all around us, including
> notable applications people run on KDE, like Firefox.

I see that Firefox and Chrome use native KDE dialogs with "Zaniechaj" in them.
I also see that you're refering to the majority, similary to Przemysław
Formela.
Please read answer I gave to him, so that I mustn't duplicate content
https://bugs.kde.org/show_bug.cgi?id=404286#c31

> Three, while I can get behind encouraging use of "purer language", I cannot
> applaud the decision to change a common UI element without soliciting
> opinions beforehand.

I get impression that you're not proud of how things changed.
Would you solicit opinions beforehand, so that everyone would agree on the
change?

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

[i18n] [Bug 404286] Absurd "cancel" polish translation

[NSLW]

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

--- Comment #32 from NSLW  ---
(In reply to Michał Dybczak from comment #28)
> Why? One of the most common motivators for people is when we see something
> we don't like, instead being passive and whiny, we take action to improve
> things. Nothing shameful in that, in fact, this should be admirable, because
> most people will only complain and won't even try to do anything. The need
> to improve even one thing is how things start and it may evolve in something
> more but it has to start somewhere.

You wrote "fight". I think that word sets negative scene and attitude for
discussion.
I think there is nothing easier than to stand in majority and throw stones at
minority here. I don't find it admirable.


> Thank you for clarifying it. I was just being general because I don't have
> all the facts and that is why I used the word MAYBE. I'm also an outside
> person without means to know all such details but from what I can remember,
> very few people were currently working on translators and very few were
> major contributors - that is what I got from the discussion. Again, note I
> wasn't giving any absolute statements showing that I accept I might be off
> with this info.

OK. One doesn't need to be inside person to know all this. The information is
public and all
one needs to do is to analyze it.

I'm concerned that facts are based on what other people say, because I would
like facts to be independent of how people processed them.


> You are just nitpicking on the details hich is a bad attitude that is super
> common among polish internet communities (of any kind). I guess this is some
> flaw in our culture. It's very hard to discuss something seriously when
> someone is constantly nitpicking and splitting hairs in two and it's a form
> of an attack, which is not a way to discuss things constructively.

By me bringing details is nitpicking for you because contribution in Polish
translation is not what you wanted to discuss?


> You seemed to miss the point. The system is so antiquated that it's not
> comprehensible by modern standards and that simply creates a huge barrier
> which I bounced off of it. I wanted to contribute because it feels fair to
> try when I already voiced my opinion. I didn't even have chance to do that
> because there was no one to help me with that, although I clearly asked for
> it. Yes, this is so confusing that if you want fresh blood, you must guide
> them like children. I expected some site, account with certain rights and
> access to the files that I can work on plus some modern way of communication
> on the project.
> So I had a genuine desire to help or at least try to, yet I'm bashed that my
> motivation is disappointing and that I didn't contribute anything. This is
> absurd and a vicious, and unfair circle.

Sorry, I based my observation on the fact that on kdei18n-pl-devel and
kdei18n-pl-uwagi under your name I only found your request for changing
translation of "krypta" and "zaniechaj" and in my inbox did not found any
e-mail from you asking me to join translations.

How did you try to get involved in translation then?


> Well, I agree that I stated it too strongly. However, from my perspective it
> looked like this:
> 
> - I submitted the bug about the translation of "the vault" and had zero
> response
> - after a while I did see the corrected translation, I was happy, but I had
> no way of knowing if me taking action was the trigger or maybe the
> translator (you) realized the mistake on your own, or maybe someone
> submitted that problem on other, more proper channels
> - so in the end I didn't feel like my voice was heard, even if translation
> was indeed fixed

The information on discussion list might have been lost initially. That
happens.
You wrote to me directly and received response, that it will be corrected
either in some definite time
or as soon as you submit correction earlier to me. Have you read attached
e-mail? 


> When I raised my voice about the Anuluj vs. Zaniechaj, I felt ignored again.
> 
> This is probably a fault of the antiquated system. We don't know how to
> communicate with each other (developers with users) so it creates unpleasant
> situation on both sides: you feel as if your work was not apprciated, we
> feel that our feedback is not appreciated or even heard either.

What would you suggest to improve situation?


> I'm happy to hear that my submission helped thou. Thank you for letting me
> know.

You're welcome.


> I absolutely don't understand you now. If I was agreeing with you, there
> would be no discussion or any reason to communicate in that case. Why
> fighting for the argument is a bad thing? You do it, so why can't I?
> Fighting for something doesn't mean that we can't establish any consensus
> or understanding.

After a fight you might reach consensus and understanding as you wrote. I see
fight 
as not required to reach consensus and understanding.

> When I was trying to
> admit 

[frameworks-kfilemetadata] [Bug 415330] Songs aren't shown if metadata

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

 CC||matthieu_gall...@yahoo.fr
Version|5.60.0  |5.64.0

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

[frameworks-kfilemetadata] [Bug 415330] Songs aren't shown if metadata

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

  Component|general |general
Product|elisa   |frameworks-kfilemetadata
Version|19.12.0 |5.60.0
   Assignee|matthieu_gall...@yahoo.fr   |pinak.ah...@gmail.com

--- Comment #1 from Matthieu Gallien  ---
Thanks for your report.
It is not an Elisa bug given all metadata reading is done by KF5 KFileMetaData
framework.
Reassigning it.

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

[i18n] [Bug 404286] Absurd "cancel" polish translation

[NSLW]

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

--- Comment #31 from NSLW  ---
(In reply to przem.formela from comment #27)
> > For me user experience isn't hurt if the word is understandable.
> User Experience isn't based on personal preference, it's a whole area of
> scientfiic expertise, grounded in gestalt laws of perception. 

According to https://www.usertesting.com/blog/gestalt-principles/
"The human brain is wired to see structure, logic, and patterns. It helps us
make sense of the world. In the 1920s a group of German psychologists developed
theories around how people perceive the world around them, called Gestalt
principles."
I think we might be over-stretching scope of gestalt principles which are about
structure, logic, and patterns. I'm not sure if Luigi meant that specifically
or in general, so I think we might slightly went off-topic here. Nevertheless
thank you for your explanation. 


> I'm disappointed that even while seeing that your change disrupts someone's
> work so much that it makes them create an account here and file a bug (which
> isn't something a regular user wants to do) you still don't consider that
> enough of a feedback to actually revert - or even consider reverting - the
> change. 

The change disrupts your work because you don't know what "zaniechaj" does and
you know what "anuluj" does?


> The way you approach actual feedback given to you isn't community-
> nor improvement-oriented.

I presume that you don't see this change as making anything valuable to you.
In our devel list I wrote:
"My motivation is to promote the use of Polish language and enhance its quality 
in software."
Don't you see it as improvement of Polish wording in software?


> > Would you like to hold the right to make all the decisions but do no work
> > and take no responsibility for it? I disagree with that point of view.
> Nobody says you have to agree with that. If you volunteer to make work for
> the community, you should at least try to respect community's needs and
> decisions.

It seems to me that you're frustrated and would require obedience from me.
By you saying "[you] work for the community" I feel disrespected because it
places
me (worker) below you (community). I believe, that I deliver work that benefits
Polish language and the community.


> > I believe community is a bunch of people who do something voluntarily.
> > Do you see it differently?
> Well, I do. I believe that community is a group of people who wants to have
> something in common - in this particular instance, using KDE. There's no
> need to volunteer (that's what volunteering means, you do it if you want
> to). 

I guess you're right. It depends on how you look at it. I wrote it in the
context of
group of people (translators, devs, designers) being directly responsible for
shaping KDE look and feel.


> You are basically trying to make people go away from KDE - and from the
> community - based on your own preferences (which nobody in this thread
> agreed with so far).

Please don't try to make false accusations. I do not try to make people go away
from KDE.

I do not agree with statement that being in majority is the proof of being
right.
I would like you to read quotes from known people, so maybe we could get on
common ground.
"Don't confuse the truth with the opinion of the majority" Jean Cocteau
"Whenever you find yourself on the side of the majority, it is time to reform
(or pause and reflect)." Mark Twain


> > The fact that I don't do as anyone would like doesn't mean that I don't
> > listen to anyone or to you particularly. 
> So you're basically telling us that you've acknowledged our needs and
> decided that you know better what they are.

Please don't try to ridicule me by saying "you know better".
I believe we all have the same need i.e. the translations to be understandable.


> > I would like you to do less emotional statements and more statements which
> > are based on facts because I would like this discussion to be productive.
> Here are the facts, then:
> You are not listening to feedback, which is one of the most important User
> Experience rules.

I'm curious if your reason for saying "you are not listening" is different from
Michał Dybczak.
Would you mind to tell me when do you think I would listen?


> > I think you would like to abide to the standard of Windows. I would like to
> > abide to the standard of Polish language. 
> You ignore the gestalt law of similarity which is the backbone of proper
> design. 

I'm not sure. According to https://www.usertesting.com/blog/gestalt-principles/
"The principle of similarity states that when things appear to be similar to
each other, we group them together. And we also tend to think they have the
same function."


> You prefer disturbing people's work for the idea of pure language,
> forgetting completely that language is constantly changing.

I've got impression that language is changing because of globalization.
There is less Polish in Polish. In my opinion, 

[elisa] [Bug 415330] New: Songs aren't shown if metadata

[Squeaky Pancakes]

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

Bug ID: 415330
   Summary: Songs aren't shown if metadata
   Product: elisa
   Version: 19.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: squeakypanca...@disroot.org
  Target Milestone: ---

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

SUMMARY
Songs that only have id3v1 tags do not show up in the songs lists.

STEPS TO REPRODUCE
1. Have a song without tag2 metadata infomation filled out
2. open the album in elisa
3. 

OBSERVED RESULT
Album browser will not show songs with older tag formats.

EXPECTED RESULT
Songs should show up regardless of id3 spec as it's still possible to get songs
using v1 spec.

Operating System: Artix Linux 
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 4.19.88-1-lts
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz
Memory: 7.6 GiB of RAM

ADDITIONAL INFORMATION

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

[dolphin] [Bug 415312] Dolphin crashes when clicking a link on a target that no longer exists or is empty

[David Hallas]

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

David Hallas  changed:

   What|Removed |Added

 CC||da...@davidhallas.dk

--- Comment #1 from David Hallas  ---
This appears to be a duplicate of bug 414227 - could you retest with KDE
Frameworks 5.65?

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

[lattedock] [Bug 415315] latte-dock freezes for 1 or 2 seconds on various situations iff Visual Studio Code is open

[Michail Vourlakos]

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

--- Comment #5 from Michail Vourlakos  ---
In such case I hope someone to find the issue then...

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

[kscreenlocker] [Bug 415329] [>] button does not take keyboard input

[Achim Bohnet]

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

--- Comment #1 from Achim Bohnet  ---
I'm using up to date KDE neon user edition:

plasma-workspace:
  Installed: 4:5.17.4-0xneon+18.04+bionic+build53

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

[kscreenlocker] [Bug 415328] arrow keys left/right do not work when password was wrong

[Achim Bohnet]

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

Achim Bohnet  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages

--- Comment #1 from Achim Bohnet  ---
I'm using up to date KDE neon user edition:

plasma-workspace:
  Installed: 4:5.17.4-0xneon+18.04+bionic+build53

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

[kscreenlocker] [Bug 415329] New: [>] button does not take keyboard input

[Achim Bohnet]

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

Bug ID: 415329
   Summary: [>] button does not take keyboard input
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: a...@mpe.mpg.de
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Enter password
2. press Tab key
3. press enter

OBSERVED RESULT
1. not visual indication that the focus changed to [>] button
2. nothing happens

EXPECTED RESULT
1. A light blue frame indicates that the [>] button has the focus
2. Password is validated and I'm logged in or I'm told that pw was wrong


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Plasma 5.17.4
Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2
Kernel Version: 4.15.0-72-generic
OS Type: 64-bit

ADDITIONAL INFORMATION
Space key works and logs me in or refuses the login depending on the pw

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

[kscreenlocker] [Bug 415328] New: arrow keys left/right do not work when password was wrong

[Achim Bohnet]

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

Bug ID: 415328
   Summary: arrow keys left/right do not work when password was
wrong
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: a...@mpe.mpg.de
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
password test field looks like other password text fields in KDE apps but does
not honour left / right keys

STEPS TO REPRODUCE
1. enter a wrong password and press enter
2. wait until the bullets are all selected (when it's possible to start typing
again)
3. Press left and/or right arrow keys

OBSERVED RESULT
Nothing happens. Bullets still selected. Text cursur does not move.


EXPECTED RESULT
 right arrow key: selection vanishes
 left arrow key: selection vanishes and text cursor jumps to the left
now
 left or right arrow keys should move the text cursor



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Plasma 5.17.4
Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2
Kernel Version: 4.15.0-72-generic
OS Type: 64-bit


ADDITIONAL INFORMATION
Use Tab and Shift-Tab to leave and reenter the keyboard focus to the password
text field -> Left and right arrow keys still do not work -> bug

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

[kdenlive] [Bug 415327] New: endless loop during file dialodue

[Manfred]

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

Bug ID: 415327
   Summary: endless loop during file dialodue
   Product: kdenlive
   Version: 17.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: manfred.h...@t-online.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Create new project with kdenlive
2. try to save the work
3. 

OBSERVED RESULT
File dialogue displays frame only. KDEnlive is running in endless loop. 

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[elisa] [Bug 407918] Does not find music on other partition (ext4 or NTFS) even when added to search paths

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

   Version Fixed In|20.04   |20.04, 19.12.1

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

[elisa] [Bug 407918] Does not find music on other partition (ext4 or NTFS) even when added to search paths

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

  Latest Commit|https://cgit.kde.org/elisa. |https://invent.kde.org/kde/
   |git/commit/?id=826e1665b6c7 |elisa/commit/63e9df2c0f1402
   |b61513618e9e7ee9074da54bcb7 |c46af9814a4b299bf90d7b7ff2
   |1   |

--- Comment #26 from Matthieu Gallien  ---
Git commit 63e9df2c0f1402c46af9814a4b299bf90d7b7ff2 by Matthieu Gallien.
Committed on 18/12/2019 at 16:54.
Pushed by mgallien into branch 'release/19.12'.

Merge branch 'disactivateBalooWhenNeeded' into release/19.12


https://invent.kde.org/kde/elisa/commit/63e9df2c0f1402c46af9814a4b299bf90d7b7ff2

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

[plasmashell] [Bug 415043] plasmashell crashed after resume and click on system tray

[Wian Potgieter]

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

Wian Potgieter  changed:

   What|Removed |Added

 CC||w...@wian.co.za

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

[plasmashell] [Bug 415043] plasmashell crashed after resume and click on system tray

[Wian Potgieter]

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

--- Comment #1 from Wian Potgieter  ---
Created attachment 124573
  --> https://bugs.kde.org/attachment.cgi?id=124573=edit
New crash information added by DrKonqi

plasmashell (5.17.4) using Qt 5.13.2

- What I was doing when the application crashed:
Resumed KDE after unplugging my PC from the work monitors and plugging into
home monitors.
Clicked on  the NetworkManager System tray entry and plasmashell crashed.

- Unusual behavior I noticed:
Desktop had difficulty switching layouts to the changed (but known) screen
setup.  Screens were switched around.

-- Backtrace (Reduced):
#6  0x7f104d058b48 in
QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x7f105a1a676f in QOpenGLContext::create() () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x7f105d9cf5ad in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f105d9d0a24 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f105d9d42b8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5

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

[dolphin] [Bug 415326] New: dolphin: dropping a file on a directory does not update the 'modified' date

[Achim Bohnet]

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

Bug ID: 415326
   Summary: dolphin: dropping a file on a directory does not
update the 'modified' date
   Product: dolphin
   Version: 19.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: a...@mpe.mpg.de
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Open 2 dolphin windows
2. Remember the modified date of a directory
3. Drop a file from one window on this directory
4. select copy or move

OBSERVED RESULT
The number of items is correctly modified by one,
but the modified date of the directory does not change

EXPECTED RESULT
The modified date of the directory changes to the current date & time of the
drop

SOFTWARE/OS VERSIONS  KDE Neon
Linux/KDE Plasma: KDE Neon 17.4
(available in About System)
KDE Frameworks 5.64.0
Qt 5.13.2 (built against 5.13.2)
The xcb windowing system

ADDITIONAL INFORMATION
dolphin:
  Installed: 4:19.12.0-0xneon+18.04+bionic+build33

Pressing F5 in dolphin updates the modified date of the directory as expected.

The bug is not new. It's there at least since a few months.

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

[plasma-pa] [Bug 415325] New: Control volume of bluetooth device

[bugzilla_noreply]

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

Bug ID: 415325
   Summary: Control volume of bluetooth device
   Product: plasma-pa
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: t.soer...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

My bluetooth speaker runs on battery and has its own volume knob. It is
possible to control its volume directly through Bluez (dbus-send --print-reply
--system --dest=org.bluez /org/bluez/hci0/dev_00_42_79_DC_D5_xx
org.bluez.MediaControl1.VolumeDown). My android phone and smart TV can also
adjust its volume.

It would be nice if the volume applet controlled the volume of the speaker
itself instead of a virtual soundcard or whatever it does now.

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

[plasmashell] [Bug 415317] click on a entry of the context menu of systray icons has no effect on Wayland

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Flags||Wayland+

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

[okular] [Bug 415291] Okular opens links in Signal?

[Yuri Chornoivan]

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

--- Comment #3 from Yuri Chornoivan  ---
Ok. Thanks.

Can you try this command?

xdg-mime default firefox.desktop text/html

Inspired by this bug report:

https://github.com/signalapp/Signal-Desktop/issues/3602

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

[plasmashell] [Bug 415317] click on a entry of the context menu of systray icons has no effect on Wayland

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[kdenlive] [Bug 415324] KDenLive User interface is blank

[Navin Agarwal]

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

--- Comment #1 from Navin Agarwal  ---
do let me know if you need any other detail to solve this issue

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

[kdenlive] [Bug 415324] New: KDenLive User interface is blank

[Navin Agarwal]

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

Bug ID: 415324
   Summary: KDenLive User interface is blank
   Product: kdenlive
   Version: unspecified
  Platform: Windows CE
OS: MS Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: nxdevelope...@gmail.com
  Target Milestone: ---

Created attachment 124572
  --> https://bugs.kde.org/attachment.cgi?id=124572=edit
Blank User Interface

SUMMARY

i am unable to view anything on the UI. I have tried installing the latest
version (kdenlive-19.08.3.exe) and even the daily updated version
(kdenlive-master-244-windows-mingw_64-gcc.exe) but the issue remains the same.
I have attached 3 screenshots in a word document for your reference.

STEPS TO REPRODUCE
1. Start KdenLive that's it.

OBSERVED RESULT
Blank UI

EXPECTED RESULT
All the features that KdenLive provides

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kate] [Bug 415323] New: Allow tabs to be displayed horizontally.

[vytas]

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

Bug ID: 415323
   Summary: Allow tabs to be displayed horizontally.
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: vytas.n...@gmail.com
  Target Milestone: ---

SUMMARY
When working with a lot (20+) of open files simultaneously, horizontal tabbing
becomes very limiting in that after 11th tab, a plus sign needs to be pressed
to select another document. When correlating multiple documents, this causes a
lot of extra clicks.

What I would like is the option to have tabs displayed vertically, i.e. on the
left side. This way much more of them would stack up, and with screens making
biggest gains horizontally, it's a small price to pay for improved scalability
when one needs it.

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

[kmymoney] [Bug 415322] New: Flathub

[Michael Carpino]

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

Bug ID: 415322
   Summary: Flathub
   Product: kmymoney
   Version: 5.0.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: mfcarp...@gmail.com
  Target Milestone: ---

Is there a reason why KMyMoney isn't on Flathub? Can it be added to Flathub?

Skooge & GnuCash are there but KMyMoney isn't

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

[neon] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

[Erasmo Caponio]

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

--- Comment #13 from Erasmo Caponio  ---
(In reply to Dan from comment #12)

After last upgrade of KDE Neon, also that workaround does not work anymore on
my system. Not only this bug is still there after several months,  it has
become worse too   

> (In reply to Subin from comment #11)
> > I faced the same bug when I upgraded my KDE neon yesterday. Is there a
> > workaround please ?
> > 
> > Can't access KMail now...
> 
> There's an apparmor workaround detailed here, although if I recall I got a
> lot of apparmor errors about missing files that I needed to create before it
> would work that I don't entirely remember and didn't document, and my Kmail
> isn't quite doing everything right... but, it mostly works fine.
> 
> https://forum.kde.org/viewtopic.php?f=215=162053

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