[Akonadi] [Bug 372329] KMail, Korganizer, KAdressBook cannot run Akonadi server in KUbuntu 16.10

[bugzilla_noreply]

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

--- Comment #5 from caesarrule...@gmail.com ---
(In reply to Christoph Feck from comment #1)
> Can you confirm the issue is the same as in bug 372236 (Test 10: Akonadi
> control process not registered at D-Bus)?

I cann't confirm right now. How can i fing Akonadi Self-Test Report?

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

[Akonadi] [Bug 372329] KMail, Korganizer, KAdressBook cannot run Akonadi server in KUbuntu 16.10

[bugzilla_noreply]

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

--- Comment #3 from caesarrule...@gmail.com ---
Created attachment 102228
  --> https://bugs.kde.org/attachment.cgi?id=102228=edit
Akonadi fails with error

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

[Akonadi] [Bug 372329] KMail, Korganizer, KAdressBook cannot run Akonadi server in KUbuntu 16.10

[bugzilla_noreply]

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

--- Comment #4 from caesarrule...@gmail.com ---
Created attachment 102229
  --> https://bugs.kde.org/attachment.cgi?id=102229=edit
Pushing button does nothing!

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

[Akonadi] [Bug 372329] KMail, Korganizer, KAdressBook cannot run Akonadi server in KUbuntu 16.10

[bugzilla_noreply]

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

--- Comment #2 from caesarrule...@gmail.com ---
Created attachment 102227
  --> https://bugs.kde.org/attachment.cgi?id=102227=edit
Akonadi lloading

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

[digikam] [Bug 372435] Use multiple cpu cores for duplicate search

[Wolfgang Scheffner]

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

Wolfgang Scheffner  changed:

   What|Removed |Added

 CC||wscheffn...@gmail.com

--- Comment #1 from Wolfgang Scheffner  ---
I support this request.

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

[krita] [Bug 372327] Snapping cannot be turned off using Guides

[bugzilla_noreply]

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

--- Comment #2 from skinnune...@gmail.com ---
Hi,

thanks for reply. I realized that I need to LOCK guides so while using the
brush tool, it doesn't change into cursor and snap/move lines.So user error
I suppose. :) Thanks for the great work you guys do!

Regards,Sari

2016-11-11 14:27 GMT+02:00 wolthera :

> https://bugs.kde.org/show_bug.cgi?id=372327
>
> wolthera  changed:
>
>What|Removed |Added
> 
> 
>  CC||griffinval...@gmail.com
>
> --- Comment #1 from wolthera  ---
> Hm, that IS strange... Could you share a kra file where this issue happens?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 372323] Camera autodetection fails when using AppImage bundle

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Git commit b5d5cf80dc6cd7035973fa0d8f2a73004c4d4ac8 by Gilles Caulier.
Committed on 14/11/2016 at 05:49.
Pushed by cgilles into branch 'master'.

remove centos6 libgphoto2 devel package before to build last offcial libgphoto2

M  +1-1project/appimage/01-build-centos6.sh

http://commits.kde.org/scratch/mwiesweg/digikam-sc/b5d5cf80dc6cd7035973fa0d8f2a73004c4d4ac8

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

[digikam] [Bug 372323] Camera autodetection fails when using AppImage bundle

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
Git commit d3b22c619f1440d349e735d2c1ac91fe58435248 by Gilles Caulier.
Committed on 14/11/2016 at 05:47.
Pushed by cgilles into branch 'master'.

use last official libgphoto2 2.5.10 to build AppImage bundle

M  +7-7project/appimage/01-build-centos6.sh

http://commits.kde.org/scratch/mwiesweg/digikam-sc/d3b22c619f1440d349e735d2c1ac91fe58435248

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

[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher

[Diego-MX]

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

Diego-MX  changed:

   What|Removed |Added

 CC||dvilla...@gmail.com

--- Comment #25 from Diego-MX  ---
I have this same issue with my KDE installation and I had initially felt lucky
for finding this thread that addresses it.  However much of what is discussed
here goes way beyond my experience;  and unfortunately, I couldn't understand
the part that discusses the solution, but instead read much about the problem
itself.  

I'd like to ask for some specific steps on fixing, for example, Firefox icons.

Cheers.

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

--- Comment #29 from Leslie Zhai  ---
Git commit ad01f86ae10f8f213db23432586f4f110a8ec49b by Leslie Zhai.
Committed on 14/11/2016 at 04:51.
Pushed by lesliezhai into branch 'cdrskin'.

Add more testcase for K3b ExternalBinManager

Summary:
1. There are already binObject for cdrecord, growisofs, cdrdao, etc. so
I need to migrate cdrskin binObject;
2. There is already CdrdaoWriter, AudioCueFileWritingJob, etc. to handle
*.cue file format. so Let wodim do the exotic CD stuff and cdrskin do
the rest ;-)

M  +1-0src/CMakeLists.txt
M  +2-0src/k3bdebuggingoutputcache.cpp
M  +1-1src/k3bdirview.cpp
M  +8-3src/k3bjobprogressdialog.cpp
M  +15   -7src/k3bthemedlabel.cpp
M  +185  -3tests/CMakeLists.txt
M  +46   -3tests/k3bexternalbinmanagertest.cpp
M  +5-2tests/k3bexternalbinmanagertest.h

http://commits.kde.org/k3b/ad01f86ae10f8f213db23432586f4f110a8ec49b

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

[akregator] [Bug 372458] New: akregattor

[arescorpio nepesh]

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

Bug ID: 372458
   Summary: akregattor
   Product: akregator
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: arescor...@tutanota.de
  Target Milestone: ---

Application: akregator (5.3.3 (QtWebEngine))
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.7-gnu-1 x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1e09c26840 (LWP 1909))]

Thread 27 (Thread 0x7f1cca8d9700 (LWP 2035)):
#0  0x7f1e057484ed in read () at /usr/lib/libc.so.6
#1  0x7f1de1963f81 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#2  0x7f1de373250e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#3  0x7f1de3732f80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f1de3733040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f1de3741069 in  () at /usr/lib/libpulse.so.0
#6  0x7f1de1992ed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7f1dfea5c454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f1e057557df in clone () at /usr/lib/libc.so.6

Thread 26 (Thread 0x7f1d5b4e5700 (LWP 1948)):
#0  0x7f1dfea6210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1df4f72f89 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f1df4f73589 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f1df4f73740 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f1df4f700dc in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f1dfea5c454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1e057557df in clone () at /usr/lib/libc.so.6

Thread 25 (Thread 0x7f1d616fa700 (LWP 1943)):
#0  0x7f1dfea6210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1df0860ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f1df0860b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f1dfea5c454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f1e057557df in clone () at /usr/lib/libc.so.6

Thread 24 (Thread 0x7f1d917fa700 (LWP 1934)):
#0  0x7f1e057484ed in read () at /usr/lib/libc.so.6
#1  0x7f1dfcccea10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1dfcc8a235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f1dfcc8a724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f1dfcc8a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f1e0628572b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f1e0622f23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f1e060520f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f1e06056d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f1dfea5c454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f1e057557df in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7f1d91ffb700 (LWP 1933)):
#0  0x7f1dfea6210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1df4f72f89 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f1df4f73589 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f1df4f73740 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f1df4f700dc in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f1dfea5c454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1e057557df in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7f1d927fc700 (LWP 1932)):
#0  0x7f1e0576202f in __libc_enable_asynccancel () at /usr/lib/libc.so.6
#1  0x7f1e05748542 in write () at /usr/lib/libc.so.6
#2  0x7f1e056df867 in _IO_new_file_write () at /usr/lib/libc.so.6
#3  0x7f1e056debb2 in new_do_write () at /usr/lib/libc.so.6
#4  0x7f1e056dffbe in __GI__IO_file_xsputn () at /usr/lib/libc.so.6
#5  0x7f1e056b6d15 in buffered_vfprintf () at /usr/lib/libc.so.6
#6  0x7f1e056b3f95 in vfprintf () at /usr/lib/libc.so.6
#7  0x7f1e05763ae9 in __fprintf_chk () at /usr/lib/libc.so.6
#8  0x7f1de62d29ee in  () at /usr/lib/libevent-2.0.so.5
#9  0x7f1de62d2be4 in event_warn () at /usr/lib/libevent-2.0.so.5
#10 0x7f1de62d72f8 in  () at /usr/lib/libevent-2.0.so.5
#11 0x7f1de62c136d in event_base_loop () at /usr/lib/libevent-2.0.so.5
#12 0x7f1df4f1e70e in  () at /usr/lib/libQt5WebEngineCore.so.5
#13 0x7f1df4f5af54 in  () at /usr/lib/libQt5WebEngineCore.so.5
#14 0x7f1df4f44ee5 in  () at /usr/lib/libQt5WebEngineCore.so.5
#15 0x7f1df4f73d6a in  () at /usr/lib/libQt5WebEngineCore.so.5
#16 

[gwenview] [Bug 354533] Support HiDPI in gwenview

[Martin Klapetek]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Martin Klapetek  ---
This is still the issue with latest master. It sadly makes Gwenview not
entirely usable on hidpi displays as the images are just blurry.

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

[okular] [Bug 372457] New: Bookmarks loosing in big documents.

[Max]

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

Bug ID: 372457
   Summary: Bookmarks loosing in big documents.
   Product: okular
   Version: 0.25.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: fmaksi...@gmail.com
  Target Milestone: ---

Created attachment 102225
  --> https://bugs.kde.org/attachment.cgi?id=102225=edit
Big pdf.

I found that all xpdf+poppler libs based PDF viewers has error with bookmarks
processing. In big pdf documents with long table of contents with many
sublevel, they cut TOC unpredictable.

I had test Okular, Evinece, xpdf and other viewers and all of them show the
same problem.

I attach a example document in samplebigpdf.zip. It was fixed in Master PDF 3
(bookmarks added for navigation).

In sample file PDF viewers do lose bookmarks:
Chapter I > 1. Some Basic Items  lost "Terms and Definitions"

Chapter I >  2. Binary and Hexadecimal Numbers lost all from 2.10

Chapter II > 3. Conceptual Structure of System Z  lost all from 3.8

and more.

The Adobe PDF Reader, Foxit Reader and PDF.js do not lose a bookmarks.

Thahks!

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

[basket] [Bug 372456] Empty notes not removed, tag shortcuts duplicated on customize, not applied within note

[David Rankin]

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

--- Comment #1 from David Rankin  ---
Note: the font-size combo list mix up (e.g. font sizes as 7 9 9 10 11) is
intermittent and will display all sizes correctly most of the time.

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

[basket] [Bug 372456] New: Empty notes not removed, tag shortcuts duplicated on customize, not applied within note

[David Rankin]

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

Bug ID: 372456
   Summary: Empty notes not removed, tag shortcuts duplicated on
customize, not applied within note
   Product: basket
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kel...@ieee.org
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

I have about 10 years of notes in basket and I would be in big trouble without
it. The current Arch package of 1.8.1 is against KDE Platform Version 4.14.26
in KDE Frameworks 5.27.0, Qt 5.7.0 (built against 5.7.0).

  There are real problems with basket 1.81 in plasma. For starters, the
following are broken or provide unexpected behavior:

 1) if you click and a new empty note is created, and you didn't mean to, it
does not automatically get deleted when you click somewhere else. Stray empty
notes were always auto-removed in the past. This can quickly lead to your
baskets turning into a giant mess;

 2) 'Tags' shortcuts are duplicated and generate errors for duplicate
keystrokes when you "Customize Tags" and then 'save'. It is like the list of
shortcuts is duplicated in memory causing basket to think each shortcut for a
tag is a duplicate. Quitting basket and restarting clears the duplicates from
memory, but this means you have to shutdown/restart basket if you change 'any'
tag setting;

 3) Changing a tag (like Title) does not update all Title tagged items in the
list;

 4) Clicking in a note and applying a tag doesn't apply the formatting if the
note already contained a tag. It is like the signals and slots get mixed up
after the first time a tag is applied (something is also funny with the
font-size combo-list, at times it will report available font sizes as 7 9 9 10
11, ... and you must manually enter 8 because it doesn't display in the list;

 5) Grouping is totally unpredictable. (probably in large part due to the
problem in (1) above.) Any unintended click slightly above/below the current
note baseline (when the Config > General > [ ] group note option is use)
creates a mess quickly. Now there is simply a pixel or two difference between
the note trying to group 'above' or group 'below' the current when clicking to
the right side of the insertion line.

 6) Configure > General > System Tray Icon [ ] Show main window when mouse
hovers over the system tray icon for 7 tenths -- no longer works at all. This
is probably due to some change in the systray in plasma, but this was a
brilliant time saving option that should be continued. (the balloon notices for
Global shortcut actions no longer works as well)

  I'm sure these are fixable and baskets is well worth the effort. Let me know
if I can provide an further information. I'm happy to do it.

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

[kdev-python] [Bug 372454] Crash while editing

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

   Target Milestone|--- |5.0.3
Product|kdevelop|kdev-python
  Component|general |general
   Assignee|kdevelop-bugs-n...@kde.org  |m...@svenbrauch.de
 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Do you have a code snippet where it crashes?

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

[konsole] [Bug 372441] Konsole Desktop file missing StartupWMClass

[Aniketh]

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

Aniketh  changed:

   What|Removed |Added

 CC||anikethgire...@gmail.com

--- Comment #1 from Aniketh  ---
I would like to fix this bug. There are different desktop file in konsole
package. They are: 

1.konsolehere.desktop  
2.konsolepart.desktop 
3.konsolerun.desktop 
4.terminalemulator.desktop
5.org.kde.konsole.desktop

Where should add the class? I guess it should be added in the 5th. Anyone can
see to it, so that I can do the fix.

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

[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session

[Christoph Feck]

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

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

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

[Touchpad-KCM] [Bug 372363] Crash: Open Touch Pad in Input Devices in Setttings (Wayland)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
This means KWin is started with a different logical DPI than the other
applications, most probably because that setting is applied asynchronously with
KWin startup.

Fedora has some cross-desktop configuration tool for this, which might be
another cause for the issue, depending on which time it is started and applies
its configuration.

I suggest to try this with a different distribution before reporting this to
Fedora developers.

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

[systemsettings] [Bug 372407] Edit Scheme Color Preview Not Working (black & white only) and No Update

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||oliv...@churlaud.com

--- Comment #2 from Christoph Feck  ---
Confirmed on master.

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

[systemsettings] [Bug 372415] Default Applications: Update gvfs if present.

[Daniel]

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

--- Comment #2 from Daniel  ---
(In reply to Christoph Feck from comment #1)
> Could you please be more specific how default applications are related to
> gvfs?

I thought that's what gvfs was used for? `gvfs-open http://google.com/` seems
to open in Firefox, and I assume that is what HexChat uses to open URLs (and
presumably some other GTK applications too).

> When changing associations via KDE systemsettings5, then those changes are
> made to the local mime database configuration, which should be respected by
> all desktop environments that follow this XDG standard.

I don't know. `xdg-open http://google.com/` works fine, so it has set that.
gvfs must be doing something weird or odd.

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

[systemsettings] [Bug 372415] Default Applications: Update gvfs if present.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |kcm_componentchooser
   Assignee|plasma-b...@kde.org |unassigned-b...@kde.org

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

[systemsettings] [Bug 372415] Default Applications: Update gvfs if present.

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Could you please be more specific how default applications are related to gvfs?

When changing associations via KDE systemsettings5, then those changes are made
to the local mime database configuration, which should be respected by all
desktop environments that follow this XDG standard.

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

[kwin] [Bug 372351] sphere cap deformation incorrectly scales sphere radius (should be cap radius only)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |effects-various
   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
Product|systemsettings  |kwin

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

[kwin] [Bug 372353] Independent zoom needed for 'cube', 'cylinder', and 'sphere' animations

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |effects-various
   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
   Severity|normal  |wishlist
Product|systemsettings  |kwin

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

[systemsettings] [Bug 372365] Changing "Global keyboard shortcut" reverses to the default after logout

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
See bug 300532 comment #24 for the procedure to change Plasma shortcuts.

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

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

[systemsettings] [Bug 300532] Custom keyboard shortcuts are reset on reboot or logout - KDE 4.8.2

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||gkor...@gmail.com

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

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

[Touchpad-KCM] [Bug 372363] Crash: Open Touch Pad in Input Devices in Setttings (Wayland)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|5.8.3   |unspecified
  Component|general |kcm
   Assignee|plasma-b...@kde.org |rajeeshknamb...@gmail.com
Product|systemsettings  |Touchpad-KCM

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

[Spectacle] [Bug 372374] Show current width and height of area

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[Spectacle] [Bug 357080] Show area when capturing a rectangolar region

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||lim...@me.com

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

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

[kdenlive] [Bug 372406] crash using razor tool on timeline

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |kdenlive
  Component|general |User Interface
   Assignee|unassigned-b...@kde.org |j...@kdenlive.org

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

[plasmashell] [Bug 359220] Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED
   Severity|major   |minor

--- Comment #9 from Christoph Feck  ---
Some widgets might indeed be movable without a delay. I do not see this as a
bug. Some windows, for example, can be moved without using the titlebar when
clicking on a background element that does not need to react to clicks.

Changing severity based on comment #8, but keeping it open for Plasma
maintainers to decide if those widgets need changes, of if the defaults could
be changed.

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

[kwin] [Bug 372455] New: Window exceeds available screen space

[André Marcelo Alvarenga]

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

Bug ID: 372455
   Summary: Window exceeds available screen space
   Product: kwin
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alvare...@kde.org
  Target Milestone: ---

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

When I open "Edit Window-Specific Settings" window (System Settings -> Window
Management -> Window Rules -> New), the bottom buttons are partially visible.
See screenshot.

My screen: 1366x768

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

[kdevelop] [Bug 372454] New: Crash while editing

[Aleix Pol]

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

Bug ID: 372454
   Summary: Crash while editing
   Product: kdevelop
   Version: 5.0.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aleix...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.0.2)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.7-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was coding my beautiful script, it was in a fancy generator expresion, if
that helps...

I get random crashes, maybe this points to something.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f23bc2c9840 (LWP 18972))]

Thread 20 (Thread 0x7f2347fff700 (LWP 19079)):
#0  0x7f23cb88f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23d541baee in QWaitConditionPrivate::wait(unsigned long)
(this=0x3b902b0, time=18446744073709551615) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:143
#2  0x7f23d541b8c9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=0x3b90210, mutex=0x3b90390, time=18446744073709551615) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:215
#3  0x7f23d1a738df in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x3b901c0, th=0x7f234c0013e0) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:594
#4  0x7f23d1a73760 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x3b901c0, th=0x7f234c0013e0, threadWasBusy=false,
suspendIfInactive=false, justReturning=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:554
#5  0x7f23d1a7e7e4 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x3b90560, th=0x7f234c0013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:66
#6  0x7f23d1a7ea32 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:61
#7  0x7f23d1a73a4f in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x3b901c0, th=0x7f234c0013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:568
#8  0x7f23d1a79870 in ThreadWeaver::Thread::run() (this=0x7f234c0013e0) at
/home/apol/devel/frameworks/threadweaver/src/thread.cpp:103
#9  0x7f23d541a33c in QThreadPrivate::start(void*) (arg=0x7f234c0013e0) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:368
#10 0x7f23cb889454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f23d48037df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f2364ff9700 (LWP 19078)):
#0  0x7f23cb88f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23d541baee in QWaitConditionPrivate::wait(unsigned long)
(this=0x3b902b0, time=18446744073709551615) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:143
#2  0x7f23d541b8c9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=0x3b90210, mutex=0x3b90390, time=18446744073709551615) at
/home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:215
#3  0x7f23d1a738df in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x3b901c0, th=0x7f23480013e0) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:594
#4  0x7f23d1a73760 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x3b901c0, th=0x7f23480013e0, threadWasBusy=false,
suspendIfInactive=false, justReturning=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:554
#5  0x7f23d1a7e7e4 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x3b90560, th=0x7f23480013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:66
#6  0x7f23d1a7ea32 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:61
#7  0x7f23d1a73a4f in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x3b901c0, th=0x7f23480013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:568
#8  0x7f23d1a79870 in ThreadWeaver::Thread::run() (this=0x7f23480013e0) at

[krusader] [Bug 356697] Copy/move progress window not visible under GNOME.

[bugzilla_noreply]

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

--- Comment #5 from kapto...@yahoo.com ---
Looks good to me now

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

[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput

[Jonatan Cloutier]

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

Jonatan Cloutier  changed:

   What|Removed |Added

 CC||cloutier...@gmail.com

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

[kmymoney4] [Bug 372453] New: KMyMoney 4.8 crashes on opening some files

[Yuri Shirman]

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

Bug ID: 372453
   Summary: KMyMoney 4.8 crashes on opening some files
   Product: kmymoney4
   Version: 4.8.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: yshir...@gmail.com
  Target Milestone: ---

Application: kmymoney (4.8.0)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.8.6-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
I upgraded to F25 beta which comes with KMyMoney 4.8.0 and the program crashes
when opening my default file. I can open the olde (about 2.5 years) version of
the file.
This probably means some inconsistency in the file (I did make some changes by
hand when I could not delete some payees inside the program). But the version
4.7.2 opens the same file without any issues.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7fd70fece92f in raise () at /lib64/libc.so.6
#7  0x7fd70fed052a in abort () at /lib64/libc.so.6
#8  0x7fd70fec6e37 in __assert_fail_base () at /lib64/libc.so.6
#9  0x7fd70fec6ee2 in  () at /lib64/libc.so.6
#10 0x7fd6f1de2f6f in  () at /lib64/libgwenhywfar.so.60
#11 0x7fd6f1723151 in AB_Job_new () at /lib64/libaqbanking.so.35
#12 0x7fd6f26b7b9e in KBankingPlugin::availableJobs(QString) () at
/usr/lib64/kde4/kmm_kbanking.so
#13 0x7fd71403ebfa in onlineJobAdministration::canSendCreditTransfer() ()
at /lib64/libkmm_mymoney.so.4
#14 0x558cb9dfb427 in KMyMoneyApp::slotUpdateActions() ()
#15 0x558cb9e01da0 in KMyMoneyApp::updateCaption(bool) ()
#16 0x558cb9e41cc8 in KMyMoneyApp::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
#17 0x7fd71117f090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#18 0x7fd713fcbf48 in MyMoneyFile::attachStorage(IMyMoneyStorage*) () at
/lib64/libkmm_mymoney.so.4
#19 0x558cb9e655f0 in KMyMoneyView::readFile(KUrl const&) ()
#20 0x558cb9e2b0d6 in KMyMoneyApp::slotFileOpenRecent(KUrl const&) ()
#21 0x558cb9de2557 in runKMyMoney(KApplication*, KStartupLogo*) [clone
.isra.9] ()
#22 0x558cb9ddf4fc in main ()

Reported using DrKonqi

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

[dolphin] [Bug 372452] New: Dolphin and Baloo crashed in complex environment.

[PiroXiline]

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

Bug ID: 372452
   Summary: Dolphin and Baloo crashed in complex environment.
   Product: dolphin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: piroxil...@ya.ru
  Target Milestone: ---

Application: dolphin (16.08.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.7-1-ARCH x86_64
Distribution: "Arch Linux"

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

Running 'kdesu nautilus'. And going through directories.

While Docker was building infrastructure. It extencively mounts/unmounts layer
devices. And Dolphin reacts to that.

>From superuser small files was opened kate.

Chromium was opened with many tabs.

Electron app Upwork running.

Ballo also crashed. I was stupid enough to look that report provided 'no
valueble information' and closed it, before viewed this one.

- Custom settings of the application:

I use Dark Mode.

Also Gnome installed. But WM and DE is full KDE Plasma with SDDM.

Running ArchLinux x86_64 4.8.7-1-ARCH with latest updates from stable Arch
repos.

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

Thread 10 (Thread 0x7ff0e4ce6700 (LWP 25855)):
#0  0x7ff113f4b48d in poll () at /usr/lib/libc.so.6
#1  0x7ff1092b1121 in  () at /usr/lib/libpulse.so.0
#2  0x7ff1092a28f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7ff1092a2f8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7ff1092a3040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7ff1092b1069 in  () at /usr/lib/libpulse.so.0
#6  0x7ff104cd3ed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7ff1096ec454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7ff113f547df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7ff0e5a23700 (LWP 16851)):
#0  0x7ff113f474ed in read () at /usr/lib/libc.so.6
#1  0x7ff1075f5a10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff1075b1235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7ff1075b1724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7ff1075b189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7ff10e0ba72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7ff10e06423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7ff10de870f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7ff10de8bd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7ff1096ec454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7ff113f547df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7ff0eaeca700 (LWP 16846)):
#0  0x7ff1096f210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff0f529888b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7ff0f52986e7 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7ff1096ec454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff113f547df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff0eb6cb700 (LWP 16845)):
#0  0x7ff1096f210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff0f529888b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7ff0f52986e7 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7ff1096ec454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff113f547df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7ff0ebecc700 (LWP 16844)):
#0  0x7ff1096f210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff0f529888b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7ff0f52986e7 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7ff1096ec454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff113f547df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7ff0ec6cd700 (LWP 16843)):
#0  0x7ff1096f210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff0f529888b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7ff0f52986e7 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7ff1096ec454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff113f547df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7ff0ed0d3700 (LWP 16842)):
#0  0x7ff1096f210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff0f529888b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7ff0f52986e7 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7ff1096ec454 in start_thread () at 

[valgrind] [Bug 367942] Segfault vgPlain_do_sys_sigaction (m_signals.c:1138)

[geeknik]

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

geeknik  changed:

   What|Removed |Added

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

--- Comment #2 from geeknik  ---
valgrind-3.13.0.SVN does not appear to crash in this instance.

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

[plasmashell] [Bug 372384] Memory leak in plasmashell

[Reuben Peterkin]

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

Reuben Peterkin  changed:

   What|Removed |Added

 CC||reube...@yahoo.com

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

[plasmashell] [Bug 371995] Plasma crashed after unlocking widgets

[Timo]

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

--- Comment #5 from Timo  ---
This got fixed in the latest update

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

[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere

[skierpage]

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

--- Comment #2 from skierpage  ---
Created attachment 102223
  --> https://bugs.kde.org/attachment.cgi?id=102223=edit
output of `kscreen-console bug`

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

[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere

[skierpage]

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

--- Comment #1 from skierpage  ---
Created attachment 10
  --> https://bugs.kde.org/attachment.cgi?id=10=edit
window screenshot showing the small pointer in the titlebar

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

[systemsettings] [Bug 372451] New: mouse cursor is small in titlebar, large elsewhere

[skierpage]

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

Bug ID: 372451
   Summary: mouse cursor is small in titlebar, large elsewhere
   Product: systemsettings
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: skierp...@gmail.com
CC: unassigned-b...@kde.org
  Target Milestone: ---

Created attachment 102221
  --> https://bugs.kde.org/attachment.cgi?id=102221=edit
window screenshot showing the large pointer

In Fedora 25 beta KDE spin with an external monitor attached. The
cursor/pointer is big on the desktop, big in window contents, but small in the
titlebar, see attached screenshots.

I was using default settings: Fedora Look and Feel (looks like Breeze),Fedora
Twenty Five desktop theme (looks like Breeze), and Breeze cursor theme. The
cursor size is "Resolution dependent". The large size matches the cursors shown
in Mouse Cursor Theme setting. I tried switching themes and got similar
behavior: in Adwaita the difference in size is less apparent, maybe because it
offers a 32 size cursor. After fiddling with themes the resize cursors on
window edge are now small where they used to be large.

I'm running System Settings 5.8.1 (and KDE Frameworks 5.27.0) but this version
is not available in the bugzilla dropdown.

Possibly KDE bug 301622 is related: the large cursors are very large, much
larger than my text size.

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

[colord-kde] [Bug 372450] New: colord-kde 0.5 does not show any monitor

[bugzilla_noreply]

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

Bug ID: 372450
   Summary: colord-kde 0.5 does not show any monitor
   Product: colord-kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Systems Settings Module (KCM)
  Assignee: dantt...@gmail.com
  Reporter: darkba...@linuxsystems.it
  Target Milestone: ---

OS is Archlinux and I'm using latest version of colord-kde on latest version of
kf5/Plasma. I think colord has some issues with DP-MST monitors, because when
my two Dell U2515H are attached it doesn't recognize any monitor at all in my
laptop: I just see "sysfs-(null)" in the KCM. Today I tried it with a TV using
an HDMI adapter and it did recognize it. I don't know if the problem with
DP-MST is in colord-kde (hardly) or upstream in colord. Can you help me? I
really don't know how to debug it because I really don't know colord.

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

[plasmashell] [Bug 372391] f25 plasma "networks" and "instant messaging" icons are invisible.

[Kevin Kofler]

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

Kevin Kofler  changed:

   What|Removed |Added

   Assignee|k...@davidedmundson.co.uk|visual-des...@kde.org
  Component|general |Theme - Breeze

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

[krita] [Bug 372449] New: Feature Request for a draw while animating feature

[bugzilla_noreply]

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

Bug ID: 372449
   Summary: Feature Request for a draw while animating feature
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: email.sic...@googlemail.com
  Target Milestone: ---

A feature like in the new GameMaker-studio 2 Beta where it is possible to let
the animation run and draw while it is running. A fast was to make really
beautiful animations while it is previewing.

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

[plasmashell] [Bug 372448] Switching back from separate session to 4k monitor crashed plasmashell

[Con Kolivas]

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

--- Comment #2 from Con Kolivas  ---
And this is the backtrace of the second one.

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f439420f8c0 (LWP 26983))]

Thread 13 (Thread 0x7f42ad0ad700 (LWP 27246)):
[KCrash Handler]
#6  0x7f438e8d750d in __strstr_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
#7  0x7f439229aaca in QSGRenderContext::initialize(QOpenGLContext*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f43922be409 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f438f01e7be in QThreadPrivate::start(void*) (arg=0x4224200) at
thread/qthread_unix.cpp:331
#10 0x7f438e10b70a in start_thread (arg=0x7f42ad0ad700) at
pthread_create.c:333
#11 0x7f438e93482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f42b75fe700 (LWP 27005)):
#0  0x7f438e1113b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f438f01fa5b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x378ba60) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f438f01fa5b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x3de8520, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f43922bd92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f43922be1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f438f01e7be in QThreadPrivate::start(void*) (arg=0x3de84a0) at
thread/qthread_unix.cpp:331
#6  0x7f438e10b70a in start_thread (arg=0x7f42b75fe700) at
pthread_create.c:333
#7  0x7f438e93482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f42b7fff700 (LWP 27004)):
#0  0x7f438e1113b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f438f01fa5b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x28b7bf0) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f438f01fa5b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x28abee0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f43922bd92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f43922be1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f438f01e7be in QThreadPrivate::start(void*) (arg=0x28abe60) at
thread/qthread_unix.cpp:331
#6  0x7f438e10b70a in start_thread (arg=0x7f42b7fff700) at
pthread_create.c:333
#7  0x7f438e93482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f42bd771700 (LWP 26996)):
#0  0x7f438e92469d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f438b701740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f42bd770ac0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7f438b701740 in g_wakeup_acknowledge (wakeup=0x7f42cc002750) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gwakeup.c:210
#3  0x7f438b6bde84 in g_main_context_check
(context=context@entry=0x7f42b8000990, max_priority=2147483647,
fds=fds@entry=0x7f42b80048c0, n_fds=n_fds@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3632
#4  0x7f438b6be340 in g_main_context_iterate
(context=context@entry=0x7f42b8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837
#5  0x7f438b6be4ac in g_main_context_iteration (context=0x7f42b8000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x7f438f2557eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f42b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f438f1fcb4a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f42bd770cc0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#8  0x7f438f019834 in QThread::exec() (this=) at
thread/qthread.cpp:503
#9  0x7f42bfc4f7d7 in KCupsConnection::run() () at
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#10 0x7f438f01e7be in QThreadPrivate::start(void*) (arg=0x3bff580) at
thread/qthread_unix.cpp:331
#11 0x7f438e10b70a in start_thread (arg=0x7f42bd771700) at
pthread_create.c:333
#12 0x7f438e93482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f42d5bfe700 (LWP 26993)):
#0  0x7f438e1113b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f438f01fa5b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x292dca0) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f438f01fa5b in QWaitCondition::wait(QMutex*, unsigned long)

[plasmashell] [Bug 372448] Switching back from separate session to 4k monitor crashed plasmashell

[Con Kolivas]

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

--- Comment #1 from Con Kolivas  ---
2 other drkonqi crashes happened at the same time. This is the backtrace of the
first one:

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fc54f5958c0 (LWP 27248))]

Thread 8 (Thread 0x7fc51d188700 (LWP 27258)):
[KCrash Handler]
#6  0x7fc549c5d50d in __strstr_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
#7  0x7fc54d620aca in QSGRenderContext::initialize(QOpenGLContext*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7fc54d644409 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7fc54a3a47be in QThreadPrivate::start(void*) (arg=0x17c3290) at
thread/qthread_unix.cpp:331
#10 0x7fc54949170a in start_thread (arg=0x7fc51d188700) at
pthread_create.c:333
#11 0x7fc549cba82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fc51d989700 (LWP 27257)):
#0  0x7fc546a43ae0 in g_main_context_prepare
(context=context@entry=0x7fc494000990, priority=priority@entry=0x7fc51d988b60)
at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3471
#1  0x7fc546a442cb in g_main_context_iterate
(context=context@entry=0x7fc494000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3820
#2  0x7fc546a444ac in g_main_context_iteration (context=0x7fc494000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#3  0x7fc54a5db7eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc4940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fc54a582b4a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fc51d988c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7fc54a39f834 in QThread::exec() (this=) at
thread/qthread.cpp:503
#6  0x7fc54d5cded6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7fc54a3a47be in QThreadPrivate::start(void*) (arg=0x178e770) at
thread/qthread_unix.cpp:331
#8  0x7fc54949170a in start_thread (arg=0x7fc51d989700) at
pthread_create.c:333
#9  0x7fc549cba82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fc51700 (LWP 27256)):
#0  0x7fc5494973b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc54efecbd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fc54efecc19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fc54949170a in start_thread (arg=0x7fc51700) at
pthread_create.c:333
#4  0x7fc549cba82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fc525f3e700 (LWP 27255)):
#0  0x7fc549caeb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc546a4439c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fc518003070, timeout=, context=0x7fc518000990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7fc546a4439c in g_main_context_iterate
(context=context@entry=0x7fc518000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7fc546a444ac in g_main_context_iteration (context=0x7fc518000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fc54a5db7eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc5180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fc54a582b4a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fc525f3dce0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fc54a39f834 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fc54cc473c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fc54a3a47be in QThreadPrivate::start(void*) (arg=0x14bd6a0) at
thread/qthread_unix.cpp:331
#9  0x7fc54949170a in start_thread (arg=0x7fc525f3e700) at
pthread_create.c:333
#10 0x7fc549cba82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fc528101700 (LWP 27254)):
#0  0x7fc546a88ae4 in g_mutex_unlock (mutex=0x7fc52990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gthread-posix.c:1347
#1  0x7fc546a44356 in g_main_context_iterate
(context=context@entry=0x7fc52990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3842
#2  0x7fc546a444ac in g_main_context_iteration (context=0x7fc52990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#3  0x7fc54a5db7eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc528c0, flags=...) at 

[plasmashell] [Bug 372448] New: Switching back from separate session to 4k monitor crashed plasmashell

[Con Kolivas]

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

Bug ID: 372448
   Summary: Switching back from separate session to 4k monitor
crashed plasmashell
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@kolivas.org
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.8.7-ck7+ x86_64
Distribution: Ubuntu 16.04.1 LTS

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

I had opened a second user session with sddm and after using that session
switched back to the first session with ctrl-alt-F7 and plasmashell had crashed
sometime between switching to and from the other session. The monitor attached
is a 4k monitor which requires two panels setup for each virtual screen that
corresponds to each half of the 4k monitor and one panel tends to regularly
disappear mandating a plasmashell restart which I had performed half a dozen
times already before this crash appeared.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f58f40d98c0 (LWP 27260))]

Thread 8 (Thread 0x7f583dbf7700 (LWP 27270)):
[KCrash Handler]
#6  0x7f58ee7a150d in __strstr_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
#7  0x7f58f2164aca in QSGRenderContext::initialize(QOpenGLContext*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f58f2188409 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f5887be in QThreadPrivate::start(void*) (arg=0x198faf0) at
thread/qthread_unix.cpp:331
#10 0x7f58edfd570a in start_thread (arg=0x7f583dbf7700) at
pthread_create.c:333
#11 0x7f58ee7fe82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f583e3f8700 (LWP 27269)):
#0  0x7f58ee7f2b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f58eb58839c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f5838003060, timeout=, context=0x7f5838000990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f58eb58839c in g_main_context_iterate
(context=context@entry=0x7f5838000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f58eb5884ac in g_main_context_iteration (context=0x7f5838000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f58ef11f7eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f58380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f58ef0c6b4a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f583e3f7c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f583834 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f58f2111ed6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f5887be in QThreadPrivate::start(void*) (arg=0x1a81cd0) at
thread/qthread_unix.cpp:331
#9  0x7f58edfd570a in start_thread (arg=0x7f583e3f8700) at
pthread_create.c:333
#10 0x7f58ee7fe82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f58c5109700 (LWP 27268)):
#0  0x7f58edfdb3b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f58f3b30bd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f58f3b30c19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f58edfd570a in start_thread (arg=0x7f58c5109700) at
pthread_create.c:333
#4  0x7f58ee7fe82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f58c694d700 (LWP 27267)):
#0  0x7f58ee7f2b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f58eb58839c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f58c0003070, timeout=, context=0x7f58c990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f58eb58839c in g_main_context_iterate
(context=context@entry=0x7f58c990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f58eb5884ac in g_main_context_iteration (context=0x7f58c990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f58ef11f7eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f58c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  

[kwin] [Bug 365994] "Titlebar color scheme" window rule is ignored for Aurorae themes

[Mircea Kitsune]

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

--- Comment #2 from Mircea Kitsune  ---
Did anyone get to take a look at this so far? The problem does throw a wrench
in some elements of system customization, as it makes the feature unusable with
the theme I currently have.

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

--- Comment #5 from Mircea Kitsune  ---
For comparison: After restarting Xorg (control + alt + backspace) and logging
back in, Xorg only used about 35 MB. That amount does slowly increase, and it's
hard to tell when it does so legitimately or when it might be the result of a
leak.

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

[plasmashell] [Bug 372386] Cannot select wallpaper in desktop settings

[Maximilian Hartert]

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

Maximilian Hartert  changed:

   What|Removed |Added

 CC||max.hart...@it-top.de

--- Comment #1 from Maximilian Hartert  ---
It is the same for me. I'am also an plasma 5.8.3 with neon.

Changing the "wallpaper type" does seem to make any difference either. But I
don't know what they mean anyway.

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

Mircea Kitsune  changed:

   What|Removed |Added

 CC||sonichedgehog_hyperblast00@
   ||yahoo.com

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

--- Comment #4 from Mircea Kitsune  ---
Created attachment 102220
  --> https://bugs.kde.org/attachment.cgi?id=102220=edit
free

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

--- Comment #2 from Mircea Kitsune  ---
Created attachment 102218
  --> https://bugs.kde.org/attachment.cgi?id=102218=edit
Screenshot

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

--- Comment #3 from Mircea Kitsune  ---
Created attachment 102219
  --> https://bugs.kde.org/attachment.cgi?id=102219=edit
top

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

[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

--- Comment #1 from Mircea Kitsune  ---
Created attachment 102217
  --> https://bugs.kde.org/attachment.cgi?id=102217=edit
Screenshot

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

[plasmashell] [Bug 372447] New: Plasma 5 causes memory leak in Xorg

[Mircea Kitsune]

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

Bug ID: 372447
   Summary: Plasma 5 causes memory leak in Xorg
   Product: plasmashell
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sonichedgehog_hyperblas...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

After approximately two days of uptime, Xorg starts consuming more memory than
it normally should. Xorg usually reaches over 200 MB, and if modifying
plasmoids or restarting the 'plasmashell' process frequently it can even go
over 400 MB!

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

[digikam] [Bug 372427] Some pictures do not display

[Mick Sulley]

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

--- Comment #2 from Mick Sulley  ---
(In reply to Maik Qualmann from comment #1)
> Do you use a MySQL or SQLite DB?
> 
> Maik

SQLite

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[Kusi]

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

--- Comment #2 from Kusi  ---
The sql command in question

  ALTER TABLE Albums 
  ADD CONSTRAINT Albums_AlbumRoots 
  FOREIGN KEY (albumRoot) 
  REFERENCES AlbumRoots (id) ON DELETE CASCADE ON UPDATE CASCADE, ADD UNIQUE
(albumRoot, relativePath(250)), ENGINE InnoDB;

runs fine without specifying the engine, that is without "ENGINE InnoDB". On my
db, according to

  SHOW TABLE STATUS FROM digikamdb;

the "Albums" table is of engine type MyISAM, not InnoDB. Is that new db engine
format wanted? Is it ok to change the engine of an existing table? It looks
like I have inconsistent engine types over all my tables (mixture between
MyISAM and InnoDB).

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

[krita] [Bug 372445] File corrupted: "not a valid krita file"

[bugzilla_noreply]

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

--- Comment #1 from doubleotrou...@hotmail.com ---
Created attachment 102216
  --> https://bugs.kde.org/attachment.cgi?id=102216=edit
The .kra file in question

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

[kajongg] [Bug 372425] Does not work with PyQt5 ?

[Sovxx]

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

--- Comment #3 from Sovxx  ---
OK, thank you

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

[plasmashell] [Bug 372446] New: Dual-screen desktop crash after ejecting the optical disk

[Sylvain]

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

Bug ID: 372446
   Summary: Dual-screen desktop crash after ejecting the optical
disk
   Product: plasmashell
   Version: 5.8.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bond.never@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I just clicked on the 'eject' button in the notification area to eject the
optical disk from the reader device. Then, I was prompt for the root password,
I entered it and clicked on OK. While removing the ejected disk, the desktop
crashed.

- Unusual behavior I noticed:
After crashing, the desktop reloaded itself and an icon notifying that a crash
occured appeared in the notification area. I also noticed that the wallpaper of
my second monitor was rested to KDE's default (but not the wallpaper of the
primary screen) and when I open back my browser (chromium), all my tabs were
closed and I wasn't prompted to retore my previous session after a crash (witch
was the expected behavior). I know that Chromium has nothing to do with KDE but
maybe the behavior is symptomatic of something ...

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

Thread 44 (Thread 0x7f5a7d17e700 (LWP 6471)):
#0  0x7f9bd9a3a48d in poll () at /usr/lib/libc.so.6
#1  0x7f9bce95b121 in  () at /usr/lib/libpulse.so.0
#2  0x7f9bce94c8f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7f9bce94cf8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f9bce94d040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f9bce95b069 in  () at /usr/lib/libpulse.so.0
#6  0x7f9bce2ebed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7f9bd923d454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9bd9a437df in clone () at /usr/lib/libc.so.6

Thread 43 (Thread 0x7f5a7e47f700 (LWP 6406)):
#0  0x7f9bd924310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9bda12ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f9bde09a395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f9bde09ac8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f9bda12dd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f9bd923d454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f9bd9a437df in clone () at /usr/lib/libc.so.6

Thread 42 (Thread 0x7f9a80ff9700 (LWP 6017)):
#0  0x7f9bd924310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9bda12ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f9b15dd31c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f9b15dd7988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f9b15dd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f9b15dd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f9b15dd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f9b15dd51f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f9bda12dd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f9bd923d454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f9bd9a437df in clone () at /usr/lib/libc.so.6

Thread 41 (Thread 0x7f9a817fa700 (LWP 6016)):
#0  0x7f9bd924310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9bda12ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f9b15dd31c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f9b15dd7988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f9b15dd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f9b15dd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f9b15dd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f9b15dd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f9b15dd2263 in

[ktorrent] [Bug 358929] Script interpreter cannot be found, but kross is installed

[Remy Glaser]

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

--- Comment #3 from Remy Glaser  ---
(In reply to Alexander Potashev from comment #2)
> If you use a Qt4-based application, it can only use a Qt4-based version of
> Kross, and it will only support Qt4-based Kross interpreter plugins.
> Specifically, kross-0.1 cannot load e.g. krosspython-16.04.1.
> 
> What version of krosspython did you have the problem with?

Thank you for your answer!

After doing a clean reinstall of Kubuntu 16.10, I was checking back into this
problem, hoping it would be fixed by now.
The current package version of krosspython is 4:15.12.3-0ubuntu1. The module is
installed in /usr/lib/x86_64-linux-gnu/qt5/plugins/krosspython.so, so it seems
this is a qt5 version.

I fixed the issue by downloading version 4.13.1-0ubuntu0.1, which is included
in ubuntu 14.04.5, from packages.ubuntu.com and then extracting krosspython.so
and copying it to /usr/lib/kde4/

This works, but it doesn’t seem to be a very user-friendly solution. There
should be a krosspython-qt4 package in ubuntu as a dependency of ktorrent.

This has been broken for a year now. Apparently I’m the only person using
Ktorrent scripts in a recent ubuntu version.

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

[digikam] [Bug 366567] Allow choosing several duplicate results [patch]

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/131b3009cb03f7b4fae1e18
   ||f6aa0eaaa0741bc22
 Resolution|--- |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Git commit 131b3009cb03f7b4fae1e18f6aa0eaaa0741bc22 by Gilles Caulier.
Committed on 13/11/2016 at 21:23.
Pushed by cgilles into branch 'master'.

Apply patch #102207 to permit multiple selection in duplicates search albums
list-view.
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +19   -12   libs/database/dbjobs/dbjob.cpp
M  +9-4libs/database/dbjobs/dbjobinfo.cpp
M  +3-2libs/database/dbjobs/dbjobinfo.h
M  +9-6libs/models/imagealbummodel.cpp
M  +1-1utilities/fuzzysearch/findduplicatesalbum.cpp
M  +14   -6utilities/fuzzysearch/findduplicatesview.cpp
M  +1-1utilities/fuzzysearch/findduplicatesview.h

http://commits.kde.org/digikam/131b3009cb03f7b4fae1e18f6aa0eaaa0741bc22

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

[digikam] [Bug 366567] Allow choosing several duplicate results [patch]

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Allow choosing several  |Allow choosing several
   |duplicate results   |duplicate results [patch]

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[bugzilla_noreply]

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

--- Comment #33 from caulier.gil...@gmail.com ---
Arnaud,

Yes, it's planed to include it for next 5.4.0 if Jan complete it in time, which
will be the case as 80% of the patch is already done...

Gilles Caulier

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

[digikam] [Bug 372442] Ordering of duplicates search by the result count is done lexicographically [patch]

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/44bddf39a72ea22f3e2e422
   ||82a0550f7a19cea1e
 Resolution|--- |FIXED

--- Comment #1 from caulier.gil...@gmail.com ---
Git commit 44bddf39a72ea22f3e2e42282a0550f7a19cea1e by Gilles Caulier.
Committed on 13/11/2016 at 21:15.
Pushed by cgilles into branch 'master'.

apply patch #102214 to Duplicates search albums ordering when count of items is
enabled.
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +4-0utilities/fuzzysearch/findduplicatesalbumitem.cpp

http://commits.kde.org/digikam/44bddf39a72ea22f3e2e42282a0550f7a19cea1e

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[Arnaud]

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

Arnaud  changed:

   What|Removed |Added

 CC||arn...@croes.be

--- Comment #32 from Arnaud  ---
Are there plans to implement this patch in the official release? I am using
Philip's PPA repository to stay up-to-date with my digikam5 version. It would
be cool to have it included there, and avoid manual patching work. I am also
having an extremely slow Digikam experience because of @eadir folders on the
nfs mounted Synology. Some time ago I just deleted all those system generated
folders, but recently had them rebuild. I would much rather have an exclude
filter on the collection discovery. Thanks, Arnaud

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

[digikam] [Bug 372427] Some pictures do not display

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Do you use a MySQL or SQLite DB?

Maik

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

[krita] [Bug 372445] New: File corrupted: "not a valid krita file"

[bugzilla_noreply]

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

Bug ID: 372445
   Summary: File corrupted: "not a valid krita file"
   Product: krita
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: doubleotrou...@hotmail.com
  Target Milestone: ---

I saved the file as well as turned it off, but later on my computer restarted,
and now the file is corrupted. I've attached the file here if anyone could
possibly restore it-- i've already spent hours upon hours on it, and had just
finished the flat colour, hoping to start the shading when I found the file
corrupted. I would really, really appreciate if someone could try to fix this
file!!!

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

[digikam] [Bug 372442] Ordering of duplicates search by the result count is done lexicographically [patch]

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Ordering of duplicates  |Ordering of duplicates
   |search by the result count  |search by the result count
   |is done lexicographically.  |is done lexicographically
   ||[patch]
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 372433] Reduce debug messages from databaseserver with internal mysql

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/48d3f2c983864d4487c4668
   ||442ff105e8610c571

--- Comment #3 from Maik Qualmann  ---
Git commit 48d3f2c983864d4487c4668442ff105e8610c571 by Maik Qualmann.
Committed on 13/11/2016 at 20:28.
Pushed by mqualmann into branch 'master'.

print running time message all 30 seconds from internal MySQL server
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +11   -2libs/database/server/databaseserver.cpp

http://commits.kde.org/digikam/48d3f2c983864d4487c4668442ff105e8610c571

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

[peruse] [Bug 372444] New: While initially fit to height, the view changes to fit to width once you resize the window.

[bugzilla_noreply]

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

Bug ID: 372444
   Summary: While initially fit to height, the view changes to fit
to width once you resize the window.
   Product: peruse
   Version: 1.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: bode...@gmail.com
  Target Milestone: ---

Straightforward enough, I think. As soon as you go fullscreen or resize the
window, the image resizes to fit the width.

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

[digikam] [Bug 372433] Reduce debug messages from databaseserver with internal mysql

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
Typically, "digikam.databaseserver: Waiting 1 seconds..." is wrapped by
qCDebug(namespace) macro, where namepace is a debug space ID which can be
disable at run time. But for the moment, i don't find a simpler way to do it,
as we can do with 4.x release through kdebugdialog (which of course do not work
with 5.x now).

http://doc.qt.io/qt-5/qloggingcategory.html

Gilles Caulier

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[bugzilla_noreply]

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

--- Comment #14 from caulier.gil...@gmail.com ---
A good start is to explore the DigiKam namespace and the doxygen documentation
relevant.

https://api.kde.org/extragear-api/graphics-apidocs/digikam/html/namespaceDigikam.html

The class names are identical than cpp file names everywhere.

Each classes are hosted in subdirectory by functions, as image container,
database interface, filters, widgets, etc...

Please give me more info about what you search exactly in source code.

Gilles Caulier

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

[kwin] [Bug 372443] New: Kwin crash when pressing alt tab using cover switch

[Alden Weddleton]

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

Bug ID: 372443
   Summary: Kwin crash when pressing alt tab using cover switch
   Product: kwin
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alden.weddle...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: KDE neon User Edition 5.8

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

Opening Kmail via the application menu.  I believe it crashed when I hit alt
tab.  Was using the cover switch type.  After the crash the switch method being
used is breeze.  The setting menu still shows cover switch as the primary
method and breeze as the alternate method.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
[Current thread is 1 (Thread 0x7f136d01b900 (LWP 1693))]

Thread 7 (Thread 0x7f134efd1700 (LWP 3671)):
#0  0x7f136cb08b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f136a9e86da in qt_safe_poll(pollfd*, unsigned long, timespec const*)
(__timeout=, __nfds=1, __fds=0x7f134fc8) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7f136a9e86da in qt_safe_poll(pollfd*, unsigned long, timespec const*)
(timeout_ts=0x0, nfds=1, fds=0x7f134fc8) at kernel/qcore_unix.cpp:93
#3  0x7f136a9e86da in qt_safe_poll(pollfd*, unsigned long, timespec const*)
(fds=0x7f134fc8, nfds=nfds@entry=1, timeout_ts=timeout_ts@entry=0x0) at
kernel/qcore_unix.cpp:112
#4  0x7f136a9e9fb8 in
QEventDispatcherUNIX::processEvents(QFlags)
(this=, flags=...) at kernel/qeventdispatcher_unix.cpp:495
#5  0x7f136a997d9a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f134efd0ca0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7f136a7bd044 in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7f13659c6685 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f136a7c1c28 in QThreadPrivate::start(void*) (arg=0x14510d0) at
thread/qthread_unix.cpp:344
#9  0x7f136686270a in start_thread (arg=0x7f134efd1700) at
pthread_create.c:333
#10 0x7f136cb1482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f133d529700 (LWP 2439)):
[KCrash Handler]
#6  0x7f136ca43428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f136ca4502a in __GI_abort () at abort.c:89
#8  0x7f136a7a8811 in QMessageLogger::fatal(char const*, ...) const
(context=..., message=) at global/qlogging.cpp:1680
#9  0x7f136a7a8811 in QMessageLogger::fatal(char const*, ...) const
(this=, msg=) at global/qlogging.cpp:793
#10 0x7f13541d0194 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#11 0x7f136a9c4f36 in QMetaObject::activate(QObject*, int, int, void**)
(a=0x7f133d528800, r=0x13db2c0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:130
#12 0x7f136a9c4f36 in QMetaObject::activate(QObject*, int, int, void**)
(sender=sender@entry=0x13db2c0, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3723
#13 0x7f136a9c5577 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x13db2c0, m=m@entry=0x7f136abe4720
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3602
#14 0x7f136aa3d790 in QTimer::timeout(QTimer::QPrivateSignal)
(this=this@entry=0x13db2c0) at .moc/moc_qtimer.cpp:198
#15 0x7f136a9d14e8 in QTimer::timerEvent(QTimerEvent*) (this=0x13db2c0,
e=) at kernel/qtimer.cpp:254
#16 0x7f136a9c5a93 in QObject::event(QEvent*) (this=0x13db2c0, e=) at kernel/qobject.cpp:1285
#17 0x7f136b28589c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x13db2c0, e=0x7f133d528b20) at
kernel/qapplication.cpp:3799
#18 0x7f136b28d296 in QApplication::notify(QObject*, QEvent*)
(this=0x7ffcccb8c020, receiver=0x13db2c0, e=0x7f133d528b20) at
kernel/qapplication.cpp:3556
#19 0x7f136a999da8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x13db2c0, event=event@entry=0x7f133d528b20) at
kernel/qcoreapplication.cpp:988
#20 0x7f136a9ec23e in QTimerInfoList::activateTimers()
(event=0x7f133d528b20, receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#21 0x7f136a9ec23e in QTimerInfoList::activateTimers()
(this=this@entry=0x7f13340af1c0) at kernel/qtimerinfo_unix.cpp:644
#22 0x7f136a9e903c in QEventDispatcherUNIXPrivate::activateTimers()

[krunner] [Bug 372017] Krunner chrashes on every input

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #3 from Kai Uwe Broulik  ---
Marco, all the WindowedWidgetsRunner does is iterating over
Plasma::PluginLoader::self()->listAppletMetaData(QString()) - I could surely
have it check for KPluginMetaData isValid but why does that list contain
invalid applets in the first place?

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

[krunner] [Bug 372017] Krunner chrashes on every input

[Kai Uwe Broulik]

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

--- Comment #2 from Kai Uwe Broulik  ---
Thanks for your bug report. Until we figure it out it should help if you
disable the "Windowed Widgets" or "Standalone Widgets" plugin in KRunner
settings.

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

[krunner] [Bug 372017] Krunner chrashes on every input

[Luca Giambonini]

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

Luca Giambonini  changed:

   What|Removed |Added

 CC||luc...@bluewin.ch

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

[krunner] [Bug 372017] Krunner chrashes on every input

[Luca Giambonini]

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

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

krunner (5.8.3) using Qt 5.7.0

when typing something krunner crash, not immediately but after 3/4 characters,
even with math expression (like =1+1) is the same

-- Backtrace (Reduced):
#6  0x7fbf0acc31d8 in KSycocaEntry::name() const () from
/usr/lib/libKF5Service.so.5
#7  0x7fbedaef63d4 in WindowedWidgetsRunner::match (this=0x1312ad0,
context=...) at
/chakra/core/plasma-workspace/src/plasma-workspace-5.8.3/runners/windowedwidgets/windowedwidgetsrunner.cpp:66
#8  0x7fbee6c07368 in Plasma::AbstractRunner::performMatch (this=0x1312ad0,
localContext=...) at
/chakra/core/krunner/src/krunner-5.28.0/src/abstractrunner.cpp:131
#9  0x7fbee69e6b37 in ThreadWeaver::Executor::run (this=,
job=..., thread=) at
/chakra/core/threadweaver/src/threadweaver-5.28.0/src/executor.cpp:52
#10 0x7fbee69e57d0 in ThreadWeaver::Job::execute (this=,
self=..., th=0x1177d60) at
/chakra/core/threadweaver/src/threadweaver-5.28.0/src/job.cpp:83

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

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

[Philippe Waroquiers]

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

--- Comment #5 from Philippe Waroquiers  ---
(In reply to Christopher Smith from comment #4)
> (In reply to Philippe Waroquiers from comment #3)
> > If your new/delete operators will have the 'normal/expected' semantic,
> > then why would the Valgrind replacement create a problem ?
> > Or, in other words, what is special in your operators that make them
> > non replaceable ?
> > You lose a lot of Valgrind functionalities if you do not replace
> > the heap functions.
> 
> Certain parts of my program do a lot of allocation/deallocation. I plan on
> adding a sort of "cache" for same sized sections of memory to prevent having
> to run malloc each time. Although I suppose this is purely a performance
> optimization and can be omitted during testing.
If the only thing that your replacement functions are doing is to do a
(local) cache of small objects, then it should be no problem
to have them replaced by Valgrind, and then benefit from all the Valgrind
features (leak search, redzone protection, etc).
It is only when your specific heap does very special actions
(such as for example releasing all small blocks at once) that
no replacement should be done. For such special heaps, you then must
use the various *MEMPOOL* requests to allow valgrind to (somewhat)
understand your specific heap.

> 
> For now, I'll use `--show-mismatched-frees=no`. I'm looking forward to this
> fix.

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

[digikam] [Bug 372433] Reduce debug messages from databaseserver with internal mysql

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Increasing the wait time is not good. DigiKam now needs 60 seconds in the worst
case until it finishes completely.

Maik

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[Albert Vaca]

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

--- Comment #5 from Albert Vaca  ---
Oh, and about the UI... I'm not sure what's the best way to present it to the
user on the desktop, but the text field in the plasmoid probably works. About
the phone side, registering it as a keyboard is the only choice available that
I'm aware of. I'm not sure if it's even possible to make it work when the
keyboard is not shown, but that would be even better.

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[Albert Vaca]

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

--- Comment #4 from Albert Vaca  ---
[continues previous comment] makes sense for capabilities to be able to disable
the part that is actually not available without disabling other features that
do work (that's what happens if we put more than one feature in the same
plugin). 

Sent from a phone, excuse typos!

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[Albert Vaca]

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

--- Comment #3 from Albert Vaca  ---
I think this is a needed addition to kdeconnect. About the format of the
packets, ideally it should be the same as the one used for desktop to phone
communication. This way, it will work desktop to desktop (eg:sending keys to a
Raspberry from my main desktop) and phone to phone too. Splitting it in
separate plugins makes sense from

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

[okular] [Bug 300992] Searching for a phrase does not find occurences split by a line break / newline in Pdf

[Marduk]

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

Marduk  changed:

   What|Removed |Added

 CC||mardu...@mac.com

--- Comment #15 from Marduk  ---
This bug is still not fixed (at least in the version included in Ubuntu 16.04).
Try searching for "viewed on" in this file
http://www.pdf995.com/samples/pdf.pdf

Firefox's JS-based PDF viewer does find the phrase.

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

[digikam] [Bug 372442] Ordering of duplicates search by the result count is done lexicographically.

[Mario Frank]

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

Mario Frank  changed:

   What|Removed |Added

 CC||mario.fr...@uni-potsdam.de

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

[digikam] [Bug 372164] Camera related photograph properties are unavailable (erroneously)

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/309a9f2865b18f082d0c0fd
   ||37148c7867f3e0cc9
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Maik Qualmann  ---
Git commit 309a9f2865b18f082d0c0fd37148c7867f3e0cc9 by Maik Qualmann.
Committed on 13/11/2016 at 19:21.
Pushed by mqualmann into branch 'master'.

fix displaying from camera make and model in the properties sidebar with MySQL
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-0libs/dmetadata/metaengine_exif.cpp

http://commits.kde.org/digikam/309a9f2865b18f082d0c0fd37148c7867f3e0cc9

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

[kmail2] [Bug 364967] Kmail message list does not remember rightmost column width

[m4ngust]

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

m4ngust  changed:

   What|Removed |Added

 CC||m4ng...@gmail.com

--- Comment #1 from m4ngust  ---
I'm facing same issue. The rightmost column width is maximized whereas all
other columns are set at the minimum. It is a bit difficult to trace. If
developers can point out how to log this gui issue - would be great!
Thanks!

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

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

[Christopher Smith]

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

--- Comment #4 from Christopher Smith  ---
(In reply to Philippe Waroquiers from comment #3)
> If your new/delete operators will have the 'normal/expected' semantic,
> then why would the Valgrind replacement create a problem ?
> Or, in other words, what is special in your operators that make them
> non replaceable ?
> You lose a lot of Valgrind functionalities if you do not replace
> the heap functions.

Certain parts of my program do a lot of allocation/deallocation. I plan on
adding a sort of "cache" for same sized sections of memory to prevent having to
run malloc each time. Although I suppose this is purely a performance
optimization and can be omitted during testing.

For now, I'll use `--show-mismatched-frees=no`. I'm looking forward to this
fix.

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

[digikam] [Bug 372442] New: Ordering of duplicates search by the result count is done lexicographically.

[Mario Frank]

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

Bug ID: 372442
   Summary: Ordering of duplicates search by the result count is
done lexicographically.
   Product: digikam
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Searches-Fuzzy
  Assignee: digikam-de...@kde.org
  Reporter: mario.fr...@uni-potsdam.de
  Target Milestone: ---

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

When ordering the results of a duplicate search by the result count, the
ordering is done lexicographically. Thus, the order by count is 2, 20, 21, ...,
for example.

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

[konsole] [Bug 372441] New: Konsole Desktop file missing StartupWMClass

[Davide Olianas]

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

Bug ID: 372441
   Summary: Konsole Desktop file missing StartupWMClass
   Product: konsole
   Version: 16.08.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: n...@davideolianas.com
  Target Milestone: ---

This bug is the same as https://bugs.kde.org/show_bug.cgi?id=350793 but for the
konsole package.

The .desktop file misses "StartupWMClass=konsole" which fixes bad behaviour
with gnome dash (see https://bugzilla.gnome.org/show_bug.cgi?id=774353).

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[Mario Frank]

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

--- Comment #13 from Mario Frank  ---
Hey Gilles,
by the wiring (of components), I mean the connection of signals to slots. The
lack on information about which class is the correct view in which situation
makes it complicated for me to get find out where to set a hook and trigger
specific updates. Is there some dev documentation going into the details of the
implementation?

Hey Simon,

I can open a bug then and submit the patch.

Cheers,
Mario

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[bugzilla_noreply]

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

--- Comment #12 from caulier.gil...@gmail.com ---
yes a separate file will be fine...

Gilles Caulier

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

[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults

[Tim Eberhardt]

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

--- Comment #7 from Tim Eberhardt  ---
On a current Tumbleweed the problem is not gone but it gets better:

The crash is gone. The on some occasions unexpected behavior is not fully
fixed. Docking/undocking and starting with different screen configurations
still sometimes results in black screens or not right positioned or overlapped
panels.

plasma 5.8.3
frameworks 5.28.0
Qt 5.7.0

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[Mario Frank]

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

--- Comment #11 from Mario Frank  ---
I do not know how the developers opinions are. But I think what you see is part
of the problem described in bug 372217 . I already adressed the lexicographical
ordering of the simmilarity. I will provide a patch for your problem at the
site for bug 372217.

Cheers,
Mario

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[Simon]

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

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com

--- Comment #10 from Simon  ---
I just discovered that there is also an issue with the duplicate count
ordering. It is done lexicographically not mathematically (e.g. 10 is before
2). I thought this is probably related, if I should open a separate bug, please
say so.

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