[kstars] [Bug 387716] KStars crashes with non-powered CCD camera in INDI

[Csaba Kertész]

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

--- Comment #2 from Csaba Kertész  ---
Strangely enough, things go wrong only if a Scheduler session is started.
Capturing an image, alignment does not exhibit the same problem.

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

[kstars] [Bug 387716] KStars crashes with non-powered CCD camera in INDI

[Jasem Mutlaq]

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

--- Comment #1 from Jasem Mutlaq  ---
I haven't checked it but when you run QHY/ZWO with NO camera attached, no
driver is defined and therefore Ekos might think that it is an incomplete
invalid startup (it is) and then pops this question to restart the process?

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

[Plasma Vault] [Bug 385445] Changing Focus to Password Dialog Upon Opening Vault from System Tray

[Ivan Čukić]

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

Ivan Čukić  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/pla
   ||sma-vault/b80ee599b39f0ffeb
   ||3bc749d9bcbc8cf592ea146
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #6 from Ivan Čukić  ---
Git commit b80ee599b39f0ffeb3bc749d9bcbc8cf592ea146 by Ivan Čukić, on behalf of
Kees vd Broek.
Committed on 09/12/2017 at 06:29.
Pushed by ivan into branch 'master'.

Fix PWD dialog

Summary:
Make password dialog have error-handling built in.
Related: bug 385985

This will show the error directly in the dialog and refuse to close
until the mount was successful (or user presses cancel).

Test Plan: {F5518252}

Reviewers: #plasma, ivan

Subscribers: abetts, colomar, jensreuterberg, ngraham, cfeck, plasma-devel

Tags: #plasma

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

M  +2-0kded/CMakeLists.txt
M  +6-45   kded/service.cpp
A  +59   -0kded/ui/mountdialog.cpp [License: GPL (v2/3)]
A  +46   -0kded/ui/mountdialog.h [License: GPL (v2/3)]
A  +181  -0kded/ui/mountdialog.ui

https://commits.kde.org/plasma-vault/b80ee599b39f0ffeb3bc749d9bcbc8cf592ea146

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

[Plasma Vault] [Bug 385985] Password dialog has wrong text

[Ivan Čukić]

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

Ivan Čukić  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/pla
   ||sma-vault/b80ee599b39f0ffeb
   ||3bc749d9bcbc8cf592ea146

--- Comment #2 from Ivan Čukić  ---
Git commit b80ee599b39f0ffeb3bc749d9bcbc8cf592ea146 by Ivan Čukić, on behalf of
Kees vd Broek.
Committed on 09/12/2017 at 06:29.
Pushed by ivan into branch 'master'.

Fix PWD dialog

Summary:
Make password dialog have error-handling built in.
Related: bug 385445

This will show the error directly in the dialog and refuse to close
until the mount was successful (or user presses cancel).

Test Plan: {F5518252}

Reviewers: #plasma, ivan

Subscribers: abetts, colomar, jensreuterberg, ngraham, cfeck, plasma-devel

Tags: #plasma

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

M  +2-0kded/CMakeLists.txt
M  +6-45   kded/service.cpp
A  +59   -0kded/ui/mountdialog.cpp [License: GPL (v2/3)]
A  +46   -0kded/ui/mountdialog.h [License: GPL (v2/3)]
A  +181  -0kded/ui/mountdialog.ui

https://commits.kde.org/plasma-vault/b80ee599b39f0ffeb3bc749d9bcbc8cf592ea146

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

[krusader] [Bug 386217] Pressing Arrow keys behaves incorrectly in quicksearch

[bugzilla_noreply]

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

--- Comment #17 from s-tr...@list.ru ---
I'm for option #3 too.

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

[krita] [Bug 387725] Ugly brush dabs when painting on 1-channel layers (ie Masks, Fill Layer) with a Build-Up brush

[Wysteria]

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

Wysteria  changed:

   What|Removed |Added

Summary|Ugly brush dabs when|Ugly brush dabs when
   |painting on a Fill Layer|painting on 1-channel
   |with a Build-Up brush   |layers (ie Masks, Fill
   ||Layer) with a Build-Up
   ||brush

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

[krita] [Bug 387725] Ugly brush dabs when painting on a Fill Layer with a Build-Up brush

[Wysteria]

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

--- Comment #2 from Wysteria  ---
Actually, it is not just Fill Layers. Transparency Masks and Filter Masks are
also affected. This is a bug about 1-channel layers.

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

[kdenlive] [Bug 387727] New: Waveform monitor and 'scopes display random information even with no clips added.

[Ken Jarstad]

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

Bug ID: 387727
   Summary: Waveform monitor and 'scopes display random
information even with no clips added.
   Product: kdenlive
   Version: 17.08.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: ken.jars...@gmail.com
  Target Milestone: ---

Kdenlive 17.08.3 install from AppImage on Linux Mint Cinnamon.

1. Start Kdenlive
2. Open View menu and add Waveform Monitor.

Waveform Monitor has full-frame response

3. Press Right-arrow key several times until WM "dances" (see video). All
'scopes exhibit strange behavior as well. Video Rendering appears unaffected.

If I boot this same PC with Knoppix 8.1 on a flash-drive which has Kdenlive
17.08.0 pre-installed the Waveform Monitor and scopes all work perfectly.

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

[krita] [Bug 387725] Ugly brush dabs when painting on a Fill Layer with a Build-Up brush

[Wysteria]

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

--- Comment #1 from Wysteria  ---
Created attachment 109267
  --> https://bugs.kde.org/attachment.cgi?id=109267=edit
Actual result of painting on fill layer with build-up brush

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

[krita] [Bug 387725] New: Ugly brush dabs when painting on a Fill Layer with a Build-Up brush

[Wysteria]

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

Bug ID: 387725
   Summary: Ugly brush dabs when painting on a Fill Layer with a
Build-Up brush
   Product: krita
   Version: git master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: nabstertopsykre...@gmail.com
  Target Milestone: ---

Created attachment 109266
  --> https://bugs.kde.org/attachment.cgi?id=109266=edit
Expected look of build-up brush on fill layer

On master, the way build-up brush dabs paint on a Fill Layer appears very
different to the way it paints on earlier Krita versions like 3.3.1, I don't
really know how to describe it, it just looks ugly and unexpected. I will
attach the example files "nice dabs.kra" (3.3.1) and "ugly dabs.kra" (master)
to demonstrate.

Alternatively here are some screenshots to show what it looks like, though I'm
no longer certain which versions I used to make them on (Also, I don't know how
long these links last):
Expected look https://my.mixtape.moe/mbmdud.png
Result https://my.mixtape.moe/uxyoky.png

How to Reproduce:
1. Make a Fill Layer, Color
2. Activate a build-up brush preset (like Pencil_texture)
3. Paint on the Fill Layer

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

[Discover] [Bug 385554] Discover crashes in AbstractResourcesBackend::Filters::shouldFilter() while searching

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[Discover] [Bug 385554] Discover crashes in AbstractResourcesBackend::Filters::shouldFilter() while searching

[Mustafa Muhammad]

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

--- Comment #6 from Mustafa Muhammad  ---
Created attachment 109265
  --> https://bugs.kde.org/attachment.cgi?id=109265=edit
New crash information added by DrKonqi

plasma-discover (5.11.3) using Qt 5.9.2

- What I was doing when the application crashed:

Just searching in Discover.

I attached full debug info, I use version 5.11.3 you mentioned on Fedora 27
(test-updates).

In case this is related, I use the flatpak backend, not likely, but may be
related.

-- Backtrace (Reduced):
#7  0x7f2435fd2de2 in AbstractResourcesBackend::Filters::shouldFilter
(this=0x5558562a45c0, res=0x555854205190) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:114
#8  0x7f2435fd30fd in AbstractResourcesBackend::Filters::filterJustInCase
(this=this@entry=0x5558562a45c0, input=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:127
#9  0x7f2435fcaf12 in ResourcesProxyModel::addResources
(this=0x5558562a4590, _res=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/ResourcesProxyModel.cpp:174
[...]
#11 0x7f2435fe23d2 in ResultsStream::resourcesFound
(this=this@entry=0x5558562ca0d0, _t1=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/x86_64-redhat-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:142
#12 0x7f2435fc2ec0 in AggregatedResultsStream::emitResults
(this=0x5558562ca0d0) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/ResourcesModel.cpp:284

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

[krusader] [Bug 386217] Pressing Arrow keys behaves incorrectly in quicksearch

[Nikita Melnichenko]

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

--- Comment #16 from Nikita Melnichenko  ---
There is a space for a 4th checkbox in the Settings dialog (Panel -> General ->
Search Bar) right under "Case sensitive" - I can add a setting to control the
behavior. Toni, is it ok with you?

S-trace, Alex, Toni - please share your opinion on the best option. If get what
Alex said in comment #14, he's for option #3.

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

[kde] [Bug 387724] Draggin widget to panel crashes plasmashell

[Tony]

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

Tony  changed:

   What|Removed |Added

   Platform|unspecified |openSUSE RPMs
Version|unspecified |Git

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

[kde] [Bug 387724] New: Draggin widget to panel crashes plasmashell

[Tony]

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

Bug ID: 387724
   Summary: Draggin widget to panel crashes plasmashell
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jodr...@live.com
  Target Milestone: ---

Application: plasmashell (5.11.90)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I added the CPU Load Monitor the desktop then dragged it to the panel.

The crash can be reproduced every time.

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

Thread 21 (Thread 0x7ff3eabef700 (LWP 27209)):
#0  0x7ff4caf2d82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff4cbd86c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ff4cfb5fa98 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7ff4cfb5feca in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7ff4cbd858d0 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff4caf27558 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff4cb6806bf in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7ff3eb5f7700 (LWP 17926)):
#0  0x7ff4caf2d82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff4cbd86c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ff4cfb5fa98 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7ff4cfb5feca in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7ff4cbd858d0 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff4caf27558 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff4cb6806bf in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7ff3ebfff700 (LWP 17620)):
#0  0x7ff4caf2d82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff4cbd86c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ff4cfb5fa98 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7ff4cfb5feca in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7ff4cbd858d0 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff4caf27558 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff4cb6806bf in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7ff4007f6700 (LWP 9415)):
#0  0x7ff4caf2d82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff4cbd86c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ff4cfb5fa98 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7ff4cfb5feca in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7ff4cbd858d0 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff4caf27558 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff4cb6806bf in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7ff400ff7700 (LWP 9414)):
#0  0x7ff4cb671a68 in read () at /lib64/libc.so.6
#1  0x7ff4c0ea9751 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7ff4c1e9ddde in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7ff4c1e9e850 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7ff4c1e9e910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7ff4c1eac779 in  () at /usr/lib64/libpulse.so.0
#6  0x7ff4c0ed8438 in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#7  0x7ff4caf27558 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff4cb6806bf in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7ff3d4bef700 (LWP 9413)):
#0  0x7ff4cb675f0b in poll () at /lib64/libc.so.6
#1  0x7ff4c6366149 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff4c636625c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff4cbfb257b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff4cbf594aa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff4cbd808da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff4cef1abd5 in QQmlThreadPrivate::run() () at
/usr/lib64/libQt5Qml.so.5
#7  0x7ff4cbd858d0 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#8  0x7ff4caf27558 in start_thread () 

[kate] [Bug 387723] New: Search symbols in Symbol List

[Chenxiong Qi]

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

Bug ID: 387723
   Summary: Search symbols in Symbol List
   Product: kate
   Version: 17.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: qcxh...@gmail.com
  Target Milestone: ---

It would be nice to be able to search symbols in Symbol list. In my mind, when
Symbol list is shown and get the focus, I can type characters directly, and
those will be shown on top of the list (probably in a text box) and symbol list
is refreshed to list symbols that contains input characters. Fuzzy search would
be great. Thanks.

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

[kate] [Bug 386758] Large numbers of tabs become hard to access

[Chenxiong Qi]

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

Chenxiong Qi  changed:

   What|Removed |Added

 CC||qcxh...@gmail.com

--- Comment #8 from Chenxiong Qi  ---
Multi-row tabs would be good, however I recently found that Documents side bar
is really useful when many files are opened. Another way to switch between
opened files is to use quick open. Each opened file is displayed in bold font
and you can type part of the word or characters to narrow the file list. I also
assigned a keyboard shortcut to show Quick Open quickly without leaving my
fingers from keyboard, which is much efficient and useful for me.

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

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 387722] Right click context menu - move to screen

[Brennan Kinney]

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

Brennan Kinney  changed:

   What|Removed |Added

 CC||polarathene-signup@hotmail.
   ||com

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

[plasmashell] [Bug 387722] New: Right click context menu - move to screen

[Brennan Kinney]

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

Bug ID: 387722
   Summary: Right click context menu - move to screen
   Product: plasmashell
   Version: master
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: polarathene-sig...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Like context menu for titlebar, there is `Move to Desktop`, but `Move to
Screen` is not available(at least on icons-only). I have had several times
where I need this as I can't see the titlebar but could use the task manager
app icon to perform this.

Discussion here:
https://www.reddit.com/r/kde/comments/7ii2y6/send_window_to_monitor/

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

[plasmashell] [Bug 368469] Configuration for second monitor gets lost

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk,
   ||plasma-b...@kde.org
   Assignee|notm...@gmail.com   |se...@kde.org
  Component|Desktop Dashboard   |Desktop Containment

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

[plasmashell] [Bug 387704] After return from hibernate have some visual deformations on text of desktop icons.

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #6 from David Edmundson  ---


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

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

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||arisel...@gmail.com

--- Comment #11 from David Edmundson  ---
*** Bug 387704 has been marked as a duplicate of this bug. ***

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

[kdeplasma-addons] [Bug 382320] Wikimedia Picture of the Day does not work

[bugzilla_noreply]

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

--- Comment #3 from filtrationun...@gmail.com ---
A very similar approach to what Anton suggested is used in the bing provider:

https://github.com/KDE/kdeplasma-addons/blob/Plasma/5.10/dataengines/potd/bingprovider.cpp

1) A request is made to find the name of the picture of the day:

https://github.com/KDE/kdeplasma-addons/blob/Plasma/5.10/dataengines/potd/bingprovider.cpp#L96

2) Once it's found it's used to get the picture:

https://github.com/KDE/kdeplasma-addons/blob/Plasma/5.10/dataengines/potd/bingprovider.cpp#L71

In the place of the %1.

Should be similar for this dataprovider.

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

[choqok] [Bug 387446] Build fails with Qt 5.10

[Andrea Scarpino]

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

Andrea Scarpino  changed:

   What|Removed |Added

Version|unspecified |Git
   Version Fixed In||1.7
 Status|UNCONFIRMED |CONFIRMED
  Latest Commit||1a4b87f8d200690b90666536ace
   ||0b70a28701b89
 Ever confirmed|0   |1

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

[kwin] [Bug 387721] New: "screenshotArea" dbus API needs a "selectArea" method or similar

[Jehan]

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

Bug ID: 387721
   Summary: "screenshotArea" dbus API needs a "selectArea" method
or similar
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: je...@zemarmot.net
  Target Milestone: ---

I have implemented screenshot through KWin API in GIMP. It is working fine
except for the rectangular area screenshot.

"org.kde.kwin.Screenshot" provides a "screenshotArea" method, but it requires
to get coordinates. While this could be done in X11, in Wayland, this can only
be done through an API.

Here is for instance GNOME API for screenshots:
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml
As you can see it provides a "SelectArea" method which allows to select a
rectangular area interactively and returns coordinates and width/length.

Could KDE implement something similar?

It looks like you could also make good usage of it. In Spectacle code, I see
that grabRectangularRegion() shows an "// unsupported", so I assume it doesn't
work in your own screenshot application (untested, just assumption! :P):
https://cgit.kde.org/spectacle.git/tree/src/PlatformBackends/KWinWaylandImageGrabber.cpp

Anyway thanks!

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

[choqok] [Bug 387446] Build fails with Qt 5.10

[Andrea Scarpino]

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

--- Comment #1 from Andrea Scarpino  ---
Git commit 1a4b87f8d200690b90666536ace0b70a28701b89 by Andrea Scarpino.
Committed on 08/12/2017 at 23:21.
Pushed by scarpino into branch 'master'.

Fix build with Qt 5.10

M  +16   -2helperlibs/twitterapihelper/twitterapioauth.cpp
M  +14   -2microblogs/pumpio/pumpiooauth.cpp

https://commits.kde.org/choqok/1a4b87f8d200690b90666536ace0b70a28701b89

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

[Craft] [Bug 386787] compiling cantor via craft fails

[Uwe Stöhr]

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

--- Comment #9 from Uwe Stöhr  ---
Many thanks!

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

[plasmashell] [Bug 387704] After return from hibernate have some visual deformations on text of desktop icons.

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
Excellent, must appreciated. I'm not too knowledgeable about graphics-related
issues myself, but I'm sure someone else with more expertise in that department
will take note of this bug report eventually.

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

[kmail2] [Bug 379997] Always "Akonadi not started" overlay on reboot

[David Faure]

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

--- Comment #1 from David Faure  ---
Pending fix: https://phabricator.kde.org/D9264

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

[kdevelop] [Bug 384711] Window grows larger and larger after every debugging session

[bugzilla_noreply]

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

tuxtor...@openmailbox.org changed:

   What|Removed |Added

 CC||tuxtor...@openmailbox.org

--- Comment #1 from tuxtor...@openmailbox.org ---
This width limit increase happens to me too.

DE : KDE
KDevelop version : 5.2.1

(I am using the «Display window geometry when moving or resizing» feature to
report the scale limits)

It looks like the values are quite random, since after some testing, I got
different values. It looks like Debug still has a bigger impact than Execute.
And Execute does not have to be clicked for Debug to make changes. (I just did
a test with Debug only : two first times, looking ok, third time, width=1719)


State 1 : Resize working well

I open the application and code.
Width limit : 1159

State 2 : Minimum width limit growing a bit

I click on «execute current launch».
Width limit : 1320
At this stage, when using an older 4/3 ratio screen (resolution: 1280×1024)
maximizing the window cuts part of it out of the screen.

State 3 : Minimum width limit growing even more

I click on «Debug current launch».
Width limit : 1421
Now, both sides are hidden. On a 1366×768 screen, the window starts to be cut
too.

State 4 : Minimum width limit increasing more or less arbitrarily

I feel like clicking on those buttons some times does increase (never decrease)
the width limit, but not always.


The panels & co. are always in the same state when testing.

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

[kmail2] [Bug 379997] Always "Akonadi not started" overlay on reboot

[David Faure]

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
   Assignee|kdepim-b...@kde.org |fa...@kde.org

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

[plasmashell] [Bug 387704] After return from hibernate have some visual deformations on text of desktop icons.

[bugzilla_noreply]

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

--- Comment #4 from arisel...@gmail.com ---
I regularly update drivers and if anything change i will report it.
And, you can ask me to help with additional informations and what I need to do.

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

[plasmashell] [Bug 387704] After return from hibernate have some visual deformations on text of desktop icons.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Assignee|se...@kde.org   |k...@davidedmundson.co.uk
  Component|Desktop Containment |general

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

[plasmashell] [Bug 387704] After return from hibernate have some visual deformations on text of desktop icons.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #3 from Nate Graham  ---
That's what I expected. This is likely an issue with the NVIDIA driver. I'll
leave this open here in case this is a known issue or there's something we can
do above the driver layer.

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

[Discover] [Bug 387718] Add Flathub by default

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
FWIW, the Linux Mint folks did this recently with their equivalent software:
https://www.linuxmint.com/rel_sylvia_cinnamon_whatsnew.php

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

[plasmashell] [Bug 387704] After return from hibernate have some visual deformations on text of desktop icons.

[bugzilla_noreply]

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

--- Comment #2 from arisel...@gmail.com ---
(In reply to Nate Graham from comment #1)
> What's your graphics hardware and driver?


Nvidia 1050ti 
nvidia 387.34

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

[kwin] [Bug 387720] New: GDBus.Error:org.kde.kwin.ColorPicker.Error.Cancelled: Color picking got cancelled

[Jehan]

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

Bug ID: 387720
   Summary: GDBus.Error:org.kde.kwin.ColorPicker.Error.Cancelled:
Color picking got cancelled
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: je...@zemarmot.net
  Target Milestone: ---

Created attachment 109264
  --> https://bugs.kde.org/attachment.cgi?id=109264=edit
Error happens with running the dbus API through d-feet as well.

Default @kde-desktop on Fedora 27, version 5.10.5 (not available in your list).
kwin-5.10.5-2.fc27.x86_64
plasma-desktop-5.10.5-1.fc27.x86_64

I am implementing color-picking on KDE for GIMP, with your API so that it works
also on KDE/Wayland.
Unfortunately calling the new "pick" method
(https://phabricator.kde.org/D3480), I constantly get the following error:

> GDBus.Error:org.kde.kwin.ColorPicker.Error.Cancelled: Color picking got 
> cancelled

I would assume there is a bug in code too, but since that's a very simple dbus
call with no arguments, I don't see where I could make a mistake. Also the
error happens if I run the call with the d-feet application as well (see
screenshot).

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

[Discover] [Bug 387719] Default priority for app visibility: 1: Flatpaks from Flathub 2: Snaps 3: Distro packages

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Default priority for|Default priority for app
   |package visibility: 1:  |visibility: 1: Flatpaks
   |Flatpaks from Flathub   2:  |from Flathub   2: Snaps
   |Snaps   3: Distro packages  |3: Distro packages

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

[Discover] [Bug 387719] Default priority for package visibility: 1: Flatpaks from Flathub 2: Snaps 3: Distro packages

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Note: I didn't consider AppImage here because you don't need software like
Discover to find, download, and install AppImages, and so AppImages are not
listed in Discover. But if at some point it would make sense to add AppImage
support (maybe pulling from https://appimage.github.io/apps/?) we could
consider adding a priority for AppImages, too.

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

[plasmashell] [Bug 387666] Plasma crashes sometimes when changing desktop layout from 'Folder View' to 'Desktop' and back

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[Discover] [Bug 387718] Add Flathub by default

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[Discover] [Bug 387719] Default priority for package visibility: 1: Flatpaks from Flathub 2: Snaps 3: Distro packages

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[yakuake] [Bug 386350] Focus jumps between splits on open/close

[bugzilla_noreply]

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

fen...@tutanota.com changed:

   What|Removed |Added

 CC||fen...@tutanota.com

--- Comment #4 from fen...@tutanota.com ---
I tried to debug this issue, and it only occurs when compositor animations are
enabled. Focus upon showing window is switched to subsequent terminal, i.e. if
active terminal was second and three terminal exists, then it third one will
have a focus. If focus belong to the last terminal, then it returns to first
one.

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

[ktorrent] [Bug 387368] Ktorrent freezes after starting

[tomas nackaerts]

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

tomas nackaerts  changed:

   What|Removed |Added

 CC||tomas.nackae...@gmail.com

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

[plasmashell] [Bug 368469] Configuration for second monitor gets lost

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #2 from Alexander Mentyu  ---
This issue could be transferred to the 'Desktop Containment' component

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

[kdenlive] [Bug 386932] Audio playback is different pitch & not smooth.

[Jesse]

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

--- Comment #11 from Jesse  ---
UPDATE #5: Closing Kdenlive, re-opening, and re-importing the audio file ends
up producing the same playback issue (even after Audio drive was changed from
automatic to OSS).

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

[kdenlive] [Bug 385914] Breeze style not present in Settings > Styles

[Jesse]

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

--- Comment #2 from Jesse  ---
UPDATE #1: Just tested the latest Kdenlive 17.12 RC Appimage (via
https://files.kde.org/kdenlive/release/kdenlive-17.12.0-x86_64.AppImage.mirrorlist),
and Breeze now shows in styles.

However, I guess it doesn't resolve the greater issue that was the reason this
bug was created: the Kdenlive Appimage doesn't have the default look of
Kdenlive when it's first opened. It opens with the "Fusion" style by default, I
believe. The expected look of Kdenlive should have it opening up with the
Breeze style, IMO.

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

[kdenlive] [Bug 386932] Audio playback is different pitch & not smooth.

[Jesse]

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

--- Comment #10 from Jesse  ---
UPDATE #4: Testing the upcoming 17.12 Appimage (via
https://files.kde.org/kdenlive/release/kdenlive-17.12.0-x86_64.AppImage.mirrorlist).
Upon opening the program, importing the audio file in the original post, and
played back in Clip Monitor. Same issue. I switched the Audio driver from
"Automatic" to "OSS", and tried playing the audio file again. The issue was
resolved.

So, there is still an issue where the expected behavior isn't working
out-of-the-box on 17.12 and Ubuntu 17.10 (gnome desktop). I don't think it's
advisable to expect the user to change the audio device setting after opening
Kdenlive every time, yeah?

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

[krita] [Bug 387708] Folder's Layer Style is not saved tp PSD.

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/b34869aca4b645529949c83b |ta/69f35b85e03fb8fa3da34dd6
   |485d393931ee612f|dc0305f397f5f499

--- Comment #11 from Dmitry Kazakov  ---
Git commit 69f35b85e03fb8fa3da34dd6dc0305f397f5f499 by Dmitry Kazakov.
Committed on 08/12/2017 at 19:24.
Pushed by dkazakov into branch 'master'.

PSD: Implement loading and saving of layer styles for group layers

Photoshop seem to use a special tag for layer styles when used in
the group layers.

M  +6-3plugins/impex/psd/psd_additional_layer_info_block.cpp
M  +1-1plugins/impex/psd/psd_additional_layer_info_block.h
M  +3-2plugins/impex/psd/psd_layer_record.cpp
M  +1-1plugins/impex/psd/psd_layer_record.h
M  +2-1plugins/impex/psd/psd_layer_section.cpp
M  +6-0plugins/impex/psd/psd_loader.cpp

https://commits.kde.org/krita/69f35b85e03fb8fa3da34dd6dc0305f397f5f499

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

[skrooge] [Bug 387682] Confirm Changes Request When Closing App EVERY TIME

[Stephane MANKOWSKI]

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

--- Comment #7 from Stephane MANKOWSKI  ---
In the screen capture, I can see that the file is well "modified" and the
reason is that you clicked on an operation check box to change its status.

Did you do that?

If not there is something strange and then, could you do that from a console?
export SKGTRACE=10
skrooge > traces.txt
play the scenario with the popup panel
close skrooge
send me by email the file traces.txt generated

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

[krita] [Bug 387708] Folder's Layer Style is not saved tp PSD.

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kri
   ||ta/b34869aca4b645529949c83b
   ||485d393931ee612f
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #10 from Dmitry Kazakov  ---
Git commit b34869aca4b645529949c83b485d393931ee612f by Dmitry Kazakov.
Committed on 08/12/2017 at 19:22.
Pushed by dkazakov into branch 'kazakov/lazy-brush-remastered'.

PSD: Implement loading and saving of layer styles for group layers

Photoshop seem to use a special tag for layer styles when used in
the group layers.

M  +6-3plugins/impex/psd/psd_additional_layer_info_block.cpp
M  +1-1plugins/impex/psd/psd_additional_layer_info_block.h
M  +3-2plugins/impex/psd/psd_layer_record.cpp
M  +1-1plugins/impex/psd/psd_layer_record.h
M  +2-1plugins/impex/psd/psd_layer_section.cpp
M  +6-0plugins/impex/psd/psd_loader.cpp

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

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

[krita] [Bug 387708] Folder's Layer Style is not saved tp PSD.

[Dmitry Kazakov]

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

--- Comment #9 from Dmitry Kazakov  ---
Created attachment 109263
  --> https://bugs.kde.org/attachment.cgi?id=109263=edit
PSD file saved in Krita

Here is the patch that implements saving and loading of lfxs section for group
layers:

https://phabricator.kde.org/P143

Please check if the attached file loads fine in PS. And if so, I will push it
into master.

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

[Discover] [Bug 387719] Default priority for package visibility: 1: Flatpaks from Flathub 2: Snaps 3: Distro packages

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Default priority for|Default priority for
   |package visibility: 1.  |package visibility: 1:
   |Flathub 2. Snapcraft 3. |Flatpaks from Flathub   2:
   |Distro packages |Snaps   3: Distro packages

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

[Discover] [Bug 387719] Default priority for package visibility: 1. Flathub 2. Snapcraft 3. Distro packages

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

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

[Discover] [Bug 387718] Add Flathub by default

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

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

[kate] [Bug 387705] Highlight PKGBUILD files as bash files

[Nate Graham]

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

--- Comment #6 from Nate Graham  ---
Excellent news!

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

[Discover] [Bug 387718] New: Add Flathub by default

[Nate Graham]

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

Bug ID: 387718
   Summary: Add Flathub by default
   Product: Discover
   Version: 5.11.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Flatpak Backend
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
CC: jgrul...@redhat.com
  Target Milestone: ---

It looks like we already have easy support for adding Flathub as a source, but
it's not already added by default. We should add Flathub by default so that
Flatpak apps appear in Discover without the user having to do anything (unless
my not seeing it is a distro packaging issue due to using an Ubuntu-based
distro, in which case oops, sorry).

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

[Discover] [Bug 387719] New: Default priority for package visibility: 1. Flathub 2. Snapcraft 3. Distro packages

[Nate Graham]

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

Bug ID: 387719
   Summary: Default priority for package visibility: 1. Flathub 2.
Snapcraft 3. Distro packages
   Product: Discover
   Version: 5.11.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

The typical Discover user is somebody who's not going to understand or think
they should have to understand distro package release schedules to know when
they get a new version of the apps they use. They instead say, "Hey, I heard
about a new version of LibreOffice/Blender/GIMP/Endless Sky/whatever; why does
Discover only show me this old version that was released a year ago?"

Flatpak, Snap, and AppImage solve this problem by decoupling app release
schedules from distro package lifecycle--but only if users are using the
Flatpak/Snap/AppImage versions of the apps!

To facilitate this, I suggest that we implement a priority system for
determining which version of an app is displayed by default in Discover when a
user browses or searches for packages. Other versions should be available but
hidden by default, and the default ordering of which version is presented by
default should be user-changeable in Discover's settings. Here's my suggestion
for the default ordering:

1. Flatpacks from Flathub (see also
https://bugs.kde.org/show_bug.cgi?id=387718)
2. Snaps
3. Distro packages

Reasons:
1. Flatpak is the most distro-agnostic approach and so far has the most
complete solution and distribution channel
2. Snap is also good, but less distro-neutral so far and not as popular or
well-developed
3. Finally, fall back to the distro package repo if the package isn't available
in either of the two above options
(obviously Ubuntu-based distros will probably reverse 1 and 2, and that's fine)


The net effect of this will be that over time, more and more of a user's
Discover-installed software will be the Flatpak or Snap versions, allowing them
to get new versions on app vendors' schedules, which is what most users want.
For the advanced users who happen to want to use Discover, they can always
change the priority and use distro packages instead, if they want.

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

[kate] [Bug 387705] Highlight PKGBUILD files as bash files

[Dominik Haumann]

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

--- Comment #5 from Dominik Haumann  ---
I am in favor of PKGBUILD*. Will change this this weekend. I believe this is
still ok and the risk of false positives is pretty low.

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

[skrooge] [Bug 387682] Confirm Changes Request When Closing App EVERY TIME

[Tim Johnson]

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

--- Comment #6 from Tim Johnson  ---
Created attachment 109262
  --> https://bugs.kde.org/attachment.cgi?id=109262=edit
Screenshot after instructions

I'm not sure what you meant by "capture the save button"

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

[digikam] [Bug 385438] Search images with 2 tags should give images with the 2 tags, not all images with one of the two tags

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.8.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Maik Qualmann  ---
Thanks for the feedback.

Maik

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

[krita] [Bug 387688] Filters don't work on duplicate layers that are mirrored

[G R]

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

--- Comment #3 from G R  ---
(In reply to Boudewijn Rempt from comment #2)
> Hm, that works here...

Did you give the layer a key on the animation timeline? These are my updated
steps:

1. Give a layer a key on the timeline
2. Duplicate the layer
3. Apply "layer>transform>mirror layer horizontally" to the duplicated layer
4. Try to apply any filter on it (blur or HSV adjustment for example), the
filter won't have any effect.

note: The same is also true for "mirror layer vertically" but the filter will
actually work on the top half of the layer for some reason.

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

[konsole] [Bug 387709] Konsole shouldn't turn "\e[1m" into intensive color format.

[Egmont Koblinger]

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

--- Comment #5 from Egmont Koblinger  ---
> Patch for adding a checkbox for whether to auto-brighten the bold characters.

Do you feel like doing this for gnome-terminal too? (Just kidding :-))

> BTW, am I at the right place for contacting the konsole developer team?

Yup, you are.

(I'm also wondering how much it's okay for me to chime in, especially before
any konsole developer says anything.)

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

[korganizer] [Bug 387717] New: korganizer crashes on exit.

[PC LX]

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

Bug ID: 387717
   Summary: korganizer crashes on exit.
   Product: korganizer
   Version: 5.4.3
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: k...@pmc.com.pt
  Target Milestone: ---

Application: korganizer (5.4.3)

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

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

korganizer crashes on exit. The crash always happens when korganizer is
exiting.
I have a local calendar folder setup and no remote calendar.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9eeed75880 (LWP 27630))]

Thread 5 (Thread 0x7f9edd8a7700 (LWP 27638)):
#0  0x7f9f1b1e900d in poll () at /lib64/libc.so.6
#1  0x7f9f12a28c94 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9f12a28d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9f1bd08e2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9f1bcb449a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9f1baee3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9f1baf2ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f9f189f466d in start_thread () at /lib64/libpthread.so.0
#8  0x7f9f1b1f4e4d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f9ede0dc700 (LWP 27636)):
#0  0x7f9f1b1e492d in read () at /lib64/libc.so.6
#1  0x7f9f12a6c690 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f9f12a2879e in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f9f12a28c38 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f9f12a28d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f9f1bd08e2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f9f1bcb449a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f9f1baee3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f9f1baf2ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f9f189f466d in start_thread () at /lib64/libpthread.so.0
#10 0x7f9f1b1f4e4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9edf2fd700 (LWP 27635)):
#0  0x7f9f12a6d974 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f9f12a28c89 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9f12a28d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9f1bd08e2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9f1bcb449a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9f1baee3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9f1f2a8635 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f9f1baf2ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f9f189f466d in start_thread () at /lib64/libpthread.so.0
#9  0x7f9f1b1f4e4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f9ee4b5d700 (LWP 27634)):
#0  0x7f9f1b1e900d in poll () at /lib64/libc.so.6
#1  0x7f9f10c86902 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f9f10c88657 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f9ee6a47be9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f9f1baf2ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f9f189f466d in start_thread () at /lib64/libpthread.so.0
#6  0x7f9f1b1f4e4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9eeed75880 (LWP 27630)):
[KCrash Handler]
#6  0x7f9f1c9124eb in QAbstractSlider::setValue(int) () at
/lib64/libQt5Widgets.so.5
#7  0x7f9f15dc0de9 in KViewStateSerializer::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.28] () at
/lib64/libKF5WidgetsAddons.so.5
#8  0x7f9f1bce23aa in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#9  0x7f9f1c817d0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#10 0x7f9f1c81ce76 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#11 0x7f9f1bcb6628 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#12 0x7f9f1bcb844b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#13 0x7f9f1bd089f3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5

[konsole] [Bug 387709] Konsole shouldn't turn "\e[1m" into intensive color format.

[bugzilla_noreply]

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

--- Comment #4 from cat.hook31...@gmail.com ---
Created attachment 109261
  --> https://bugs.kde.org/attachment.cgi?id=109261=edit
Patch for adding a checkbox for whether to auto-brighten the bold characters.

Thank for your detailed explanation! I also implemented a patch based on your
proposal: have a checkbox whether to auto-brighten or not in the schema editor.

BTW, am I at the right place for contacting the konsole developer team?

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

[valgrind] [Bug 383010] Add support for AVX-512 instructions

[Julian Seward]

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

--- Comment #11 from Julian Seward  ---
Sorry for the delay.  I will review in the coming week (11-15 Dec).

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

[kstars] [Bug 387716] New: KStars crashes with non-powered CCD camera in INDI

[Csaba Kertész]

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

Bug ID: 387716
   Summary: KStars crashes with non-powered CCD camera in INDI
   Product: kstars
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: csaba.kert...@gmail.com
  Target Milestone: ---

The problem is related to a secondary CCD camera driver in INDI when it is not
connected.

Steps to reproduce:

1. Run KStars.
2. Run a local INDI server with Ekos: EQMod (simulation mode), GPhoto
(simulation mode) and QHY or ZWO (no camera connected) Aux 1 driver.
3. Load a session in the Ekos Scheduler.
4. Execute the Scheduler session.

Outcome:
KStars shows a wrong dialog "an other INDI server is running. Stop it? Yes or
No".
If the answer is Yes then KStars crashes, if No then duplicate EQMod and GPhoto
tabs appear in the INDI window and the Ekos Scheduler fails to execute the
session.

The problem is not specific to the INDI drivers, the simulation mode or
remote/local INDI server. It is reproducible always. It is maybe related to the
fact that a non-powered QHY or ZWO camera driver does not appear at all in the
INDI window? Then KStars thinks that the INDI client session in KStars and the
INDI server are not the same.

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

[valgrind] [Bug 385408] s390x: z13 vector "support" instructions not implemented

[Julian Seward]

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

--- Comment #24 from Julian Seward  ---
Sorry for the delay.  I will review it in Monday.

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

[valgrind] [Bug 385408] s390x: z13 vector "support" instructions not implemented

[Julian Seward]

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

--- Comment #25 from Julian Seward  ---
*on* Monday, that is.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Sebastian Wessalowski]

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

--- Comment #273 from Sebastian Wessalowski  ---
I can confirm that this Bug reappeared. Probably with the Upgrade to Plasma
5.11.
I am on Gentoo with a fresh profile on the latest versions of frameworks,
plasma and Qt.
Very disappointing to see this happening again.
It seems to depend on the configuration.

It happens on my main notebook with a panel on the second screen. The main
panel disappears and the secondary panel appears on the main screen on
disconnecting the external screens.
It doesnt appear on my X200 without a secondary panel

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

[skrooge] [Bug 387682] Confirm Changes Request When Closing App EVERY TIME

[Stephane MANKOWSKI]

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

--- Comment #5 from Stephane MANKOWSKI  ---
Are you sure that after this screen capture Skrooge displayed "document has
been modified" ?

The document is not modified.

Could you do that ?
-Open skrooge
-Close skrooge
-When you have the message "document has been modified", cancel the closure
-Capture the history and the save button

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

[valgrind] [Bug 385408] s390x: z13 vector "support" instructions not implemented

[Vadim Barkov]

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

--- Comment #23 from Vadim Barkov  ---
(In reply to Andreas Arnez from comment #12)
> (In reply to Vadim Barkov from comment #10)
> > Created attachment 108579 [details]
> > Initial vector support (chapter 21) (remastered)
> > 
> > Changes:
> >  - Removed ALL trailing whitespaces changes (patch size decreased in five
> > times)
> >  - Removed some __inline__ 's from guest_s390_toIR.c
> >  - Rearranged code in sequence of commits (patches) to make the review
> > process easier
> 
> Yeah, that looks much better.  Good work!  A few comments:
> * In /none/tests/s390x/vector.c, you use z13 instructions in __asm__
> directives.  This is probably OK if you make sure that this test is executed
> only on systems that support this.  See, for instance how this is done for
> AVX using the build-time variable BUILD_AVX_TESTS defined in configure.ac.
> * When running auxprogs/s390-check-opcodes.pl with the appropriate
> parameters, I get some warnings.  It would be nice if you could get rid of
> them.

Is the current patch okay? Could you merge it or tell me what's wrong with it
please?

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

[plasmashell] [Bug 358827] Switching between Alternatives on Desktop loses / breaks applet geometry

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #2 from Alexander Mentyu  ---
Can confirm that 'Application Laucher/Dashboard' desktop widget changes it's
size after switching to 'Application Menu' alternative

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic

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

[Heaptrack] [Bug 386256] Loading files using multiple threads to readuce load times

[Edward Kigwana]

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

Edward Kigwana  changed:

   What|Removed |Added

Summary|Loading files using |Loading files using
   |multiple threads to read|multiple threads to readuce
   |load times  |load times

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

[digikam] [Bug 385438] Search images with 2 tags should give images with the 2 tags, not all images with one of the two tags

[bugzilla_noreply]

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

--- Comment #3 from philippe.quag...@laposte.net ---
Hello, tried it again today, and works fine. Maybe did I made a wrong
manipulation, sorry. I think this may be closed.

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

[plasmashell] [Bug 363289] plasma and kactivitymonitord crash when a fourth VM is started in virt-manager

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
Can't reproduce in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic

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

[konsole] [Bug 387709] Konsole shouldn't turn "\e[1m" into intensive color format.

[Egmont Koblinger]

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

--- Comment #3 from Egmont Koblinger  ---
> Then what's your opinion about having a option for whether to use bold font 
> or not.

I have vaguely proposed removing it from gnome-terminal at
https://bugzilla.gnome.org/show_bug.cgi?id=762247#c1 (I wanted to link this
bugreport previously, I mistakenly linked a duplicate of this), but I don't
have a firm opinion about it.

I tend to believe that users should configure their apps not to ask to output
bold text in that case.

Many terminal emulators traditionally have an option to disable bold, and/or an
option for a "bold color" which is being used when the default foreground color
is made bold. The latter one only makes sense in spirit of the legacy "bold is
bright" model; if for the standard 8 palette colors one should be able to
specify their bold ahemm bright counterpart, they should probably be able to
specify one for the default foreground color too (which is not necessarily the
white or black one of the palette).

As for entirely disabling bold: The 256-color (let alone truecolor) extension
started to clarify that for the ambiguous "\e[1m" the correct meaning should be
bold and not bright, since the color has a dedicated escape sequence of its
own. (And while at it, "\e[2m" aka faint/dim is also a truly stupid one. A
thinner font stroke could make sense instead, although it's not a standard
typesetting practice, and its usefulness is highly questionable.)

> Maybe some users just don't like the bold fonts and want to use normal font 
> weight
> for all cases.

If we're talking about users simply not liking it, then what about users who
don't like italic, users who don't like underlined text, users who don't like
certain colors (or combinations thereof) etc.?? Some terminal emulators provide
some options for these, e.g. some can enforce a minimum contrast between the
foreground and background color of each cell (by disobeying even explilcit RGB
foreground colors if it's too close to the background), and I guess every
emulator that supports blinking allows to disable it. And what about users
using this font in other apps too where they just as much don't like its bold
counterpart?? Maybe they should configure their system globally not to use it
(e.g. for GNOME this can probably be done at fontconfig level; not sure about
KDE). Pushing even further, I'm wondering: why would someone get rid of this
useful way of emphasizing text, rather than picking a different font whose bold
variant they also like??

That being said, if a terminal emulator lets you disable bold (or maybe choose
a different font for bold), so be it. But then at the very least it should
probably offer this for italic too. I just personally don't see too much point
in these options and I'm not convinced the terminal emulator is the right place
for such hacks.

Anyway, your original request and my response to that was more of a technical
one, this one is more opinion-based, so Konsole developers' opinion should
matter more, not mine. :-)

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

[plasmashell] [Bug 363656] Desktop Settings -> Mouse Actions -> Window Switcher only works when VD>1

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
может быть только одинфCan confirm this in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic

What could be the solution? - there can be only one desktop in the menu?

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

[systemsettings] [Bug 387307] System Settings crash

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kxm
   ||lgui/037a4ffa467d8ff720e3fa
   ||6e20adfe739e88d21f
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from David Edmundson  ---
Git commit 037a4ffa467d8ff720e3fa6e20adfe739e88d21f by David Edmundson.
Committed on 08/12/2017 at 15:46.
Pushed by davidedmundson into branch 'master'.

Disconnect shortcutedit slot on widget destruction

Summary:
If the widget is destroyed the connect still exists with a dangling
capture.

Test Plan: Compiles.

Reviewers: #plasma

Subscribers: plasma-devel, #frameworks

Tags: #plasma, #frameworks

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

M  +1-1src/kshortcuteditwidget.cpp

https://commits.kde.org/kxmlgui/037a4ffa467d8ff720e3fa6e20adfe739e88d21f

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

[plasmashell] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #5 from Alexander Mentyu  ---
KWin isn't crashing when moving systray widget - but it displays part Desktop
part Systray settings window on right/handle click - and there is a text in
'Wallpaper' section of the settings window - 'Layout changes must be applied
before other changes can be made' just like after layout change

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic

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

[plasmashell] [Bug 365286] 90 degree screen rotation causes plasmoids to move, don't move back if screen returns to original orientation

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
Can confirm - if widgets were stored on the most right position before the
rotate - they do not return to the most right position after the rotate and
stay somewhere in the middle presumably depending on your monitor screen aspect
ratio

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic

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

[kate] [Bug 387705] Highlight PKGBUILD files as bash files

[Ashark]

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

--- Comment #4 from Ashark  ---
I understand that. The problems could be if somebody calls their file like
"PKGBUILD instructions.txt".
Maybe better instead of "PKGBUILD*" rule make "PKGBUILD-*". It should reduce
unwanted behavior cases.
By the way, I have found that archlinux maintainers applied patch for pkgbuild
highliting
https://git.archlinux.org/svntogit/packages.git/tree/trunk/pkgbuild-syntax-highlight.patch?h=packages/syntax-highlighting.

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

[plasmashell] [Bug 363855] Widgets positioning on desktop containment gets rearranged when loging in or changing activities

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #3 from Alexander Mentyu  ---
Can't reproduce in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic
Type: 64-bit

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

[krita] [Bug 387708] Folder's Layer Style is not saved tp PSD.

[Boudewijn Rempt]

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

--- Comment #8 from Boudewijn Rempt  ---
Created attachment 109260
  --> https://bugs.kde.org/attachment.cgi?id=109260=edit
cs2 erroring out

Just for reference, here's the error cs2 gives when loading that file.

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

[plasma-nm] [Bug 387715] [Feature Request] OpenVPN with lz4 as compression algorithm

[Stefan Schmid]

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

Stefan Schmid  changed:

   What|Removed |Added

URL||https://community.openvpn.n
   ||et/openvpn/wiki/Openvpn24Ma
   ||nPage

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

[plasma-nm] [Bug 387715] New: [Feature Request] OpenVPN with lz4 as compression algorithm

[Stefan Schmid]

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

Bug ID: 387715
   Summary: [Feature Request] OpenVPN with lz4 as compression
algorithm
   Product: plasma-nm
   Version: master
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: schmidi...@gmail.com
  Target Milestone: ---

With OpenVPN 2.4 comes support for lz4 as compression algorithm and some
Servers need this on Client side to establish a connection.

See "--compress [algorithm]" in OpenVPN-Wiki:
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage

Please modify the Option-Dialog to make it possible to use it.

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

[plasmashell] [Bug 365926] Desktop Icons (non folder view) can't be properly resized

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
Currently icons are resizing a little bit after releasing of mouse button - but
that's because of the desktop grid

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic
Type: 64-bit

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

[plasmashell] [Bug 365950] Neon 5.7.2 - Desktop icons stay highlighted

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #3 from Alexander Mentyu  ---
I don't think this is a bug

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

[systemsettings] [Bug 387584] Desktop Theme KCM crashes System Settings

[David Edmundson]

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

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

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

[systemsettings] [Bug 387569] Configurações do Sistema

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk
 Resolution|--- |DUPLICATE

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 381317] Crash when closing window (XWindowTasksModel::Private::removeWindow, :TaskGroupingProxyModel::Private::sourceRowsAboutToBeRemoved)

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||andrew.findlay@skills-1st.c
   ||o.uk

--- Comment #44 from David Edmundson  ---
*** Bug 387676 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 387676] Plasma crash on switching virtual desktop

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 337711] Dragging a Firefox tab to the desktop (so it creates a new firefox window for it) doesn't work.

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #7 from Alexander Mentyu  ---
Can confirm - the issue is reproducible in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic
Type: 64-bit

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

[plasmashell] [Bug 387666] Plasma crashes sometimes when changing desktop layout from 'Folder View' to 'Desktop' and back

[David Edmundson]

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

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

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

[plasmashell] [Bug 387668] Plasma randomly crashed when i was browsing bugs here

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
If you see it ends with 

QV4::MemoryManager::mark

just before 
[KCrash Handler]

it's all the same

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

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

[krita] [Bug 387708] Folder's Layer Style is not saved tp PSD.

[Dmitry Kazakov]

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

--- Comment #7 from Dmitry Kazakov  ---
Created attachment 109259
  --> https://bugs.kde.org/attachment.cgi?id=109259=edit
Test SPD file rom Paul Geraskin

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

[konsole] [Bug 387709] Konsole shouldn't turn "\e[1m" into intensive color format.

[bugzilla_noreply]

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

--- Comment #2 from cat.hook31...@gmail.com ---
Then what's your opinion about having a option for whether to use bold font or
not.  Maybe some users just don't like the bold fonts and want to use normal
font weight for all cases.

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

[krita] [Bug 387708] Folder's Layer Style is not saved tp PSD.

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #6 from Dmitry Kazakov  ---
I have checked the test file, it seems like PS stores the layer styles for
Group Layers in a section with a special ID: 'lfxs'. The rest of the format is
exactly the same.

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

[kate] [Bug 386758] Large numbers of tabs become hard to access

[k3bBug]

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

--- Comment #7 from k3bBug  ---
A Multi-Row tab bar would be sweet. Please consider it.
The other options are not as user friendly.
Note there is an addon for firefox that provides multi-row tab bar and another
that provides multi-row bookmarks -  both are quite popular. What does that say
about firefox's current method of handling multiple pages/bookmarks?

"The problem is that a large number of files is always hard to access with a
tabbar."
If its because the tabs shrink in width - then yes, I would agree, a multi-row
tab bar solves this problem. dropping filenames off the tab bar into a list (as
done currently) also doesn't help things.

The Ctrl-Alt-O + typing part of a filename thing is unwieldy compared to a
multi-row tab bar.

Until you have worked using a multi-row tab bar you just can not appreciate how
user friendly it is, its also a time saver. Consider what its like to work in
Kate with say 4 files open, the tabs work nicely right? I'm just asking to have
this extended a bit and to say that you will just hit this issue again as the
number of files goes up is a non-starter. There is a normal intuitive usage
pattern that does not extend indefinitely and most people know that at some
point you need to close some files but I'd hazard a guess and say that having
10-15 or so files open at once isn't unreasonable, but at some point no matter
how user friendly things are you are overwhelmed and its time to close some
stuff and I think that limit isn't too much above 25 or so. For sure no one in
their right mind wants to have 5-100 or more files open, its just not
manageable. 
I don't care if the multi-row-tab-bar has a 3 row limit and a max tab count of
say 16-20. That's completely reasonable and it helps people work. Squishing
tabs to the point they are unreadable means the tabs have lost there purpose
and does not help people work.

As for contributing patches, sure, if your a programmer. Not everyone is. I
have not looked at Kate code but the tab bar is already there, is it really a
lot of work to make it multi-row? Maybe it is, I'm asking not commenting.

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