[frameworks-kio] [Bug 391199] Display speed of transfer for file operations.

[Kai Uwe Broulik]

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

--- Comment #2 from Kai Uwe Broulik  ---
As for the graph, that has to be done in plasmashell's notification center (I'm
its maintainer and am actually a huge fan of this modern Windows copy dialog)
but we first need to figure out how to actually get that data to the
application in the first place.

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

[frameworks-kio] [Bug 391199] Display speed of transfer for file operations.

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

Product|dolphin |frameworks-kio
 CC||k...@privat.broulik.de,
   ||kdelibs-b...@kde.org
  Component|general |general
   Assignee|dolphin-bugs-n...@kde.org   |fa...@kde.org

--- Comment #1 from Kai Uwe Broulik  ---
The problem is in KIO which manages such jobs. Copy job creates a subjob for
every file it copies, however, they only report speed after 1 seconds at which
point the job has already finished and the next one started. This is why you
can see transfer rate for large files but not when copying many small ones.

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

[kwin] [Bug 391279] Wrong behavior with multi displays

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

Product|kde |kwin
 CC||k...@privat.broulik.de
   Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org
  Component|general |general

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

[kmail2] [Bug 391278] autotests/libksieve fails autotests on sieveeditor-autocreatescripts-selectheadertypecomboboxtest

[Rik Mills]

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

Rik Mills  changed:

   What|Removed |Added

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

--- Comment #2 from Rik Mills  ---
Fixed with:

https://cgit.kde.org/libksieve.git/commit/?id=01cd24a30822414e71335887ee958b88dc8706fc

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

[kde] [Bug 391279] Wrong behavior with multi displays

[Yura Shinkarev]

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

--- Comment #1 from Yura Shinkarev  ---
Add link to screnshot:
https://yshinkarev.ru/images/kde_bug_multi_display_2018.03.02_10-18-55-Screenshot.png

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

[kde] [Bug 391279] New: Wrong behavior with multi displays

[Yura Shinkarev]

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

Bug ID: 391279
   Summary: Wrong behavior with multi displays
   Product: kde
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bugs.kde@yshinkarev.ru
  Target Milestone: ---

Created attachment 28
  --> https://bugs.kde.org/attachment.cgi?id=28=edit
xrand, lshw, uname, plasmashell data

I have laptop Lenovo G710.
I Connect 2 fullhd external monitors by hdmi and vga.
Now I have strange behaviour on moving any window from one monitor (primary) to
second. From some X position window stop showing.
Second moment, I have empty space (vertical line) between taskbar and right
edge of primary moninor. So, you can see window content at this space.


Linux lenovog710 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
plasmashell 5.8.8
Important, I add http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu

Also I add link to
video:https://yshinkarev.ru/videos/kde_bug_multi_display_20180302_102128.mkv
(21MB)

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

[Spectacle] [Bug 391183] When using from the context menu in the launcher, the menu appears in the screenshot

[bugzilla_noreply]

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

--- Comment #5 from drokerg...@gmail.com ---
Created attachment 27
  --> https://bugs.kde.org/attachment.cgi?id=27=edit
showing my current desktop theme

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

[kmail2] [Bug 391278] autotests/libksieve fails autotests on sieveeditor-autocreatescripts-selectheadertypecomboboxtest

[Rik Mills]

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

--- Comment #1 from Rik Mills  ---
I note this is fixed in master branch.

https://cgit.kde.org/libksieve.git/commit/?id=9cf070c6a6dfbd2ebb47bf18d8e5446860c544da

Please apply to 17.12 branch for 17.12.3 release

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

[Spectacle] [Bug 391183] When using from the context menu in the launcher, the menu appears in the screenshot

[bugzilla_noreply]

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

--- Comment #4 from drokerg...@gmail.com ---
(In reply to Nate Graham from comment #3)
> Are you using a 3rd-party theme? It looks like your context menu fades out
> over a period of time that isn't long enough to fully disappear before
> Spectacle captures the screenshot. Does this reproduce for you when using
> Breeze?

Im only using arc dark as desktop theme, im uploading a new vid

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

[kmail2] [Bug 391278] New: autotests/libksieve fails autotests on sieveeditor-autocreatescripts-selectheadertypecomboboxtest

[Rik Mills]

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

Bug ID: 391278
   Summary: autotests/libksieve fails autotests on
sieveeditor-autocreatescripts-selectheadertypecombobox
test
   Product: kmail2
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sieve
  Assignee: kdepim-b...@kde.org
  Reporter: rikmi...@kubuntu.org
  Target Milestone: ---

Failure on KDE CI Since November 2017

sieveeditor-autocreatescripts-selectheadertypecomboboxtest

https://build.kde.org/job/Applications%20libksieve%20stable-kf5-qt5%20SUSEQt5.9/21/testReport/(root)/TestSuite/sieveeditor_autocreatescripts_selectheadertypecomboboxtest/

Also seen from apps 17.12 on ubuntu autotests

qt.qpa.screen: adding QXcbScreen(0x6111bfc0, name="screen",
geometry=1600x1200+0+0, availableGeometry=1600x1200+0+0, devicePixelRatio=1.0,
logicalDpi=QPair(100.1,99.9), physicalSize=406.0x305.0mm, screenNumber=0,
virtualSize=1600x1200 (1600.0x1200.0mm),
orientation=Qt::ScreenOrientation(LandscapeOrientation), depth=24,
refreshRate=0.0, root=32e, windowManagerName="Openbox") (Primary: true )
qt.qpa.screen: primary output is "screen"
qt.qpa.input.devices: XInput version 2.2 is available and Qt supports 2.2 or
greater
qt.qpa.input.devices: input device  Virtual core XTEST pointer ID 4
qt.qpa.input.devices:has 10 buttons
qt.qpa.input.devices:has valuator "Rel X" recognized? true
qt.qpa.input.devices:has valuator "Rel Y" recognized? true
qt.qpa.input.devices:it's a scrolling device
qt.qpa.input.devices: input device  Xvfb mouse ID 6
qt.qpa.input.devices:has 3 buttons
qt.qpa.input.devices:has valuator "Rel X" recognized? true
qt.qpa.input.devices:has valuator "Rel Y" recognized? true
qt.qpa.gl: Choosing xcb gl-integration based on following priority
 ("xcb_glx", "xcb_egl")
qt.qpa.gl: Xcb GLX gl-integration created
qt.qpa.gl: Xcb GLX gl-integration successfully initialized
* Start testing of SelectHeaderTypeComboBoxTest *
Config: Using QtTest library 5.9.4, Qt 5.9.4 (x86_64-little_endian-lp64 shared
(dynamic) release build; by GCC 7.3.0)
PASS   : SelectHeaderTypeComboBoxTest::initTestCase()
PASS   : SelectHeaderTypeComboBoxTest::shouldHaveDefaultValue()
PASS   : SelectHeaderTypeComboBoxTest::shouldSetCode(empty)
PASS   : SelectHeaderTypeComboBoxTest::shouldSetCode(empty only header)
FAIL!  : SelectHeaderTypeComboBoxTest::shouldSetCode(from) Compared values are
not the same
   Actual   (combox.currentIndex()): 7
   Expected (index): 8
   Loc: [/home/jenkins/workspace/Applications libksieve stable-kf5-qt5
SUSEQt5.9/src/ksieveui/autocreatescripts/autotests/selectheadertypecomboboxtest.cpp(98)]
PASS   : SelectHeaderTypeComboBoxTest::cleanupTestCase()
Totals: 5 passed, 1 failed, 0 skipped, 0 blacklisted, 182ms
* Finished testing of SelectHeaderTypeComboBoxTest *

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

[dolphin] [Bug 175495] filter bar - ability to place on top of window, below or aside the address bar

[Roman Inflianskas]

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

Roman Inflianskas  changed:

   What|Removed |Added

 CC||jospoortvl...@gmail.com

--- Comment #11 from Roman Inflianskas  ---
*** Bug 304684 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 304684] show the filter bar on the right of the location bar like web browsers do

[Roman Inflianskas]

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

Roman Inflianskas  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||infr...@gmail.com

--- Comment #12 from Roman Inflianskas  ---


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

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

[Touchpad-KCM] [Bug 389710] Setting to disable middle click paste

[bugzilla_noreply]

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

jeremy9...@gmail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from jeremy9...@gmail.com ---
Even elementary OS / Pantheon have it now

https://medium.com/elementaryos/juno-progress-for-january-february-9b276042716e

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

[i18n] [Bug 391266] Falsche Übersetzung in trojita

[Unknown]

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

Unknown  changed:

   What|Removed |Added

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

--- Comment #1 from Unknown  ---
SVN commit 1511597 by lueck:

update and fix for wrong translation reported by Wolfgang Bauer, thanks


 M  +47 -51trojita_common.po  


WebSVN link: http://websvn.kde.org/?view=rev=1511597

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

[dolphin] [Bug 391199] Display speed of transfer for file operations.

[Zakhar]

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

Zakhar  changed:

   What|Removed |Added

Version|5.12.2  |unspecified
Product|plasmashell |dolphin
   Target Milestone|1.0 |---
   Assignee|k...@privat.broulik.de   |dolphin-bugs-n...@kde.org
  Component|Notifications   |general

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

[krusader] [Bug 388321] Own scripts refuse to start via contex menu

[Nikita Melnichenko]

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

Nikita Melnichenko  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from Nikita Melnichenko  ---
I tried to repro using the reporter's script (only replacing xfce4-terminal
with konsole) - still it could be run on my side without issues.

>From comment #4, the reporter seems to be satisfied with adjusting the scripts.
I'm closing the issue and will track if someone reports the same.

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[David Mattatall]

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

--- Comment #28 from David Mattatall  ---
Hi Albert,

Provide instruction and I'd be happy to test

Cheers,
David A. Mattatall | 778-323-7857

On 03/01/2018 02:41 PM, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=388991
>
> --- Comment #27 from Albert Astals Cid  ---
> (In reply to Lukasz from comment #24)
>> It's happening to me as well:
> Lukasz can you reproduce this easily? Do you know how to run kdeconnect under
> valgrind? I'd help me quite a bit having the valgrind trace to understand
> what's going on.
>

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

[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop

[Marian Kyral]

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

Marian Kyral  changed:

   What|Removed |Added

 CC||mky...@email.cz

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

[okular] [Bug 350366] Tree view search bar in left side bar is not searching root items of the tree view.

[Dileep Sankhla]

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

Dileep Sankhla  changed:

   What|Removed |Added

 CC||sankhla.dilee...@gmail.com

--- Comment #1 from Dileep Sankhla  ---
It is not reproducible in okular version 1.3.2

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

[krusader] [Bug 389413] Krusader crashes when entering directories with read errors

[Nikita Melnichenko]

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

Nikita Melnichenko  changed:

   What|Removed |Added

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

--- Comment #15 from Nikita Melnichenko  ---
You are welcome! Thanks for testing. I'll do a bit of refactoring and push the
change for review then.

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

[krusader] [Bug 388420] Dotted line artifact when switching focused item

[Nikita Melnichenko]

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

--- Comment #9 from Nikita Melnichenko  ---
Thanks, I was able to change the Widget Style to QtCurve, however I could not
repro the issue in both light and dark themes.

I noticed you're using a different current item selection mode - it's filled
with gray. Mine is just the border decoration. Do you know what that setting
is? Can you attach your ~/.config/krusaderrc file?

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

[systemsettings] [Bug 391277] New: Application Global shortcuts broken

[Edward Kigwana]

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

Bug ID: 391277
   Summary: Application Global shortcuts broken
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_khotkeys
  Assignee: k...@michael-jansen.biz
  Reporter: edwardw...@gmail.com
  Target Milestone: ---

I have a logitech internet keyboard with a calculator launch button. If I add a
Global Shortcut to launch kcalc and assign a global key or alternate, nothing
happens when the keys are pressed.

Creating a "Custom Shortcut" and assigning a trigger and action works as
expected.

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

[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed

[Andrew Crouthamel]

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

--- Comment #12 from Andrew Crouthamel  ---
Looks like it works in my Dev Unstable VM, the display button passes through.
I'll test via USB stick tomorrow, but otherwise, this looks good!

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

[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)

[Martin Flöser]

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

--- Comment #19 from Martin Flöser  ---
(In reply to Nate Graham from comment #18)
> > My preferred option is still for KWin to start ignoring windows that have 
> > SkipPager set in Present Windows (because my argument remains that any 
> > summarized view of windows is conceptually a pager).
> 
> Makes sense to me. Do the KWin maintainers feel otherwise?

Yes

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

[choqok] [Bug 391276] New: Choqok does not look good in discover

[bugzilla_noreply]

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

Bug ID: 391276
   Summary: Choqok does not look good in discover
   Product: choqok
   Version: 1.6
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mehrdad.mom...@gmail.com
  Reporter: evo8...@gmail.com
CC: scarp...@kde.org
  Target Milestone: ---

Created attachment 25
  --> https://bugs.kde.org/attachment.cgi?id=25=edit
Screenshot of Choqok in Discover on Fedora 27

As seen in the attached screenshot, only the name and description of Choqok.
The application was installed using the built-in Fedora repository.

Fedora 27 x86_64
choqok.x86_64 version 1.6.0.3-fc27
plasma-discover.x86_64 version 5.11.5-1.fc27

Not sure where the issue lies, because the source code downloaded from the
Choqok website has a valid appstream.xml file.

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

[kwin] [Bug 391271] When loging out wayland session, do the windows get a proper close signal?

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
It's totally possible that the termination process is wrong.

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

[plasmashell] [Bug 391275] New: Kicker backend feature: combined "history/favorites/newly installed" view

[Nate Graham]

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

Bug ID: 391275
   Summary: Kicker backend feature: combined
"history/favorites/newly installed" view
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: n...@kde.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

I pitched this idea to Eike privately and got a positive reception, so I
figured I'd file a formal feature request.

For the upcoming Kicker backend rewrite project, I'd like to propose a dynamic
view that can show favorites, recently used apps and documents, and also
newly-installed apps.

It would be primarily a history/recently used view, with the additional feature
that Favorited items would always show up at the top of the list, perhaps with
a little pin or star badge in the corner.

In addition, every newly-installed app (or at least, those installed using
Discover) would also show up in this view, so users can easily find them (which
is a big discoverability problem right now). New Apps would likewise receive a
badge, or perhaps a different background color--something to distinguish them
as newly installed for the first few times they're launched

The idea here is to create a user-friendly view that can show your average user
everything they really need 99% of the time:
- Their favorite apps
- The apps and documents they've used recently
- Newly-installed apps

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

[kmymoney] [Bug 391251] Double free or corruption when creating a new asset account.

[Alexandre]

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

Alexandre  changed:

   What|Removed |Added

 CC||alexandre...@gmail.com

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

[ksysguard] [Bug 391176] System monitor stopped saving settings

[bugzilla_noreply]

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

--- Comment #5 from raph.sa...@gmail.com ---
Found out this is a QT 5.10.1 problem. Enabled kde-unstable repository in my
Arch pacman.conf:
[kde-unstable]
Include = /etc/pacman.d/mirrorlist

And updated my system with pacman -Syu. New QT libraries were pulled in
(5.11.0). Do not observe this problem anymore.

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

[Spectacle] [Bug 391183] When using from the context menu in the launcher, the menu appears in the screenshot

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Are you using a 3rd-party theme? It looks like your context menu fades out over
a period of time that isn't long enough to fully disappear before Spectacle
captures the screenshot. Does this reproduce for you when using Breeze?

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

[elisa] [Bug 391267] No music playback

[Michael D]

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

Michael D  changed:

   What|Removed |Added

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

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

[elisa] [Bug 391267] No music playback

[Michael D]

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

--- Comment #1 from Michael D  ---
I figured out the issue: some gstreamer codec must not have been installed,
though I'm not sure which. I installed a bunch that do not come installed by
default with tumbleweed (which causes several headaches). Playback works like a
charm now.

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

[gwenview] [Bug 390929] Audio volume slider is out of position

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
Would you be interested in submitting a patch, Kavinda? Our documentation for
this can be found at:
- https://community.kde.org/Get_Involved/development
- https://community.kde.org/Infrastructure/Phabricator

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

[gwenview] [Bug 390929] Audio volume slider is out of position

[Kavinda]

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

Kavinda  changed:

   What|Removed |Added

 CC||harindudilsha...@gmail.com

--- Comment #3 from Kavinda  ---
When you change the volume, boundingRect() of HudSlider seems to change for no
reason at all. Perhaps it's related to QGraphicsWidget.

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

[dolphin] [Bug 391274] New: Crash when unmounting volume from the Places view in dolphin

[Aleix Pol]

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

Bug ID: 391274
   Summary: Crash when unmounting volume from the Places view in
dolphin
   Product: dolphin
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: aleix...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (18.03.70)
 (Compiled from sources)
Qt Version: 5.10.1
Frameworks Version: 5.43.0
Operating System: Linux 4.15.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
As soon as I unmounted the volume it crashed. Didn't say good bye.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa19e5a7840 (LWP 32458))]

Thread 3 (Thread 0x7fa19082c700 (LWP 32460)):
#0  0x7fa1a9fa13d8 in read () from /usr/lib/libc.so.6
#1  0x7fa1a279e7d1 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fa1a2758ac8 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7fa1a2758f96 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7fa1a275910e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7fa1aae71feb in QEventDispatcherGlib::processEvents
(this=0x7fa18c000b20, flags=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#6  0x7fa1aae15a8a in QEventLoop::exec (this=this@entry=0x7fa19082bd60,
flags=..., flags@entry=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:212
#7  0x7fa1aac2b67a in QThread::exec (this=) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread.cpp:522
#8  0x7fa1aac3084f in QThreadPrivate::start (arg=0x560635f0b530) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:376
#9  0x7fa1a6b1008c in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fa1a9fafe7f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fa19c39f700 (LWP 32459)):
#0  0x7fa1a9fa597b in poll () from /usr/lib/libc.so.6
#1  0x7fa1a2758ff3 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fa1a275910e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fa1aae71feb in QEventDispatcherGlib::processEvents
(this=0x7fa194000b20, flags=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425
#4  0x7fa1aae15a8a in QEventLoop::exec (this=this@entry=0x7fa19c39ed30,
flags=..., flags@entry=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventloop.cpp:212
#5  0x7fa1aac2b67a in QThread::exec (this=this@entry=0x7fa1ac885da0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread.cpp:522
#6  0x7fa1ac8116d5 in QDBusConnectionManager::run (this=0x7fa1ac885da0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/apol/devel/frameworks/qt5/qtbase/src/dbus/qdbusconnection.cpp:178
#7  0x7fa1aac3084f in QThreadPrivate::start (arg=0x7fa1ac885da0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:376
#8  0x7fa1a6b1008c in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fa1a9fafe7f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fa19e5a7840 (LWP 32458)):
[KCrash Handler]
#6  0x7fa1a9eee860 in raise () from /usr/lib/libc.so.6
#7  0x7fa1a9eefec9 in abort () from /usr/lib/libc.so.6
#8  0x7fa1aac1b047 in qt_message_fatal (context=..., message=...) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:1716
#9  QMessageLogger::fatal (this=this@entry=0x7ffe4d1215d0,
msg=msg@entry=0x7fa1aaeda050 "ASSERT: \"%s\" in file %s, line %d") at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:822
#10 0x7fa1aac15dd6 in qt_assert (assertion=, file=, line=) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qglobal.cpp:3126
#11 0x7fa1b1bd33ef in PlacesPanel::slotStorageSetupDone
(this=0x560635b9f210, index=10, success=true) at
/home/apol/devel/frameworks/dolphin/src/panels/places/placespanel.cpp:449
#12 0x7fa1b1bd6938 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (PlacesPanel::*)(int, bool)>::call
(f=(void (PlacesPanel::*)(PlacesPanel * const, int, bool)) 0x7fa1b1bd3330
, o=0x560635b9f210,
arg=0x7ffe4d1218d0) at
/home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:136
#13 0x7fa1b1bd6883 in 

[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||subd...@gmail.com

--- Comment #18 from Nate Graham  ---
> My preferred option is still for KWin to start ignoring windows that have 
> SkipPager set in Present Windows (because my argument remains that any 
> summarized view of windows is conceptually a pager).

Makes sense to me. Do the KWin maintainers feel otherwise?

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

[plasma-pa] [Bug 391264] Resume output selection

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[Spectacle] [Bug 391179] System halt if I have applications that are running in full-screen mode

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 CC||rk...@lab12.net

--- Comment #1 from Henrik Fehlauer  ---
Thanks for the report.

Could you detail what you mean with "system halt"?

Perhaps it is just the window manager (KWin) crashing. Please try to observe
closely what happens to the title bars of windows once you triggered the
problem.

Also, do you have "Delay" set to "No Delay", and could you test with another
delay?

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Steven Haigh]

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

--- Comment #89 from Steven Haigh  ---
Well, me being a sucker for punishment - with a new laptop - I set up kmail on
a fresh install of Fedora 27.

Sync'ed my gmail account to it.

The very next day, hit by this problem.

>From the console:
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Unknown error."
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Unknown error."
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Unknown error."
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Unknown error."
org.kde.pim.akonadicore: Creating/updating items from the akonadi database
failed: "Multiple merge candidates, aborting"

So yeah - this is still an issue.

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

[Spectacle] [Bug 391118] Kwin crash when using Active Window screenshot method

[Andrew Crouthamel]

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

--- Comment #4 from Andrew Crouthamel  ---
Created attachment 24
  --> https://bugs.kde.org/attachment.cgi?id=24=edit
My test system

If I maximize that window and run the Active Window screenshot, Kwin will die.

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

[Spectacle] [Bug 391118] Kwin crash when using Active Window screenshot method

[Andrew Crouthamel]

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

--- Comment #3 from Andrew Crouthamel  ---
(In reply to Henrik Fehlauer from comment #1)
> Hmh, cannot reproduce in a VM.
Me either, I tried Neon Dev Unstable in VirtualBox.
> For Spectacle it's always interesting to know if you have KWin's compositing
> enabled or not (check in the settings or press Shift+Alt+F2 and look at the
> shadows).
I do have compositing on (Kubuntu defaults).
> Also, try capturing a screenshot of your complete desktop and mark the
> window you wanted to screenshot originally. Maybe you've got an unusual
> setup?
I have some more information on this. It is only when windows are maximized.
Doesn't matter which window, any of them. For example, Konsole. In a small
size, floating on the desktop, Active Window screenshot works fine. Maximized
(but still not "full screen", as I have a standard panel on the left), Kwin
dies.

Interestingly, I do not get a crash pop-up. So maybe it's not a "crash" but
something else (process kill?).
> For crash bugs, submit a backtrace. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports. You should be able to start KWin with
> "kwin_x11 --replace".
I can easily get kwin back with "kwin &" each time. Which is good, makes it
easy to test. I'm trying to work out the -dbg package for kwin. I do have
kdelibs5-dbg installed.

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

[krita] [Bug 391273] New: Crash when animating

[Sam Hagin]

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

Bug ID: 391273
   Summary: Crash when animating
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: randallha...@gmail.com
  Target Milestone: ---

Created attachment 23
  --> https://bugs.kde.org/attachment.cgi?id=23=edit
Crash while animating

Crashed when dragging several keyframes around. Also, when I restarted Krita
and created the animation it would not play it correctly. It would skip over
keyframes until it reached the end of the animation set which was 33 frames
then do the animation in half a sec as if I set keyframes up one after another.
When I moved the keyframes around to make the animation take longer it did the
same thing but the image would also blink.

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

[Spectacle] [Bug 391118] Kwin crash when using Active Window screenshot method

[Henrik Fehlauer]

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

--- Comment #2 from Henrik Fehlauer  ---
> Shift+Alt+F2
Shift+Alt+F12

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

[Spectacle] [Bug 391118] Kwin crash when using Active Window screenshot method

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 CC||rk...@lab12.net

--- Comment #1 from Henrik Fehlauer  ---
Hmh, cannot reproduce in a VM.

For Spectacle it's always interesting to know if you have KWin's compositing
enabled or not (check in the settings or press Shift+Alt+F2 and look at the
shadows).

Also, try capturing a screenshot of your complete desktop and mark the window
you wanted to screenshot originally. Maybe you've got an unusual setup?

For crash bugs, submit a backtrace. See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports.
You should be able to start KWin with "kwin_x11 --replace".

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

[ktorrent] [Bug 391272] New: webseed are not loaded

[bugzilla_noreply]

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

Bug ID: 391272
   Summary: webseed are not loaded
   Product: ktorrent
   Version: 5.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: lestofant...@gmail.com
  Target Milestone: ---

Created attachment 22
  --> https://bugs.kde.org/attachment.cgi?id=22=edit
example of webseed torrent

I have created a series of .torrent file using mktorrent that contains multiple
webseed. None of them is visible in the "webseed" view, and also is not
possible to manyally add any. The download never start.

The same torrents work on qBitTorrent. No one of the torrent is working (the
only source is the webseed)

As attachment one the problematic torrent

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

[kalgebra] [Bug 390940] Separators shown as menu items when Application menu is used

[Aleix Pol]

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

--- Comment #5 from Aleix Pol  ---
Can you confirm this fixes the issue? My session has issues with Global Menu.

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

[kalgebra] [Bug 390940] Separators shown as menu items when Application menu is used

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kal
   ||gebra/df36977e2e58b4b5b7d1d
   ||b4f0c2a808b5652e722
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Aleix Pol  ---
Git commit df36977e2e58b4b5b7d1db4f0c2a808b5652e722 by Aleix Pol.
Committed on 02/03/2018 at 00:13.
Pushed by apol into branch 'master'.

Add actions as separators rather than menus

M  +2-2src/kalgebra.cpp

https://commits.kde.org/kalgebra/df36977e2e58b4b5b7d1db4f0c2a808b5652e722

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

[kmenuedit] [Bug 390737] App icons look pixelated when I increase display scale

[Henrik Fehlauer]

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

--- Comment #13 from Henrik Fehlauer  ---
The bug you linked is probably unrelated, and I doubt changes in Qt 5.11 will
help in our case (I only know about https://phabricator.kde.org/D5109#162592).

IMO it's quite unrealistic to expect you to fix KIconLoader if even more
experienced developers are stuck (see https://phabricator.kde.org/D6313). Also,
https://phabricator.kde.org/D10532 clearly applied a similar fix and it was
allowed to go in.

Looking at the "Open With" dialog you get for "Add Program", you'll observe the
problem with QIcon::fromTheme we've talked about elsewhere (which I believe
should possibly be fixed in Breeze): Going from 1x scaling to 1.5x scaling, the
Akregator icon changes colour. Now, given for this dialog it's somewhat broken,
I'd suggest to just go with QIcon::fromTheme for your patch too.

Let me know where you are stuck, or upload a WIP version. I tried it myself,
and the patch really is not all that complicated. Just try to understand what
the code is doing in both cases, and you should be able to adapt it.

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

[kate] [Bug 385628] [Wayland] Kate crash on close.

[Aleix Pol]

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

--- Comment #12 from Aleix Pol  ---
Discussing it with David (few months ago) suggested the issue to be in
QtWayland, which all applications use.

Kate for example doesn't use any of this KWayland::Client and also gets the
crash.

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

[gwenview] [Bug 364822] SVGs are not zoomed to fit

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/gwe
   ||nview/9b1714fc7b50be746f39e
   ||835c8b3146c38a9ddd9
   Version Fixed In||17.12.3

--- Comment #3 from Henrik Fehlauer  ---
Git commit 9b1714fc7b50be746f39e835c8b3146c38a9ddd9 by Henrik Fehlauer.
Committed on 01/03/2018 at 23:27.
Pushed by rkflx into branch 'Applications/17.12'.

Enlarge small SVGs too

Summary:
For images smaller than the viewport at 100% zoom, Gwenview allows to
scale up the image to {nav Fit} the window if {nav Enlarge smaller images}
is checked in the configuration dialog. So far this only worked for
raster-based images, but not for SVGs.

`mEnlargeSmallerImages` is meant to be handled by the abstract base
class `AbstractImageView`, however when f00cef3c0 moved code over there
from `RasterImageView`, it was missed to also adapt `SvgImageView`. This
can be fixed by implementing the missing function.

In addition, a left-over `bool` is removed.
FIXED-IN: 17.12.3

Test Plan:
- Open `icons/hisc-apps-gwenview.svgz`, press {nav Fit}: Small icon shown.
- Check {nav Enlarge smaller images}, press {nav Fit} again: Icon scaled up to
fit window.
- Enlarging raster-based images still works fine.

Reviewers: #gwenview, huoni, muhlenpfordt, ngraham

Reviewed By: #gwenview, huoni, muhlenpfordt, ngraham

Subscribers: ngraham, muhlenpfordt, huoni

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

M  +0-2lib/documentview/rasterimageview.cpp
M  +6-0lib/documentview/svgviewadapter.cpp
M  +2-0lib/documentview/svgviewadapter.h

https://commits.kde.org/gwenview/9b1714fc7b50be746f39e835c8b3146c38a9ddd9

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

[krita] [Bug 391270] Crash with weird GDB backtrace after attempting to manipulate a transform mask on a file layer.

[wolthera]

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

--- Comment #1 from wolthera  ---

Thread 1416 (Thread 0x7fff7b06e700 (LWP 6642)):
#0  0x7fffc72bc146 in KoCompositeOpGenericSC::composeColorChannels (channelFlags=...,
opacity=, 
maskAlpha=255 '\377', dstAlpha=255 '\377', 
dst=0x7fff949d92d8 '\377' ,
"\346\346\346\377\360\360\360\377\372\372\372", '\377' ...,
srcAlpha=, src=0x7fff630f62d8 "")
at
/home/wolthera/krita/src/libs/pigment/compositeops/KoCompositeOpGeneric.h:75
#1  KoCompositeOpBase
>::genericComposite (channelFlags=..., 
params=..., this=)
at
/home/wolthera/krita/src/libs/pigment/compositeops/KoCompositeOpBase.h:115
#2  KoCompositeOpBase
>::composite (this=, params=...)
at
/home/wolthera/krita/src/libs/pigment/compositeops/KoCompositeOpBase.h:81

#3  0x71486ff8 in KoColorSpace::bitBlt (this=0x1369e90,
srcSpace=0x1369e90, params=..., 
op=op@entry=0x38e6c40, 
   
renderingIntent=renderingIntent@entry=KoColorConversionTransformation::IntentPerceptual,
 
conversionFlags=...) at
/home/wolthera/krita/src/libs/pigment/KoColorSpace.cpp:515
#4  0x7256bfed in KisPainter::bitBltImpl (this=0x7fff7b06db70,
dstX=1536, dstY=2048, 
srcDev=..., srcX=1536, srcY=2048, srcWidth=512, srcHeight=512)
at /home/wolthera/krita/src/libs/image/kis_painter.cc:729
#5  0x72565ada in KisPainter::bitBlt (this=,
dstX=, 
dstY=, srcDev=..., srcX=, srcY=, srcWidth=512, 
srcHeight=512) at /home/wolthera/krita/src/libs/image/kis_painter.cc:751
#6  0x72565b85 in KisPainter::bitBlt (this=this@entry=0x7fff7b06db70,
pos=..., srcDev=..., 
---Type  to continue, or q  to quit---
srcRect=...) at /home/wolthera/krita/src/libs/image/kis_painter.cc:757
#7  0x726769f2 in KisLayerProjectionPlane::apply (this=0x145b7f90,
painter=0x7fff7b06db70, rect=...)
at /home/wolthera/krita/src/libs/image/kis_layer_projection_plane.cpp:99
#8  0x7262c362 in KisAsyncMerger::compositeWithProjection (rect=...,
leaf=..., this=0x146fac28)
at /home/wolthera/krita/src/libs/image/kis_async_merger.cpp:350
#9  KisAsyncMerger::startMerge (this=this@entry=0x146fac28, walker=...,
notifyClones=notifyClones@entry=true)
at /home/wolthera/krita/src/libs/image/kis_async_merger.cpp:274
#10 0x7279450c in KisUpdateJobItem::runMergeJob (this=0x146fabe0)
at
/home/wolthera/krita/build/libs/image/../../../src/libs/image/kis_update_job_item.h:117
#11 KisUpdateJobItem::run (this=0x146fabe0)
at
/home/wolthera/krita/build/libs/image/../../../src/libs/image/kis_update_job_item.h:85
#12 0x752c6b37 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x752ca6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fffee4376ba in start_thread (arg=0x7fff7b06e700) at
pthread_create.c:333
#15 0x749c141d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1415 (Thread 0x7fff97f46700 (LWP 6641)):
#0  0x7fffc72bc141 in KoCompositeOpGenericSC::composeColorChannels (channelFlags=...,
opacity=, 
maskAlpha=255 '\377', dstAlpha=255 '\377', dst=0x7fff602ccee8 '\377'
..., 
srcAlpha=, src=0x7fff63109ee8 "")
at
/home/wolthera/krita/src/libs/pigment/compositeops/KoCompositeOpGeneric.h:75
#1  KoCompositeOpBase
>::genericComposite (channelFlags=..., 
params=..., this=)
at
/home/wolthera/krita/src/libs/pigment/compositeops/KoCompositeOpBase.h:115
---Type  to continue, or q  to quit---
#2  KoCompositeOpBase
>::composite (this=, params=...)
at
/home/wolthera/krita/src/libs/pigment/compositeops/KoCompositeOpBase.h:81
#3  0x71486ff8 in KoColorSpace::bitBlt (this=0x1369e90,
srcSpace=0x1369e90, params=..., 
op=op@entry=0x38e6c40, 
   
renderingIntent=renderingIntent@entry=KoColorConversionTransformation::IntentPerceptual,
 
conversionFlags=...) at
/home/wolthera/krita/src/libs/pigment/KoColorSpace.cpp:515
#4  0x7256bfed in KisPainter::bitBltImpl (this=0x7fff97f45b70,
dstX=2048, dstY=2048, 
srcDev=..., srcX=2048, srcY=2048, srcWidth=512, srcHeight=512)
at /home/wolthera/krita/src/libs/image/kis_painter.cc:729
#5  0x72565ada in KisPainter::bitBlt (this=,
dstX=, 
dstY=, srcDev=..., srcX=, srcY=, srcWidth=512, 
srcHeight=512) at /home/wolthera/krita/src/libs/image/kis_painter.cc:751
#6  

[krita] [Bug 391270] New: Crash with weird GDB backtrace after attempting to manipulate a transform mask on a file layer.

[wolthera]

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

Bug ID: 391270
   Summary: Crash with weird GDB backtrace after attempting to
manipulate a transform mask on a file layer.
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com
  Target Milestone: ---

This isn't reproducable, I am just posting in case the resulting backtrace
might point to a useful thing to fix.

I had a transform mask on a file layer. Adjusted it once, adjust it twice, and
at some point activating the transform mask with the transform tool, the whole
file layer (visually) dissapears and this backtrace appears:


--

*** Error in `/home/wolthera/krita/inst/bin/krita': double free or corruption
(fasttop): 0x7fff74045b10 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x749317e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7493a37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7493e53c]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x139568)[0x72545568]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x139964)[0x72545964]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x147550)[0x72553550]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x147739)[0x72553739]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x2a28f7)[0x726ae8f7]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZNK14KisPaintDevice20calculateExactBoundsEb+0xff)[0x726a67af]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x2a83af)[0x726b43af]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x2a163f)[0x726ad63f]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZNK14KisPaintDevice11exactBoundsEv+0x16)[0x726a5356]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZN18KisTransformWorker3runEv+0x20)[0x726da7d0]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so(+0x5d92a)[0x7fffbda1192a]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so(_ZNK23KisTransformMaskAdapter15transformDeviceE12KisSharedPtrI7KisNodeES0_I14KisPaintDeviceES4_+0xb7)[0x7fffbd9e0c07]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZNK16KisTransformMask12decorateRectER12KisSharedPtrI14KisPaintDeviceES3_RK5QRectN7KisNode16PositionToFilthyE+0x1f7)[0x7261b6f7]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZNK7KisMask5applyE12KisSharedPtrI14KisPaintDeviceERK5QRectS5_N7KisNode16PositionToFilthyE+0xf3c)[0x7268c4fc]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZNK8KisLayer10applyMasksE12KisSharedPtrI14KisPaintDeviceES2_RK5QRectS0_I7KisNodeES7_+0x8b8)[0x72672008]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZN8KisLayer16updateProjectionERK5QRect12KisSharedPtrI7KisNodeE+0x188)[0x72672698]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x26a248)[0x72676248]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(_ZN14KisAsyncMerger10startMergeER18KisBaseRectsWalkerb+0x11c1)[0x7262cc21]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.16(+0x38850c)[0x7279450c]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0xaab37)[0x752c6b37]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0xae6eb)[0x752ca6eb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fffee4376ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x749c141d]
=== Memory map: 
0040-0096b000 r-xp  08:01 4223775   
/home/wolthera/krita/inst/bin/krita
00b6a000-00b6b000 r--p 0056a000 08:01 4223775   
/home/wolthera/krita/inst/bin/krita
00b6b000-00c3e000 rw-p 0056b000 08:01 4223775   
/home/wolthera/krita/inst/bin/krita
00c3e000-1ccd8000 rw-p  00:00 0  [heap]
7fff48d86000-7fff4b45a000 rw-p  00:00 0 
7fff4db2e000-7fff61b33000 rw-p  00:00 0 
7fff61b33000-7fff61ba3000 rw-s  00:05 1974591/drm
mm object (deleted)
7fff61ba3000-7fff61c13000 rw-s  00:05 1974578/drm
mm object (deleted)
7fff61c13000-7fff61c83000 rw-s  00:05 1974565/drm
mm object (deleted)
7fff61c83000-7fff61cf3000 rw-s  00:05 1974552/drm
mm object (deleted)
7fff61cf3000-7fff61d63000 rw-s  00:05 1974539/drm
mm object (deleted)
7fff61d63000-7fff61dd3000 rw-s  

[kwin] [Bug 391271] New: When loging out wayland session, do the windows get a proper close signal?

[Michail Vourlakos]

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

Bug ID: 391271
   Summary: When loging out wayland session, do the windows get a
proper close signal?
   Product: kwin
   Version: 5.12.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mvourla...@gmail.com
  Target Milestone: ---

I am updating Latte implementation for wayland and I dont get a clean exit when
plasma is exiting the wayland session. I have added debug messages on exiting
on the destructor of the main class but these messages arent shown at all.
Instead it is shown the following message:

"The Wayland connection broke. Did the Wayland compositor die?"

So is there a chance that the kwin wayland compositor is closing before all the
windows exit?

One more thing I noticed is that during logging out all Qt windows dont close
but instead the Firefox one does, which is using XWayland I suppose.

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

[neon] [Bug 390937] neon-settings fontconfig 56-neon-noto.conf is incompatible with 56-twemoji-color.conf

[Adrien Beau]

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

--- Comment #2 from Adrien Beau  ---
Thanks for your detailed answer.

I did not know about Noto Emoji, it is interesting to know there is some choice
in this area. However, looking at
https://github.com/googlei18n/noto-emoji/issues/36 it appears you need very
recent fontconfig and/or cairo to have it working out of the box.

Indeed, I removed Twitter Color Emoji, restored the Neon fontconfig files, and
put NotoColorEmoji.ttf in ~/.local/share/fonts as you suggested, and it was
totally ignored by fontconfig. I also put NotoEmoji-Regular.ttf there, it was
not ignored, but it only contains outdated black-and-white glyphs according to
the noto-emoji README.

The prepend hack may be ugly, but it also appears to be widely done by users in
https://github.com/googlei18n/noto-emoji/issues/36 (at least until the very
recent fontconfig version gets distributed more widely). Without it, I get
glyphs from /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf and they suffer
from a huge style clash: some of the most basic emojis are ugly black-and-white
glyphs, while the rest has nice coloring. The emoji coverage is also very poor.

Currently, it appears TwitterColorEmoji-SVGinOT.ttf is the one providing a font
with full support and consistent style that just works under the Xenial
software stack. The prepend hack, while unsavory, seems necessary to make it
work in all cases. (Or maybe getting rid of DevaVuSans is a solution...)

I also tried renaming 56-neon-noto.conf to 56-x-neon-noto.conf and it solves my
issue as you expected. Thanks!

Should I close this issue, or would you prefer to keep it open to include a
workaround in your package?

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

[frameworks-baloo] [Bug 391252] Baloo unable to find files in hidden folders

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Version|17.12.2 |5.43.0
Product|dolphin |frameworks-baloo
 CC||n...@kde.org
   Assignee|dolphin-bugs-n...@kde.org   |baloo-bugs-n...@kde.org
  Component|search  |general
Summary|Dolphin "Find" feature  |Baloo unable to find files
   |unable to find files|in hidden folders

--- Comment #3 from Nate Graham  ---
FWIW Baloo is now maintained once more. So there is definitely the promise of
future bugfixes and new features.

I believe KFind is basically a graphical `find`, rather than building a whole
index the way Baloo does, which is why KFind finds it. By default, I believe
Baloo doesn't index the contents of hidden folders; Sending to frameworks-baloo
to decide whether to confirm and WONTFIX, turn this on by default, or add a
switch to control it.


> Another example. In the home directory...

One issue per bug report please. See
https://community.kde.org/Get_Involved/Bug_Reporting#One_issue_per_bug_report

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

[plasma-pa] [Bug 391264] Resume output selection

[Germano Massullo]

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

--- Comment #2 from Germano Massullo  ---
Created attachment 20
  --> https://bugs.kde.org/attachment.cgi?id=20=edit
volume setting 1

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

[plasma-pa] [Bug 391264] Resume output selection

[Germano Massullo]

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

--- Comment #3 from Germano Massullo  ---
Created attachment 21
  --> https://bugs.kde.org/attachment.cgi?id=21=edit
volume setting 2

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

[konsole] [Bug 391255] Konsole within Dolphin panel) does not read .bashrc when a closed activity is resumed

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Product|dolphin |konsole
 CC||n...@kde.org
   Assignee|dolphin-bugs-n...@kde.org   |konsole-de...@kde.org
  Component|panels: terminal|general
Summary|Konsole does not read   |Konsole within Dolphin
   |.bashrc when a closed   |panel) does not read
   |activity is resumed |.bashrc when a closed
   ||activity is resumed

--- Comment #1 from Nate Graham  ---
Starting with Konsole

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

[frameworks-baloo] [Bug 391253] a baloo_file process continue to run when X session is stopped

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[krita] [Bug 390371] Polygonal Selection tool - modes

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com
 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Scott Petrovic  ---
replace is the default currently. That is what most people use so we are
leaving it as the default for now.

One reason we won't change this is that no other applications has "add" mode as
the default. This would make krita pretty intuitive as it would work different
than every other application.

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

[plasma-pa] [Bug 391264] Resume output selection

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Discover] [Bug 391262] Crash and messagem in updates about ARGUMENTS MISSING

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #4 from Nate Graham  ---
What distro are you using?

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

[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2

[CapSel]

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

--- Comment #4 from CapSel  ---
Your patch works. Thank You!

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

[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)

[Eike Hein]

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

--- Comment #17 from Eike Hein  ---
My preferred option is still for KWin to start ignoring windows that have
SkipPager set in Present Windows (because my argument remains that any
summarized view of windows is conceptually a pager).

In lieu of that, we need a new SkipSwitcher state in the KWindowSystem API (for
X11) as well as in the PlasmaWindowManagement protocol (for Wayland).

IMHO the rule-based approach is a hack.

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

[plasmashell] [Bug 391269] New: Make plasma animations non-blocking

[Eric Mesa]

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

Bug ID: 391269
   Summary: Make plasma animations non-blocking
   Product: plasmashell
   Version: 5.11.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ericsbinarywo...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Currently I am copying and pasting 2 files totaling 10BG using Dolphin from a
folder locally onto a folder on an NFS share. Plasma has gone into disk sleep
and is completely unresponsive. The mouse works, as does any program. But I
cannot click on any plasma components - the "start menu", the task switch, the
activity switcher, and other components all do nothing.

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[Albert Astals Cid]

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

--- Comment #27 from Albert Astals Cid  ---
(In reply to Lukasz from comment #24)
> It's happening to me as well:

Lukasz can you reproduce this easily? Do you know how to run kdeconnect under
valgrind? I'd help me quite a bit having the valgrind trace to understand
what's going on.

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

[dolphin] [Bug 183429] open externally called folder in new tab

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||junior-jobs

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

[dolphin] [Bug 183429] open externally called folder in new tab

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||correcho...@hotmail.com

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

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

[dolphin] [Bug 391254] Open media in new tab instead of new window

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

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


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

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

[krita] [Bug 391268] Smudge brush cant draw black on masks

[wolthera]

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #1 from wolthera  ---
Caused by the colorsmudge fix after the first beta.

>From what I gather, the problem is on ln 282 in the composite there. You see,
transparency masks are alpha colorspaces. I think it's confused on how to
handle this alpha color space, because there black is transparent! So it just
goes, well, this is transparent, let's not do anything :p

Some qdebugs show this quite clearly:

With darkgray:
Color   "Alpha 63335"
dulling "Alpha 46893"
dulling after composite "Alpha 47741"

with black
Color   "Alpha 0"
dulling "Alpha 65535"
dulling after composite "Alpha 65535"

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

[plasmashell] [Bug 391237] Plasma panel or Latte dock crash when changing the systray entries visibility

[bugzilla_noreply]

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

yst...@posteo.net changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from yst...@posteo.net ---
(Confirmed because I was able to reproduce on my machine with the same steps).

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

[kdevelop] [Bug 391127] svn+ssh doesn't work with password auth

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||chris...@gmx.de

--- Comment #1 from Kevin Funk  ---
CC'ing Christoph who might be interested in looking at this.

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

[lattedock] [Bug 390017] [wayland] - Latte panel on top edge shows a centered transparent box after login

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #7 from Michail Vourlakos  ---
I can reproduce.

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

[krita] [Bug 391268] New: Smudge brush cant draw black on masks

[ZSpratt]

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

Bug ID: 391268
   Summary: Smudge brush cant draw black on masks
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: zachman...@gmail.com
  Target Milestone: ---

When using the smudge brush to paint onto a transparency or filter mask, only
white can be drawn.
Black has no effect, and lighter colors appear as white, regardless of
brightness.

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

[lattedock] [Bug 390020] Latte dock crash when closing settings (Wayland)

[Michail Vourlakos]

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

--- Comment #5 from Michail Vourlakos  ---
Please recheck in a few days because I updated the Latte wayland architecture
and fixed some crashes.
There is a chance that this is fixed...

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration [KDevelop::ExecuteCompositeJob::doKill]

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

  Latest Commit||8430d3058f92725b4e6b7d85d8d
   ||68550ce12ee79

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

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration [KDevelop::ExecuteCompositeJob::doKill]

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D10874

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

[kdevelop] [Bug 375635] Wrong code completion on switch with strongly-typed enum

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.2.2
  Latest Commit||https://commits.kde.org/kde
   ||velop/76d7b807825ddc1b30c41
   ||11bb27754f84a63c0a1
URL||https://phabricator.kde.org
   ||/D10738
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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

[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2

[David Strobach]

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

David Strobach  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from David Strobach  ---
@CapSel: Could you please check whether the attached patch fixes the bug for
you? If it does, I'll post it to Phabricator for review, commit it and close
the bug eventually. Thanks.

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

[krita] [Bug 391261] Runtime crash when opening some files from older Krita versions

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #5 from Boudewijn Rempt  ---
Oh, good to hear that the crash is gone :-)

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

[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)

[Nate Graham]

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

--- Comment #16 from Nate Graham  ---
OK, so then it seems we have four options:
- KWin exposes something for launchers to signal that they don't want to be
displayed in the effect
- We ship KWin with a default skipSwitcher rule for launchers
- KWin does nothing, and it's up to distros to ship with the rule (and we
continue to get bug reports from users of other distros)
- Nothing happens, and we continue to get bug reports

Is that correct?

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

[krita] [Bug 391261] Runtime crash when opening some files from older Krita versions

[bugzilla_noreply]

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

--- Comment #4 from kali...@wp.pl ---
The beta3 build opened the files without any problem, thanks :)

The issue was not in text fields, since I had that problem with other files
that had no text in them (I only chose this one, since it was the smallest I
found around that failed to open). I remember the warnings though and I'm
making backups of every file I convert to Krita4, thanks :)

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

[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)

[Eike Hein]

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

--- Comment #15 from Eike Hein  ---
It doesn't currently exist in the way that matters from the launcher side:

https://api.kde.org/frameworks/kwindowsystem/html/classKWindowSystem.html#a2fcec2ab4297afe9edae7971b1a4cd86

https://api.kde.org/frameworks/kwindowsystem/html/classNET.html#a08dce7f5ea8a2a6d1d38aea3498f00ee

If it was a simple as that I'd have done it long ago.

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

[konsole] [Bug 389746] Output is garbled when many lines are printed at once

[Egmont Koblinger]

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

--- Comment #6 from Egmont Koblinger  ---
How reproducible is this?

What's the value of $TERM outside of tmux?

I believe the first big step in debugging would be to locate whether this is a
bug in konsole/yakuake or tmux. I can easily imagine both, and not being able
to reproduce in xterm could be due to different timing of things if it's a tmux
issue.

Here's how I'd proceed:

- Take a note of the window size (e.g. "stty size").

- Start "script", and then start "tmux".

- Reproduce the bug in as few steps as possible.

- Quit tmux, then quit script (e.g. press ^D twice).

- Attach the resulting "typescript" file, and also share the window size with
us.

- We could then manually investigate whether what appears in konsole's window
matches the contents of "typescript" or not. By cutting off the end of the
"typescript" file (the bits corresponding to exiting, most notably tmux leaving
alternate screen) we should be able to deterministically reproduce the faulty
result using a simple "cat typescript" at the same terminal size, and even do
this in other terminal emulators. If by cat'ing typescript the result is the
same in all terminal emulators, namely the bad rendering, then it's tmux asking
for stupid things from konsole. If cat'ing is only broken in konsole, or is
still random (e.g. depends on timing) then it's a konsole issue.

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

[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|present windows shows the   |present windows shows
   |Application Dashboard   |launchers (Kicker, Kickoff,
   |fullscreen window   |Application Dashboard,
   ||SimpleMenu, etc)
 CC||n...@kde.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #14 from Nate Graham  ---
We have multiple bug reports about this issue, and it's not intended or useful
behavior from a user perspective (not a developer perspective); in short, it's
a bug. The question is how we resolve it.

skipSwitcher does in fact exist, and is visible in System Settings > Window
Management > Window Behavior > [new rule] > Arrangement & Access.

Setting a rule and targeting my launcher works like a charm: no more launcher
in the Present Windows effect. So fixing this bug is possible; the question is
just whose responsibility it is do do it: should (could?) launchers signal that
they want to be skipped, or do we need a built-in KWin rule?

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

[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem

[David Tonhofer]

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

--- Comment #16 from David Tonhofer  ---
I agree

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

[plasmashell] [Bug 375921] present windows shows the Application Dashboard fullscreen window

[Nate Graham]

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

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

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

[plasmashell] [Bug 391233] present windows: app launcher appears when the super key is hit

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #9 from Nate Graham  ---


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

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

[konsole] [Bug 389746] Output is garbled when many lines are printed at once

[Egmont Koblinger]

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

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

--- Comment #5 from Egmont Koblinger  ---
Took me a while to realize, so let's emphasize: In the screenshot, the first
column is full of B's.

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

[plasmashell] [Bug 391233] present windows: app launcher appears when the super key is hit

[Eike Hein]

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

--- Comment #8 from Eike Hein  ---
There is no "skip switcher".

See https://bugs.kde.org/show_bug.cgi?id=375921 for the last discussion.

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

[plasmashell] [Bug 368078] Problem with many windows of Sierra Charts (Windows/wine)

[Eike Hein]

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

--- Comment #24 from Eike Hein  ---
Please make sure you're using a wine version new enough to contain this patch:
https://bugs.winehq.org/show_bug.cgi?id=32699#c16

We worked with wine last year to make this better there.

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

[dolphin] [Bug 240873] When "Paste Clipboard Contents" is active in Dolphin, browsing folders becomes a bit sluggish

[Ahmad Samir]

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

--- Comment #6 from Ahmad Samir  ---
Actually, I haven't used klipper in a long time (definitely more than 4-5
years).

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

[dolphin] [Bug 261869] Bug with flash or/and adsense in preview

[BRULE Herman]

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

BRULE Herman  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |INVALID
 Status|NEEDSINFO   |RESOLVED

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

[dolphin] [Bug 261869] Bug with flash or/and adsense in preview

[BRULE Herman]

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

--- Comment #6 from BRULE Herman  ---
Closed, should work (flash not used now)

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

[elisa] [Bug 391267] New: No music playback

[Michael D]

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

Bug ID: 391267
   Summary: No music playback
   Product: elisa
   Version: 0.0.81
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: nortex...@gmail.com
  Target Milestone: ---

I'm using the Elisa package from the opensuse tumbleweed official repo. All
music is detected in my Music folder, and I can load it into the playlist, but
it provides no option for playblack. The little playback button on each track
in the playlist is grayed out.

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

[kexi] [Bug 390794] kexi crashes at startup

[Jarosław Staniek]

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

--- Comment #11 from Jarosław Staniek  ---
Update: Qt potentially fixed for 5.11, see this comment:
https://bugreports.qt.io/browse/QTBUG-65478?focusedCommentId=393560=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-393560

Now a question what to do on the KEXI side. One clever idea is to add an option
to kexirc that hides this feature (in config, not at build time). Users
unfortunate enough that use crashing Qt version can disable the feature before
starting KEXI. 

We can even disable the feature by default when 5.10.1 <= Qt < 5.11.

Opinions welcome.

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[Lukasz]

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

Lukasz  changed:

   What|Removed |Added

Version|unspecified |5.43.0

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

[kwin] [Bug 296673] Please preserve the window geometry relative to it's original screen instead of globally when adding a screen

[Ganton]

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

--- Comment #52 from Ganton  ---
New developments are talked about in:
Connecting new screens
https://vizzzion.org/blog/2018/02/connecting-new-screens/

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

[kwin] [Bug 296673] Please preserve the window geometry relative to it's original screen instead of globally when adding a screen

[Ganton]

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

Ganton  changed:

   What|Removed |Added

 CC||ku...@gmx.com

--- Comment #51 from Ganton  ---
New developments are talked about in:
Connecting new screens
https://vizzzion.org/blog/2018/02/connecting-new-screens/

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

[digikam] [Bug 388320] Selecting print layout does not stay selected.

[Maik Qualmann]

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

--- Comment #8 from Maik Qualmann  ---
If you are using a custom photo layout, this is actually always reset to the
first entry in the list, it is programmed in the code. Why can not I tell you
at the moment which side effect it might otherwise have. I will check it.

Maik

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