[kwin] [Bug 416093] client screen property now readonly?

[LinG]

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

--- Comment #12 from LinG  ---
(In reply to Vlad Zahorodnii from comment #11)
> (In reply to LinG from comment #10)
> > Alright, where can I find the most recent documentation about the methods
> > and properties that I should use?
> Unfortunately, only source code. API dox is not generated for KWin since KDE
> Plasma 5.

Alright, could you point out to me where I can find the code that is related to
the KWin::client and KWin::toplevel (assuming client still inherits from
toplevel as in 4.9). The scripting/workspace_wrapper.h is very readable so I'm
fine with working with that but I didn't find a client_wrapper.h or something
in this directory

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

[lattedock] [Bug 416919] Lateral panels and docks constantly change size (see attached)

[Iván R .]

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

Iván R.  changed:

   What|Removed |Added

 CC||ivan.rinco...@gmail.com

--- Comment #1 from Iván R.  ---
Created attachment 125524
  --> https://bugs.kde.org/attachment.cgi?id=125524=edit
video shows how errors occur in side views

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

[Discover] [Bug 416866] applications undiscoverable

[THUON Mohasal]

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

--- Comment #2 from THUON Mohasal  ---
my software aplication explorer named "Discover" in Krama OS, KOOMPI laptop
is unable to install and search for any applications in store since the
upgrade to version 5.17.5.
hope to see any update to find the applicationsjust like as old version
bata!

On Wed, Jan 29, 2020 at 2:34 AM Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=416866
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|REPORTED|NEEDSINFO
>  CC||n...@kde.org
>
> --- Comment #1 from Nate Graham  ---
> Can you clarify what the problem is? I'm having trouble understanding.
>
> If you need help filing bug reports, please see
>
> https://community.kde.org/Get_Involved/Issue_Reporting#Step_6:_File_a_high-quality_Bugzilla_ticket
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[lattedock] [Bug 416919] New: Lateral panels and docks constantly change size (see attached)

[Iván R .]

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

Bug ID: 416919
   Summary: Lateral panels and docks constantly change size (see
attached)
   Product: lattedock
   Version: 0.9.8
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: ivan.rinco...@gmail.com
  Target Milestone: ---

SUMMARY

For a couple of days, possibly since the upgrade to version 0.9.8, panels
located on the right and on the left show very strange behavior (see attached
video) Instead, the upper and lower panels are displayed correctly.

STEPS TO REPRODUCE
Always happens

OBSERVED RESULT
Panels located on the right and on the left constantly change size

EXPECTED RESULT
Proper functioning

SOFTWARE/OS VERSIONS
* Linux 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64
GNU/Linux
* KDE neon User Edition 5.17
* KDE Plasma Version: 5.17.5
* Qt Version: 5.13.2

ADDITIONAL INFORMATION
X.Org 1.19.6
GPU: NVidia Geforce GTX 1050 Ti
Driver Nvidia: 435.21
Laptop Dell G3 17

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

[krita] [Bug 416918] "Default colour model for new images" is ignored

[Ahab Greybeard]

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

Ahab Greybeard  changed:

   What|Removed |Added

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

--- Comment #1 from Ahab Greybeard  ---
I can confirm this for the Jan 28th 4.3.0 prealpha appimage git(049dd11)

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

[krita] [Bug 416894] krita full screen in wrong monitor

[Rebecca Breu]

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

Rebecca Breu  changed:

   What|Removed |Added

 CC||rebe...@rbreu.de

--- Comment #1 from Rebecca Breu  ---
I can't reproduce it on Debian, neither with the 4.2.8 appimage nor the recent
nightly appimage. Might be a Windows-specific issue?

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

[krita] [Bug 416892] Contiguous Selection Tool behavior

[Ahab Greybeard]

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

Ahab Greybeard  changed:

   What|Removed |Added

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

--- Comment #2 from Ahab Greybeard  ---
I can confirm this for the Jan 28th 4.3.0 prealpha appimage git(049dd11)

The contiguous selection tool and the similar colour selection tool both do a
binary (alpha equals 0  or alpha not equal to 0) selection with a gradient on a
transparent background.

For the contiguous selection tool, a workaround for this is to put a
contrasting solid colour layer under the gradient-on-transparent layer and then
use the tool with limit to current layer turned off.

That workaround does not work for the similar colour selector tool. You have to
merge a copy of the gradient with a contrasting filled layer and use it on that
to get a selection that is correct and controllable.

There have been other previous concerns about how pixels with alpha less than 1
are treated so this may be one of those situations.

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

[krita] [Bug 416918] New: "Default colour model for new images" is ignored

[Mark Raynsford]

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

Bug ID: 416918
   Summary: "Default colour model for new images" is ignored
   Product: krita
   Version: 4.2.8
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: co+org@io7m.com
  Target Milestone: ---

SUMMARY

In Colour Management -> General, there's a setting to select the default colour
model for new images. The standard Krita default appears to be "RGB/Alpha
(8-bit integer/channel)". If you set this to, for example, "RGB/Alpha (16-bit
float/channel)", this should be the new default for all new images. However,
the setting appears to be ignored.

STEPS TO REPRODUCE
1. Set the default colour model to anything other than "RGB/Alpha (8-bit
integer/channel)"
2. Save settings
3. Create a new image
4. Observe that the colour model is still set to "RGB/Alpha (8-bit
integer/channel)"

OBSERVED RESULT

Here's a video that shows me selecting a 16-bit floating point colour model,
and a linear display profile. Note that the display profile *is* respected, but
the colour model isn't:

  https://ataxia.io7m.com/2020/01/29/krita_depth.mkv

EXPECTED RESULT

New images should have the correct colour model.

SOFTWARE/OS VERSIONS

Krita

 Version: 4.2.8
 Languages: en_GB
 Hidpi: true

Qt

  Version (compiled): 5.13.2
  Version (loaded): 5.14.0

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.4.15-arch1-1
  Pretty Productname: Arch Linux
  Product Type: arch
  Product Version: unknown

OpenGL Info

  Vendor:  "X.Org" 
  Renderer:  "AMD NAVI10 (DRM 3.35.0, 5.4.15-arch1-1, LLVM 9.0.1)" 
  Version:  "4.5 (Compatibility Profile) Mesa 19.3.2" 
  Shading language:  "4.50" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:QSurfaceFormat(version 4.5, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 4.5
 Supports deprecated functions true 
 is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsOpenGLES: true 
  isQtPreferOpenGLES: false 

Hardware Information

  GPU Acceleration: auto
  Memory: 32098 Mb
  Number of Cores: 12
  Swap Location: /tmp

Current Settings

Current Swap Location: /tmp
Undo Enabled: 1
Undo Stack Limit: 30
Use OpenGL: 1
Use OpenGL Texture Buffer: 1
Use AMD Vectorization Workaround: 0
Canvas State: OPENGL_SUCCESS
Autosave Interval: 900
Use Backup Files: 1
Number of Backups Kept: 1
Backup File Suffix: ~
Backup Location: Same Folder as the File
Use Win8 Pointer Input: 0
Use RightMiddleTabletButton Workaround: 0
Levels of Detail Enabled: 0
Use Zip64: 0


ADDITIONAL INFORMATION

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

[frameworks-kio] [Bug 416895] kdeinit5 crashes in KIO::SlaveBase::waitForAnswer() after return from suspend

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
One of the best ways to ask these kinds of questions is to submit a patch with
"[RFC]" prepended to the title; the maintainers and other interested parties
willbe able to answer your questions.

Alternatively you could ask in the #kde-devel freenode IRC/Matrix room before
submitting.

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

[systemsettings] [Bug 416805] Touchpad: Two finger tap: Add option to disable two finger tap

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |UPSTREAM
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Nate Graham  ---
Thanks. Unfortunately that isn't something that I believe Libinput currently
supports. You'd need to request support from them before we can add a setting
to toggle the behavior.

You can do so here: https://gitlab.freedesktop.org/libinput/libinput/issues

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

[systemsettings] [Bug 416801] Impossible to start Plasma session with a user account created by User Manager. SDDM says "Authentication failed".

[Patrick Silva]

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

--- Comment #5 from Patrick Silva  ---
I have just tested both methods on Arch Linux, confirming password firstly with
keyboard and after with mouse. Login fails on both cases.

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

[systemsettings] [Bug 416805] Touchpad: Two finger tap: Add option to disable two finger tap

[bugzilla_noreply]

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

--- Comment #2 from udevn...@t-online.de ---
Yes, I would like to be able to single-finger tap, but disable two-finger-tap.
Two-finger-scrolling is often being interpreted as two-finger-tap.

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

[systemsettings] [Bug 416801] Impossible to start Plasma session with a user account created by User Manager. SDDM says "Authentication failed".

[Méven Car]

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

Méven Car  changed:

   What|Removed |Added

 CC||meve...@gmail.com

--- Comment #4 from Méven Car  ---
Hey Patrick, did you use the keyboard to confirm the user password or the mouse
to click on ok ?

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

[frameworks-kirigami] [Bug 416860] FormLayout content moved too far to the right in certain circumstances

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kir
   ||igami/c53382e9e600444616ce7
   ||d9ac996b0bc57e5e0a8

--- Comment #8 from Marco Martin  ---
Git commit c53382e9e600444616ce7d9ac996b0bc57e5e0a8 by Marco Martin.
Committed on 29/01/2020 at 16:57.
Pushed by mart into branch 'master'.

proper size hint for the gridlayout

M  +1-1src/controls/FormLayout.qml

https://commits.kde.org/kirigami/c53382e9e600444616ce7d9ac996b0bc57e5e0a8

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

[kwin] [Bug 416906] KWin crash, maybe related to context menu or to desktop change

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #5 from Nate Graham  ---
There should no such thing as kdelibs5 anymore; what you want is the debug
package for libkwineffects.

if `apt search libkwineffects` doesn't reveal anything then it sounds like
either you don't have a debug repo installed, or you do and it isn't enabled,
or it is but it doesn't have a debug package for libkwineffects.

Either way, please ask the Ubuntu folks for help with this. They'll know best.

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

[krita] [Bug 416864] (Semi) Reliable, fast way to krita crash and file corruption using undo while colorize masked editing tool

[Ahab Greybeard]

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

Ahab Greybeard  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||ahab.greybe...@hotmail.co.u
   ||k
 Resolution|--- |WAITINGFORINFO

--- Comment #7 from Ahab Greybeard  ---
I can't reproduce this with the Jan 28th 4.3.0 prealpha appimage git(049dd11)
and both the provided test .kra files open ok and behave well.

I can't reproduce this with the 4.2.8 appimage but both the provided test .kra
files cause a vanishment crash when opened.

I can't reproduce this with the Jan 20th 4.3.0 prealpha Windows standalone .zip
package git (07888a2) and both the provided test .kra files open ok and behave
well.

I can't reproduce this with the 4.2.8 Windows standalone .zip package  but both
the provided test .kra files cause a vanishment crash when opened.

My inability to reproduce the crash may be due to not replicating the process
exactly as you did,

Can you test this with the latest Nightly Build from
https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/lastSuccessfulBuild/artifact/krita-nightly-x64-v4.3.0-prealpha-1071-g065745731c.zip
and see if still happens?

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

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

[Craig]

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

Craig  changed:

   What|Removed |Added

Version|5.7.2   |5.13.1
 CC||craig.finne...@gmail.com

--- Comment #14 from Craig  ---
Any updates or workarounds on this anyone's figured? Major bummer as I love
kontact/KDE but moved to Thunderbird some while back due to this and other
issues, came back to it stoked to see the EWS support etc all working great and
how I've missed it! Then sent a reply and everything is always double spaced :(
In my case I sent a reply to an email sent to myself using Thunderbird, so not
an Outlook only issue - makes unusable especially in
business/contracting/professional capacity and biggest bummer ever!

Anyone have any ideas or hopefully devs can provide some input? I know there
was a bugfix on the qt side bit ago but per comments in here the issue is now
the default html/stylesheet being used by kmail

Arch Linux running latest kdepim 5.13.1 and qt etc

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

[plasmashell] [Bug 412588] feature to duplicate a panel or save a panels config

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com
   Severity|normal  |wishlist

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

[kdenlive] [Bug 416917] New: Fast forward and backward activating wrong monitor

[Massimo Stella]

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

Bug ID: 416917
   Summary: Fast forward and backward activating wrong monitor
   Product: kdenlive
   Version: Appimage - Refactoring
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: maxs...@tin.it
  Target Milestone: ---

SUMMARY
Fast forward and backward activating the wrong monitor

STEPS TO REPRODUCE
1. Open a project and load one clip in the Clip Monitor and put one clip in the
timeline
2. Click the play button by mouse on one of the 2 Monitor (Clip Monitor or the
Program - the 2 have to be visible on the GUI at the same time)
3. Click on the fast forward or backward on the window which is not playing
back

OBSERVED RESULT
The video in the window you are playing back changes playback speed following
the direction you clicked
EXPECTED RESULT
The video in the window you are playing back stops and the fast playback in the
chosen direction start in the window you clicked on.
A similar behaviour for loop zone was corrected here:
https://cgit.kde.org/kdenlive.git/commit/?id=6a068663a4f210a5872d780f92273e2902907353
SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[Active Window Control] [Bug 416916] New: I was just poking around with the active window control in the application menu bar and trying some stuff the bar and the desktop vanished.

[NikiNokix]

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

Bug ID: 416916
   Summary: I was just poking around with the active window
control in the application menu bar and trying some
stuff the bar and the desktop vanished.
   Product: Active Window Control
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: zrenf...@gmail.com
  Reporter: guto.ebone3...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
I was just poking around with the active window control in the application menu
bar and trying some stuff the bar and the desktop vanished. 

STEPS TO REPRODUCE
1. Open 'configure Active window control'
2. In section 'Appearence'
3. In 'Fit text:' set 'fit on hover'
4. And in 'Tooltip text:' 'Application name'
5. Apply

OBSERVED RESULT
The desktop wallpaper went black, right click on the desktop wont work, the
latte bar went invisible.

EXPECTED RESULT


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

ADDITIONAL INFORMATION
I uploaded a video on youtube showing the bug: https://youtu.be/ZrWzjefl3Ss

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

[frameworks-solid] [Bug 415474] Crash while closing the "Energy Information" window

[bugzilla_noreply]

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

--- Comment #6 from calvin.f@gmail.com ---
I can confirm this bug on OpenSUSE Tumbleweed.
Opening Energy Information via any other method (e.g. application launcher)
produces the same result.

Distro: openSUSE Tumbleweed x86_64
Kernel version: 5.3.5-1-default
Plasma version: 5.17.5
Frameworks version: 5.66.0
Qt version: 5.14


-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7eff96a88080 (LWP 3611))]

Thread 7 (Thread 0x7eff859d8700 (LWP 3618)):
#0  0x7eff986f26a5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7eff8784588b in ?? () from /usr/lib64/dri/i965_dri.so
#2  0x7eff87845707 in ?? () from /usr/lib64/dri/i965_dri.so
#3  0x7eff986ebf2a in start_thread () from /lib64/libpthread.so.0
#4  0x7eff9adf138f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7eff861d9700 (LWP 3617)):
#0  0x7eff986f26a5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7eff8784588b in ?? () from /usr/lib64/dri/i965_dri.so
#2  0x7eff87845707 in ?? () from /usr/lib64/dri/i965_dri.so
#3  0x7eff986ebf2a in start_thread () from /lib64/libpthread.so.0
#4  0x7eff9adf138f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7eff869da700 (LWP 3616)):
#0  0x7eff986f26a5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7eff8784588b in ?? () from /usr/lib64/dri/i965_dri.so
#2  0x7eff87845707 in ?? () from /usr/lib64/dri/i965_dri.so
#3  0x7eff986ebf2a in start_thread () from /lib64/libpthread.so.0
#4  0x7eff9adf138f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7eff871db700 (LWP 3615)):
#0  0x7eff986f26a5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7eff8784588b in ?? () from /usr/lib64/dri/i965_dri.so
#2  0x7eff87845707 in ?? () from /usr/lib64/dri/i965_dri.so
#3  0x7eff986ebf2a in start_thread () from /lib64/libpthread.so.0
#4  0x7eff9adf138f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7eff8fb11700 (LWP 3613)):
#0  0x7eff9ade6abf in poll () from /lib64/libc.so.6
#1  0x7eff97a262ee in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7eff97a2640f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7eff99851bdb in QEventDispatcherGlib::processEvents
(this=0x7eff88000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7eff997f9d5b in QEventLoop::exec (this=this@entry=0x7eff8fb10d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#5  0x7eff9962563e in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#6  0x7eff9a8e6507 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7eff99626708 in QThreadPrivate::start (arg=0x7eff9a968da0) at
thread/qthread_unix.cpp:342
#8  0x7eff986ebf2a in start_thread () from /lib64/libpthread.so.0
#9  0x7eff9adf138f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7eff949e7700 (LWP 3612)):
#0  0x7eff9ade6abf in poll () from /lib64/libc.so.6
#1  0x7eff983e0752 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7eff983e140a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7eff94be39a0 in QXcbEventQueue::run (this=0x55a941493d90) at
qxcbeventqueue.cpp:228
#4  0x7eff99626708 in QThreadPrivate::start (arg=0x55a941493d90) at
thread/qthread_unix.cpp:342
#5  0x7eff986ebf2a in start_thread () from /lib64/libpthread.so.0
#6  0x7eff9adf138f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7eff96a88080 (LWP 3611)):
[KCrash Handler]
#6  QPointer::data (this=0x28) at
/usr/include/qt5/QtCore/qpointer.h:85
#7  Solid::DeviceInterfacePrivate::backendObject (this=0x20) at
/usr/src/debug/solid-5.66.0-1.1.x86_64/src/solid/devices/frontend/deviceinterface.cpp:110
#8  0x7eff8fd20655 in Solid::DevicePrivate::~DevicePrivate (this=, this=) at
/usr/src/debug/solid-5.66.0-1.1.x86_64/src/solid/devices/frontend/device.cpp:222
#9  0x7eff8fd20759 in Solid::DevicePrivate::~DevicePrivate (this=, this=) at
/usr/src/debug/solid-5.66.0-1.1.x86_64/src/solid/devices/frontend/device.cpp:225
#10 0x7eff8fd216e4 in Solid::DeviceManagerPrivate::~DeviceManagerPrivate
(this=, this=) at
/usr/include/c++/9/bits/atomic_base.h:413
#11 0x7eff8fd21829 in Solid::DeviceManagerPrivate::~DeviceManagerPrivate
(this=, this=) at
/usr/src/debug/solid-5.66.0-1.1.x86_64/src/solid/devices/frontend/devicemanager.cpp:63
#12 0x7eff9962b960 in QThreadStorageData::finish (p=0x55a941468200) at
thread/qthreadstorage.cpp:200
#13 0x7eff997fd559 in QCoreApplicationPrivate::cleanupThreadData
(this=this@entry=0x55a941471340) at kernel/qcoreapplication.cpp:523
#14 0x7eff99c05564 in QGuiApplicationPrivate::~QGuiApplicationPrivate
(this=0x55a941471340, __in_chrg=) at
kernel/qguiapplication.cpp:1681

[frameworks-solid] [Bug 415474] Crash while closing the "Energy Information" window

[bugzilla_noreply]

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

calvin.f@gmail.com changed:

   What|Removed |Added

 CC||calvin.f@gmail.com

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

[kate] [Bug 416812] keyboard input useless

[steven myers]

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

--- Comment #6 from steven myers  ---
 can I download and install this independent of their distribution?

On Tuesday, January 28, 2020, Christoph Feck 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=416812
>
> Christoph Feck  changed:
>
>What|Removed |Added
> 
> 
>  Resolution|--- |UNMAINTAINED
>  Status|REPORTED|RESOLVED
>
> --- Comment #5 from Christoph Feck  ---
> The KDE software that is shipped with Ubuntu 16.04 is no longer maintained
> by
> KDE developers. Either request support at the bug tracker of your
> distribution,
> or update to a distribution which has recent software versions.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[frameworks-kio] [Bug 416895] kdeinit5 crashes in KIO::SlaveBase::waitForAnswer() after return from suspend

[Frank Fischer]

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

--- Comment #2 from Frank Fischer  ---
(In reply to Nate Graham from comment #1)
> Would you be interested in submitting a patch to fix the issue, or at least
> downgrade it to a warning?

Sure, I could do this. However, I'm totally unfamiliar with the kio code and do
not know whether just returning an error code is ok with the rest of the code.
In particular, I do not know whether this would result in some kind of
inconsistent or invalid internal state of the slave (are there some assumptions
about the internal state? Is all code expected to reset internal date to some
valid state in case of an error, e.g. by cancelling the active connection?).
So, in any case I would need some assistance to verify whether my changes make
sense.

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

[plasmashell] [Bug 416915] broken keep of destination coordinates in drag-and-drop operations

[painless roaster]

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

--- Comment #1 from painless roaster  ---
Created attachment 125521
  --> https://bugs.kde.org/attachment.cgi?id=125521=edit
drag fix

fix is very simple

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

[plasmashell] [Bug 416914] Connecting external monitor freezes Plasma

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org,
   ||plasma-b...@kde.org
   Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk
Summary|Connecting of external  |Connecting external monitor
   |monitor gets stuck Plasma   |freezes Plasma
  Component|generic-crash   |general

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

[frameworks-kio] [Bug 416895] kdeinit5 crashes in KIO::SlaveBase::waitForAnswer() after return from suspend

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|kdeinit5 crashes after  |kdeinit5 crashes in
   |return from suspend |KIO::SlaveBase::waitForAnsw
   ||er() after return from
   ||suspend
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Would you be interested in submitting a patch to fix the issue, or at least
downgrade it to a warning?

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

[plasmashell] [Bug 416903] no wallpaper or toolbar after upgrade to 5.17.90

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---
Sounds like Plasma didn't launch. There appears to be a packaging or
configuration problem causing necessary libraries to not be installed or found:

> kdeinit5: preparing to launch 'libkdeinit5_kded5'
> Could not open kded5 using a library: Cannot load library libkdeinit5_kded5:
> (libkdeinit5_kded5: cannot open shared object file: No such file or directory)
If you didn't reboot yet, please do so and try again. If you already did and it
didn't help, please contact the packagers for your distro. If you *are* the
distro because everything is done by hand, then you'll need to figure out the
issue. :)

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

[plasmashell] [Bug 416915] New: broken keep of destination coordinates in drag-and-drop operations

[painless roaster]

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

Bug ID: 416915
   Summary: broken keep of destination coordinates in
drag-and-drop operations
   Product: plasmashell
   Version: 5.17.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: notm...@gmail.com
  Reporter: painless.roas...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY

broken keep of destination coordinates in drag-and-drop operations


STEPS TO REPRODUCE

1. open folder in desktop
2. try copy file from folder to desktop

OBSERVED RESULT

the position of the copied file is aligned to the first free position


EXPECTED RESULT

the position of the copied file must match the drop coordinates

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

[plasmashell] [Bug 416904] Autohiding Panel Glitches on login for new notifications.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 416904] Autohiding Panel Glitches on login for new notifications.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de,
   ||n...@kde.org

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

[plasmashell] [Bug 384470] Crash in QSGBatchRenderer::Renderer::renderBatches

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||gudv...@gmail.com

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

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

[plasmashell] [Bug 384470] Crash in QSGBatchRenderer::Renderer::renderBatches

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[plasmashell] [Bug 416905] Plasma crash in Kickoff

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---


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

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

[kate] [Bug 416907] Kate overwrites Color Schemes.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[valgrind] [Bug 416667] gcc10 ppc64le impossible constraint in 'asm' in test_isa

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #11 from Carl Love  ---
closed issue

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

[plasmashell] [Bug 416909] Clicking-and-holding on a widget's scrollbar enters edit mode

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
  Component|general |Desktop Containment
   Severity|normal  |minor
 Status|REPORTED|CONFIRMED
Summary|Holding the mouse button|Clicking-and-holding on a
   |over an applet's scrollbar  |widget's scrollbar enters
   |arrow enters edit mode  |edit mode
 Ever confirmed|0   |1
   Assignee|k...@davidedmundson.co.uk|notm...@gmail.com

--- Comment #1 from Nate Graham  ---
Heh, whoops.

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

[gwenview] [Bug 416910] Operations tab squashes rather than becoming scrollable when the window is forced to a small size e.g. with quarter-tiling

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Summary|buggy quadrant operations   |Operations tab squashes
   |menu|rather than becoming
   ||scrollable when the window
   ||is forced to a small size
   ||e.g. with quarter-tiling
 Status|REPORTED|CONFIRMED
   Severity|normal  |minor
 CC||n...@kde.org

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

[frameworks-kwidgetsaddons] [Bug 416912] Window resizing can break the layout of a KMessageWidget

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
   Severity|normal  |minor
 Status|REPORTED|CONFIRMED
Summary|window resizing can break   |Window resizing can break
   |the layout of an inline |the layout of a
   |message |KMessageWidget
 Ever confirmed|0   |1

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

[plasmashell] [Bug 412628] Network Monitor arrows can be obscured by graph

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasmashell] [Bug 416914] New: Connecting of external monitor gets stuck Plasma

[waldauf]

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

Bug ID: 416914
   Summary: Connecting of external monitor gets stuck Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: wwwald...@gmail.com
  Target Milestone: 1.0

SUMMARY
Connecting an external monitor to my laptop Lenovo T470p (over HDMI, or mDP or
over docking station) caused hang of plasmashell. 

On Arch forum I found out other people having the same problem.

STEPS TO REPRODUCE
1. Run KDE
2. Connect external monitor
3. Work

OBSERVED RESULT
Symptoms:
* Clock gets stuck
* Not possible to click with the mouse anywhere - choose some window,
right-click, application menu.
* Not possible to unlock screen (SDDM must be restarted)
* Multimedia keys for volume don't work
* Windows react to mouse click with delay (i.e. switch tab in browser)
* Wallpapers disappeared (often)
* Default panel disappeared (almost everytime)
* Kwin is loading one from 8 CPU to 100% (sometimes)
* Keyboard works (mostly), so you can switch to TTYx and restart SDDM

Quick win is in while loop restart of plasmashell:
while true; do killall plasmashell && kstart5 plasmashell; sleep 120; done


EXPECTED RESULT
Working KDE environment.


SOFTWARE/OS VERSIONS
Information about system & KDE:
Operating System: Arch Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
Kernel Version: 5.4.15-arch1-1


Packages containing plasma:
extra/plasma-workspace-wallpapers 5.17.5-1
extra/plasma-workspace 5.17.5-2
extra/plasma-sdk 5.17.5-1
extra/plasma-pa 5.17.5-1
extra/plasma-nm 5.17.5-1
extra/plasma-integration 5.17.5-1
extra/plasma-framework 5.66.0-1
extra/plasma-desktop 5.17.5-2

ADDITIONAL INFORMATION

I found out how to debug kwin_x11 (https://community.kde.org/KWin/Debugging):
$ gdb --pid `pidof kwin_x11` 2>&1 | tee kwin.gdb
Excess command line arguments ignored. (1277)
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 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-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
90290: No such file or directory.
Attaching to process 325239
[New LWP 325281]
[New LWP 325296]
[New LWP 325341]
[New LWP 325345]
[New LWP 325346]
[New LWP 325347]
[New LWP 325348]
[New LWP 325360]
[New LWP 325554]
[New LWP 350054]
[New LWP 359730]
[New LWP 2468705]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x7fa28238bae6 in ppoll () from /usr/lib/libc.so.6
/usr/lib/../share/gcc-9.2.0/python/libstdcxx/v6/xmethods.py:731: SyntaxWarning:
list indices must be integers or slices, not str; perhaps you missed a comma?
  refcounts = ['_M_refcount']['_M_pi']
(gdb)
(gdb)
(gdb) continue
Continuing.
[Thread 0x7fa271931700 (LWP 325554) exited]
[Thread 0x7fa279ac8700 (LWP 325281) exited]
[Thread 0x7fa25febe700 (LWP 325345) exited]
[Thread 0x7fa25f6bd700 (LWP 325346) exited]
[Thread 0x7fa25e6bb700 (LWP 325348) exited]
[Thread 0x7fa25eebc700 (LWP 325347) exited]
[Thread 0x7fa278dc8700 (LWP 325296) exited]

Thread 1 "kwin_x11" received signal SIGSEGV, Segmentation fault.
0x7fa27f01d39b in ?? () from /usr/lib/libKF5GlobalAccel.so.5
(gdb) bt
#0  0x7fa27f01d39b in  () at /usr/lib/libKF5GlobalAccel.so.5
#1  0x7fa27f0138e5 in  () at /usr/lib/libKF5GlobalAccel.so.5
#2  0x7fa280db83be in  () at /usr/lib/libQt5Core.so.5
#3  0x7fa280db2aa0 in QObject::destroyed(QObject*) () at
/usr/lib/libQt5Core.so.5
#4  0x7fa280db6787 in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#5  0x7fa281814d77 in QAction::~QAction() () at /usr/lib/libQt5Widgets.so.5
#6  0x7fa281814daa in QAction::~QAction() () at /usr/lib/libQt5Widgets.so.5
#7  0x7fa280dacc8e in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#8  0x7fa280db6558 in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#9  0x7fa282017d40 in  () at /usr/lib/libkwin.so.5
#10 0x7fa280dacc8e in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#11 0x7fa280db6558 in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#12 0x7fa278596e7a in KWin::X11StandalonePlatform::~X11StandalonePlatform()
() at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#13 

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

--- Comment #11 from Vlad Zahorodnii  ---
(In reply to LinG from comment #10)
> Alright, where can I find the most recent documentation about the methods
> and properties that I should use?
Unfortunately, only source code. API dox is not generated for KWin since KDE
Plasma 5.

> (What method should I use to send clients to different desktops and is there
> also something available to send clients to different activities?)
So, with the new virtual desktop model, a client can enter and leave more than
just one desktop. On X11, a client can be either only on one or on all
desktops, though. The relevant AbstractClient property I'm talking about is
x11DesktopsIds.

It seems like scripts can modify only legacy `desktop` property. :/

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

[kmymoney] [Bug 416827] libofx dtd files are not found in AppImage

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

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

--- Comment #2 from Thomas Baumgart  ---
Adding the files is only half of the solution: seems that we need to tweak the
path were libofx should look for them also. They are not searched for in the
appimage but things work fine when they are installed on the hosts
/usr/share/libofx directory.

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

[kwin] [Bug 412709] Libreoffice windows and virtual desktops

[Sammy]

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

--- Comment #9 from Sammy  ---
You can workaround this bug by selecting the Libreiffice Open/Save Dialogs
under Extras > Options > Libreoffice > General.

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

[akregator] [Bug 330472] ownCloud News App support

[bugzilla_noreply]

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

kde.sebac...@simplelogin.co changed:

   What|Removed |Added

 CC||kde.sebac...@simplelogin.co

--- Comment #6 from kde.sebac...@simplelogin.co ---
any news about this?

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

[plasmashell] [Bug 412641] When multiple copies of an app are installed from different sources (e.g. deb,flatpak,snap), only one is shown in menu

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #1 from Patrick Silva  ---
dupe of bug 389035 ?

I think this problem extremely annoying.
I need to rename the entries of my flatpaks to "App (flatpak)"
or manually create entries for apps from distro repos using kmenueditor to get
around it.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

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

[kwin] [Bug 416093] client screen property now readonly?

[LinG]

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

--- Comment #10 from LinG  ---
(In reply to Vlad Zahorodnii from comment #8)
> (In reply to LinG from comment #7)
> > I've always used this screen property of the client the same way as I have
> > been using the desktop property and am still using. So it's interesting to
> > me that you say that this property has never been writable.
> You shouldn't actually use that property, it's deprecated.

Alright, where can I find the most recent documentation about the methods and
properties that I should use?

(What method should I use to send clients to different desktops and is there
also something available to send clients to different activities?)

> 
> > Question 1: What would be the reason to not make the screen property
> > writable like the desktop property on a client? I'm fine with using your
> > proposed method as well, but isn't the former more in line with the rest of
> > the API?
> It matches what KWin is doing whenever it needs to send a client to another
> screen.

That's fair, keeping the API as close to the internals seems like the best way
to me as well.

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

[krita] [Bug 416899] Offsets and ratio goes wrong when using Transform Tool

[Ahab Greybeard]

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

Ahab Greybeard  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[krita] [Bug 416899] Offsets and ratio goes wrong when using Transform Tool

[Ahab Greybeard]

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

Ahab Greybeard  changed:

   What|Removed |Added

 CC||ahab.greybe...@hotmail.co.u
   ||k

--- Comment #2 from Ahab Greybeard  ---
Created attachment 125520
  --> https://bugs.kde.org/attachment.cgi?id=125520=edit
Bad Transform Effects Screenshots

I see this with the Jan 28th appimage git(049dd11).
It only happens with a vector shape, not a paint layer content.

I attach zipped screenshots a,b,c,d

a: Original 600 x 600 square

b: Offset/position drift after performing a corner drag with Shift key held.
It was necessary to do very rapid sylus movements over a long time to get this.

When the transform was finalised with the Return key, the on-screen image
returned to its original square appearance.

When the transform tool was activated again, the 'b' image reappeared and could
be transformed to:-

c: Additional stretch of the transform preview.

When the transform was finalised with the Return key, the on-screen image
returned to its original square appearance.

At this stage, the Move tool did not work on the original image. Its bounding
box moved but there was no on-screen movement of content or movement when the
Return key was pressed.

If I drew a green line at the top of the screen then that line did not appear.

If I then turned off and then on the layer visibility, I got:-

d: A fragment.

I saw other fragmentation and artifact effects as I did more messing around but
I didn't think it was productive to investigate further at this stage.

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

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

Vlad Zahorodnii  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/76297196e898c838ed89d21f4
   ||4e8a8560cd7391f
 Resolution|--- |FIXED
   Version Fixed In||5.18.0
 Status|REPORTED|RESOLVED

--- Comment #9 from Vlad Zahorodnii  ---
Git commit 76297196e898c838ed89d21f44e8a8560cd7391f by Vlad Zahorodnii.
Committed on 29/01/2020 at 15:14.
Pushed by vladz into branch 'Plasma/5.18'.

[scripting] Expose Workspace::sendClientToDesktop()

Summary:
FIXED-IN: 5.18.0

Test Plan: Only compile-time check.

Reviewers: #kwin, davidedmundson

Reviewed By: #kwin, davidedmundson

Subscribers: kwin

Tags: #kwin

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

M  +8-0scripting/workspace_wrapper.cpp
M  +5-0scripting/workspace_wrapper.h

https://commits.kde.org/kwin/76297196e898c838ed89d21f44e8a8560cd7391f

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

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

--- Comment #8 from Vlad Zahorodnii  ---
(In reply to LinG from comment #7)
> I've always used this screen property of the client the same way as I have
> been using the desktop property and am still using. So it's interesting to
> me that you say that this property has never been writable.
You shouldn't actually use that property, it's deprecated.

> Question 1: What would be the reason to not make the screen property
> writable like the desktop property on a client? I'm fine with using your
> proposed method as well, but isn't the former more in line with the rest of
> the API?
It matches what KWin is doing whenever it needs to send a client to another
screen.

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

[konqueror] [Bug 416913] New: windows keep opening

[AlexKo]

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

Bug ID: 416913
   Summary: windows keep opening
   Product: konqueror
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: alexander.kopr...@areopa.com
  Target Milestone: ---

SUMMARY
Keeps opening new windows until PC is blocked

STEPS TO REPRODUCE
1. when it starts always same result
2. Ubuntu
3. 

OBSERVED RESULT
Multiple new windows opened quickly

EXPECTED RESULT


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

ADDITIONAL INFORMATION
-KDE Frameworks 5.54.0
-Qt 5.11.3 (built against 5.11.3)
-The xcb windowing system

Sorry I am a new Linux user.

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

[Breeze] [Bug 415431] LibreOffice icon set: Breeze, Breeze (SVG), Breeze dark

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
Awesome!

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

[kate] [Bug 412659] Documents Modified on Disk: Case "Deleted": Add "Close Document" button

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #5 from Nate Graham  ---
Agreed. Much nicer now.

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

[kwin] [Bug 416454] Prevent child dialog windows from being tiled

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
We basically have two kinds of dialogs, from a user perspective:

1. A "real window" that just happens to be a dialog. For example: open/save
dialogs, settings windows, etc. These usually make sense to be tile-able as
they are large and generally lay out their content acceptably when made bigger.

2. A "dialog box" that shows you a message or asks for some quick choice. For
example: KMessageBox and its subclasses, job progress windows, the file
overwrite dialog, etc. These never make sense to tile or even resize.

Maybe there's a way to only prevent tiling (and potentially even resizing) for
dialog type #2, but not #1.

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

[kwin] [Bug 412709] Libreoffice windows and virtual desktops

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #8 from Patrick Silva  ---
I have just seen this issue on X11 session of my system. Al least Wayland
session is not affected.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

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

[frameworks-kwidgetsaddons] [Bug 416912] New: window resizing can break the layout of an inline message

[Patrick Silva]

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

Bug ID: 416912
   Summary: window resizing can break the layout of an inline
message
   Product: frameworks-kwidgetsaddons
   Version: 5.66.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: bugsefor...@gmx.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 125519
  --> https://bugs.kde.org/attachment.cgi?id=125519=edit
screen recording

SUMMARY
Watch the attached screen recording please.

EXPECTED RESULT
layout of an inline message should be never broken

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

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

[rkward] [Bug 416911] New: Titlebar or global menu not working with RKWard and opened script

[bugzilla_noreply]

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

Bug ID: 416911
   Summary: Titlebar or global menu not working with RKWard and
opened script
   Product: rkward
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: rkward-de...@kde.org
  Reporter: fl...@mailoo.org
  Target Milestone: ---

VERSION 0.7.1

SUMMARY
When a R script is opened in RKWard and Kwin is configured for placing the
menus in the titlebar (or a globalmenu bar), the menu of RKWard becomes
inaccessible. It is invisible in-app (as it should), but also not placed in a
titlebar button (while it should) and not accessible through other means such
as Plasma-HUD.

STEPS TO REPRODUCE
1. When the menu bar is set to be exported in the title bar (adding the "App
Menu" button to the buttons of the title bar is enough nowadays).
2. Open RKWard directly, the app menu button is shown, and the menu is
accessible.
3. Now open a script within RKWard, the app menu button disappears and the menu
is not accessible anymore. Closing the script leave the app menu inaccessible,
it doesn't come back.

Of course, it doesn't happen when the appmenu is shown, as it is by default.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20200125
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
Kernel Version: 5.4.13-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 15,6 Gio

ADDITIONAL INFORMATION

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

[digikam] [Bug 416755] Tag with "." not processed correctly, likely to result in data loss

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
Ok, I just took another look at the IPTC Guide, which speaks of commas or other
separators. Not of points. Then it would be a mistake in digiKam and easy to
change.

Maik

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

[plasmashell] [Bug 416347] plasma crashed on Wayland when I reconnected external monitor to hdmi port

[waldauf]

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

--- Comment #6 from waldauf  ---
Next symptom is delay in working with window - switch window, scroll page, ...
.

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

[kate] [Bug 396213] Create Flatpak package for Kate in Flathub

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||bugsefor...@gmx.com
 Resolution|--- |FIXED

--- Comment #2 from Patrick Silva  ---
Kate is already available on flathub
https://flathub.org/apps/details/org.kde.kate

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

[gwenview] [Bug 416910] New: buggy quadrant operations menu

[johnathan]

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

Bug ID: 416910
   Summary: buggy quadrant operations menu
   Product: gwenview
   Version: 19.12.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: testing1237a-...@yahoo.com
  Target Milestone: ---

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

SUMMARY

select any image and move gwenview to quandrant. the operations tab does not
show any scrollbar and squishes the entire text.

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

[kmail2] [Bug 377554] "Show HTML for this contact" no longer works

[Tony Green]

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

Tony Green  changed:

   What|Removed |Added

 CC||k...@web-brewer.co.uk

--- Comment #3 from Tony Green  ---
Created attachment 125517
  --> https://bugs.kde.org/attachment.cgi?id=125517=edit
Log from KMail session

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

[kwin] [Bug 416093] client screen property now readonly?

[LinG]

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

--- Comment #7 from LinG  ---
(In reply to Vlad Zahorodnii from comment #3)
> (In reply to LinG from comment #0)
> > The screen property of a client is now readonly? I'm pretty sure it used to
> > be read and write, thus allowing me to change the screen on which a client
> > resides but now I can't? How do I change the screen on which a client
> > resides through the scripting API now?
> As far as I know, it has always been read-only.

I've always used this screen property of the client the same way as I have been
using the desktop property and am still using. So it's interesting to me that
you say that this property has never been writable.

Question 1: What would be the reason to not make the screen property writable
like the desktop property on a client? I'm fine with using your proposed method
as well, but isn't the former more in line with the rest of the API?

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

[plasmashell] [Bug 405606] [Wayland] virtual desktops OSD is not centered on screen

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---
Now OSD is centered on Wayland session of Arch (Plasma 5.18 beta) and Neon
unstable edition. :)

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

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

[kwin] [Bug 416546] Minimize, restore/maximize and close buttons of Firefox CSD stop working after the window to be unmaximized

[Patrick Silva]

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

--- Comment #2 from Patrick Silva  ---
I think your command only works with apps running natively on Wayland, I see no
output here.
My Firefox runs on Xwayland, it is completely unusable for me when running
natively on Wayland.

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

[Breeze] [Bug 415431] LibreOffice icon set: Breeze, Breeze (SVG), Breeze dark

[Postix]

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

--- Comment #3 from Postix  ---
https://wiki.documentfoundation.org/ReleaseNotes/6.4#Icon_Theme

> Breeze & Sifr icon themes got SVG variant of dark version. 
> tdf#128849 [1] (Luca > Carlon & Rizal Muttaqin)
> It will be available in 6.4.1.
[1] https://bugs.documentfoundation.org/show_bug.cgi?id=128849

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

[kate] [Bug 412972] "Overwrite", "Reload" and "Ignore changes" buttons of "Documents modified on disk" dialog should be disabled until at least one document is selected in it

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

Summary|Nothing happens when|"Overwrite", "Reload" and
   |"Overwrite", "Reload" and   |"Ignore changes" buttons of
   |"Ignore changes" buttons|"Documents modified on
   |are clicked in "Documents   |disk" dialog should be
   |modified on disk" dialog|disabled until at least one
   ||document is selected in it
Version|19.08.2 |19.12.1

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

[kate] [Bug 412972] Nothing happens when "Overwrite", "Reload" and "Ignore changes" buttons are clicked in "Documents modified on disk" dialog

[Patrick Silva]

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

--- Comment #1 from Patrick Silva  ---
Created attachment 125516
  --> https://bugs.kde.org/attachment.cgi?id=125516=edit
screenshot showing "Documents modified on disk" with all buttons enabled even
if no document is selected

Humm, nothing happens if the buttons are clicked without I select the file
before.
The buttons should be disabled when no file is selected in the files list.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

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

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

--- Comment #6 from Vlad Zahorodnii  ---
It would be great if you could test my patch. ;-)

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

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

--- Comment #5 from Vlad Zahorodnii  ---
(In reply to Lo from comment #4)
> So how does one move a client from a screen to another?
See https://phabricator.kde.org/D26988.

You would do `workspace.sendClientToScreen(client, screen);` or something.

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

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

Vlad Zahorodnii  changed:

   What|Removed |Added

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

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

[kate] [Bug 412659] Documents Modified on Disk: Case "Deleted": Add "Close Document" button

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #4 from Patrick Silva  ---
"Document modified on disk" window was very confuse to me too.
I can confirm Christoph's comment when using Kate 19.12.1 and I think that this
issue is now solved.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

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

[plasmashell] [Bug 416909] New: Holding the mouse button over an applet's scrollbar arrow enters edit mode

[Wolfgang Bauer]

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

Bug ID: 416909
   Summary: Holding the mouse button over an applet's scrollbar
arrow enters edit mode
   Product: plasmashell
   Version: 5.17.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wba...@tmo.at
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Some applets on the desktop may have scrollbars, e.g. the folderview or notes
applet.

STEPS TO REPRODUCE
1. Add a notes or folderview applet to your desktop
2. Make sure the scrollbar appears (e.g. by configuring a folder with a lot of
files, or pasting/typing more text than fits into the visible area)
3. Click on a scrollbar arrow and hold the mouse button pressed to scroll
continuously

OBSERVED RESULT
The applet switches to edit mode after a few seconds

EXPECTED RESULT
Should continue scrolling without entering edit mode

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION

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

[kwin] [Bug 416093] client screen property now readonly?

[Lo]

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

--- Comment #4 from Lo  ---
So how does one move a client from a screen to another?

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

[kwin] [Bug 416906] KWin crash, maybe related to context menu or to desktop change

[Daniel Levai]

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

--- Comment #4 from Daniel Levai  ---
I am more than sorry for my questions, but I just can't find the kdelibs5-dbg
and I only have libkwineffects12 in my repositories. Is there some problem with
my sources.list? I have these lines in my sources.list (I have omitted the
commented lines):

deb http://hu.archive.ubuntu.com/ubuntu/ eoan main restricted
deb http://hu.archive.ubuntu.com/ubuntu/ eoan-updates main restricted
deb http://hu.archive.ubuntu.com/ubuntu/ eoan universe
deb http://hu.archive.ubuntu.com/ubuntu/ eoan-updates universe
deb http://hu.archive.ubuntu.com/ubuntu/ eoan multiverse
deb http://hu.archive.ubuntu.com/ubuntu/ eoan-updates multiverse
deb http://hu.archive.ubuntu.com/ubuntu/ eoan-backports main restricted
universe multiverse

deb http://security.ubuntu.com/ubuntu/ eoan-security main restricted
deb http://security.ubuntu.com/ubuntu/ eoan-security universe
deb http://security.ubuntu.com/ubuntu/ eoan-security multiverse

and wine and slack and other repos

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

[kwin] [Bug 416093] client screen property now readonly?

[Vlad Zahorodnii]

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

--- Comment #3 from Vlad Zahorodnii  ---
(In reply to LinG from comment #0)
> The screen property of a client is now readonly? I'm pretty sure it used to
> be read and write, thus allowing me to change the screen on which a client
> resides but now I can't? How do I change the screen on which a client
> resides through the scripting API now?
As far as I know, it has always been read-only.

(In reply to Lo from comment #2)
> There seems to be a sendToScreen method (
> https://github.com/KDE/kwin/blob/fbfd1ac705212892f417aa5cc9df5fcd9ce9cb52/
> abstract_client.h#L453 ) however it's not accessible to scripts.
No, what you need is Workspace::sendClientToScreen(), which is not exposed to
scripting API unfortunately.

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

[kwin] [Bug 416454] Prevent child dialog windows from being tiled

[Postix]

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

--- Comment #3 from Postix  ---
(In reply to Vlad Zahorodnii from comment #2)
> Well, it depends on the dialog. For example, the settings dialog from
> Konsole looks okay-ish when it's quick tiled.

That's true!

> Yeah, maybe we have to blacklist dialogs.

Or to whitelist dialogs, depending on what is less effort and easier to
achieve, which I cannot evaluate.

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

[kwin] [Bug 416546] Minimize, restore/maximize and close buttons of Firefox CSD stop working after the window to be unmaximized

[Vlad Zahorodnii]

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

Vlad Zahorodnii  changed:

   What|Removed |Added

Summary|[Wayland] minimize, |Minimize, restore/maximize
   |restore/maximize and close  |and close buttons of
   |buttons of Firefox CSD stop |Firefox CSD stop working
   |working after the window to |after the window to be
   |be unmaximized  |unmaximized
  Flags||Wayland+

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

[kwin] [Bug 416546] [Wayland] minimize, restore/maximize and close buttons of Firefox CSD stop working after the window to be unmaximized

[Vlad Zahorodnii]

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

--- Comment #1 from Vlad Zahorodnii  ---
Could you please run firefox with WAYLAND_DEBUG=1 and attach the resulting
terminal output to this bug report? It would be great if you save the terminal
output to a text file.

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

[kwin] [Bug 416454] Prevent child dialog windows from being tiled

[Vlad Zahorodnii]

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

--- Comment #2 from Vlad Zahorodnii  ---
(In reply to Postix from comment #0)
> The close dialog of the Firefox can be resized or tiled, which does not make
> much sense actually and which looks kind of weird if it's done.
Well, it depends on the dialog. For example, the settings dialog from Konsole
looks okay-ish when it's quick tiled.

> Maybe it can be prevented from doing so? I can't remember that this is
> possible on other operating systems like Gnome Desktop or Windows 10.
Yeah, maybe we have to blacklist dialogs.

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

[kate] [Bug 412987] Close Icon Missing on Tabs

[Greg Lepore]

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

Greg Lepore  changed:

   What|Removed |Added

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

--- Comment #4 from Greg Lepore  ---
Not sure which update fixed this bug, but the close icon is now appearing on
tabs.

Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2
Kernel Version: 4.15.0-74-generic
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 7.8 GiB of RAM

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

[kwin] [Bug 415872] kwin_wayland random segfault libQt5Qml.so.5.14.0[7fe09a171000+307000]

[Vlad Zahorodnii]

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

--- Comment #3 from Vlad Zahorodnii  ---
> Generally around every 6-8 hours of use, sometimes sooner.
It would be really helpful if you could retrieve the backtrace of the crash.

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

[frameworks-kio] [Bug 412664] Incrementally create and delete folder structures when doing a recursive copy

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[dolphin] [Bug 412666] Drag and drop a file from one window to another: keep source window below

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kwin] [Bug 416906] KWin crash, maybe related to context menu or to desktop change

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
Please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

For exact -dbgsym package names, please ask for help in a forum of your
distribution.

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

[lattedock] [Bug 416748] Settings of battery applet within system tray not saved after logout

[bugzilla_noreply]

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

--- Comment #14 from lk.d...@hotmail.fr ---
Created attachment 125515
  --> https://bugs.kde.org/attachment.cgi?id=125515=edit
The screenshot appearing after Right Click Dock > Layouts > Configure

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

[frameworks-kio] [Bug 412669] Copy/Move existing folder from one filesystem to another: different folder sizes of empty folder can cause confusion

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kwin] [Bug 416906] KWin crash, maybe related to context menu or to desktop change

[Daniel Levai]

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

--- Comment #2 from Daniel Levai  ---
> Could you please install debug symbols for libkwineffects (or kwin in 
> general) and attach a new backtrace to this bug report?

I have googled for a guide which package should I install and how and didn't
found anything meaningful. Are there instructions somewhere how do I install
the debug flags and create a new backtrace?

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

[plasmashell] [Bug 412670] In properties dialog for item on the Desktop in Folder View, "Location" field inaccurately shows "/ (desktop)" instead of correct path

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasmashell] [Bug 416908] New: Plasmashell crash after clicking twice on ethernet connection while connecting

[Thiago Sueto]

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

Bug ID: 416908
   Summary: Plasmashell crash after clicking twice on ethernet
connection while connecting
   Product: plasmashell
   Version: 5.17.90
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (5.17.90)

Qt Version: 5.12.5
Frameworks Version: 5.66.0
Operating System: Linux 5.4.0-12-generic x86_64
Windowing system: X11
Distribution: Ubuntu Focal Fossa (development branch)

-- Information about the crash:

I was having trouble connecting to my ethernet connection. The cable was in but
it wasn't connecting.
I clicked the Network widget (plasma-nm?), clicked once on the name of the
ethernet connection, clicked once again to see if the Details pane would appear
since I assumed the pane also appears when trying to reconnect.
Plasmashell then crashed. I verified that this was reproducible every time as
long as the ethernet was trying to connect.

Since this was my work machine, I tried to remove the ethernet cable and put it
back to restore connection, it didn't work.
Then I tried deleting the ethernet connection, remove the ethernet cable and
put it back, and the network was restored.
After it was restored, the crash was no longer reproducible.

In other words, under the correct conditions, the crash can be reproduced every
time. With proper internet connection it cannot.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x559e4f390190) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
[Current thread is 1 (Thread 0x7f337d347300 (LWP 949))]

Thread 11 (Thread 0x7f334901e700 (LWP 1534)):
[KCrash Handler]
#6  0x7f3369337d10 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so
#7  0x7f336933965b in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so
#8  0x7f3380e88848 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f33829e14c4 in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f33829875a8 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f338298b308 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7f3380c95a42 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f3380134669 in start_thread (arg=) at
pthread_create.c:479
#14 0x7f3380918333 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f33499e9700 (LWP 1527)):
#0  __GI___libc_read (nbytes=16, buf=0x7f33499e8b90, fd=33) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=33, buf=0x7f33499e8b90, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f337f5714bf in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f337f528c1e in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f337f529072 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f337f529203 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f3380eb4943 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3380e5b8bb in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3380c947f5 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f3380c95a42 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f3380134669 in start_thread (arg=) at
pthread_create.c:479
#11 0x7f3380918333 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f3360ef0700 (LWP 1523)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x559e4d908b94) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559e4d908b40,
cond=0x559e4d908b68) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x559e4d908b68, mutex=0x559e4d908b40) at
pthread_cond_wait.c:638
#3  0x7f3380c9bb7f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3380c9bc71 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f338298b0f9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f338298b39d in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f3380c95a42 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3380134669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7f3380918333 in clone () at

[kate] [Bug 416907] New: Kate overwrites Color Schemas.

[Xeno Idaltu]

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

Bug ID: 416907
   Summary: Kate overwrites Color Schemas.
   Product: kate
   Version: 18.08.0
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: xenoida...@gmail.com
  Target Milestone: ---

This issue happens in Editor Component => Font & Color Schemas.

If I'm using a color scheme of my choice and then accidentally click on Use KDE
Color Scheme button, it will automatically overwrite the color scheme I was
using. I tried this on all preinstalled color schemes and they all turned into
my default KDE Color Scheme. This can be annoying when testing color schemes.


KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

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

[kate] [Bug 416907] Kate overwrites Color Schemes.

[Xeno Idaltu]

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

Xeno Idaltu  changed:

   What|Removed |Added

Summary|Kate overwrites Color   |Kate overwrites Color
   |Schemas.|Schemes.

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

[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz

[bugzilla_noreply]

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

hoperidesal...@protonmail.ch changed:

   What|Removed |Added

 CC||hoperidesalone@protonmail.c
   ||h

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

[frameworks-kio] [Bug 412671] Properties dialog: Separate filesystem info clearer from selected folder

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kwin] [Bug 416906] KWin crash, maybe related to context menu or to desktop change

[Vlad Zahorodnii]

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

Vlad Zahorodnii  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Vlad Zahorodnii  ---
Could you please install debug symbols for libkwineffects (or kwin in general)
and attach a new backtrace to this bug report?

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

[digikam] [Bug 416757] Tags incorrectly displayed when deleted from Edit Metadata / IPTC

[bugzilla_noreply]

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

--- Comment #2 from harald.a...@web.de ---
Maik,

All the pictures I am currently experimenting with originally contain the same
tags both in iptc:keywords and xmp:subject. I have then "done something" with
these tags (added, deleted, modified); in digiKam, but potentially also outside
of digiKam. I purposely only ever modified these two locations but don't know
what other places might have been also modified.

I then went to "Edit Metadata / Edit IPTC" and deleted all the tags there.
Which sometimes (but by no means always), under "digiKam properties", resulted
in a list of tags that was neither empty nor corresponding to the tags shown
under "Edit Metadata / Edit XMP".

I am sorry I have not been able to reliably reproduce this. Also, it is a
rather artificial scenario not likely to happen in real use, which is why I
consider this issue of minor importance. But wanted to let you know about just
the same.

Best regards,
Harald

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

[kdeconnect] [Bug 412665] kdeconnect-cli cannot start kdeconnectd.exe on Windows in Chinese

[jingyu9575]

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

--- Comment #2 from jingyu9575  ---
(In reply to dianlujitao from comment #1)
> Changing to `Exec=kdeconnectd` fixes the problem as well.

Yes, I'm also using this value now. I remember when I simply commented it out
there will be a "cannot find file" error after running a long time. With
`Exec=kdeconnectd` I have not seen this error yet.

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

[digikam] [Bug 416755] Tag with "." not processed correctly, likely to result in data loss

[bugzilla_noreply]

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

--- Comment #2 from harald.a...@web.de ---
Maik,

So it’s a feature, not a bug. But this is unique to digiKam, isn’t it? I have
not observed this behavior with any of the other software I use (e.g.
Lightroom, Picasa, IrfanView, exiftool).

Your guess is right. I had changed the order for tags, putting
iptc.application2.keywords first. Reason for that was that many of my photos
contain *only* iptc:keywords, and I wanted to make sure that those are used,
and not some potentially arbitrary contents of a different field that some
software might have written without me intending so.

Now, I did „reset to default“; read in a photo with „a.b.c“ tag both in
iptc:keywords and xmp:subject, and it worked :-)

Are there any other pitfalls to be avoided? 

Best regards,
Harald

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

[kwin] [Bug 416906] New: KWin crash, maybe related to context menu or to desktop change

[Daniel Levai]

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

Bug ID: 416906
   Summary: KWin crash, maybe related to context menu or to
desktop change
   Product: kwin
   Version: 5.16.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: levai...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.16.5)

Qt Version: 5.12.4
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-24-generic x86_64
Distribution: Ubuntu 19.10

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

I've just woken up my system and I think I changed desktop while opening a menu
of an application.

I haven't been able to reproduce this problem, but the Crash Reporting
Assistant suggested me to report nevertheless.

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

Thread 12 (Thread 0x7f0c9fc27700 (LWP 586)):
#0  0x7f0d5c0a42c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f331dea7c0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7f0d5c0a42c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55f331dea770, cond=0x55f331dea798) at pthread_cond_wait.c:508
#2  0x7f0d5c0a42c6 in __pthread_cond_wait (cond=0x55f331dea798,
mutex=0x55f331dea770) at pthread_cond_wait.c:638
#3  0x7f0d5cb35def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0d5cb35ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0d5bbcb7b9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f0d5bbcba1a in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f0d5cb2fcc2 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0d5c09d669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7f0d5e296323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f0c8e149700 (LWP 10733)):
#0  0x7f0d5c0a42c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f32fbd0a80) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7f0d5c0a42c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55f32fbd0a30, cond=0x55f32fbd0a58) at pthread_cond_wait.c:508
#2  0x7f0d5c0a42c6 in __pthread_cond_wait (cond=0x55f32fbd0a58,
mutex=0x55f32fbd0a30) at pthread_cond_wait.c:638
#3  0x7f0d5cb35def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0d5cb35ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0d5bbcb7b9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f0d5bbcba1a in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f0d5cb2fcc2 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0d5c09d669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7f0d5e296323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f0d3eb37700 (LWP 7122)):
#0  0x7f0d5c0a42c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f3304480b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7f0d5c0a42c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55f330448060, cond=0x55f330448088) at pthread_cond_wait.c:508
#2  0x7f0d5c0a42c6 in __pthread_cond_wait (cond=0x55f330448088,
mutex=0x55f330448060) at pthread_cond_wait.c:638
#3  0x7f0d5cb35def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0d5cb35ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0d5bbcb7b9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f0d5bbcba1a in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f0d5cb2fcc2 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0d5c09d669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7f0d5e296323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f0d4edee700 (LWP 7121)):
#0  0x7f0d5e289d26 in __GI_ppoll (fds=0x7f0d34082c98, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f0d5cd4a5f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0d5cd4bb64 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0d5ccf563b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0d5cb2ea75 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0d5b83d319 in  () at