[krunner] [Bug 423255] [feature request] web shortcut for deepl.com

2020-06-26 Thread Michael K.
https://bugs.kde.org/show_bug.cgi?id=423255

--- Comment #4 from Michael K.  ---
\O/
Thank you very much!

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

[dolphin] [Bug 423549] File renamed while in search mode: filename showed is not updated if search bar is closed and reopened

2020-06-26 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=423549

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---


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

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

[dolphin] [Bug 392456] Dolphin does not update search results view after a file is deleted or renamed

2020-06-26 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=392456

Patrick Silva  changed:

   What|Removed |Added

 CC||16f8...@gmail.com

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

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

[plasmashell] [Bug 417604] Scrolling direction inverted in some Plasma scrollviews

2020-06-26 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=417604

Patrick Silva  changed:

   What|Removed |Added

 CC||matejm98m...@gmail.com

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

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

[plasmashell] [Bug 423550] In wayland session some apps use "Natural scrolling" even though it's not enabled

2020-06-26 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=423550

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---


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

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

[plasmashell] [Bug 417086] Crash after getting many notifications.

2020-06-26 Thread Benjamin Smith
https://bugs.kde.org/show_bug.cgi?id=417086

Benjamin Smith  changed:

   What|Removed |Added

 CC||bsmith7...@gmail.com

--- Comment #1 from Benjamin Smith  ---
I just switched wifi networks a few times because my home wifi is acting up.
Plasmashell crashed immediately after the notification appeared that the wifi
was connected. 

Plasma 5.19.2 
Manjaro Linux with kernel 5.7.6.

Jun 27 01:01:08 bens-laptop systemd-coredump[9716]: Process 1041 (plasmashell)
of user 1000 dumped core.

Stack trace of thread 1337:
#0  0x7fc487b1a355 raise (libc.so.6 + 0x3c355)
#1  0x7fc487b1a3e0 __restore_rt (libc.so.6 + 0x3c3e0)
#2  0x7fc469639fb4 n/a (libkquickcontrolsaddonsplugin.so + 0x27fb4)
#3  0x7fc48816d906 n/a (libQt5Core.so.5 + 0x2e9906)
#4  0x7fc489c37115 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSizeS2_
(libQt5Quick.so.5 + 0x254115)
#5  0x7fc489bd9a3f n/a (libQt5Quick.so.5 + 0x1f6a3f)
#6  0x7fc489bda3d7 n/a (libQt5Quick.so.5 + 0x1f73d7)
#7  0x7fc487f51e0f n/a (libQt5Core.so.5 + 0xcde0f)
#8  0x7fc4872ea422 start_thread (libpthread.so.0 + 0x9422)
#9  0x7fc487bddbf3 __clone (libc.so.6 + 0xffbf3)

Stack trace of thread 1041:
#0  0x7fc4872f0e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 +
0xfe32)
#1  0x7fc487f57d64 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer
(libQt5Core.so.5 + 0xd3d64)
#2  0x7fc489bdc157 n/a (libQt5Quick.so.5 + 0x1f9157)
#3  0x7fc489c450a7 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5 +
0x2620a7)
#4  0x7fc488c5a702
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x15c702)
#5  0x7fc48813669a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent
(libQt5Core.so.5 + 0x2b269a)
#6  0x7fc4884ffe59 _ZN15QPlatformWindow11windowEventEP6QEvent
(libQt5Gui.so.5 + 0x12ae59)
#7  0x7fc488c6145c _ZN12QApplication6notifyEP7QObjectP6QEvent
(libQt5Widgets.so.5 + 0x16345c)
#8  0x7fc48813669a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent
(libQt5Core.so.5 + 0x2b269a)
#9  0x7fc48818e595 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 +
0x30a595)
#10 0x7fc48818ee42 n/a (libQt5Core.so.5 + 0x30ae42)
#11 0x7fc4865e943c g_main_context_dispatch (libglib-2.0.so.0 + 0x5243c)
#12 0x7fc486636fa9 n/a (libglib-2.0.so.0 + 0x9ffa9)
#13 0x7fc4865e8221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
#14 0x7fc48818f211
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x30b211)
#15 0x7fc48813501c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2b101c)
#16 0x7fc48813d4a4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 +
0x2b94a4)
#17 0x560348271f5d n/a (plasmashell + 0x1df5d)
#18 0x7fc487b05002 __libc_start_main (libc.so.6 + 0x27002)
#19 0x56034827219e _start (plasmashell + 0x1e19e)

Stack trace of thread 1273:
#0  0x7fc4872f0e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 +
0xfe32)
#1  0x7fc487f57d64 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer
(libQt5Core.so.5 + 0xd3d64)
#2  0x7fc489bd7e7b n/a (libQt5Quick.so.5 + 0x1f4e7b)
#3  0x7fc489bda41b n/a (libQt5Quick.so.5 + 0x1f741b)
#4  0x7fc487f51e0f n/a (libQt5Core.so.5 + 0xcde0f)
#5  0x7fc4872ea422 start_thread (libpthread.so.0 + 0x9422)
#6  0x7fc487bddbf3 __clone (libc.so.6 + 0xffbf3)

Stack trace of thread 1268:
#0  0x7fc487bd305f __poll (libc.so.6 + 0xf505f)
#1  0x7fc486636f38 n/a (libglib-2.0.so.0 + 0x9ff38)
#2  0x7fc4865e8221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
#3  0x7fc48818f211
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x30b211)
#4  0x7fc48813501c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2b101c)
#5  0x7fc487f50c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccc32)
#6  0x7fc48988d789 n/a (libQt5Qml.so.5 + 0x30b789)
#7  0x7fc487f51e0f n/a (libQt5Core.so.5 + 0xcde0f)
#8  0x7fc4872ea422 start_thread (libpthread.so.0 + 0x9422)
#9  0x7fc487bddbf3 __clone (libc.so.6 + 0xffbf3)

Stack trace of thread 1272:
#0  0x7fc4872f0e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 +
0xfe32)
#1  0x7fc472d5b3bc n/a (iris_dri.so + 0x4ae3bc)
#2  0x7fc472d59db8 n/a (iris_dri.so + 0x4acdb8)
#3  0x7fc4872ea422 start_thread (libpthread.so.0 + 0x9422)
#4  0x7fc487bddbf3 __clone (libc.so.6 + 0xffbf3)

Stack trace of thread 1332:
#0  0x7fc4872f0e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 +
0xfe32)
#1  0x7fc487f57d64 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer
(libQt5Core.so.5 + 0xd3d64)
#2  0x7fc489bd7e7b n/a (libQt5Quick.so.5 + 0x1f4e7b)
#3  0x7fc489bda41b n/a (libQt5Quick.so.5 + 0x1f741b)
#4  0x7fc487f51e0f n/a (libQt5Core.so.5 + 0xcde0f)
#5  

[dragonplayer] [Bug 423569] New: Dragonplayer's *snap package* crashes each time one tries to play a video.

2020-06-26 Thread Sai Vinoba
https://bugs.kde.org/show_bug.cgi?id=423569

Bug ID: 423569
   Summary: Dragonplayer's *snap package* crashes each time one
tries to play a video.
   Product: dragonplayer
   Version: 19.04
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: s...@sumati.net
CC: myr...@kde.org
  Target Milestone: ---

Created attachment 129714
  --> https://bugs.kde.org/attachment.cgi?id=129714=edit
dragonplayer-crash-error-log

SUMMARY
The snap version of dragonplayer crashes (each time one tries to play a movie)

STEPS TO REPRODUCE
1. Choose a movie to play.
2. Select 'Open with' and choose dragon plyaer (snap version)

OBSERVED RESULT
The player crashes.

EXPECTED RESULT
Normal operation; play the selected movie.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Lubuntu 20.04 / 20.10 
SW Version: 19.04.2
KDE Frameworks Version: 5.61
Qt Version: 5.12.3

ADDITIONAL INFORMATION
The .deb package works just fine. It is the snap package that is crashing. The
deb package is at higher version (version: 20.04.2, frameworks: 5.71, Qt
version: 5.14.2) than snap, which is surprising to me, as a snap (or flatpak)
is understood to be always latest?!

I've attached error log that I get when I try to launch dragonplayer from
terminal. It mainly gives error about not having permission to
/usr/share/alsa/alsa.conf. See attachement.

I asked for assistance in snapcraft forum
(https://forum.snapcraft.io/t/dragon-player-crashing/18491) and was asked to
check snap connections. Following is what I have.

sai@lubox:~/Documents$ snap connections dragon 
Interface Plug  Slot   
  Notes
content[kde-frameworks-5-core18-all]  dragon:kde-frameworks-5-plug 
kde-frameworks-5-core18:kde-frameworks-5-core18-slot  -
dbus  -
dragon:session-dbus-interface -
desktop   dragon:desktop   
:desktop  -
desktop-legacydragon:desktop-legacy
:desktop-legacy   -
home  dragon:home   :home  
  -
network   dragon:network   
:network  -
network-bind  dragon:network-bind  
:network-bind -
opengldragon:opengl :opengl
  -
pulseaudiodragon:pulseaudio
:pulseaudio   -
unity7dragon:unity7 :unity7
  -
x11   dragon:x11:x11   
  -

>From the comments, the connections seem OK, except that the snap uses
the obsolete pulseaudio interface instaed of the new
“audio-playback/audio-record” ones .

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

[krita] [Bug 422883] When I use Free hand brush tool some brushes didn't want to work

2020-06-26 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=422883

--- 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.

[korganizer] [Bug 399434] GENERAL

2020-06-26 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=399434

--- 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.

[systemsettings] [Bug 422953] KWin toggle shortcut do not work anymore!

2020-06-26 Thread Rajinder Yadav
https://bugs.kde.org/show_bug.cgi?id=422953

Rajinder Yadav  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #6 from Rajinder Yadav  ---
Hello this is now working with the latest update for openSUSE Tumbleweed.

Closing as fixed.

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

[krunner] [Bug 423255] [feature request] web shortcut for deepl.com

2020-06-26 Thread Alexander Lohnau
https://bugs.kde.org/show_bug.cgi?id=423255

Alexander Lohnau  changed:

   What|Removed |Added

   Version Fixed In||5.72
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kio/commit/cea57a5bc
   ||57d4f618f931891e70ad1db238b
   ||8eac

--- Comment #3 from Alexander Lohnau  ---
Git commit cea57a5bc57d4f618f931891e70ad1db238b8eac by Alexander Lohnau.
Committed on 27/06/2020 at 04:17.
Pushed by alex into branch 'master'.

Add webshortcut for DeepL
FIXED-IN: 5.72

A  +6-0src/urifilters/ikws/searchproviders/deepl.desktop

https://invent.kde.org/frameworks/kio/commit/cea57a5bc57d4f618f931891e70ad1db238b8eac

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

[kate] [Bug 390043] New tabs should be inserted on the right, like other tabbed apps/views

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=390043

Nate Graham  changed:

   What|Removed |Added

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

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

[kate] [Bug 390043] New tabs should be inserted on the right, like other tabbed apps/views

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=390043

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||20.08.0
  Latest Commit||https://invent.kde.org/util
   ||ities/kate/commit/2d4c501bf
   ||7512e218599640ffc09115c32f2
   ||761c

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

[plasmashell] [Bug 422736] Media player widget popup is too tall and narrow when used as widget on the panel

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=422736

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.19.3

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

[krunner] [Bug 304276] Spaces converted to + when using web shortcuts

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=304276

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[dolphin] [Bug 423537] hold N previews in memory (i.e. multi-level preview caching)

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=423537

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[krita] [Bug 423568] New: crash on layer reorder

2020-06-26 Thread nikola
https://bugs.kde.org/show_bug.cgi?id=423568

Bug ID: 423568
   Summary: crash on layer reorder
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: MS Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: nikola.knezevic@gmail.com
  Target Milestone: ---

Created attachment 129713
  --> https://bugs.kde.org/attachment.cgi?id=129713=edit
kritacrash.log

This bug doesn't occur in stable version 4.3.
It is easy to reproduce on 5.0.0-prealpha (git 23be7ef) and few earlier
versions.

STEPS TO REPRODUCE
1. run Krita
2. File -> new
3. Make sure the Layers docker is visible
4. Add layer
5. Drag it (or click on down-arrow) to send layer 2 below layer 1
6. Krita crash


SOFTWARE/OS VERSIONS
Krita Version: 5.0.0-prealpha (git 23be7ef), Qt version compiled: 5.12.8,
loaded: 5.12.8.

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

[kwin] [Bug 421486] No input in nested session

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=421486

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kate] [Bug 412185] Settings > Configure Editor inconsistency

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=412185

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||20.08.0
  Latest Commit||https://invent.kde.org/util
   ||ities/kate/commit/0234b8a02
   ||f638555c2fc18fe23cc2bdfdcb4
   ||8785
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Nate Graham  ---
Fixed with
https://invent.kde.org/utilities/kate/commit/0234b8a02f638555c2fc18fe23cc2bdfdcb48785

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

[plasmashell] [Bug 423567] New: Firefox icon can't be removed from Panel

2020-06-26 Thread mireiner
https://bugs.kde.org/show_bug.cgi?id=423567

Bug ID: 423567
   Summary: Firefox icon can't be removed from Panel
   Product: plasmashell
   Version: 5.19.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: mir.ei...@freenet.de
  Target Milestone: 1.0

SUMMARY
Firefox icon can't be removed from Panel

STEPS TO REPRODUCE
1. Right click on Firefox icon
2. There's no removal option
3. Any other application that can be placed on the panel has a removal option

OBSERVED RESULT
Firefox icon can't be removed from panel. 
I like to have a clean panel on left side of the screen. Using it mainly for
task switching and overview of running applications. Because the Firefox icon
can't be removed if one runs a Firefox instance then there are two Firefox
icons on the panel which is confusing.

EXPECTED RESULT
Firefox can be removed with right mouse click option

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neo (user edition 2020-06-25)
(available in About System)
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 423563] PLASMA_USE_QT_SCALING=1 causes Plasma to select a wallpaper appropriate for the logical DPI, not the physical DPI

2020-06-26 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=423563

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/119

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

[krunner] [Bug 423566] New: Backspace can displace input text above the text box in some situations

2020-06-26 Thread Brendan Early
https://bugs.kde.org/show_bug.cgi?id=423566

Bug ID: 423566
   Summary: Backspace can displace input text above the text box
in some situations
   Product: krunner
   Version: 5.18.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: m-...@evermiss.net
CC: plasma-b...@kde.org
  Target Milestone: ---

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

SUMMARY

When using Backspace or Ctrl + Backspace, sometimes text will appear above the
input text box.

STEPS TO REPRODUCE
1. Open krunner
2. Type until autocomplete suggestions show
3. Press the down arrow on keyboard
4. Press backspace

OBSERVED RESULT

See attached video

EXPECTED RESULT

Word or character is deleted without text displacement.

SOFTWARE/OS VERSIONS
Operating System: Fedora 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.6.19-300.fc32.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM

ADDITIONAL INFORMATION
Resolution: 3840x2160
Scale: 150%

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

[elisa] [Bug 423565] New: Elisa is not finding new songs added to my ~/Music folder

2020-06-26 Thread Nishant Kumar
https://bugs.kde.org/show_bug.cgi?id=423565

Bug ID: 423565
   Summary: Elisa is not finding new songs added to my ~/Music
folder
   Product: elisa
   Version: 20.04.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: nishant@gmail.com
  Target Milestone: ---

SUMMARY
Elisa is not finding new songs added to my ~/Music folder. Today I added two
mp3 songs in my ~/Music folder, then opened the Elisa to play it, but they were
not found, so I refreshed the Music Collection. Even after that, the Songs were
not found. First I thought I might be using the wrong file type but Cantata
found the music immediately.

STEPS TO REPRODUCE
1. Add the Song to ~/Music folder
2. Open Elisa
3. Refresh Music Collection

OBSERVED RESULT
New songs were not shown in Tracks

EXPECTED RESULT
Songs should be present in tracks and playable

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel (5.4.48-1-lts)
(available in About System)
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

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

[krita] [Bug 423564] New: Crashes, ends up off-time after render, and autosave does not work.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423564

Bug ID: 423564
   Summary: Crashes, ends up off-time after render, and autosave
does not work.
   Product: krita
   Version: 4.2.8
  Platform: Windows CE
OS: Microsoft Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: swaggy...@gmail.com
  Target Milestone: ---

Created attachment 129711
  --> https://bugs.kde.org/attachment.cgi?id=129711=edit
I was going to make this for my dad for father's day, but the timing was
literally so off, I was ashamed. Also, in the midst of creating this, IT
CRASHED PROBABLY OVER 3 TIMES. I gave up cause of u

SUMMARY
Crashes, ends up off-time after render, and autosave does not work.

STEPS TO REPRODUCE
1. Read
2. The
3. Below

OBSERVED RESULT
It crashes so much and then it 'autosaves' my work but it doesn't actually save
my work and DELETES A LOT OF WHAT I DID, which is what I call autodelete :((.
Please fix this. Crashes way too much as well. Also, fix your render because
every time I finish rendering an animation it goes off-time and my lip sync
that I spent so long drawing got messed up; fix it! Please! I also heard that
these are VERY common bugs, so I'm curious why you haven't fixed it yet. It is
almost certain that a lot of Krita haters are the ones who have experienced one
or multiple of the problems I have mentioned. For now, I'm going to switch to a
better software. I would rather buy another software (with real money) than use
Krita again. Very disappointed. I'm uninstalling Krita.

EXPECTED RESULT
I expected it to be normal with no bugs and crashes and off-timing.

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

[plasmashell] [Bug 423563] PLASMA_USE_QT_SCALING=1 causes Plasma to select a wallpaper appropriate for the logical DPI, not the physical DPI

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=423563

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED
   Assignee|notm...@gmail.com   |n...@kde.org

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-26 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=418758

--- Comment #5 from Jack  ---
Have you diagnosed what is happening in a debugger, or are you assuming?  In my
case, on both Windows and Linux, it is able to open a file with # in the name,
using the File/Open dialog, or when launced by command line. so there is likely
something different between our systems.  What locale (country/language) are
you using?  I have en_US.UTF-8, although I have no idea if it matters.

(Note that when replying by email, you can remove what you are replying to, as
it is already posted to the bug.)

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

[frameworks-baloo] [Bug 422393] Baloo file indexer crashes on login

2020-06-26 Thread Navneet Vikram Tey
https://bugs.kde.org/show_bug.cgi?id=422393

--- Comment #3 from Navneet Vikram Tey  ---
Created attachment 129710
  --> https://bugs.kde.org/attachment.cgi?id=129710=edit
New crash information added by DrKonqi

baloo_file_extractor (5.71.0) using Qt 5.15.0

- What I was doing when the application crashed:
Login, It started happening for a few times but then it started happening
everytime
- Unusual behavior I noticed:
Crashing
- Custom settings of the application:
Never used it

-- Backtrace (Reduced):
#11 0x7f511980c615 in mdb_cursor_put () from /usr/lib/liblmdb.so
#12 0x7f511980f46b in mdb_put () from /usr/lib/liblmdb.so
#13 0x7f511b2bf40e in Baloo::PostingDB::put(QByteArray const&,
QVector const&) () from /usr/lib/libKF5BalooEngine.so.5
#14 0x7f511b2cd328 in Baloo::WriteTransaction::commit() () from
/usr/lib/libKF5BalooEngine.so.5
#15 0x7f511b2c5bf2 in Baloo::Transaction::commit() () from
/usr/lib/libKF5BalooEngine.so.5

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

[frameworks-baloo] [Bug 422393] Baloo file indexer crashes on login

2020-06-26 Thread Navneet Vikram Tey
https://bugs.kde.org/show_bug.cgi?id=422393

Navneet Vikram Tey  changed:

   What|Removed |Added

 CC||navneetvikramtey@protonmail
   ||.com

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

[plasmashell] [Bug 423563] New: PLASMA_USE_QT_SCALING=1 causes Plasma to select a wallpaper appropriate for the logical DPI, not the physical DPI

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=423563

Bug ID: 423563
   Summary: PLASMA_USE_QT_SCALING=1 causes Plasma to select a
wallpaper appropriate for the logical DPI, not the
physical DPI
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: n...@kde.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

With PLASMA_USE_QT_SCALING=1 set, the wallpaper chooser selects a wallpaper of
an inappropriate size. For example if you have a 3840 x 2160 screen and you use
a 2x scale factor, it will select a 1920x1080 wallpaper instead of the 3840 x
2160 version. Looks like it's looking at the logical screen resolution instead
of the physical screen resolution.

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

[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=356446

Nate Graham  changed:

   What|Removed |Added

 Depends on||423563


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=423563
[Bug 423563] PLASMA_USE_QT_SCALING=1 causes Plasma to select a wallpaper
appropriate for the logical DPI, not the physical DPI
-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 423563] PLASMA_USE_QT_SCALING=1 causes Plasma to select a wallpaper appropriate for the logical DPI, not the physical DPI

2020-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=423563

Nate Graham  changed:

   What|Removed |Added

 Blocks||356446


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=356446
[Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 415819] Notification entry in history too small in height resulting in an overlap

2020-06-26 Thread Squeaky Pancakes
https://bugs.kde.org/show_bug.cgi?id=415819

Squeaky Pancakes  changed:

   What|Removed |Added

 CC||squeakypanca...@disroot.org

--- Comment #2 from Squeaky Pancakes  ---
I also see this issue on 5.19.2

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-26 Thread Richard Ferguson
https://bugs.kde.org/show_bug.cgi?id=418758

--- Comment #4 from Richard Ferguson  ---
OS NameMicrosoft Windows 10 Home
Version10.0.18363 Build 18363

Okular version 1.9.2.

It does not matter whether the characters following the "#" are blank,
numbers or letters.  As soon as Okular parses to the "#" it stops parsing
and because the file name is incomplete, the file cannot be opened.

On Fri, Jun 26, 2020 at 3:59 PM Jack  wrote:

> https://bugs.kde.org/show_bug.cgi?id=418758
>
> Jack  changed:
>
>What|Removed |Added
>
> 
>  CC|
> |ostroffjh@users.sourceforge
>||.net
>
> --- Comment #3 from Jack  ---
> (reposting from one of the duplicate bugs)  I just tested on (Gentoo)
> Linux,
> okular 1.9.3 (I see 1.10 is out) and it works fine.  I also tested 1.9.2
> (latest available in the Windows Store) in a Wind 10 guest in VirtualBox,
> and
> it also works fine whether # is at the beginning or in the middle of the
> file
> name.  What version of Windows are you on?
>
> Might the behavior depend on whether what is after the # are just digits,
> or
> non-digit alpha characters.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 422899] Kwin crashed when using present window option via hot corners.

2020-06-26 Thread Sebastian
https://bugs.kde.org/show_bug.cgi?id=422899

Sebastian  changed:

   What|Removed |Added

 CC||afonte...@hotmail.com

--- Comment #3 from Sebastian  ---
I run into the same problem. After a crash, I lose OpenGL rendering. When I go
to settings -> compositor I can enable it by switching to XRender and then
OpenGL again. As soon as I go to the hot corner, the same crash happens. Here
some system information:

Operating System: Arch Linux
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
Kernel Version: 5.7.4-arch1-1
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 11.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

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

[okular] [Bug 423560] [Windows Store] Filename extension associations and updates resetting them

2020-06-26 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=423560

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-26 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=418758

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #3 from Jack  ---
(reposting from one of the duplicate bugs)  I just tested on (Gentoo) Linux,
okular 1.9.3 (I see 1.10 is out) and it works fine.  I also tested 1.9.2
(latest available in the Windows Store) in a Wind 10 guest in VirtualBox, and
it also works fine whether # is at the beginning or in the middle of the file
name.  What version of Windows are you on?

Might the behavior depend on whether what is after the # are just digits, or
non-digit alpha characters.

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

[plasmashell] [Bug 423561] Widgets in the System Tray can no longer be disabled by default

2020-06-26 Thread The Feren OS Dev
https://bugs.kde.org/show_bug.cgi?id=423561

The Feren OS Dev  changed:

   What|Removed |Added

Summary|Notifications can no longer |Widgets in the System Tray
   |be disabled by default  |can no longer be disabled
   ||by default

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

[plasmashell] [Bug 423561] Notifications can no longer be disabled by default

2020-06-26 Thread The Feren OS Dev
https://bugs.kde.org/show_bug.cgi?id=423561

--- Comment #2 from The Feren OS Dev  ---
Update: I managed to use a bit of scripting and file editing to get around this
issue, however I've also come to find out that this issue also affects ANY
widget in the System Tray that can be disabled in configurations.

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

[kate] [Bug 417507] Kate ignores new mode/filetypes

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417507

--- Comment #1 from torokat...@gmail.com ---
Kate 20.04.1 is still affected.

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

[kate] [Bug 417507] Kate ignores new mode/filetypes

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417507

torokat...@gmail.com changed:

   What|Removed |Added

 CC||torokat...@gmail.com

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

[okular] [Bug 423517] Text in enabled form fields becomes smaller when the window is made wider, and eventually disappears; but only with certain widget styles.

2020-06-26 Thread Brendan Early
https://bugs.kde.org/show_bug.cgi?id=423517

--- Comment #10 from Brendan Early  ---
I'm just realizing that this is due to the zoom level changing when the window
is made wider.

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

[okular] [Bug 423517] Text in enabled form fields becomes smaller when the window is made wider, and eventually disappears; but only with certain widget styles.

2020-06-26 Thread Brendan Early
https://bugs.kde.org/show_bug.cgi?id=423517

--- Comment #9 from Brendan Early  ---
(In reply to David Hurka from comment #8)
> I think what you write makes sense.

It makes sense that the text size should change along with the rest of the
document. I do not think it makes sense that the form text size becomes smaller
when the rest of the document becomes bigger.

> But I still believe this is an issue with the widget style you are using. Is
> “Arc” the widget style?

My widget style is Breeze, Arc is only set for window decorations. I still see
this with a version I built using kdesrc-build & kdesrc-run.

> Another interpretation is that Okular shoudn’t rely on the system widget
> style to render form fields. For the same reason as why I think text
> highlight background shouldn’t follow the system color scheme: Form fields
> are inside a WYSIWYG graphics area, which shouldn’t and mostly doesn’t
> follow system stuff, but should do what the document says.

+1

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

[krita] [Bug 423562] New: Krita hangs on loading file that's not on the same drive

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423562

Bug ID: 423562
   Summary: Krita hangs on loading file that's not on the same
drive
   Product: krita
   Version: 4.3.0
  Platform: MS Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: kali...@wp.pl
  Target Milestone: ---

Yesterday I updated Krita 4.2.9->4.3.0 (installed on C:) and worked a bit on a
pretty small file (20MB .kra) that was stored on D:. Today I tried to run Krita
again and it won't load at all - it hangs somewhere at/after loading main
window (in fact freezes completely - I left it for more than half an hour and
nothing). It allowed to load only when I changed that file name (i.e. Krita
lost track of it).
Then I tried to start Krita via that file - freeze again.
Then I moved the file to C: - opened instantly.

At first it seemed to happen only to files created/saved in 4.3, but then I
opened an older file and saved it under different name in a folder that
contained files which were opening without issues before, even though they were
stored on D:. After closing Krita, it failed to open files from that folder any
more, even those that I haven't saved in 4.3. Moving any of these files to C:
allows to open them instantly.

I tried to remove and re-instal - nothing changed.

STEPS TO REPRODUCE
1. Create a file and save it on different drive than the on Krita is installed
on.
2. Close the app.
3. Try to open Krita again (either via .exe or that created file).

OBSERVED RESULT
Krita won't load.

EXPECTED RESULT
Krita loads.

SOFTWARE/OS VERSIONS
Windows 10 Pro

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

[okular] [Bug 423517] Text in enabled form fields becomes smaller when the window is made wider, and eventually disappears; but only with certain widget styles.

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=423517

David Hurka  changed:

   What|Removed |Added

Summary|Unable to see text typed|Text in enabled form fields
   |when filling forms  |becomes smaller when the
   ||window is made wider, and
   ||eventually disappears; but
   ||only with certain widget
   ||styles.

--- Comment #8 from David Hurka  ---
I think what you write makes sense.

But I still believe this is an issue with the widget style you are using. Is
“Arc” the widget style?

Another interpretation is that Okular shoudn’t rely on the system widget style
to render form fields. For the same reason as why I think text highlight
background shouldn’t follow the system color scheme: Form fields are inside a
WYSIWYG graphics area, which shouldn’t and mostly doesn’t follow system stuff,
but should do what the document says.

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

[okular] [Bug 423560] [Windows Store] Filename extension associations and updates resetting them

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=423560

--- Comment #1 from David Hurka  ---
Is it possible that Okular sets only some obvious extensions (like .pdf, .epub,
.okular), and you are missing extentions like .png, which are usually better
handled by other applications?

My memories of configuring standard applications was that Windows will refuse
to open files with other applications afterwards. (I am currently not a windows
user.) Is that still true? If so, installing Okular with all filename
extensions would cause serious trouble to most Windows users. Or can an
application mark these extensions as something like optional?

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

[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears

2020-06-26 Thread Thomas
https://bugs.kde.org/show_bug.cgi?id=416739

--- Comment #27 from Thomas  ---
Status after some tests: 

ACTUAL system software:

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-39-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz
Memory: 7,5 GiB of RAM



1 It appears after every reboot
2. Very usual setup - Laptop with an external monitor on VGA. Directly
connected or via a docking station, doesn't matter 
3. Only few differences in the .desktop-appletsrc files.  

 WORKING file (only the related entries) 

[Containments][10][Configuration]
PreloadWeight=10 

[Containments][2][Applets][6][Configuration]
PreloadWeight=100
SystrayContainmentId=7

[Containments][7][Applets][16][Configuration]
PreloadWeight=51 

[ScreenMapping]
itemsOnDisabledScreens=1,1,desktop:/moneyplex.desktop
screenMapping=desktop:/moneyplex.desktop,0,desktop:/FoxitReader.desktop,0  


** BAD file after reboot with missing panel 

[Containments][10][Configuration]
PreloadWeight=0

[Containments][2][Applets][6][Configuration]
PreloadWeight=99
SystrayContainmentId=7

[Containments][7][Applets][16][Configuration]
PreloadWeight=56

[ScreenMapping]
itemsOnDisabledScreens=
screenMapping=desktop:/moneyplex.desktop,1,desktop:/FoxitReader.desktop,1


The PreloadWeight entries may be part of the problem.

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

[okular] [Bug 423517] Unable to see text typed when filling forms

2020-06-26 Thread Brendan Early
https://bugs.kde.org/show_bug.cgi?id=423517

--- Comment #7 from Brendan Early  ---
> I've never seen an application change text size depending on window width.

I feel a bit silly for writing this. I think the intended behaviour here should
be that the text size should be the same as the rendered form text.

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=418758

David Hurka  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=406831

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=418758

--- Comment #2 from David Hurka  ---
If the document URL contains a #, Okular tries to focus the page specified by
the number following the #. Of course this fails if # is part of the actual
URL.

It was already suggested to interpret only #page=1234 as page number command,
currently Okular expects #1234 which doesn’t match the behavior of other
applications.

There is another older bug report about the original issue in this bug report,
but I don’t find it right now.

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

[okular] [Bug 406831] RFC compliant URL to specify page number not treated properly

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=406831

David Hurka  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=418758

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

[okular] [Bug 422856] Fails to open PDFs when name contains hash ('#')

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=422856

David Hurka  changed:

   What|Removed |Added

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

--- Comment #4 from David Hurka  ---


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

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=418758

David Hurka  changed:

   What|Removed |Added

 CC||withholdpurposefully@yahoo.
   ||com

--- Comment #1 from David Hurka  ---
*** Bug 422856 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 423517] Unable to see text typed when filling forms

2020-06-26 Thread Brendan Early
https://bugs.kde.org/show_bug.cgi?id=423517

--- Comment #6 from Brendan Early  ---
Pretty much, though it doesn't disappear when using Breeze. I'm pretty sure
I've never seen an application change text size depending on window width.

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

[plasmashell] [Bug 423561] Notifications can no longer be disabled by default

2020-06-26 Thread The Feren OS Dev
https://bugs.kde.org/show_bug.cgi?id=423561

--- Comment #1 from The Feren OS Dev  ---
Correction* org.kde.plasma.private.systemtray/contents/config/main.xml

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

[okular] [Bug 423517] Unable to see text typed when filling forms

2020-06-26 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=423517

--- Comment #5 from David Hurka  ---
Ah, ok, now I realize it. So the bug is:

Text in form fields becomes smaller when the window is made wider, and
eventually disappears. But when form fields are disabled, everthing is fine.

Correct?

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

[okular] [Bug 423560] [Windows Store] Filename extension associations and updates resetting them

2020-06-26 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=423560

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org,
   ||cullm...@kde.org,
   ||kde-wind...@kde.org

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

[plasmashell] [Bug 423561] New: Notifications can no longer be disabled by default

2020-06-26 Thread The Feren OS Dev
https://bugs.kde.org/show_bug.cgi?id=423561

Bug ID: 423561
   Summary: Notifications can no longer be disabled by default
   Product: plasmashell
   Version: 5.19.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: ferenos...@outlook.com
  Target Milestone: 1.0

SUMMARY
In Plasma 5.19.2, editing the default configuration of System Tray to exclude
the Notifications Plasmoid from the tray by default no longer disables the
Notifications Plasmoid in the tray by default, therefore breaking any
configurations where Notifications was present in a Latte Dock, etc rather than
in System Tray. This worked in Plasma 5.18.5, but stopped working in 5.19.2.



STEPS TO REPRODUCE
1. Configure System Tray to disable the Notifications widget
2. Copy the values saved to plasma-org.kde.plasma.desktop-appletsrc into the
/usr/share/plasma/plasmoids/org.kde.plasma.private.notifications/config/main.xml
file under their appropriate locations
3. Re-apply a Desktop Layout

OBSERVED RESULT
The Notifications widget gets re-added to the System Tray by Plasma despite the
default configs telling it not to

EXPECTED RESULT
The notifications widget will be disabled in the System Tray by default once
this default configurations change is in place.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Feren OS with KDE neon User Edition's 5.19.2
(available in About System)
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
I need this to work for Feren OS's default configuration as it otherwise breaks
the Latte Dock instance of the Notifications widget.

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

[okular] [Bug 423560] New: [Windows Store] Filename extension associations and updates resetting them

2020-06-26 Thread Beybalaev Murad Felixovich
https://bugs.kde.org/show_bug.cgi?id=423560

Bug ID: 423560
   Summary: [Windows Store] Filename extension associations and
updates resetting them
   Product: okular
   Version: 1.10.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: gness...@gmail.com
  Target Milestone: ---

Created attachment 129708
  --> https://bugs.kde.org/attachment.cgi?id=129708=edit
Registry patch

I use Okular distributed on Windows Store on my Windows 10 OS.
Upon installation **and updates** Okular sets its filename extension
associations to only a handful of formats. It is in fact able to parse many
more formats but limitations of Windows Apps platform, subject to Windows
Store, make it impossible to open any arbitrary filetype in Okular straight
from OS without first launching Okular and using its "Open" dialog.

Note, that trying to associate an "App" installed through Windows Store using
the legacy OS "Open with" dialog just does not accomplish anything other than
leave you with a registry mess to clean up if forced.

I had to resort to writing my own registry patch (attached) to add all
supported associations bindings (and some that seem underdeveloped in the
Windows build, but it doesn't hurt anyway).

If you take a look at the attached registry patch, note that only the first key
with its many values (first 60 lines) is required — rest is just for extended
support and can be omitted AFAIC.
Also note, that key name (path) includes the version string.

Now for the meat of the issue: not only do I have to reapply the registry patch
on every update, but I also have to edit it in accordance with the new version
string every time.

I could write a script to heuristically accomplish this for me but it doesn't
feel like it's too much to ask you, as developers, to instead open the whole
array of associations by default or at least give me, as a user, an option to
enable further filename extension associations.

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

[okular] [Bug 422856] Fails to open PDFs when name contains hash ('#')

2020-06-26 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=422856

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #3 from Jack  ---
Just tested on (Gentoo) Linux, okular 1.9.3 (I see 1.10 is out) and it works
fine.  I also tested 1.9.2 (latest available in the Windows Store) in a Wind 10
guest in VirtualBox, and it also works fine whether # is at the beginning or in
the middle of the file name.  What version of Windows are you on?

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

[systemsettings] [Bug 423459] On second chose in any options of left panel, systemsettings crash

2020-06-26 Thread frnobre
https://bugs.kde.org/show_bug.cgi?id=423459

frnobre  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

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

[plasmashell] [Bug 423559] New: plasmashell segmentation fault in DeclarativeMimeData::DeclarativeMimeData when dragging and dropping a link from Firefox to Konsole

2020-06-26 Thread Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=423559

Bug ID: 423559
   Summary: plasmashell segmentation fault in
DeclarativeMimeData::DeclarativeMimeData when dragging
and dropping a link from Firefox to Konsole
   Product: plasmashell
   Version: 5.19.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: matthew.fagn...@utoronto.ca
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.19.2)

Qt Version: 5.14.2
Frameworks Version: 5.71.0
Operating System: Linux 5.8.0-0.rc2.20200625git8be3a53e18e0.1.fc33.x86_64
x86_64
Windowing system: Wayland
Distribution: Fedora 33 (KDE Plasma Prerelease)

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

I was using a Fedora Rawhide KDE Plasma spin installation with Plasma 5.19.2,
KF 5.71.0, Qt 5.14.2. I started Plasma on Wayland. I started Konsole 20.04.2 on
Wayland. I opened Firefox Nightly 79.0a1 (2020-6-26) on Wayland. I went to
youtube. I resized Firefox. I dragged and dropped a link from Firefox to
Konsole. A plasmashell segmentation fault in
DeclarativeMimeData::DeclarativeMimeData at
/usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:55
in kf5-kdeclarative-5.71.0-1.fc33 happened. The link showed up correctly in
Konsole.

- Unusual behavior I noticed:
The task manager bar disappeared from the bottom of the screen and reappeared.

I tried the same procedure a few times, but the crash didn't happen again.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x7f716ef0fa63 in DeclarativeMimeData::DeclarativeMimeData
(this=0x55e8b255ca10, copy=0x55e8b232f970) at
/usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:55
#5  0x7f716ef0efb0 in DeclarativeDragDropEvent::mimeData
(this=0x7ffea00cc8c0) at /usr/include/qt5/QtGui/qevent.h:656
#6  0x7f716ef09d35 in DeclarativeDragDropEvent::qt_static_metacall
(_a=, _id=, _c=, _o=) at
/usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/x86_64-redhat-linux-gnu/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:121
#7  DeclarativeDragDropEvent::qt_static_metacall (_o=,
_c=, _id=, _a=) at
/usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/x86_64-redhat-linux-gnu/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:93
#8  0x7f71bf06e0b1 in QQmlPropertyData::readPropertyWithArgs
(args=0x7ffea00caa10, target=0x7ffea00cc8c0, this=0x55e8b3052c28) at
../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:274
#9  QQmlPropertyData::readProperty (property=0x7ffea00ca9f0,
target=0x7ffea00cc8c0, this=0x55e8b3052c28) at
../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:268
#10 loadProperty (v4=0x55e8b0f9c1f0, object=0x7ffea00cc8c0, property=...) at
jsruntime/qv4qobjectwrapper.cpp:138
#11 0x7f71bf08c3c1 in QV4::Moth::VME::interpret (frame=0x7ffea00cac10,
engine=0x55e8b0f9c1f0, code=0x7f715a6a94ba
":\004:\005\030\b\022>\030\v\246\006\b\001\v\030\b\006b\bL\005\246\a\006") at
jsruntime/qv4vme_moth.cpp:638
#12 0x7f71bf0909c7 in QV4::Moth::VME::exec
(frame=frame@entry=0x7ffea00cac10, engine=engine@entry=0x55e8b0f9c1f0) at
jsruntime/qv4vme_moth.cpp:463
#13 0x7f71bf02d53d in QV4::Function::call (this=this@entry=0x55e8b19cb160,
thisObject=, argv=argv@entry=0x7f71a9bc2508, argc=, context=) at jsruntime/qv4function.cpp:69
#14 0x7f71bf194955 in QQmlJavaScriptExpression::evaluate
(this=this@entry=0x55e8b19b12b0, callData=callData@entry=0x7f71a9bc24d8,
isUndefined=isUndefined@entry=0x0) at
../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343
#15 0x7f71bf14bf5e in QQmlBoundSignalExpression::evaluate (this=, a=) at
../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95
#16 0x7f71bf14c498 in QQmlBoundSignal_callback (e=0x55e8b19b6fd0,
a=0x7ffea00cc890) at
../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69
#17 0x7f71bf17a5bd in QQmlNotifier::emitNotify (endpoint=,
a=0x7ffea00cc890) at qml/qqmlnotifier.cpp:104
#18 0x7f71bdb92ee2 in doActivate (sender=0x55e8b196de30,
signal_index=30, argv=argv@entry=0x7ffea00cc890) at
/usr/include/c++/10/bits/atomic_base.h:741
#19 0x7f71bdb8d7f8 in QMetaObject::activate
(sender=sender@entry=0x55e8b196de30, m=m@entry=0x7f716ef17480
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffea00cc890)
at kernel/qobject.cpp:3930
#20 0x7f716ef09663 in DeclarativeDropArea::dragEnter

[systemsettings] [Bug 423459] On second chose in any options of left panel, systemsettings crash

2020-06-26 Thread frnobre
https://bugs.kde.org/show_bug.cgi?id=423459

--- Comment #5 from frnobre  ---
I made a fresh install of Tumbleweed and error is gone.

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

[Discover] [Bug 349594] Muon updater. After download updates . This software doesn't have able installing that updates.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=349594

madbro9...@gmail.com changed:

   What|Removed |Added

 CC||madbro9...@gmail.com

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

[plasmashell] [Bug 423558] New: System tray has no items after update to 5.19.1

2020-06-26 Thread Jeroen
https://bugs.kde.org/show_bug.cgi?id=423558

Bug ID: 423558
   Summary: System tray has no items after update to 5.19.1
   Product: plasmashell
   Version: 5.19.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: jrfo...@xs4all.nl
  Target Milestone: 1.0

Created attachment 129707
  --> https://bugs.kde.org/attachment.cgi?id=129707=edit
Contains files for debugging: plasmashell replace nohup, screenshot of system
tray, plasmoidviewer systemtray, plasma-org.kde.plasma.desktop-appletsrc

SUMMARY
My systray is completely broken, no items are available at all. Also those
pop-ups I usually get for media controls (for example when I connect my
bluetooth speakers you get a pop-up) are completely gone. I have attempted
various manual changes to the plasma-org.kde.plasma.desktop-appletsrc and while
I was able to remove some widgets that even after removing were still present
by deleting the configurations from this file, it had no effect on my systray
at all. After a desparate attempt to fix this by deleting the whole .config and
.cache folders, I still have no systay but I cannot change my background
anymore either. When I right-click on the desktop and select "Configure
Desktop...". It throws an error saying "Layout changes must be applied before
...". The menu is empty and apply now does nothing. Everythis is grayed out.
Also my keyboard shortcuts are no longer working.

Creating a new user via the system settings only copies over files from
/etc/skel to the new user, it does not setup plasma (another bug?). Logging in
anyway gives me an empty desktop with a default background and no panel /
widgets / icons whatsoever. Creating the systray widget on the desktop gives me
and empty box with no systray items. Creating a new user seems to be broken as
well it seems, but that's a different issue.

I didn't install any additional plasmoids, my . I do have latte-dock. Removing
it has no effect.

Updating to 5.19.2 doesn't solve my issue.

I was advised to no longer use bug 423107 but to create a new one.


STEPS TO REPRODUCE
1. Update to 5.19.1
2. Reboot
2. All plasma systray items are gone, my own like transgui and keepass are
still there
3. Reboot
4. All systray items are gone

OBSERVED RESULT
No Items in system tray

EXPECTED RESULT
Items in system tray

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.19
(available in About System)
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

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

[frameworks-kirigami] [Bug 403837] ScrollablePage should not allow drag-scrolling on desktop

2020-06-26 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=403837

Ismael Asensio  changed:

   What|Removed |Added

 CC||isma...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[frameworks-kio] [Bug 423057] Dolphin incorrectly displays the partition size

2020-06-26 Thread Nazar Kalinowski
https://bugs.kde.org/show_bug.cgi?id=423057

--- Comment #1 from Nazar Kalinowski  ---
I've done some debugging, and found out that that the file that is taking 128TB
(and it is taken into account when displaying total size) is 'proc/kcore'.
No idea what to do next with this information, so I will just leave it here.

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

[Akonadi] [Bug 423557] New: imap resource crashes when pressing "restart" it there is issues with connection to the server

2020-06-26 Thread Vadim A. Misbakh-Soloviov
https://bugs.kde.org/show_bug.cgi?id=423557

Bug ID: 423557
   Summary: imap resource crashes when pressing "restart" it there
is issues with connection to the server
   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: k...@mva.name
  Target Milestone: ---

Application: akonadi_imap_resource (5.13.2 (19.12.2))
 (Compiled from sources)
Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.7.4 x86_64
Windowing system: X11
Distribution: "Gentoo GNU/Linux"

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

I have problem with this exact agent and can geit it to work and sync emails
(after few months of being offline).
As one of the things, I pressed "Restart" button in KMail's "accounts" dialog.
That triggered the crash...

The crash can be reproduced every time.

-- Backtrace:
Application: PDD (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f811ca48dc0 (LWP 789314))]

Thread 15 (Thread 0x7f80e1c2c700 (LWP 864639)):
#0  0x7f814294cf10 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f81429016bf in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8142901db2 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8142901f2f in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f81485f545b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f81485a03fb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f81483f6c5e in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f81483f7c8c in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f814526134a in start_thread () at /lib64/libpthread.so.0
#9  0x7f8147c70f6f in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f80aad08700 (LWP 864526)):
#0  0x7f8147c65023 in poll () at /lib64/libc.so.6
#1  0x7f8142901e0e in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8142901f2f in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f81485f545b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f81485a03fb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f81483f6c5e in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f81483f7c8c in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f814526134a in start_thread () at /lib64/libpthread.so.0
#8  0x7f8147c70f6f in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f8093fff700 (LWP 864259)):
#0  0x7f8147c60712 in read () at /lib64/libc.so.6
#1  0x7f8142948b2f in g_wakeup_acknowledge () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8142901967 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8142901db2 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8142901f2f in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f81485f545b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f81485a03fb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f81483f6c5e in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f81483f7c8c in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f814526134a in start_thread () at /lib64/libpthread.so.0
#10 0x7f8147c70f6f in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f80e2c2e700 (LWP 808570)):
#0  0x7f8147c60768 in read () at /lib64/libc.so.6
#1  0x7f8142948b2f in g_wakeup_acknowledge () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8142901967 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8142901db2 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8142901f2f in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f81485f545b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f81485a03fb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f81483f6c5e in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f81483f7c8c in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f814526134a in start_thread () at /lib64/libpthread.so.0
#10 0x7f8147c70f6f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f810c9c2700 (LWP 807832)):
#0  0x7f8147c65023 in poll () at /lib64/libc.so.6
#1  0x7f8142901e0e in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8142901f2f in g_main_context_iteration 

[kwin] [Bug 423436] kwin_rules_dialog closed unexpectedly

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423436

gr...@kde.org changed:

   What|Removed |Added

 CC||gr...@kde.org

--- Comment #3 from gr...@kde.org ---
Problem appears to (have been) that kitemmodels QML plugin was missing in
packaging. I just updated the packaging with that plugin and the crash has gone
away.

(Leaving the bug in WAITINGFORINFO state because I'd like tcberner to confirm
it's fixed now)

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

[Powerdevil] [Bug 423556] New: Undefined Behaviour of the applet in displaying battery charging/discharging status

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423556

Bug ID: 423556
   Summary: Undefined Behaviour of the applet in displaying
battery charging/discharging status
   Product: Powerdevil
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kesarl...@outlook.com
  Target Milestone: ---

SUMMARY

I am using the latest version of KDE-plasma5 on latest Pop!_OS (20.04). The
battery Icon in the tray shows undefined behaviour.

There are 2 states to the behaviour:

1. It shows the change (i.e. power has been plugged in/out about an hour later)

2. It remains in the state it was when I powered on my Laptop even when I
disconnect/ plugin. (i.e. if it was plugged in at boot time, it keeps showing 
plugged in even when the cord has been disconnected and vice versa.)

Here I would like to note that whenever I hover in the applet, it shows the
current charge of the battery accurately. However, it fails to recognise the
state. Also, when I click on the applet, the widget detects the state
accurately. 

The annoying part is when the Laptop gets suspended as the applet cannot
recognize the battery level (at times it has suspended at 100% battery)

STEPS TO REPRODUCE
1. Plug in the charger
2. Boot the Laptop
3. See the state of the applet
4. Remove the charging cord

OBSERVED RESULT

Undefined Behaviour of the applet in displaying battery charging/discharging
status (as mentioned above)


EXPECTED RESULT
Well, do I really need to put anything here? ;)

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

ADDITIONAL INFORMATION

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

[Powerdevil] [Bug 423556] Undefined Behaviour of the applet in displaying battery charging/discharging status

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423556

kesarl...@outlook.com changed:

   What|Removed |Added

 CC||kesarl...@outlook.com

--- Comment #1 from kesarl...@outlook.com ---
Created attachment 129706
  --> https://bugs.kde.org/attachment.cgi?id=129706=edit
Snaps of the error

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

[solid] [Bug 269855] KDE daemon crashed after connecting power

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=269855

kesarl...@outlook.com changed:

   What|Removed |Added

 CC||kesarl...@outlook.com

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

[kde] [Bug 423555] Reducing # of monitors causes kdeinit to core and login not to complete or hang.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423555

--- Comment #4 from whten...@up.com ---
The work around at this time is to remove the below file.  However, the login
process should recognize that the # of screens changed and the configs should
be adjusted for this scenario.

~/.kde/share/config/plasma-desktop-appletsrc

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

[kde] [Bug 423555] Reducing # of monitors causes kdeinit to core and login not to complete or hang.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423555

--- Comment #3 from whten...@up.com ---
Here is the config file that was re-generated that allowed the login to
complete.

# cat plasma-desktop-appletsrc
[ActionPlugins]
MidButton;NoModifier=paste
RightButton;NoModifier=contextmenu
wheel:Vertical;NoModifier=switchdesktop

[AppletGlobals][plasma_applet_launcher]
brasero=
ca.desrt.dconf-editor=
emacs=
emacsclient=
esc=
firefox=
firewall-config=
gimp=
gnome-abrt=
gvim=
htop=
java-1.8.0-openjdk-1.8.0.232.b09-0.el7_7.x86_64-policytool=
kde4-Help=
kde4-Home=
kde4-KCharSelect=
kde4-akonaditray=
kde4-akregator=
kde4-ark=
kde4-bluedevil-monolithic=
kde4-dolphin=
kde4-gwenview=
kde4-kaddressbook=
kde4-kalarm=
kde4-kate=
kde4-kcalc=
kde4-kcolorchooser=
kde4-kdf=
kde4-kfind=
kde4-kget=
kde4-kgpg=
kde4-kinfocenter=
kde4-kleopatra=
kde4-klipper=
kde4-kmag=
kde4-kmix=
kde4-knetattach=
kde4-knotes=
kde4-konqbrowser=
kde4-konsole=
kde4-korganizer=
kde4-krfb=
kde4-kruler=
kde4-ksnapshot=
kde4-ksshaskpass=
kde4-ksysguard=
kde4-ksystemlog=
kde4-ktimer=
kde4-ktimetracker=
kde4-kuser=
kde4-kwalletmanager=
kde4-kwikdisk=
kde4-kwrite=
kde4-nepomukbackup=
kde4-nepomukcleaner=
kde4-nepomukcontroller=
kde4-okular=
kde4-sweeper=
kde4-systemsettings=
libreoffice-base=
libreoffice-calc=
libreoffice-draw=
libreoffice-impress=
libreoffice-writer=
nvidia-settings=
obconf-qt=
org.gnome.ColorProfileViewer=
org.gnome.DiskUtility=
org.gnome.GPaste.Ui=
org.gnome.Nautilus=
org.gnome.Terminal=
org.gnome.clocks=
org.gnome.font-viewer=
qt4-assistant=
qt4-designer=
qt4-linguist=
setroubleshoot=
system-config-date=
vncviewer=
wireshark=
x11vnc=
xterm=

[Containments][1]
activity=
activityId=
desktop=-1
formfactor=2
geometry=0,-41,3840,35
immutability=1
lastDesktop=-1
lastScreen=0
location=4
plugin=panel
screen=0
zvalue=0

[Containments][1][ActionPlugins]
RightButton;NoModifier=contextmenu

[Containments][1][Applets][2]
geometry=0,3,32,32
immutability=1
plugin=launcher
zvalue=0

[Containments][1][Applets][2][LayoutInformation]
Order=0

[Containments][1][Applets][3]
geometry=36,3,32,32
immutability=1
plugin=org.kde.showActivityManager
zvalue=0

[Containments][1][Applets][3][LayoutInformation]
Order=1

[Containments][1][Applets][4]
geometry=72,3,0,32
immutability=1
plugin=pager
zvalue=0

[Containments][1][Applets][4][Configuration]
hideWhenSingleDesktop=true

[Containments][1][Applets][4][LayoutInformation]
Order=2

[Containments][1][Applets][5]
geometry=76,3,3534,32
immutability=1
plugin=tasks
zvalue=0

[Containments][1][Applets][5][LayoutInformation]
Order=3

[Containments][1][Applets][6]
geometry=3614,3,134,32
immutability=1
plugin=systemtray
zvalue=0

[Containments][1][Applets][6][Configuration]
DefaultAppletsAdded=true

[Containments][1][Applets][6][Configuration][Applets][1]
geometry=0,0,24,24
immutability=1
plugin=printmanager
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][12]
geometry=0,0,24,24
immutability=1
plugin=org.kde.networkmanagement
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][12][PopupApplet]
DialogHeight=328
DialogWidth=570

[Containments][1][Applets][6][Configuration][Applets][13]
geometry=0,0,24,24
immutability=1
plugin=notifier
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][14]
geometry=0,0,24,24
immutability=1
plugin=org.kde.notifications
zvalue=0

[Containments][1][Applets][6][Configuration][Shortcuts]
SystemTray-Klipper-6=Ctrl+Alt+V

[Containments][1][Applets][6][LayoutInformation]
Order=4

[Containments][1][Applets][7]
geometry=3752,3,64,32
immutability=1
plugin=digital-clock
zvalue=0

[Containments][1][Applets][7][LayoutInformation]
Order=5

[Containments][1][Configuration]
maximumSize=3840,35
minimumSize=3840,35

[Containments][10]
activity=
activityId=
desktop=-1
formfactor=2
geometry=0,-117,3840,35
immutability=1
lastDesktop=-1
lastScreen=1
location=4
plugin=panel
screen=1
zvalue=0

[Containments][10][ActionPlugins]
RightButton;NoModifier=contextmenu

[Containments][10][Applets][11]
geometry=0,3,3816,32
immutability=1
plugin=tasks
zvalue=0

[Containments][10][Applets][11][Configuration]
showOnlyCurrentScreen=true

[Containments][10][Applets][11][LayoutInformation]
Order=0

[Containments][10][Configuration]
maximumSize=3840,35
minimumSize=3840,35

[Containments][8]
ActionPluginsSource=Global
activity=Desktop
activityId=1c316c68-ef7a-4773-adae-5a088a60856f
desktop=-1
formfactor=0
geometry=0,0,3840,2160
immutability=1
lastDesktop=-1
lastScreen=0
location=0
plugin=desktop
screen=0
wallpaperplugin=image
wallpaperpluginmode=SingleImage
zvalue=0

[Containments][9]
ActionPluginsSource=Global
activity=Desktop
activityId=1c316c68-ef7a-4773-adae-5a088a60856f
desktop=-1
formfactor=0
geometry=3846,0,3840,2160
immutability=1
lastDesktop=-1
lastScreen=1
location=0
plugin=desktop
screen=1
wallpaperplugin=image
wallpaperpluginmode=SingleImage
zvalue=0

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

[kde] [Bug 423555] Reducing # of monitors causes kdeinit to core and login not to complete or hang.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423555

--- Comment #2 from whten...@up.com ---
Solution:

Removed this file: ~/.kde/share/config/plasma-desktop-appletsrc


Here is the plasma-desktop-appletsrc file that would prevent 2 monitor from
completing the kde login process and also cause kdeinit to core dump.

# cat plasma-desktop-appletsrc
[ActionPlugins]
MidButton;NoModifier=paste
RightButton;NoModifier=contextmenu
wheel:Vertical;NoModifier=switchdesktop

[AppletGlobals][plasma_applet_launcher]
brasero=
ca.desrt.dconf-editor=
emacs=
emacsclient=
esc=
firefox=
firewall-config=
gimp=
gnome-abrt=
gvim=
htop=
java-1.8.0-openjdk-1.8.0.232.b09-0.el7_7.x86_64-policytool=
kde4-Help=
kde4-Home=
kde4-KCharSelect=
kde4-akonaditray=
kde4-akregator=
kde4-ark=
kde4-bluedevil-monolithic=
kde4-dolphin=
kde4-gwenview=
kde4-kaddressbook=
kde4-kalarm=
kde4-kate=
kde4-kcalc=
kde4-kcolorchooser=
kde4-kdf=
kde4-kfind=
kde4-kget=
kde4-kgpg=
kde4-kinfocenter=
kde4-kleopatra=
kde4-klipper=
kde4-kmag=
kde4-kmix=
kde4-knetattach=
kde4-knotes=
kde4-konqbrowser=
kde4-konsole=
kde4-korganizer=
kde4-krfb=
kde4-kruler=
kde4-ksnapshot=
kde4-ksshaskpass=
kde4-ksysguard=
kde4-ksystemlog=
kde4-ktimer=
kde4-ktimetracker=
kde4-kuser=
kde4-kwalletmanager=
kde4-kwikdisk=
kde4-kwrite=
kde4-nepomukbackup=
kde4-nepomukcleaner=
kde4-nepomukcontroller=
kde4-okular=
kde4-sweeper=
kde4-systemsettings=
libreoffice-base=
libreoffice-calc=
libreoffice-draw=
libreoffice-impress=
libreoffice-writer=
nvidia-settings=
obconf-qt=
org.gnome.ColorProfileViewer=
org.gnome.DiskUtility=
org.gnome.GPaste.Ui=
org.gnome.Nautilus=
org.gnome.Terminal=
org.gnome.clocks=
org.gnome.font-viewer=
qt4-assistant=
qt4-designer=
qt4-linguist=
setroubleshoot=
system-config-date=
vncviewer=
wireshark=
x11vnc=
xterm=

[Containments][1]
activity=
activityId=
desktop=-1
formfactor=2
geometry=0,-41,3840,35
immutability=1
lastDesktop=-1
lastScreen=0
location=4
plugin=panel
screen=0
zvalue=0

[Containments][1][ActionPlugins]
RightButton;NoModifier=contextmenu

[Containments][1][Applets][2]
geometry=0,3,32,32
immutability=1
plugin=launcher
zvalue=0

[Containments][1][Applets][2][Configuration]
icon=system-logo-icon

[Containments][1][Applets][2][LayoutInformation]
Order=0

[Containments][1][Applets][3]
geometry=36,3,32,32
immutability=1
plugin=org.kde.showActivityManager
zvalue=0

[Containments][1][Applets][3][LayoutInformation]
Order=1

[Containments][1][Applets][4]
geometry=72,3,0,32
immutability=1
plugin=pager
zvalue=0

[Containments][1][Applets][4][Configuration]
hideWhenSingleDesktop=true

[Containments][1][Applets][4][LayoutInformation]
Order=2

[Containments][1][Applets][5]
geometry=76,3,3562,32
immutability=1
plugin=tasks
zvalue=0

[Containments][1][Applets][5][LayoutInformation]
Order=3

[Containments][1][Applets][6]
geometry=3642,3,106,32
immutability=1
plugin=systemtray
zvalue=0

[Containments][1][Applets][6][Configuration]
DefaultAppletsAdded=true

[Containments][1][Applets][6][Configuration][Applets][1]
geometry=0,0,24,24
immutability=1
plugin=printmanager
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][2]
geometry=0,0,24,24
immutability=1
plugin=org.kde.networkmanagement
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][2][PopupApplet]
DialogHeight=216
DialogWidth=570

[Containments][1][Applets][6][Configuration][Applets][24]
plugin=notifications

[Containments][1][Applets][6][Configuration][Applets][30]
geometry=0,0,24,24
immutability=1
plugin=notifier
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][31]
geometry=0,0,24,24
immutability=1
plugin=org.kde.notifications
zvalue=0

[Containments][1][Applets][6][Configuration][Applets][31][PopupApplet]
DialogHeight=108
DialogWidth=412

[Containments][1][Applets][6][Configuration][Shortcuts]
SystemTray-Klipper-6=Ctrl+Alt+V

[Containments][1][Applets][6][LayoutInformation]
Order=4

[Containments][1][Applets][7]
geometry=3752,3,64,32
immutability=1
plugin=digital-clock
zvalue=0

[Containments][1][Applets][7][LayoutInformation]
Order=5

[Containments][1][Configuration]
maximumSize=3840,35
minimumSize=3840,35

[Containments][10]
activity=
activityId=
desktop=-1
formfactor=2
geometry=0,-117,3840,35
immutability=1
lastDesktop=-1
lastScreen=1
location=4
plugin=panel
screen=1
zvalue=0

[Containments][10][ActionPlugins]
RightButton;NoModifier=contextmenu

[Containments][10][Applets][11]
geometry=0,3,3816,32
immutability=1
plugin=tasks
zvalue=0

[Containments][10][Applets][11][Configuration]
showOnlyCurrentScreen=true

[Containments][10][Applets][11][LayoutInformation]
Order=0

[Containments][10][Configuration]
maximumSize=3840,35
minimumSize=3840,35

[Containments][12]
ActionPluginsSource=Global
activity=Desktop
activityId=1c316c68-ef7a-4773-adae-5a088a60856f
desktop=-1
formfactor=0
geometry=0,2316,3840,2160
immutability=1
lastDesktop=-1
lastScreen=2
location=0
plugin=desktop
screen=2
wallpaperplugin=image
wallpaperpluginmode=SingleImage
zvalue=0

[Containments][12][Wallpaper][image]

[kate] [Bug 411165] Make GoTo line work backward

2020-06-26 Thread Nazar Kalinowski
https://bugs.kde.org/show_bug.cgi?id=411165

Nazar Kalinowski  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/ktexteditor/commit/7
   ||1b4295ab447f17d3a12f7dd38db
   ||4a345c5087d5
 Resolution|--- |FIXED

--- Comment #5 from Nazar Kalinowski  ---
Git commit 71b4295ab447f17d3a12f7dd38db4a345c5087d5 by Nazar Kalinowski.
Committed on 25/06/2020 at 13:26.
Pushed by cullmann into branch 'master'.

Make "goto line" work backwards

This patch allows "goto line" feature to work backwards with negative numbers.

M  +13   -5src/dialogs/katedialogs.cpp

https://invent.kde.org/frameworks/ktexteditor/commit/71b4295ab447f17d3a12f7dd38db4a345c5087d5

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

[kde] [Bug 423555] Reducing # of monitors causes kdeinit to core and login not to complete or hang.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423555

--- Comment #1 from whten...@up.com ---
Troubleshooting:

# cd /var/spool/abrt
# cd ccpp-2020-06-25-14\:59\:19-3397/
# cat core_backtrace
{   "signal": 11
,   "executable": "/usr/bin/kdeinit4"
,   "stacktrace":


# eu-unstrip -n --core=./coredump
0x40+0x20f000 a7227b2dcab83588117493d6efe2e99805f4c54a@0x400284 .
/usr/lib/debug/usr/bin/kdeinit4.debug /usr/bin/kdeinit4
0x7ffd55b8+0x1000 7f945b2385125e0b9a6c187543a8c96f8f9400c0@0x7ffd55b80328 .
- linux-vdso.so.1


# yum install gdb elfutils
#  yum install colord-kde-debuginfo.x86_64 kde-baseapps-debuginfo.x86_64
kde-plasma-networkmanagement-debuginfo.x86_64
kde-print-manager-debuginfo.x86_64 kde-runtime-debuginfo.x86_64
kde-workspace-debuginfo.x86_64 kdeadmin-debuginfo.x86_64
kdeartwork-debuginfo.x86_64 kdegraphics-strigi-analyzer-debuginfo.x86_64
kdegraphics-thumbnailers-debuginfo.x86_64 kdelibs-debuginfo.x86_64
kdenetwork-debuginfo.x86_64 kdepim-debuginfo.x86_64
kdepim-runtime-debuginfo.x86_64 kdepimlibs-debuginfo.x86_64
kdeplasma-addons-debuginfo.x86_64 kdesdk-debuginfo.x86_64
libblockdev-debuginfo.x86_64 lockdev-debuginfo.x86_64
polkit-kde-debuginfo.x86_64 pykde4-debuginfo.x86_64
xsettings-kde-debuginfo.x86_64

# debuginfo-install OpenEXR-libs-1.7.1-7.el7.x86_64 akonadi-1.9.2-4.el7.x86_64
attica-0.4.2-1.el7.x86_64 bzip2-libs-1.0.6-13.el7.x86_64
compat-libical1-1.0.1-2.el7.x86_64 dbus-libs-1.10.24-13.el7_6.x86_64
dbusmenu-qt-0.9.2-7.el7.x86_64 elfutils-libelf-0.176-2.el7.x86_64
elfutils-libs-0.176-2.el7.x86_64 expat-2.1.0-10.el7_3.x86_64
flac-libs-1.3.0-5.el7_1.x86_64 fontconfig-2.13.0-4.3.el7.x86_64
freetype-2.8-14.el7.x86_64 gamin-0.1.10-16.el7.x86_64 glib2-2.56.1-5.el7.x86_64
glibc-2.17-292.el7.x86_64 gsm-1.0.13-11.el7.x86_64 ilmbase-1.0.3-7.el7.x86_64
jasper-libs-1.900.1-33.el7.x86_64 jbigkit-libs-2.0-11.el7.x86_64
kactivities-4.10.5-3.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.15.1-37.el7_7.2.x86_64 libICE-1.0.9-9.el7.x86_64
libSM-1.2.2-2.el7.x86_64 libX11-1.6.7-2.el7.x86_64
libXScrnSaver-1.2.2-6.1.el7.x86_64 libXau-1.0.8-2.1.el7.x86_64
libXcomposite-0.4.4-4.1.el7.x86_64 libXcursor-1.1.15-1.el7.x86_64
libXdamage-1.1.4-4.1.el7.x86_64 libXdmcp-1.1.2-6.el7.x86_64
libXext-1.3.3-3.el7.x86_64 libXfixes-5.0.3-1.el7.x86_64
libXft-2.3.2-2.el7.x86_64 libXi-1.7.9-1.el7.x86_64
libXinerama-1.1.3-2.1.el7.x86_64 libXpm-3.5.12-1.el7.x86_64
libXrandr-1.5.1-2.el7.x86_64 libXrender-0.9.10-1.el7.x86_64
libXtst-1.2.3-1.el7.x86_64 libacl-2.2.51-14.el7.x86_64
libasyncns-0.8-7.el7.x86_64 libattr-2.4.46-13.el7.x86_64
libcap-2.22-10.el7.x86_64 libcom_err-1.42.9-16.el7.x86_64
libffi-3.0.13-18.el7.x86_64 libgcc-4.8.5-39.el7.x86_64
libgcrypt-1.5.3-14.el7.x86_64 libglvnd-1.0.1-0.8.git5baa1e5.el7.x86_64
libglvnd-glx-1.0.1-0.8.git5baa1e5.el7.x86_64 libgpg-error-1.12-3.el7.x86_64
libicu-50.2-3.el7.x86_64 libjpeg-turbo-1.2.90-8.el7.x86_64
libmng-1.0.10-14.el7.x86_64 libogg-1.3.0-7.el7.x86_64
libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-14.1.el7.x86_64
libsndfile-1.0.25-10.el7.x86_64 libstdc++-4.8.5-39.el7.x86_64
libtiff-4.0.3-32.el7.x86_64 libuuid-2.23.2-61.el7.x86_64
libvorbis-1.3.3-8.el7.1.x86_64 libxcb-1.13-1.el7.x86_64
libxml2-2.9.1-6.el7_2.3.x86_64 lz4-1.7.5-3.el7.x86_64
openssl-libs-1.0.2k-19.el7.x86_64 pcre-8.32-17.el7.x86_64
phonon-4.6.0-10.el7.x86_64 pulseaudio-libs-10.0-5.el7.x86_64
pulseaudio-libs-glib2-10.0-5.el7.x86_64 qca2-2.0.3-7.el7.x86_64
soprano-2.9.2-3.el7.x86_64 strigi-libs-0.7.7-13.20120626.el7.x86_64
systemd-libs-219-67.el7_7.2.x86_64 tcp_wrappers-libs-7.6-77.el7.x86_64
xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64


# gdb -e /usr/bin/kdeinit4 -c coredump
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
.

warning: core file may not match specified executable file.
[New LWP 3462]
[New LWP 3463]
[New LWP 3465]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `kdeinit4: plasma-desktop [kdeinit] '.
Program terminated with signal 11, Segmentation fault.
#0  0x7f1b76e254bb in raise (sig=11) at
../nptl/sysdeps/unix/sysv/linux/pt-raise.c:36
36 return INLINE_SYSCALL (tgkill, 3, pid, THREAD_GETMEM (THREAD_SELF, tid),
(gdb) bt
#0  0x7f1b76e254bb in raise (sig=11) at
../nptl/sysdeps/unix/sysv/linux/pt-raise.c:36
#1  0x7f1b7824b11f in KCrash::defaultCrashHandler(int) () from
/lib64/libkdeui.so.5
#2  
#3  0x7f1b4b1ad85c in Tasks::init (this=0x10a3d50) at
/usr/src/debug/kde-workspace-4.11.19/plasma/desktop/applets/tasks/tasks.cpp:103
#4  0x7f1b62b3491c in 

[kde] [Bug 423555] New: Reducing # of monitors causes kdeinit to core and login not to complete or hang.

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423555

Bug ID: 423555
   Summary: Reducing # of monitors causes kdeinit to core and
login not to complete or hang.
   Product: kde
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: whten...@up.com
  Target Milestone: ---

SUMMARY
When reducing the monitors from 6 to 2, KDE would not complete login to the
workspace after password had been completed.  Sound would load and then hang at
the icons loading at the bottom left of the monitor.

STEPS TO REPRODUCE
1. Unplug 4 of the 6 monitors, leaving only 2
2. Reboot
3. Login with credentials

OBSERVED RESULT
The sound would notify and the speakers would notify of login.  However the
screen would not complete the login to the workspace.  The icons loading in the
lower left hand screen were stuck on the KDE icons.

EXPECTED RESULT
Login

SOFTWARE/OS VERSIONS

CentOS Linux release 7.7.1908 (Core)
kernel-3.10.0-1062.4.1.el7.x86_64  

Linux/KDE Plasma: 

(available in About System)
KDE Plasma Version: 4.10.5-5.el7
KDE Frameworks Version: 4.14.8-11.el7_7
Qt Version: 

ADDITIONAL INFORMATION

Good log:
6 monitor /var/log/messages -->

Jun 25 10:36:49 MYMACHINE org.kde.powerdevil.backlighthelper: no kernel
backlight interface found
Jun 25 10:36:49 MYMACHINE dbus[1767]: [system] Successfully activated service
'org.kde.powerdevil.backlighthelper'
Jun 25 10:36:54 MYMACHINE NetworkManager[1801]:   [1593099414.9926]
agent-manager: req[0x564331135ad0, :1.36/org.kde.networkmanagement/0]: agent
registered
Jun 25 10:36:59 MYMACHINE spice-vdagent[3617]: Cannot access vdagent virtio
channel /dev/virtio-ports/com.redhat.spice.0
Jun 25 10:36:59 MYMACHINE systemd: Started PC/SC Smart Card Daemon.

Bad log:
2 monitor /var/log/messages -->

Jun 25 10:48:07 MYMACHINE org.kde.powerdevil.backlighthelper: no kernel
backlight interface found
Jun 25 10:48:07 MYMACHINE dbus[1749]: [system] Successfully activated service
'org.kde.powerdevil.backlighthelper'
Jun 25 10:48:11 MYMACHINE abrt-hook-ccpp: Process 4588 (kdeinit4) of user 0
killed by SIGSEGV - dumping core
Jun 25 10:48:12 MYMACHINE kernel: plasma-desktop[4597]: segfault at 0 ip
7f76f2c1785c sp 7ffd6f2cd220 error 4 in
plasma_applet_tasks.so[7f76f2c07000+1e000]
Jun 25 10:48:12 MYMACHINE abrt-hook-ccpp: Process 4597 (kdeinit4) of user 0
killed by SIGSEGV - ignoring (repeated crash)
Jun 25 10:48:13 MYMACHINE abrt-server: Generating core_backtrace
Jun 25 10:48:16 MYMACHINE abrt-server: Duplicate: core backtrace
Jun 25 10:48:16 MYMACHINE abrt-server: DUP_OF_DIR:
/var/spool/abrt/ccpp-2020-06-24-10:57:10-3462
Jun 25 10:48:16 MYMACHINE abrt-server: Deleting problem directory
ccpp-2020-06-25-10:48:11-4588 (dup of ccpp-2020-06-24-10:57:10-3462)
Jun 25 10:48:16 MYMACHINE dbus[1749]: [system] Activating service
name='org.freedesktop.problems' (using servicehelper)
Jun 25 10:48:16 MYMACHINE dbus[1749]: [system] Successfully activated service
'org.freedesktop.problems'
Jun 25 10:48:22 MYMACHINE spice-vdagent[4688]: Cannot access vdagent virtio
channel /dev/virtio-ports/com.redhat.spice.0
Jun 25 10:48:22 MYMACHINE systemd: Started PC/SC Smart Card Daemon.

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

[okular] [Bug 422856] Fails to open PDFs when name contains hash ('#')

2020-06-26 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=422856

--- Comment #2 from Christoph Cullmann  ---
Hmm, no direct idea why this fails :/

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

[amarok] [Bug 423536] audio played is very choppy. have tried importing different versions (mp3, wav) but all don't work. have also tried importing different audio. still doesn't work

2020-06-26 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=423536

Myriam Schweingruber  changed:

   What|Removed |Added

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

--- Comment #1 from Myriam Schweingruber  ---
which exact version is this about?
Which Phonon backend is used?
FWIW: playback is done by Phonon, not by Amarok, you need to be more detailed
about the versions of those libraries

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

[amarok] [Bug 423534] Resume Playback on start not working

2020-06-26 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=423534

Myriam Schweingruber  changed:

   What|Removed |Added

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

--- Comment #1 from Myriam Schweingruber  ---
Which Amarok version is this about? If it is a git build, please specify the
date of the build

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

[trojita] [Bug 404697] CVE-2019-10734: Decryption Oracle based on replying to PGP or S/MIME encrypted emails

2020-06-26 Thread Jan Kundrát
https://bugs.kde.org/show_bug.cgi?id=404697

Jan Kundrát  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/pim/
   ||trojita/commit/8db7f450d525
   ||39b4c72ee968384911b6813ad1e
   ||7
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #11 from Jan Kundrát  ---
Git commit 8db7f450d52539b4c72ee968384911b6813ad1e7 by Jan Kundrát.
Committed on 26/06/2020 at 10:29.
Pushed by jkt into branch 'master'.

Prevent a possible decryption oracle attack

Thanks to Jens Mueller (Ruhr-Uni Bochum and FH Münster) for reporting
this. The gist is that an attacker can embed arbitrary ciphertext into
their messages. Trojita decrypts that, and when we hit reply, the
original *cleartext* gets quoted and put into a reply for the attacker
to see.

Fix this by not quoting any plaintext which originated in an encrypted
message. That's pretty draconian, but hey, it works and we never came up
with any better patch. Also, given that Trojita does not encrypt
outgoing messages yet, this is probably also a conservative thing to do.

Change-Id: I84c45b9e707eb7c99eb7183c6ef59ef41cd62c43
CVE: CVE-2019-10734

M  +2-0src/Cryptography/GpgMe++.cpp
M  +8-1src/Gui/MessageView.cpp
M  +8-0src/Gui/PartWidget.cpp
M  +1-1src/Imap/Model/ItemRoles.h

https://invent.kde.org/pim/trojita/commit/8db7f450d52539b4c72ee968384911b6813ad1e7

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

[kwin] [Bug 421564] New Window Rules kcm takes some seconds to show the configured window rules

2020-06-26 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=421564

Ismael Asensio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Ismael Asensio  ---
Hi Patrick,

Could you confirm if this is still an issue after Plasma 5.19.1?

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

[frameworks-kio] [Bug 178678] Navigating mounted network locations is extremely slow in Dolphin compared to command line

2020-06-26 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=178678

--- Comment #78 from Germano Massullo  ---
Created attachment 129705
  --> https://bugs.kde.org/attachment.cgi?id=129705=edit
gwenview multiple files "move to"

(In reply to Harald Sitter from comment #77)
> Are you 100% confident that previews aren't enabled?

Yes and moreover I found out that this happens also on Gwenview when:
1. I select **more than one picture** pictures, then rightclick "Move to"
2. on the new move to window, there is a path textbox. As soon I start to write
the path that is in the remote SSHFS mount, Gwenvew completely freezes and I
can see the same network activity between the server and the client.

> Do you know how to use gdb so we can verify that?

I know how to use it, but I would like to receive detailed step by step
procedure so I can better provide all informations you may need

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

[kwin] [Bug 421405] kwin_rules_dialog shows an empty dialog on wayland

2020-06-26 Thread Scott Loga
https://bugs.kde.org/show_bug.cgi?id=421405

--- Comment #7 from Scott Loga  ---
Ismael,

As suggested, I created a new bug report #423554.

Regards,

Scott

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

[kwin] [Bug 423554] New: x11-wm/plasma5-kwin kwin_rules_dialog closed unexpectedly

2020-06-26 Thread Scott Loga
https://bugs.kde.org/show_bug.cgi?id=423554

Bug ID: 423554
   Summary: x11-wm/plasma5-kwin kwin_rules_dialog closed
unexpectedly
   Product: kwin
   Version: 5.19.1
  Platform: FreeBSD Ports
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: scott.l...@me.com
  Target Milestone: ---

Created attachment 129704
  --> https://bugs.kde.org/attachment.cgi?id=129704=edit
KDE Crash Handler Output

SUMMARY

x11-wm/plasma5-kwin kwin_rules_dialog closed unexpectedly

STEPS TO REPRODUCE
1. Right click on any Window Title Bar
2. Choose "More Actions"
3. Select either "Configure Special Window Settings" or "Configure Special
Application Settings"

OBSERVED RESULT

KDE Crash Handler displays "kwin_rules_closes unexpectedly"


EXPECTED RESULT



SOFTWARE/OS VERSIONS

FreeBSD/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

Details:

Executable: kwin_rules_dialog PID: 32543 Signal: Segmentation fault (11) Time:
6/23/20 12:04:20 PM CDT

Attached is the crash information provided by the KDE Crash Handler.

I also created a new user on the system and the same results occurred.

If more information is needed, please don't hesitate to ask.

Regards,

Scott

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

[kwin] [Bug 421405] kwin_rules_dialog shows an empty dialog on wayland

2020-06-26 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=421405

--- Comment #6 from Ismael Asensio  ---
(In reply to Scott Loga from comment #5)
> Confirmed Behavior in FreeBSD/KDE5:
> 
> OS - 12.1-RELEASE-p6 GENERIC amd64
> KDE Plasma 5.19.1, KDE Frameworks 5.71.0, Qt 5.14.2
> 
> On any Window Title Bar, if one right clicks and chooses More Actions then
> Configure Special Window Settings, the KDE Crash Handler displays
> "kwin_rules_closes unexpectedly"
> 
> Details:
> 
> Executable: kwin_rules_dialog PID: 32543 Signal: Segmentation fault (11)
> Time: 6/23/20 12:04:20 PM CDT
> 
> Attached is the crash information provided by the KDE Crash Handler.
> 
> I also created a new user on the system and the same results occurred.
> 
> If more information is needed, please don't hesitate to ask.
> 
> Regards,
> 
> Scott

Hi Scott, by the crash info, this seems a different issue as the ones avobe.
Those affect Wayland, while these seems specific to *BSD systems.

Would you mind to open a new bug report with the information you posted here?
That will help us to try and replicate it, and better track the issue.

Thanks in advance!

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

[plasmashell] [Bug 422848] Global Menu w/Dual Monitors displays menu items on incorrect screen 5.19.0

2020-06-26 Thread noons
https://bugs.kde.org/show_bug.cgi?id=422848

noons  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #2 from noons  ---
Saving a new xorg.conf seemed to resolve the issue. Not sure why it suddenly
popped up with 5.19. Going to mark this as closed.

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

[plasmashell] [Bug 422948] startup sound cut off

2020-06-26 Thread Colin J Thomson
https://bugs.kde.org/show_bug.cgi?id=422948

Colin J Thomson  changed:

   What|Removed |Added

 CC||colin.thom...@g6avk.co.uk

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

[okular] [Bug 423553] New: No smooth scrolling in small scales after Windows 10 2004 update

2020-06-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=423553

Bug ID: 423553
   Summary: No smooth scrolling in small scales after Windows 10
2004 update
   Product: okular
   Version: 1.10.1
  Platform: Windows CE
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: savilov...@gmail.com
  Target Milestone: ---

SUMMARY

Scrolling after zoom is not smooth after Windows 10 2004 update.

STEPS TO REPRODUCE
1. Set up Windows 10 2004 update
2. Open PDF file
3. Zoom in text
4. Try to scroll

OBSERVED RESULT

Scrolling is smooth before zoom, but after zoom, it isn't.

EXPECTED RESULT

Always smooth scrolling.

SOFTWARE/OS VERSIONS

Windows 10 ver. 2004

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

[krita] [Bug 423473] Krita silently crashes when lowering newly created layer after move action in a new document from clipboard

2020-06-26 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=423473

Ahab Greybeard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||ahab.greybe...@hotmail.co.u
   ||k
 Ever confirmed|0   |1

--- Comment #1 from Ahab Greybeard  ---
I can confirm this for the 24 Jun 5.0.0 prealpha (git 9b02ae2) appimage.

It does not happen with the 24 Jun 4.3.1 alpha (git 23a6ab6) appimage.

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

[plasmashell] [Bug 423552] Mouse cursor shadow sometimes pulses above certain windows

2020-06-26 Thread Matej Mrenica
https://bugs.kde.org/show_bug.cgi?id=423552

Matej Mrenica  changed:

   What|Removed |Added

 CC||matejm98m...@gmail.com

--- Comment #1 from Matej Mrenica  ---
Created attachment 129703
  --> https://bugs.kde.org/attachment.cgi?id=129703=edit
Video

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

[plasmashell] [Bug 423552] New: Mouse cursor shadow sometimes pulses above certain windows

2020-06-26 Thread Matej Mrenica
https://bugs.kde.org/show_bug.cgi?id=423552

Bug ID: 423552
   Summary: Mouse cursor shadow sometimes pulses above certain
windows
   Product: plasmashell
   Version: 5.19.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: matejm98m...@gmail.com
  Target Milestone: 1.0

See the video.

SOFTWARE/OS VERSIONS 
KDE Frameworks Version: 5.71
Qt Version: 5.15.0

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

[kwin] [Bug 423551] New: Regression in some XWayland popups

2020-06-26 Thread Carson Black
https://bugs.kde.org/show_bug.cgi?id=423551

Bug ID: 423551
   Summary: Regression in some XWayland popups
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: uhh...@gmail.com
  Target Milestone: ---

SUMMARY
Some XWayland popups seem to have become transparent to mouse input; you're
unable to interact with them using the mouse.


STEPS TO REPRODUCE
[ Method One ]
1. Open Chrome/ium
2. Click lock icon in omnibox (by the refresh button and before the URL)
3. Try and interact with elements on the popup

[ Method Two ]
1. Open VSCode/ium
2. Bring up a menu
3. Try and interact with it

OBSERVED RESULT
Popups pass mouse input through to their parents

EXPECTED RESULT
Popups are correctly interacted with

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

[krita] [Bug 423470] Crash when try to use Fill Tool

2020-06-26 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=423470

Ahab Greybeard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||ahab.greybe...@hotmail.co.u
   ||k
 Ever confirmed|0   |1

--- Comment #1 from Ahab Greybeard  ---
I can confirm this for the 24 Jun 5.0.0 prealpha (git 9b02ae2) and 4.3.1 alpha
(git 23a6ab6) appimages.

It also doesn't crash if 'Fill entire selection' is enabled.

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

[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs

2020-06-26 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=423397

--- Comment #10 from Andrius Štikonas  ---
(In reply to Laosom from comment #9)
> I checked and find it was not running.

ok. And can you run fsck manually afterwards? To see if it's still failing? As
I've said before, maybe partition manager does not wait long enough for block
device to get ready.

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

[krusader] [Bug 418077] Kio_iso crash

2020-06-26 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418077

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/utilities/krusader/-/merge_requests/17

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

[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs

2020-06-26 Thread Laosom
https://bugs.kde.org/show_bug.cgi?id=423397

--- Comment #8 from Laosom  ---
Created attachment 129702
  --> https://bugs.kde.org/attachment.cgi?id=129702=edit
PM error automounter

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

[krita] [Bug 423150] Layer Style Stroke - Layer Duplication Loses Color

2020-06-26 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=423150

Dmitry Kazakov  changed:

   What|Removed |Added

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

--- Comment #11 from Dmitry Kazakov  ---
The bug is fixed now (and two more different bugs).

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

[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs

2020-06-26 Thread Laosom
https://bugs.kde.org/show_bug.cgi?id=423397

--- Comment #9 from Laosom  ---
I checked and find it was not running.

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

[krita] [Bug 423150] Layer Style Stroke - Layer Duplication Loses Color

2020-06-26 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=423150

--- Comment #7 from Dmitry Kazakov  ---
Git commit c77027bbae9e8c4d26a8eb364d5df7ff99d65cd9 by Dmitry Kazakov.
Committed on 26/06/2020 at 15:36.
Pushed by dkazakov into branch 'master'.

Fix cloning of a stroke layers style with "center" position

It was obviously a copy-paste mistake :)

M  +9-1libs/image/layerstyles/kis_layer_style_projection_plane.cpp

https://invent.kde.org/graphics/krita/commit/c77027bbae9e8c4d26a8eb364d5df7ff99d65cd9

--- Comment #8 from Dmitry Kazakov  ---
Git commit ea9daff5a71a1fb817c87778d88129c2a462ea07 by Dmitry Kazakov.
Committed on 26/06/2020 at 15:36.
Pushed by dkazakov into branch 'master'.

Fix cloning of stroke layer style

KisLayerStyleKnockoutBlower should clone the internal selection
as well.

M  +10   -0libs/image/layerstyles/KisLayerStyleKnockoutBlower.cpp
M  +3-0libs/image/layerstyles/KisLayerStyleKnockoutBlower.h
M  +1-0   
libs/image/layerstyles/kis_layer_style_filter_projection_plane.cpp

https://invent.kde.org/graphics/krita/commit/ea9daff5a71a1fb817c87778d88129c2a462ea07

--- Comment #9 from Dmitry Kazakov  ---
Git commit a37cbcec401cab859c240037e3f377e12dbbd757 by Dmitry Kazakov.
Committed on 26/06/2020 at 15:40.
Pushed by dkazakov into branch 'master'.

Fix a thread-safety problem in Stroke layer style

It should not write into a knockout-selection outside its
applyRect, becasue there are no thread-safety guarantees outside it.

# Conflicts:
#   libs/image/layerstyles/kis_ls_stroke_filter.cpp

M  +15   -14   libs/image/layerstyles/kis_ls_stroke_filter.cpp

https://invent.kde.org/graphics/krita/commit/a37cbcec401cab859c240037e3f377e12dbbd757

--- Comment #10 from Dmitry Kazakov  ---
Git commit 689fe924c56712ee1986269fdbace1c7450f7549 by Dmitry Kazakov.
Committed on 26/06/2020 at 15:41.
Pushed by dkazakov into branch 'master'.

Add a unittest for cloning layer styles

M  +46   -10   libs/image/tests/kis_layer_style_projection_plane_test.cpp

https://invent.kde.org/graphics/krita/commit/689fe924c56712ee1986269fdbace1c7450f7549

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

  1   2   3   >