[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

[via KDE Bugzilla]

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

--- Comment #12 from a.skemb...@gmail.com ---

I was informed I came across this bug, see
https://forum.kde.org/viewtopic.php?f=111=130565 for the investigation that
took place.

In order to reproduce the bug consistently, using an aurorae-based theme and a
dual monitor set up, I do the following:

1) Open a VM in Virtualbox in the second monitor and close Virtualbox Manager
so that only the VM window is in the second monitor, maximized.
2) Open Firefox (via taskbar icon).

Firefox will try to open on the main monitor and kwin will crash, with no
DrKonqi to help out. Breeze decorations don't have this problem.

The VM window needs to be the last active window before opening firefox,
otherwise it's not triggered.

I have attached a backtrace using gdb, but some symbols are missing, not sure
from which packages.

I am on OpenSUSE Tumbleweed, with KWin 5.5.3. Can reproduce consistently on
Intel graphics laptop and ATI graphics desktop.

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working on video files

[Evert Vorster via KDE Bugzilla]

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

--- Comment #4 from Evert Vorster  ---
Hmm, hitting refresh on an album with photos in does indeed refresh the
thumbnails of the photos, but not videos, so this behaviour is specific to
video clips. 

So, how can I tell DigiKam to re-do one thumbnail of a video clip?

Opening the folder in Dolphin shows the correct thumbnail, so DigiKam has a
thumbnail cached somewhere, and in this case it's for the wrong clip.

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

[krita] [Bug 333169] Bigger thumbnails option for predefined brushes

[JayJay via KDE Bugzilla]

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

--- Comment #2 from JayJay  ---
The thumbnails are big enough now, I think

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

[krita] [Bug 333168] Cutout filter like Photoshop

[JayJay via KDE Bugzilla]

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

--- Comment #2 from JayJay  ---
This was a request for making option in Krita to get random abstractions from
one image so shape generations can be quick and fun. I think Wolthera mentioned
in the forums that I shud be able to get similar results with Inkscape
converting bitmap to vector (dont remember exactly) and I did try that, it was
okay but not great, a fast slider that 'messes up' the image and gets more and
more abstract wud be great...this isnt the most necessary thing but cud be
greatAlso Krita cud make something different than PS, of course feedback
more users wud be useful...

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

[kwin] [Bug 358566] Trippe clicking window title shades again

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
"triple" ;-)

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

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[André Marcelo Alvarenga via KDE Bugzilla]

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

André Marcelo Alvarenga  changed:

   What|Removed |Added

 CC||alvare...@kde.org

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

[krita] [Bug 358422] Deleted layer content reappears after select.

[Piotr via KDE Bugzilla]

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

--- Comment #8 from Piotr  ---
May it be that published windows build is bad? I don't know how to help
further.

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

[kmymoney] [Bug 358579] New: Node was not TRANSACTION dans le fichier e:\r\build\extragear\kmymoney-4.6.1-20110918\work\kmymoney-4.7.2\kmymoney\mymoney\mymoneytransaction.cpp à la ligne 53

[MGR via KDE Bugzilla]

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

Bug ID: 358579
   Summary: Node was not TRANSACTION dans le fichier
e:\r\build\extragear\kmymoney-4.6.1-20110918\work\kmym
oney-4.7.2\kmymoney\mymoney\mymoneytransaction.cpp à
la ligne 53
   Product: kmymoney
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: mgr...@aol.com

Node was not TRANSACTION dans le fichier
e:\r\build\extragear\kmymoney-4.6.1-20110918\work\kmymoney-4.7.2\kmymoney\mymoney\mymoneytransaction.cpp
à la ligne 53

Reproducible: Always


Actual Results:  
Entering QIF files to fill up a new count manager,when I work the counts to
exit the faults and duplications

Expected Results:  
A pop up box telling the problem, then closing the programm. And after,
impossible to open a count.

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

Summary|Maintenance tool rebuild|Maintenance tool rebuild
   |thumbnails not working for  |thumbnails directory filter
   |video files |not working

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

[kdenlive] [Bug 358583] New: Gt Master 2016-01-26 - cannot make a proxy of a stabilised .mlt file.

[Evert Vorster via KDE Bugzilla]

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

Bug ID: 358583
   Summary: Gt Master 2016-01-26 - cannot make a proxy of a
stabilised .mlt file.
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: evert.vors...@yandex.com

I work with proxy clips, as my filter stacks are big, and my footage bigger. 

I have just discovered that one can't make a proxy clip of a stabilised .mlt
file, but it might be true of all .mlt files. 

Seeing as how .mlt files already introduce an overhead, having a proxy of such
a file would be a good thing, unless it's not supported at all, and then one
should not have the option of making a proxy of an .mlt file. 

Here is a short clip, showing the issue:

https://youtu.be/5BN7-Ek5cWk

Reproducible: Always

Steps to Reproduce:
1. Run "vidstab" on a clip
2. Add the output .mlt file to the project. 
3. Notice that even though "Generate proxies by default" is selected, no proxy
is generated.
4. Manually generate a proxy

Actual Results:  
Proxy generation fails with "Clip is invalid"

Expected Results:  
Either a proxy clip of the .mlt file, or the proxy clip option greyed out.

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

[krita] [Bug 352519] Delete, cut copy and paste recursively from a group or multiple selected layer

[Dmitry Kazakov via KDE Bugzilla]

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

--- Comment #6 from Dmitry Kazakov  ---
WISHGROUP: Stretchgoal : up to a couple of weeks or a month of work

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working on video files

[via KDE Bugzilla]

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

--- Comment #5 from caulier.gil...@gmail.com ---
digiKam do not share thumbnail with the rest of KDE. It use a dedicated
database with waveltes compression to optimize space and support removable
media.

Gilles Caulier

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

[kmymoney] [Bug 358573] Unable to enter fraction part when decimal point of current locale differs from "."

[Alexey Chernov via KDE Bugzilla]

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

--- Comment #1 from Alexey Chernov <4er...@gmail.com> ---
Here's a review request for it: https://git.reviewboard.kde.org/r/126888

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

[plasmashell] [Bug 358575] New: Cannot drag again after a drop

[Elvis Angelaccio via KDE Bugzilla]

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

Bug ID: 358575
   Summary: Cannot drag again after a drop
   Product: plasmashell
   Version: 5.5.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: elvis.angelac...@kdemail.net
CC: plasma-b...@kde.org

Let's say you have a bunch of icons under Favorites, and you want to sort them
by drag-and-drop.

Reproducible: Always

Steps to Reproduce:
1. Drag and drop the first of those icons to the intended position
2. Move the mouse towards the next icon that you want to move


Actual Results:  
The target icon is not "highlighted" on mouse hover and cannot be chosen for
drag-and-drop. Neither are the other icons, except the one that was dropped in
step 1.

Expected Results:  
All the icons should be highlighted on mouse hover, so that they could be
dragged and dropped.

There are workarounds, e.g. click anywhere the Kickoff panel. But it would be
nice if this could be fixed.

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

[kdeplasma-addons] [Bug 355190] copy current date/time into clipboard

[via KDE Bugzilla]

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

--- Comment #8 from cher...@aip.de ---
My most frequent usecases. Usual click flows for these in KDE 4 was right click
on clock - copy date (there were a lot of formats, even chinese year and so
on... but I used only two of them).

- I create a folder, and I want to have that folder having the current date in
-MM-DD. 

- I create a journal entry in my journal (text file) - heading should be
"hh:mm, weekday, DD(st/nd/rd/th) month, YEAR"

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

[Breeze] [Bug 358578] Active window taskbar entry background too bright in Breeze Dark theme

[Radics Péter via KDE Bugzilla]

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

--- Comment #1 from Radics Péter  ---
Created attachment 96848
  --> https://bugs.kde.org/attachment.cgi?id=96848=edit
proposed tasks decortation for breeze-dark theme

Feel free to use the attached tasks.svgz if you think it's an improvement for
breeze-dark.

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

[plasmashell] [Bug 349557] Notifications with Dual Screen and Konversation

[Nick Cross via KDE Bugzilla]

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

--- Comment #8 from Nick Cross  ---
>From what I can see the notifications are appearing on the desktop with the
panel. There are still quirks with multiscreen handling (screen waking up etc)
but that is unrelated to this issue. Thanks!

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

[Breeze] [Bug 358576] Default and Breeze color scheme have different window decoration colors

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
@Kai: should be defined in kdeglobals on section WM.

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

[Kubuntu Notifications Helper] [Bug 358572] New: Notifications and jobs do not store any notifications in Plasma 5

[vitoriung via KDE Bugzilla]

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

Bug ID: 358572
   Summary: Notifications and jobs do not store any notifications
in Plasma 5
   Product: Kubuntu Notifications Helper
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: vitori...@gmail.com

After upgrade from Kubuntu 14.10  to Plasma 5 (Kubuntu 15.04 -> recently to
Kubuntu 15.10)
the notification applet does not store any notifications, the pop-ups work
fine, but when I am not at the computer, I don't have chance to see any
notification that popped up when I was away. Even when I am at the computer I
miss some notifications if I do not look fast enough as  they pop up for 5
seconds only.

If I click on notifications, I always see message "No new notifications", I
should fin there at least messages from Konversation, which I configured to
receive notification for private messages.

It worked fine previously in Kubuntu 14.10 but since I upgraded it never worked
for me.

Reproducible: Always

Steps to Reproduce:
1. Receive notification (eg. via Konvesration)
2. Click on Notification applet
3. See "No new notifications"

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

[Breeze] [Bug 358576] Default and Breeze color scheme have different window decoration colors

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Kai Uwe Broulik  ---
I couldn't figure out where to set the decoration color in KColorScheme. I
think the Breeze theme sets additional config entries for KWin.

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

[digikam] [Bug 358577] New: Git master 2016-01-10 - Maintenance tool filters not working

[Evert Vorster via KDE Bugzilla]

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

Bug ID: 358577
   Summary: Git master 2016-01-10 - Maintenance tool filters not
working
   Product: digikam
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: evert.vors...@yandex.com

I have serious issues with thumbnails, both in the QT4 version of digikam, and
the recent beta. 
I have noticed this specific bug before in the QT4 version, but since the QT5
version of digikam is slightly better at thumbnailing, I have uploaded a clip
showing the issue here. 

https://youtu.be/1Mse6guHoro

In short, I can see that one of the thumbnails for a clip is wrong. I suspect
that the clip got the wrong thumbnail due to a race condition that I created
when importing from two sources at once. ( I don't suppose many people hit this
bug )

Pressing F5 while the album is selected I would expect to see a refresh of that
album, but that does not work. 
I then go into the maintenance tools, and select just that folder, and "rebuild
thumbnails" When I then click OK, the process returns instantly, and the
folder's thumbnails are not updated. 

Since I have terabytes of pictures and video, I am reluctant to rebuild the
entire thumbnail database. 

Reproducible: Always

Steps to Reproduce:
1. Select Maintenance tools. 
2. Select one folder only, no tags. 
3. Select "Rebuild Thumbnails"
4. Select "OK"

Actual Results:  
Thumbnails for the selected folder are not re-built

Expected Results:  
Re-built thumbnails. 

I am running on Arch Linux, and rebuilding digikam from git is no sweat, so I
am willing to test any fixes almost as soon as they hit git.

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

[kdev-python] [Bug 355094] Kdevelop unresponsive, possibly hang, when editing python 2.x code

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

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

--- Comment #22 from Sven Brauch  ---


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

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

[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||p.v.niek...@hccnet.nl

--- Comment #2 from Sven Brauch  ---
*** Bug 355094 has been marked as a duplicate of this bug. ***

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

[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Sven Brauch  ---
Good find, that is certainly the same as bug 355094. I'll look into it now that
I have more specific information.

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails not working for video files

[via KDE Bugzilla]

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

--- Comment #2 from caulier.gil...@gmail.com ---
video files support is delegate to Qt5::Multimedia. There is no code in digiKam
to handle video file directly.

It know that  Qt5::Multimedia has problem with GStreamer. It must be fixed with
qt 5.5.x

Gilles Caulier

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

[calligrawords] [Bug 358581] New: Calligra word crashes on trying to print web page from Konqueror

[Hannu Lehtimäki via KDE Bugzilla]

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

Bug ID: 358581
   Summary: Calligra word crashes on trying to print web page from
Konqueror
   Product: calligrawords
   Version: 2.9.7
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: hannu.lehtim...@iki.fi

Application: calligrawords (2.9.7)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Prerequisites
Operating system: Kubuntu 15.10
Installed Calligra suite from binary distributions of ubuntu
Version of Calligra words was 2.9.7

Steps to reproduce
1 Launch Konqueror
2. At Konqueror, navigate to some web site (e.g.
http://wiki.freepascal.org/Main_Page)
3. press pulldown menu at draw area of page. Pulldown menu opens
4. Select item Actions -> Print with Calligra words

-- Backtrace:
Application: Calligra Words (calligrawords), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f9ce281e24f in KoMainWindow::slotFilePrint
(this=this@entry=0x1d9b560) at
/build/calligra-ld8dSW/calligra-2.9.7/libs/main/KoMainWindow.cpp:1410
#7  0x7f9ce27f6d32 in KoApplication::start (this=this@entry=0x7ffd844a2b40)
at /build/calligra-ld8dSW/calligra-2.9.7/libs/main/KoApplication.cpp:556
#8  0x7f9ce2e833b0 in kdemain (argc=, argv=)
at /build/calligra-ld8dSW/calligra-2.9.7/words/app/main.cpp:42
#9  0x7f9ce2ad6a40 in __libc_start_main (main=0x4006e0 ,
argc=3, argv=0x7ffd844a2c88, init=, fini=,
rtld_fini=, stack_end=0x7ffd844a2c78) at libc-start.c:289
#10 0x00400719 in _start ()

Reported using DrKonqi

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

[krita] [Bug 352519] Delete, cut copy and paste recursively from a group or multiple selected layer

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|RESOLVED|REOPENED

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

[krita] [Bug 352519] Delete, cut copy and paste recursively from a group or multiple selected layer

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

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

[kdenlive] [Bug 358427] 15.13 git master: monitor audio levels have no indicators for 0, -5, -10, -20 dB

[via KDE Bugzilla]

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

--- Comment #13 from wegwerf-1-...@gmx.de ---
(rant on: why do people worry about metric versus inches, when we can have
commas versus dots over here :D /rant off)

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

[kwin] [Bug 357450] Double click on the titlebar is not a standalone event

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||a...@1stleg.com

--- Comment #5 from Thomas Lübking  ---
*** Bug 358566 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 358577] Git master 2016-01-10 - Maintenance tool filters not working

[Evert Vorster via KDE Bugzilla]

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

--- Comment #1 from Evert Vorster  ---
Oh, and the slider at the bottom of video clips don't work either. 

;)

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

[Breeze] [Bug 358578] New: Active window taskbar entry background too bright in Breeze Dark theme

[Radics Péter via KDE Bugzilla]

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

Bug ID: 358578
   Summary: Active window taskbar entry background too bright in
Breeze Dark theme
   Product: Breeze
   Version: 5.5.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: mitchnull+...@gmail.com

Breeze Dark theme is using the same background setting for taskbar entries as
the default Breeze theme, but the default bright-blue background for active
(focused) windows is too bright on the dark theme (it is like the window wants
"attention", it keeps distracting).  I've modified the tasts.svgz file from the
default breeze theme to only add a blue border to the active (focused) window,
not tint the whole taskbar entry.  Unfortunately placing this file under
/usr/share/plasma/desktoptheme/breeze-dark/widgets/ doesn't seem to be enough,
so at the moment I overwrite the default (under 
/usr/share/plasma/desktoptheme/default/widgets/).

Please consider changing the breeze-dark tasks.svgz to be a less bright (less
attention-demanding) version.  



Reproducible: Always

Steps to Reproduce:
1) change plasma theme to Breeze Dark
2) open a window (like a browser)
3) focus the new window

Actual Results:  
the visual feedback for active window in the taskbar with the breeze-dark theme
is too bright, demanding attention

Expected Results:  
the taskbar entry for the window (when it is focused) should provide visual
feedback about being focused, but not be too distracting

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

[krita] [Bug 358530] Layer Style: Bevel in Wrap Around Mode

[Timm via KDE Bugzilla]

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

Timm  changed:

   What|Removed |Added

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

--- Comment #4 from Timm  ---
What is the next status?

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

[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #33 from Thomas Lübking  ---
For a KMainWindow solution, one should not require a nasty global eventfilter
on the application - handling KMainWindow::closeEvent() should be sufficient,
but there might be an additional pitfall on modal windows (ie. if there's
already a save dialog, we might have to forcefully activate that to cause user
interaction)

However, as long as QGuiApplication cancels the session lougout as long as any
close event is ignored, this cannot be applied either (ie. still requires your
new patch to Qt) and, of course, this doesn't provide a solution for Qt5 either
- session management on Qt5 will remain broken forever and just some KDE
applications work around that. That's a pretty crappy situation :-(

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

[Akonadi] [Bug 358580] New: possible problem when accessing IMAP where the cert is out of date

[Con Hennessy via KDE Bugzilla]

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

Bug ID: 358580
   Summary: possible problem when accessing IMAP where the cert is
out of date
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: con.henne...@gmail.com
CC: kdepim-b...@kde.org, vkra...@kde.org

Application: akonadi_imap_resource ()

Qt Version: 5.5.1
Operating System: Linux 4.4.0-rc8-1.ge628e30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
The cert was an old SHA1 cert and I was warned about it and asked to confirm if
I wanted to use it. I selected the 'current session only' option. However I was
also sending other emails, but I hope/think that they are not related.

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

Thread 8 (Thread 0x7f3ffccd7700 (LWP 2235)):
#0  0x7f400e80ec1d in poll () at /lib64/libc.so.6
#1  0x7f400a37f422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f400a38100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f3ffea023c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f400f11d32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f400b7d40a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f400e81704d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f3ff7330700 (LWP 2251)):
#0  0x7f400e80ec1d in poll () at /lib64/libc.so.6
#1  0x7f4009c5ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4009c5cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f400f34fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f400f2f6d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f400f11861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f400f11d32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f400b7d40a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f400e81704d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f3ff6b2f700 (LWP 2263)):
#0  0x7f400e80ec1d in poll () at /lib64/libc.so.6
#1  0x7f4009c5ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4009c5cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f400f34fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f400f2f6d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f400f11861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f400f11d32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f400b7d40a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f400e81704d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f3ff591e700 (LWP 2339)):
#0  0x7f400e80ec1d in poll () at /lib64/libc.so.6
#1  0x7f4009c5ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4009c5cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f400f34fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f400f2f6d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f400f11861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f400f11d32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f400b7d40a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f400e81704d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f3fc27fa700 (LWP 2767)):
#0  0x7f400e80ec1d in poll () at /lib64/libc.so.6
#1  0x7f4009c5ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4009c5cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f400f34fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f400f2f6d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f400f11861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f400f11d32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f400b7d40a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f400e81704d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3fd26b8700 (LWP 2769)):
#0  0x7f4009c9ecf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4009c5c4b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4009c5cd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4009c5cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f400f34fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f400f2f6d53 in
QEventLoop::exec(QFlags) () at

[kdeconnect] [Bug 339367] Broken Crypto

[Albert Vaca via KDE Bugzilla]

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

--- Comment #3 from Albert Vaca  ---
It's not merged yet, but we made some progress recently so it soon will be.

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working on video files

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

Summary|Maintenance tool rebuild|Maintenance tool rebuild
   |thumbnails directory filter |thumbnails directory filter
   |not working |not working on video files

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

[krita] [Bug 358422] Deleted layer content reappears after select.

[Piotr via KDE Bugzilla]

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

--- Comment #9 from Piotr  ---
Created attachment 96849
  --> https://bugs.kde.org/attachment.cgi?id=96849=edit
Recording of the behaviour

Freshly launched app.

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

[okular] [Bug 358584] New: print 4 pages on one with print to pdf

[via KDE Bugzilla]

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

Bug ID: 358584
   Summary: print 4 pages on one with print to pdf
   Product: okular
   Version: 0.24.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: i...@andreas-winter.eu

I cannot print 4 pages on one page via Print to PDF option in Okular. The
created file still shows one page for every page of the old pdf.

Reproducible: Always

Steps to Reproduce:
1. Open document with some pages inside
2. File/Print/Select Print to File (PDF) and your output-file
3. In options/pages select "4 pages for every page"
4. Print it

Actual Results:  
You get a pdf document which is exactly the same as the original one.

Expected Results:  
You should get a pdf on which pages are 4 pages of the printed version. So if
you have an original file with 16 pages. You should get a pdf with 4 pages, 4
small pages on every page.

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working on video files

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #6 from caulier.gil...@gmail.com ---
Maik,

You don't have fixed this kind of dysfunction in the past, especially with last
Qt4 implementation ?

Gilles

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

[kmymoney] [Bug 358573] New: Unable to enter fraction part when decimal point of current locale differs from "."

[Alexey Chernov via KDE Bugzilla]

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

Bug ID: 358573
   Summary: Unable to enter fraction part when decimal point of
current locale differs from "."
   Product: kmymoney
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: 4er...@gmail.com

It's impossible to enter decimal separator to the fields of cash amount, so
even entering the sum in calculator prints nothing to the field.
As it turned out, the problem was in kMyMoneyMoneyValidator, the patch will
follow.

Reproducible: Always

Steps to Reproduce:
0. Select some affected locale, e.g. German or Russian (they have "," as a
decimal point).
1. Go to "Ledgers" view, select any account.
2. Create another operation or edit some existing one.
3. Try to enter some sum in the "Amount" field, either manually or with
calculator opened.

Actual Results:  
Notice that you can't enter decimal point sign, when you close the calculator,
nothing is entered in the field.

Expected Results:  
The sum should have been entered successfully.

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

[systemsettings] [Bug 358574] New: Monitor starts flickering occasionally until I do *any* change to the compositor settings

[Bjarke via KDE Bugzilla]

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

Bug ID: 358574
   Summary: Monitor starts flickering occasionally until I do
*any* change to the compositor settings
   Product: systemsettings
   Version: 5.5.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bjarkemoens...@gmail.com

I'm using the Cube setup for multiple workspaces (3x3) in Kubuntu. After a few
days, my monitor started flickering, especially (but not only) when changing
between workspaces. I Googled that I should select 'full screen repaints' under
'vsync' in the compositor settings. This momentarily solved the problem, but it
returned a couple of days later. The problem goes a few for a few days when I
perform seemingly any change in the compositor settings and click 'apply' -
even if I, say, select a different setting for vsync, select the original one
again, and only THEN click 'apply', so it seems something magical is happening
when the apply button is pressed.
Feel free to contact me with any questions.

Reproducible: Sometimes

Steps to Reproduce:
1. Enable multiple workspaces (3x3) with cube animation.
2. Change compositor settings
3. Reboot a few times (there doesn't seem to be a pattern)

Actual Results:  
Monitor flickers wildly until compositor settings are changed again.

Expected Results:  
Monitor would stop flickering permanently after selecting 'full screen
repaints' for vsync settings.

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

[Breeze] [Bug 358576] New: Default and Breeze color scheme have different window decoration colors

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 358576
   Summary: Default and Breeze color scheme have different window
decoration colors
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: mgraess...@kde.org

The "default" color scheme has a blue window decoration color, while breeze has
a dark color. Given that the "default" should be breeze this needs to be the
same color

Reproducible: Always

Steps to Reproduce:
1. Open Systemsettings
2. Open Color
3. Look at preview list

Actual Results:  
Top right color preview of Default and Breeze are not the same

Expected Results:  
Should be the same

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

[plasmashell] [Bug 354386] System tray panel changes to secondary monitor that is on top/above on dual-monitor config

[Elias Probst via KDE Bugzilla]

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

Elias Probst  changed:

   What|Removed |Added

 CC||m...@eliasprobst.eu

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

[plasmashell] [Bug 354029] crash plasma in openSUSE Leap 42.1

[venember via KDE Bugzilla]

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

venember  changed:

   What|Removed |Added

 CC||m...@ship.hu

--- Comment #3 from venember  ---
The error remained, this is not such a  bug, says Tumbleweed forum operator.

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

[KBibTeX] [Bug 358446] Non free file

[roucaries via KDE Bugzilla]

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

--- Comment #2 from roucaries  ---
https://git-scm.com/docs/git-filter-branch is better

git filter-branch --index-filter 'git rm --cached --ignore-unmatch filename'
HEAD

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails not working for video files

[Evert Vorster via KDE Bugzilla]

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

--- Comment #3 from Evert Vorster  ---
The thumbnails for this folder is cached. 

In the maintenance tool, when selecting the entire database, and selecting
"Rebuild Thumbnails" All of the thumbnails are re-built. 
When selecting only one folder, NO thumbnails are re-built. 

How is this the fault of QT5?

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

[via KDE Bugzilla]

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

a.skemb...@gmail.com changed:

   What|Removed |Added

 CC||a.skemb...@gmail.com

--- Comment #11 from a.skemb...@gmail.com ---
Created attachment 96847
  --> https://bugs.kde.org/attachment.cgi?id=96847=edit
Backtrace of KWin stopped process when crash happens

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

[umbrello] [Bug 338649] Extend C++ import for C++11

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #12 from Ralf Habacker  ---
(In reply to Patric Schmitz from comment #10)
> >> If this is a basic limitation to using clang, is this really the way the 
> >> project should go? 
> 
> Probably the most reasonable way to go about it after all?

For now yes

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

[rekonq] [Bug 358582] New: Rekonq constant crashes

[Wim Entrop via KDE Bugzilla]

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

Bug ID: 358582
   Summary: Rekonq constant crashes
   Product: rekonq
   Version: 2.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: adj...@gmail.com
  Reporter: eindjed...@gmail.com

Application: rekonq (2.4.2)
KDE Platform Version: 4.14.15
Qt Version: 4.8.6
Operating System: Linux 4.2.0-27-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
visiting URL www.telegraaf.nl

rekonq crash all the times but not on the same place in webpage. Looks if
rekonq is opening embedded stuff and crashes

The crash can be reproduced every time.

-- Backtrace:
Application: rekonq (rekonq), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa5a269f840 (LWP 1648))]

Thread 13 (Thread 0x7fa58ae13700 (LWP 1649)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa5a13998cd in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fa5a1e2c6b4 ) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/FastMalloc.cpp:2575
#2  0x7fa5a1399929 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7fa5a1e2c6b4 ) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/FastMalloc.cpp:1771
#3  0x7fa598b706aa in start_thread (arg=0x7fa58ae13700) at
pthread_create.c:333
#4  0x7fa5a1f48eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fa548c1d700 (LWP 1651)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa5a10bbca1 in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fa58a588398) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x7fa5a13cc066 in WTF::wtfThreadEntryPoint (param=0x6e8310) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x7fa598b706aa in start_thread (arg=0x7fa548c1d700) at
pthread_create.c:333
#4  0x7fa5a1f48eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fa542d53700 (LWP 1664)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa5a07b48d4 in WebCore::IconDatabase::syncThreadMainLoop() () at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/SegmentedVector.h:129
#2  0x7fa5a07b4b19 in WebCore::IconDatabase::iconDatabaseSyncThread() () at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/SegmentedVector.h:129
#3  0x7fa5a13cc066 in WTF::wtfThreadEntryPoint (param=0xcb0f60) at
/build/qtwebkit-source-HZiiC7/qtwebkit-source-2.3.2/Source/WTF/wtf/ThreadingPthreads.cpp:196
#4  0x7fa598b706aa in start_thread (arg=0x7fa542d53700) at
pthread_create.c:333
#5  0x7fa5a1f48eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fa542452700 (LWP 1665)):
#0  0x7fa5a1f3d8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa5998761ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5998762fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa59c2f620e in QEventDispatcherGlib::processEvents
(this=0x7fa5340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fa59c2c40d1 in QEventLoop::processEvents
(this=this@entry=0x7fa542451d90, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fa59c2c4445 in QEventLoop::exec (this=this@entry=0x7fa542451d90,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fa59c1b34f9 in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7fa59c1b5d1c in QThreadPrivate::start (arg=0x8a4ef0) at
thread/qthread_unix.cpp:349
#8  0x7fa598b706aa in start_thread (arg=0x7fa542452700) at
pthread_create.c:333
#9  0x7fa5a1f48eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fa540c28700 (LWP 1667)):
#0  0x7fa599875c78 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa599876190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5998762fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa59c2f620e in QEventDispatcherGlib::processEvents
(this=0x7fa5280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fa59c2c40d1 in QEventLoop::processEvents
(this=this@entry=0x7fa540c27d40, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fa59c2c4445 in QEventLoop::exec (this=this@entry=0x7fa540c27d40,
flags=...) at kernel/qeventloop.cpp:204
#6  

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

[via KDE Bugzilla]

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

--- Comment #14 from a.skemb...@gmail.com ---
 (In reply to Martin Gräßlin from comment #13)
> > 2) Open Firefox (via taskbar icon).
> 
> you mean launching a firefox instance?

Yes, It definitely triggers when the only and last activated window is the
Virtualbox window, and I click on the taskbar icon of Firefox. I also have an
icon in the  "Desktop folder" widget, but I hardly use it.

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #15 from Martin Gräßlin  ---
For me the steps don't work. This could either mean there is more in it to
reproduce it or it's fixed with Qt 5.6 (which I doubt).

The backtraces never show from where in KWin the crash happens. If there is a
chance to get the ?? sections in the backtrace filled, I have hope that we can
fix it.

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #16 from Martin Gräßlin  ---
> or it's fixed with Qt 5.6

which might be the case. The code in question changed significantly. The line 
QV4::Heap::StringObject::StringObject (this=, engine=0x2ac1220,
val=...)
at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4stringobject.cpp:91

doesn't exist at all in 5.6 branch.

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

[digikam] [Bug 358609] ‘Labels’ easily confused with ‘tags’ – new name?

[via KDE Bugzilla]

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

--- Comment #2 from caulier.gil...@gmail.com ---
http://photography.tutsplus.com/tutorials/unlocking-the-power-of-lightroom-color-labels--cms-21876

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

[krita] [Bug 358619] New: Moving a layer to the top is annoying

[zottg via KDE Bugzilla]

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

Bug ID: 358619
   Summary: Moving a layer to the top is annoying
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: zottgram...@gmail.com

1. Have at least 2 layers. Layer 1 and 2, 2 is at the top.
2. Try to click and drag and move Layer 1 above layer 2.

There is a 1 pixel window/border where the cursor has to land and release to
allow this move. This is a very precise requirement for a simple and common
action. It seems to be an inefficient UX.

Suggest: Increasing the target size to something like 10pixels or so to make it
easier to 'land' on it.

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

[kate] [Bug 358553] "Open recent" entries should be added on file open rather than file close

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #3 from Dominik Haumann  ---
...or it also could be, that a sync of the kate session is missing. As iirc,
the recent files are per session.

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

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

[Tom Hughes via KDE Bugzilla]

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

--- Comment #1 from Tom Hughes  ---
This is epoll_create1.

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

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

[via KDE Bugzilla]

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

--- Comment #2 from alexander.ress...@gmail.com ---
Yes, it's epol_create1.

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

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

[Tom Hughes via KDE Bugzilla]

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

Tom Hughes  changed:

   What|Removed |Added

Summary|WARNING: unhandled syscall: |ARM: unhandled syscall: 357
   |357 |
 CC||t...@compton.nu

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

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

[brancaleone via KDE Bugzilla]

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

brancaleone  changed:

   What|Removed |Added

 CC||cedric.devill...@gmail.com

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

[plasmashell] [Bug 358624] Plasma Panel stays on disconnected Primary Output

[Malte S . Stretz via KDE Bugzilla]

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

Malte S. Stretz  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

--- Comment #1 from Malte S. Stretz  ---
This happens on Kubuntu 15.10 (wily); KDE from the kubuntu-ppa. I notice this
because everything worked fine with plasma 4 on Kubuntu 14.04.

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

[okular] [Bug 319839] --unique-per-file option

[Jonathan Verner via KDE Bugzilla]

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

--- Comment #4 from Jonathan Verner  ---
(In reply to Walter Rudametkin from comment #3)
> Hi,
> 
> Is there anything missing for your patch to be applied? I'd really like to
> see this in Okular.
> 
> Regards,

It is not fully tested yet (missing unit tests)... If you are brave, you might
try downloading Okular's source, applying the patch and building it yourself.

I planned to work on it at the end of last year but unfortunately life again
got into the way. As it stands, I currently don't have much time, so the
chances of me finishing it soon are rather slim :-( Sorry for that.

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

[krunner] [Bug 350901] krunner segfault might because KDeclarative::QmlObject is NULL

[Leslie Zhai via KDE Bugzilla]

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

Leslie Zhai  changed:

   What|Removed |Added

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

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

[kdeplasma-addons] [Bug 358298] QuickShare plasmoid don't work as share

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Aleix Pol  ---
Yes, the functionality changed slightly over the port. If there's a server you
especially look forward to, please let us know. (or even better, come up with a
patch! :D).

If you manage to predictably reproduce the error or find some information,
don't hesitate to reopen.

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

[kmail2] [Bug 358621] New: crash at first startup after login

[Bruno Friedmann via KDE Bugzilla]

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

Bug ID: 358621
   Summary: crash at first startup after login
   Product: kmail2
   Version: 5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: br...@ioda-net.ch

Application: kmail (5.1)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160121) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I'm using a global shortcut to
launch at the same time korganizer & kmail.
Meta+A -> /usr/bin/korganizer & /usr/bin/kmail

Immediately this crash is reported, but kmail start and work correctly
afterwards.


Nvidia drivers : 352.79 
double écran hiDPI ( 3840 x 2160 )

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc5e318f940 (LWP 3220))]

Thread 16 (Thread 0x7fc5bcb4b700 (LWP 3222)):
#0  0x7fc5e01d724d in poll () at /lib64/libc.so.6
#1  0x7fc5d3610432 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc5d3612007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc5beea4e29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc5e0adf94f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc5e01dfbdd in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fc5b64fc700 (LWP 3225)):
#0  0x7fc5d6a17cfc in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7fc5d6a11bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2  0x7fc5d5529fcc in  () at /usr/X11R6/lib64/libGL.so.1
#3  0x7fc5d552eb11 in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7fc5d552f018 in  () at /usr/X11R6/lib64/libGL.so.1
#5  0x7fc5ca73c001 in  () at /usr/lib64/tls/libnvidia-tls.so.352.79
#6  0x7fc5d6534210 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7fc5d64f1d94 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#8  0x7fc5d64f2208 in  () at /usr/lib64/libglib-2.0.so.0
#9  0x7fc5d64f236c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#10 0x7fc5e0d0452b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#11 0x7fc5e0cae63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#12 0x7fc5e0adab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#13 0x7fc5e0adf94f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fc5b4e76700 (LWP 3923)):
#0  0x7fc5e01d322d in read () at /lib64/libc.so.6
#1  0x7fc5ca73bf75 in  () at /usr/lib64/tls/libnvidia-tls.so.352.79
#2  0x7fc5d6534210 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc5d64f1d94 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc5d64f2208 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fc5d64f236c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7fc5e0d0452b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7fc5e0cae63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7fc5e0adab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7fc5e0adf94f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fc5a7fff700 (LWP 3927)):
#0  0x7fc5d64f18d1 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fc5d64f2193 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc5d64f236c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc5e0d0452b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc5e0cae63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc5e0adab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc5e0adf94f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fc5e01dfbdd in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fc5a77fe700 (LWP 3930)):
#0  0x7fc5d6a1507f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc5d147c3bb in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc5d147c3f9 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc5e01dfbdd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fc5b5677700 (LWP 3941)):
#0  0x7fc5e01d322d in read () at /lib64/libc.so.6
#1  0x7fc5ca73bf75 in  () at 

[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled

[Federico Lorenzi via KDE Bugzilla]

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

--- Comment #3 from Federico Lorenzi  ---
I posted a link to a Reddit thread:
https://www.reddit.com/r/kde/comments/31s438/plasma_52_flickering_on_short_alttab/
that has my original YouTube video showing the problem in Plasma 5.2 (
https://www.youtube.com/watch?v=NJPUF8iT0UY ), as well as a few "me toos".

I've taken some new videos now (on the exact machine that the support info is
from):

Showing the bug (Show selected window enabled):
https://www.youtube.com/watch?v=b-05weuHDUM=youtu.be (slow speed)
https://www.youtube.com/watch?v=Pa2YjI-ikMA=youtu.be (normal speed)

Not showing the bug (Show selected window disabled):
https://www.youtube.com/watch?v=n8IZLYs3D0A=youtu.be (normal speed)
https://www.youtube.com/watch?v=BF_7qM0-QVA=youtu.be (slow speed)

The behavior mirrors what I see exactly (ie, there are no screen recording
artifacts). 

I'm not sure what you mean about the flicker being persistent? It happens every
time I alt-tab, but once it has happened (ie, done alt-tabbing) everything is
normal.

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

[kinfocenter] [Bug 358623] New: core dumped, when using AMD open source driver

[via KDE Bugzilla]

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

Bug ID: 358623
   Summary: core dumped, when using AMD open source driver
   Product: kinfocenter
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: OpenGL
  Assignee: hubn...@gmail.com
  Reporter: ali.sheri...@yahoo.com

If I run $ xrandr --setprovideroffloadsink radeon intel then open the program
with $ DRI_PRIME=1 kinfocenter, KInfoCenter crashes, after I click on OpenGL.
Arch is up to date.
Error messsage: Segmentation fault (core dumped)

Reproducible: Always

Steps to Reproduce:
1. Run xrandr --setprovideroffloadsink radeon intel.
2. Run DRI_PRIME=1 kinfocenter.
3. Click on OpenGL

Actual Results:  
Segmentation fault (core dumped)

Expected Results:  
I see OpenGL data.

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

[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position

[Anthony via KDE Bugzilla]

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

--- Comment #13 from Anthony  ---
Any results here?

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

[kdelibs] [Bug 358622] New: Crash after resume from suspend to disk, unlock screen

[via KDE Bugzilla]

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

Bug ID: 358622
   Summary: Crash after resume from suspend to disk, unlock screen
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kded
  Assignee: unassigned-b...@kde.org
  Reporter: opensuse.lietuviu.ka...@gmail.com

Application: kded4 (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

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

I suspend computer to hard disk at evening. In morning I boot computer, Linux
system with KDE resumed. I entered password to unlock desktop. I see crash
notification. This isfirst time I see such notification.

-- Backtrace:
Application: KDE tarnyba (kded4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f06de355780 (LWP 3617))]

Thread 4 (Thread 0x7f06b7214700 (LWP 3630)):
#0  0x7f06d8a9d337 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f06d8a9db03 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f06d8a9dcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f06dcfeb0de in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f06a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f06dcfbce6f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f06b7213e20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f06dcfbd165 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f06b7213e20, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f06dceba0bf in QThread::exec() (this=) at
thread/qthread.cpp:538
#7  0x7f06c271a287 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#8  0x7f06dcebc79f in QThreadPrivate::start(void*) (arg=0x1b34e10) at
thread/qthread_unix.cpp:349
#9  0x7f06dcc260a4 in start_thread (arg=0x7f06b7214700) at
pthread_create.c:309
#10 0x7f06db99308d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f06b6a13700 (LWP 3631)):
#0  0x7f06dcc2ca9d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f06d8ade750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f06d8a9d714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f06d8a9db7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f06d8a9dcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f06dcfeb0de in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f06940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f06dcfbce6f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f06b6a12e60, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f06dcfbd165 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f06b6a12e60, flags=...) at kernel/qeventloop.cpp:204
#8  0x7f06dceba0bf in QThread::exec() (this=) at
thread/qthread.cpp:538
#9  0x7f06dcebc79f in QThreadPrivate::start(void*) (arg=0x1b20b30) at
thread/qthread_unix.cpp:349
#10 0x7f06dcc260a4 in start_thread (arg=0x7f06b6a13700) at
pthread_create.c:309
#11 0x7f06db99308d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f06b6212700 (LWP 3632)):
#0  0x7f06db98ac5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f06d8a9dbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f06d8a9dcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f06dcfeb0de in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f068c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f06dcfbce6f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f06b6211e20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f06dcfbd165 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f06b6211e20, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f06dceba0bf in QThread::exec() (this=this@entry=0x1cb0090) at
thread/qthread.cpp:538
#7  0x7f06dcf9e783 in QInotifyFileSystemWatcherEngine::run()
(this=0x1cb0090) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f06dcebc79f in QThreadPrivate::start(void*) (arg=0x1cb0090) at
thread/qthread_unix.cpp:349
#9  0x7f06dcc260a4 in start_thread (arg=0x7f06b6212700) at
pthread_create.c:309
#10 0x7f06db99308d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f06de355780 (LWP 3617)):
[KCrash Handler]
#6  0x7f06dcfc4847 in QMetaObject::cast(QObject*) const
(this=0x7f06dcc05e60 , obj=0x160) at
kernel/qmetaobject.cpp:274
#7  0x7f06dc1fb56e in createWriteHandlerHelper(QIODevice*, QByteArray
const&) (object=) at ../../src/corelib/kernel/qobject.h:380
#8  0x7f06dc1fb56e in createWriteHandlerHelper(QIODevice*, QByteArray
const&) 

[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled

[Federico Lorenzi via KDE Bugzilla]

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

--- Comment #2 from Federico Lorenzi  ---
Created attachment 96863
  --> https://bugs.kde.org/attachment.cgi?id=96863=edit
Output of qdbus org.kde.KWin /KWin supportInformation

This is the output from my desktop, running the binary Nvidia drivers. However,
the exact same problem appears on my laptop (using the open source Intel
drivers). Tweaking VSync / Compositor settings don't seem to make a difference
(it still happens with XRender compositing).

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

[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #92 from Martin Gräßlin  ---
hey all, as you now even point me to the code of conduct: The code of conduct
does not force me to write code or to review code.

So let me explain why I won't implement it and won't let a feature go back in:
because I'm sick of this report. Sick of the behavior expressed by the small
number of people here. Sick of the accusations thrown at me. It's a waste of my
time to comment on this bug report. I just don't want to have anything to do
with it any more. The easiest way would be to just let the feature in again,
but I don't make maintainer decisions based on bullying by a small number of
people.

Everything regarding this bug report has been said. There won't be new
information going in and nobody of those wanting the feature back, will accept
the arguments we presented. So why should we continue to spend time on it?

If you think that this is all badly handled and you think I violate the code of
conduct I urge you to contact the community working group.

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

[kalarm] [Bug 358625] New: klarm crashed when opening from systray

[Vit Pelcak via KDE Bugzilla]

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

Bug ID: 358625
   Summary: klarm crashed when opening from systray
   Product: kalarm
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: djar...@kde.org
  Reporter: v...@pelcak.org

Application: kalarm (2.11.3-5ak)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160121) (x86_64)"

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

I had Kalarm in systray and when I clicked on its icon, I got segfault.
Now when I want to reproduce it, kalarm won't create icon in systray.

-- Backtrace:
Application: KAlarm (kalarm), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb178831940 (LWP 2657))]

Thread 4 (Thread 0x7fb157577700 (LWP 2658)):
#0  0x7fb16fed424d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb16a2d3432 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fb157576b80) at /usr/include/bits/poll2.h:46
#2  0x7fb16a2d3432 in _xcb_conn_wait (c=c@entry=0x2118b40,
cond=cond@entry=0x2118b80, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x7fb16a2d5007 in xcb_wait_for_event (c=0x2118b40) at xcb_in.c:693
#4  0x7fb15929fe29 in QXcbEventReader::run() (this=0x2123200) at
qxcbconnection.cpp:1229
#5  0x7fb1707dc94f in QThreadPrivate::start(void*) (arg=0x2123200) at
thread/qthread_unix.cpp:331
#6  0x7fb16a4f04a4 in start_thread (arg=0x7fb157577700) at
pthread_create.c:334
#7  0x7fb16fedcbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fb15568c700 (LWP 2659)):
#0  0x7fb16fed424d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb169baf264 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb148003020, timeout=, context=0x7fb148000990) at
gmain.c:4135
#2  0x7fb169baf264 in g_main_context_iterate
(context=context@entry=0x7fb148000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7fb169baf36c in g_main_context_iteration (context=0x7fb148000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7fb170a0152b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb1480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fb1709ab63a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb15568bc90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fb1707d7b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fb1707dc94f in QThreadPrivate::start(void*) (arg=0x21f6e90) at
thread/qthread_unix.cpp:331
#8  0x7fb16a4f04a4 in start_thread (arg=0x7fb15568c700) at
pthread_create.c:334
#9  0x7fb16fedcbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb154e8b700 (LWP 23572)):
#0  0x7fb16fed424d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb169baf264 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb14c002e50, timeout=, context=0x7fb14c002cb0) at
gmain.c:4135
#2  0x7fb169baf264 in g_main_context_iterate
(context=context@entry=0x7fb14c002cb0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7fb169baf36c in g_main_context_iteration (context=0x7fb14c002cb0,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7fb170a0152b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb14c003f10, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fb1709ab63a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb154e8ac90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fb1707d7b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fb1707dc94f in QThreadPrivate::start(void*) (arg=0x2626cb0) at
thread/qthread_unix.cpp:331
#8  0x7fb16a4f04a4 in start_thread (arg=0x7fb154e8b700) at
pthread_create.c:334
#9  0x7fb16fedcbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb178831940 (LWP 2657)):
[KCrash Handler]
#6  0x7fb170192b98 in main_arena () at /lib64/libc.so.6
#7  0x7fb1592b5329 in QXcbWindow::mapToNative(QRect const&, QXcbScreen
const*) const (this=, rect=..., screen=0x2125b80) at
qxcbwindow.cpp:203
#8  0x7fb1592bbab3 in QXcbWindow::setGeometry(QRect const&)
(this=0x25f3960, rect=...) at qxcbwindow.cpp:732
#9  0x7fb171c91032 in QWidgetPrivate::show_sys()
(this=this@entry=0x2221880) at kernel/qwidget.cpp:7889
#10 0x7fb171c99ee6 in QWidgetPrivate::show_helper()
(this=this@entry=0x2221880) at kernel/qwidget.cpp:7827
#11 0x7fb171c9c845 in QWidget::setVisible(bool) (this=0x2295ce0,
visible=) at kernel/qwidget.cpp:8111
#12 0x7fb171c99c18 in QWidgetPrivate::showChildren(bool)

[kmail2] [Bug 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi

[Martin Steigerwald via KDE Bugzilla]

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

--- Comment #40 from Martin Steigerwald  ---
Please retest with most recent KDEPIM + Akonadi 15.12.

It has a ton of performance fixes that are not going to be backported due to
shift from Akonadi from Qt4 to Qt5.

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

[konsole] [Bug 356482] crash on closing help window

[Cobus Carstens via KDE Bugzilla]

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

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

konsole (15.08.0) using Qt 5.5.1

- What I was doing when the application crashed:
I resumed the laptop and plugged in a second screen.

-- Backtrace (Reduced):
#6  0x7f64aef738ff in
QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x7f64aef5eadb in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x7f64aef5f003 in QXcbConnection::processXcbEvents() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x7f64bd94d7b1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f64be2129dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working on video files

[Evert Vorster via KDE Bugzilla]

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

--- Comment #9 from Evert Vorster  ---
I have QT5 thumbnailer installed. 

How else would I get the thumbnails in the first place?

A little bit of history... 
DigiKam 4.xx started failing on thumbnails for video recently, and so I
installed DigiKam 5.0.0.
I re-built my entire data base's thumbnails, and it took many hours. 
Everything looked to be fine. 

Then I imported from two sources at once, my wife's phone and an SD card
reader. 
One of the video thumbnails is incorrect in DigiKam only, and shows correct on
Dolphin. (5)
Refreshing the album does not fix the thumbnail in DigiKam.

Using the maintenance tools also does not delete the cached thumbnail. 

I do not want to delete ALL my thumbnails again, since it will take a very long
tie to re-create all of them. It should be easy to delete a thumbnail and let
DigiKam re-create it as if it is a new file.

Hy, I just found an easy workaround. 
I navigated to the directory in a console, and just touched the file with bad
thumbnail. 
DigiKam then re-created the thumbnail, and got it right this time. 
:)

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

[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon

[Anthony via KDE Bugzilla]

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

--- Comment #5 from Anthony  ---
This is not Klipper at all, it's device mounter when click it show status of
mounted device in the panel.

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

[plasmashell] [Bug 348514] Device Notifier missing KDE 4 actions

[Eric S via KDE Bugzilla]

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

Eric S  changed:

   What|Removed |Added

 CC||subscri...@blackbrook.org

--- Comment #1 from Eric S  ---
Maybe this is distro-specific but all my actions from kde4 are in
/usr/share/apps/solid/actions.

It seems to me one solution or workaround might be distros handled this. KDE
ought to highlight the need for this to the distros in some info prominently
provided to them when they get the Plasma 5 sources.

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

[digikam] [Bug 358609] ‘Labels’ easily confused with ‘tags’ – new name?

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from caulier.gil...@gmail.com ---
Labels are tags, technically in digiKam core database, but dedicated for
specific tasks.

- Color Labels to mark images with customized  colored mark in workflow.
- Pick Labels to mark wanted images with a flag while sorting.
- Rating to mark images with stars after sorting.

Tags are text annotation, not a graphical mark.

LightRoom (and also other pro photo tools) use also "Labels" terms about
graphical marks to apply on images, and "Tags" about text annotations.

Gillles Caulier

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

[plasmashell] [Bug 358618] New: Plasma crashed when closing an application

[Vince Radice via KDE Bugzilla]

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

Bug ID: 358618
   Summary: Plasma crashed when closing an application
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vhrad...@cfl.rr.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-301.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
I was shutting own for the night and was closing the open applications.  I
tried to close a Firefox browser and Plasma crashed.

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

Thread 8 (Thread 0x7f2215f02700 (LWP 12484)):
#0  0x7f222d816fdd in poll () at /lib64/libc.so.6
#1  0x7f2233cce272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f2233ccfee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f2217e8cda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f222e41f3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0
#6  0x7f222d822a4d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f220f3ea700 (LWP 12503)):
#0  0x7f222d816fdd in poll () at /lib64/libc.so.6
#1  0x7f2228d3d16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f2228d3d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f222e656ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f222e5fdeca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f2232765b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f222e41f3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0
#9  0x7f222d822a4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f220656d700 (LWP 12504)):
#0  0x7f222d816fdd in poll () at /lib64/libc.so.6
#1  0x7f2228d3d16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f2228d3d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f222e656ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f222e5fdeca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f2232765b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f222e41f3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0
#9  0x7f222d822a4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f2204b08700 (LWP 12505)):
#0  0x7f222d816fdd in poll () at /lib64/libc.so.6
#1  0x7f2228d3d16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f2228d3d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f222e656ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f222e5fdeca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f2232765b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f222e41f3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0
#9  0x7f222d822a4d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f21ff19a700 (LWP 12506)):
#0  0x7f222cb5fb10 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f22355be514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f22355be559 in  () at /lib64/libQt5Script.so.5
#3  0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0
#4  0x7f222d822a4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f2177636700 (LWP 12507)):
#0  0x7f222d816fdd in poll () at /lib64/libc.so.6
#1  0x7f2228d3d16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f2228d3d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f222e656ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f222e5fdeca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f22333138d6 in QQuickPixmapReader::run() () at
/lib64/libQt5Quick.so.5
#7  

[valgrind] [Bug 358620] New: WARNING: unhandled syscall: 357

[via KDE Bugzilla]

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

Bug ID: 358620
   Summary: WARNING: unhandled syscall: 357
   Product: valgrind
   Version: 3.7.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: alexander.ress...@gmail.com

I have an ARMv6 Raspberry Pi that I'm compiling and testing a small TCP server
on. I'm using the epoll system call in my c/c++ program. The program runs fine
when I don't use valgrind. However, when I use valgrind, the call to
'epoll_wait' returns -1, which indicates a kernel level error. This doesn't
happen with valgrind and the same program on my typical desktop with an intel
i7 cpu.

See the results of valgrind below.

==2615== Memcheck, a memory error detector
==2615== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==2615== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==2615== Command: ./src/app/bserver
==2615== 
--2615-- WARNING: unhandled syscall: 357
--2615-- You may be able to write your own handler.
--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2615-- Nevertheless we consider this a bug.  Please report
--2615-- it at http://valgrind.org/support/bug_reports.html.
--2615-- WARNING: unhandled syscall: 357
--2615-- You may be able to write your own handler.
--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2615-- Nevertheless we consider this a bug.  Please report
--2615-- it at http://valgrind.org/support/bug_reports.html.
 disInstr(arm): unhandled instruction: 0xF1010200
 cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==2615== valgrind: Unrecognised instruction at address 0x4842588.
==2615==at 0x4842588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==2615== Your program just tried to execute an instruction that Valgrind
==2615== did not recognise.  There are two possible reasons for this.
==2615== 1. Your program has a bug and erroneously jumped to a non-code
==2615==location.  If you are running Memcheck and you just saw a
==2615==warning about a bad jump, it's probably your program's fault.
==2615== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2615==i.e. it's Valgrind's fault.  If you think this is the case or
==2615==you are not sure, please let us know and we'll try to fix it.
==2615== Either way, Valgrind will now raise a SIGILL signal which will
==2615== probably kill your program.
==2615== 
==2615== Process terminating with default action of signal 4 (SIGILL)
==2615==  Illegal opcode at address 0x4842588
==2615==at 0x4842588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==2615== 
==2615== HEAP SUMMARY:
==2615== in use at exit: 44,142 bytes in 302 blocks
==2615==   total heap usage: 347 allocs, 45 frees, 48,218 bytes allocated
==2615== 
==2615== LEAK SUMMARY:
==2615==definitely lost: 0 bytes in 0 blocks
==2615==indirectly lost: 0 bytes in 0 blocks
==2615==  possibly lost: 3,060 bytes in 87 blocks
==2615==still reachable: 41,082 bytes in 215 blocks
==2615== suppressed: 0 bytes in 0 blocks
==2615== Rerun with --leak-check=full to see details of leaked memory
==2615== 
==2615== For counts of detected and suppressed errors, rerun with: -v
==2615== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Killed

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

[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon

[Bhushan Shah via KDE Bugzilla]

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

--- Comment #6 from Bhushan Shah  ---
??? In comment #1 you said its Clipboard now you say device mounter??

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

[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon

[Anthony via KDE Bugzilla]

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

--- Comment #7 from Anthony  ---
It's *MUST* be Klipper, but it's device mounter. It's clear now?

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

[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Martin Gräßlin  ---
With slow animation speed I'm able to reproduce. My guess is it's a mishandling
in either sliding popup or blur effect.

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

[kwin] [Bug 344278] deco kcm segfault in KDecoration2::Decoration::update()

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||jessetalav...@aol.com

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

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

[systemsettings] [Bug 358616] Crash when trying to change window decorations

[Christoph Feck via KDE Bugzilla]

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

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 344278 ***

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

[Spectacle] [Bug 358608] Enable "Print images" kipi plugin

[Boudhayan Gupta via KDE Bugzilla]

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

--- Comment #1 from Boudhayan Gupta  ---
I don't want to re-enable the KIPI plugin for this, for a few reasons:

1) Eventually KIPI support will be dropped as Purpose matures.
2) Printing is a core feature, we don't want to rely on an external plugin for
this.
3) Having two Print actions (one core, one via KIPI) will only confuse users.

Not having those additional print settings is a bummer though. Perhaps the way
to fix this bug is to try incorporate those features into Spectacle's own print
feature?

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

[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage

[Anthony via KDE Bugzilla]

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

--- Comment #117 from Anthony  ---
(In reply to painless roaster from comment #113)
> Faster test:
>  - download plasmoid thermal monitor and set:
>  - refresh speed - 0.1s
>  - create 5 fields for temperature monitoring (physical id and 4 cores)
>  - in this test is leak speed is 12MB / minute
> 
> Is any chance for use memory leak profiler please? For example compile
> plasma-workspace with library jemalloc and use jeprof.
> Valgrind is too slow and not monitor during run. But jemalloc is ideal
> library for memory monitoring.

I cannot confirm i use it regular since it created, not remember, not leak at
all. Tell your graphic driver, mine is radeon, your nvidia?

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

[kwin] [Bug 356318] I can run wayland plasma session from terminal, not from sddm

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
> sddm looks freezed and I only have a mouse curser moving

does kwin start at all in that case? Are we still on sddm or did KWin take over
the session?

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

[frameworks-solid] [Bug 358603] unlocking luks encrypted drive gives an error

[Éric Brunet via KDE Bugzilla]

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

--- Comment #1 from Éric Brunet  ---
I forgot to mention that everything used to work fine on my fedora 21 system
(with kde 4), so this is a regression.

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

[plasmashell] [Bug 358624] New: Plasma Panel stays on disconnected Primary Output

[Malte S . Stretz via KDE Bugzilla]

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

Bug ID: 358624
   Summary: Plasma Panel stays on disconnected Primary Output
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: m...@apache.org
CC: plasma-b...@kde.org

This is probably the same issue as bug 355466 and bug 356608 but I file a new
one since the way of getting there is differently.

Reproducible: Always

Steps to Reproduce:
1. Connect a second monitor to your laptop (HDMI3 below)
2. Set that display as the Primary
3. Configure you Panel to be on that screen
4. Shut down
5. Disconnect the Primary monitor
6. Power up your machine again

Actual Results:  
The panel is lost, probably still on the primary monitor. It is impossible to
use desktop unless you know your tricks (eg. how to pull up KRunner).

Expected Results:  
The Panel should be available on the sole available screen (unless otherwise
configured). Especially if there's only one panel.

When the primary is disconnected, no screen is marked as primary anymore:

Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x
174mm
   1600x900  60.01*+  40.00  
   1440x900  59.89  
   1368x768  60.00  
   1360x768  59.8059.96  
   1152x864  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   800x450   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

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

[Spectacle] [Bug 358557] "Online services" menu is empty

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Boudhayan Gupta  ---
In a few months, all distributions will start shipping kf5-based kipi plugins
by default. Any additional effort on this bug will be wasted.

I'm closing this as wontfix. Feel free to re-open if you have *strong*
objections to this.

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

[okular] [Bug 275466] [Wish] Brochure printing / Booklet printing

[Phil Schaf via KDE Bugzilla]

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

Phil Schaf  changed:

   What|Removed |Added

 CC||flying-sh...@web.de

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

[kdenlive] [Bug 358427] 15.13 git master: monitor audio levels have no indicators for 0, -5, -10, -20 dB

[via KDE Bugzilla]

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

--- Comment #11 from wegwerf-1-...@gmx.de ---
Works now. Thank you very much Jean-Baptiste for this lightning fast fix!

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

[frameworks-solid] [Bug 347052] Solid reports "not connected" for interface brought up manually using dhclient

[Gunter Ohrner via KDE Bugzilla]

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

Gunter Ohrner  changed:

   What|Removed |Added

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

--- Comment #1 from Gunter Ohrner  ---
Cannot reproduce any more with my current installation, which currently is at
KDE Frameworks 5.18, kMail 5.0.3 and Network Manager 1.0.4.

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

[kdenlive] [Bug 358427] 15.13 git master: monitor audio levels have no indicators for 0, -5, -10, -20 dB

[via KDE Bugzilla]

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

--- Comment #12 from wegwerf-1-...@gmx.de ---
One really minor thing: when there is no audio data at all, then the meter
shows -20dB. As soon as there is audio data, the new low dB values kick in.
Could this be the "old" -20dB (-1000?) default in the Kdenlive meter display?

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

[valgrind] [Bug 358569] New: Unhandled instructions cause creation of "orphan" stack traces in XML output

[Adriaan Schmidt via KDE Bugzilla]

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

Bug ID: 358569
   Summary: Unhandled instructions cause creation of "orphan"
stack traces in XML output
   Product: valgrind
   Version: 3.11.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: adriaan.schmidt.siem...@gmail.com

When encountering unhandled instructions, Valgrind will provide a warning/error
message and a stack trace.
When running with --xml=yes, the warning will still appear in the console
output, but the stack trace will go to the XML.



Reproducible: Always

Steps to Reproduce:
Run:
valgrind --tool= --xml=yes --xml-file=out.xml /program/with/unhandled/insn

In my case, I run Helgrind on ARM, on a binary that uses libcrypto and thus
runs into bug 331178.

Actual Results:  
Running:
valgrind --tool=helgrind --xml=yes --xml-file=out.xml /my/program

I see on my console:
disInstr(arm): unhandled instruction: 0xEE190F1D
 cond=14(0xE) 27:20=225(0xE1) 4:4=1 3:0=13(0xD)
==909== valgrind: Unrecognised instruction at address 0x4d1cbf68.
==909== Your program just tried to execute an instruction that Valgrind
==909== did not recognise.  There are two possible reasons for this.
==909== 1. Your program has a bug and erroneously jumped to a non-code
==909==location.  If you are running Memcheck and you just saw a
==909==warning about a bad jump, it's probably your program's fault.
==909== 2. The instruction is legitimate but Valgrind doesn't handle it,
==909==i.e. it's Valgrind's fault.  If you think this is the case or
==909==you are not sure, please let us know and we'll try to fix it.
==909== Either way, Valgrind will now raise a SIGILL signal which will
==909== probably kill your program.

My XML output starts with:




4
helgrind


  Helgrind, a thread error detector
  Copyright (C) 2007-2015, and GNU GPL'd, by OpenWorks LLP et al.
  Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright
info
  Command: /my/program


909
907
helgrind


  
/usr/local/bin/valgrind
--tool=helgrind
--xml=yes
--xml-file=out.xml
  
  
/my/program
  



  RUNNING
  00:00:01:35.229 


  

  0x4D1CBF68
  /lib/libcrypto.so.1.0.0

  

  1
  



Expected Results:  
I would suggest that the stack trace be sent to console in this case.

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

[dolphin] [Bug 358571] New: Information panel does not efficiently display information

[Michael D via KDE Bugzilla]

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

Bug ID: 358571
   Summary: Information panel does not efficiently display
information
   Product: dolphin
   Version: 15.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: nortex...@gmail.com

When the information panel is set to be relatively narrow, which I assume is a
common configuration, the information is not efficiently displayed when there
are comments, due to the dual column nature. I've attached a screenshot showing
this.

The information would be better displayed under one column, with the headings
"Tags", "Ratings", etc. appearing e.g. centered and bolded. E.g. instead of

Comment: Lewis's
  amendment to
  the simple
  conditional
  analysis

we would have
   Comment
Lewis's amendment to the
simple conditional analysis

Perhaps this is better marked as a wish rather than bug.

Reproducible: Always

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

[kdenlive] [Bug 358427] 15.13 git master: monitor audio levels have no indicators for 0, -5, -10, -20 dB

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #10 from Jean-Baptiste Mardelle  ---
Git commit 67e3f6057ebf01a3aefe7b381a6442f5fd40207e by Jean-Baptiste Mardelle.
Committed on 26/01/2016 at 08:30.
Pushed by mardelle into branch 'master'.

Fix audio level on locale with comma

M  +4-2src/monitor/glwidget.cpp

http://commits.kde.org/kdenlive/67e3f6057ebf01a3aefe7b381a6442f5fd40207e

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

[kdenlive] [Bug 358570] New: feature request: timeline scene guides attached to clips that automatically move with clip

[via KDE Bugzilla]

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

Bug ID: 358570
   Summary: feature request: timeline scene guides attached to
clips that automatically move with clip
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

Kdenlive currently has timeline guides as well as clip markers. Markers belong
to clips, but are only visible within this particular clip in the timeline.
They are thus hard to spot in more complex projects. In contrast, timeline
guides are clearly visible. However, they are fixed to a particular position in
the timeline. As a project grows and clips gets inserted or deleted, scenes
often move. Unfortunately, timeline guides never move to accommodate for scene
edits, moves, et cetera.

I would like to propose that timeline guides can be attached to a particular
clip in the timeline. Typically, this would be the leading clip for a scene
opening. This way, the a "clip'ed" guide would automatically move accordingly
with the clip it is attached to as scenes move in the timeline.

Such "smart" guides would be a great help in more complex projects with maybe
five or ten "scenes". The guides would offer, well, guide and would always
correctly indicate the beginning of a scene without having them to maintain
manually in a project.

Reproducible: Always

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

[dolphin] [Bug 358571] Information panel does not efficiently display information

[Michael D via KDE Bugzilla]

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

--- Comment #1 from Michael D  ---
Created attachment 96846
  --> https://bugs.kde.org/attachment.cgi?id=96846=edit
Screenshot of issue

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