[kscreenlocker] [Bug 359680] ActiveChanged signal broken

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Gräßlin  ---
marking as fixed as of comment #4 - that's what I expected given that the
change mentioned in comment #2 got merged.

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

[kipiplugins] [Bug 361440] Panorama Tool can`t find a pto2mk.

[Yuri Fabl via KDE Bugzilla]

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

Yuri Fabl  changed:

   What|Removed |Added

  Component|DLNAExport  |general

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

[konsole] [Bug 358560] Konsole crashes when I unplug a second monitor

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #6 from Bernd Steinhauser  ---
I have not seen any issues with konsole crashing or disappearing when
disconnecting a screen during the last two months or so.

I think that this was (somehow?) fixed. Maybe you can confirm.

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

[kipiplugins] [Bug 361440] New: Panorama Tool can`t find a pto2mk.

[Yuri Fabl via KDE Bugzilla]

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

Bug ID: 361440
   Summary: Panorama Tool can`t find a pto2mk.
   Product: kipiplugins
   Version: 4.14.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DLNAExport
  Assignee: kde-imag...@kde.org
  Reporter: fabirovs...@gmail.com

When I open a panorama tool, the program can`t find a pto2mk.
I know that hugin, which is used in panorama tool no longer use pto2mk. That I
read in this article:
http://www.zdnet.com/article/how-i-solved-a-digikam-panorama-hiccup/
There is more detail about this problem. In this article says that I can use
hugin as a stand-alone program, but i don`t wont.
I hope, you will fix it.

Reproducible: Always

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

[plasmashell] [Bug 361439] New: plasma crash when session locked

[Fabrice Marchon via KDE Bugzilla]

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

Bug ID: 361439
   Summary: plasma crash when session locked
   Product: plasmashell
   Version: 5.6.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: fabrice.marc...@unil.ch
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.1)

Qt Version: 5.6.0
Frameworks Version: 5.20.0
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Nothing special, I locked my current session ; when I unlocked it the next day,
a warning about a crash occured.

The crash can be reproduced sometimes.

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

Thread 36 (Thread 0x7f719262d700 (LWP 18870)):
#0  0x7f71a2dd4bbd in poll () at /lib64/libc.so.6
#1  0x7f71a7d03422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f71a7d0500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f7194fb3979 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f71a34d1079 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f71a25de0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f71a2ddcfed in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f718bfff700 (LWP 18871)):
#0  0x7ffded3b0b26 in clock_gettime ()
#1  0x7f71a2de9c3d in clock_gettime () at /lib64/libc.so.6
#2  0x7f71a357beb6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f71a36e0a59 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f71a36e0fd5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f71a36e21ce in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f719f4be4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f719f4bed80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f719f4bef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f71a36e23fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f71a369004b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f71a34cc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f71a444d095 in  () at /usr/lib64/libQt5DBus.so.5
#13 0x7f71a34d1079 in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f71a25de0a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7f71a2ddcfed in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7f718abe9700 (LWP 18875)):
#0  0x7ffded3b0b26 in clock_gettime ()
#1  0x7f71a2de9c3d in clock_gettime () at /lib64/libc.so.6
#2  0x7f71a357beb6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f71a36e0a59 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f71a36e0fd5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f71a36e21ce in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f719f4be4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f719f4bed80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f719f4bef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f71a36e23fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f71a369004b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f71a34cc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f71a67c74d8 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7f71a34d1079 in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f71a25de0a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7f71a2ddcfed in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f717a2f1700 (LWP 18914)):
#0  0x7f71a2dd4bbd in poll () at /lib64/libc.so.6
#1  0x7f719f4bee64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f719f4bef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f71a36e23fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f71a369004b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f71a34cc5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f71a67c74d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f71a34d1079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f71a25de0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f71a2ddcfed in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f7178a26700 (LWP 18918)):
#0  0x7ffded3b0b26 in clock_gettime ()
#1  0x7f71a2de9c3d in clock_gettime () at /lib64/libc.so.6
#2  0x7f71a357beb6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f71a36e0a59 in 

[digikam] [Bug 361438] New: Dragging thumbnail to Tag produces wrong offer to tag.

[Jim Russell via KDE Bugzilla]

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

Bug ID: 361438
   Summary: Dragging thumbnail to Tag produces wrong offer to tag.
   Product: digikam
   Version: 4.14.0
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: jimrussell4...@gmail.com

Dragging thumbnail to Tag produces offer to tag with whatever is highlighted in
the Tag browser, rather than the tag on which you drop the item.

Reproducible: Always

Steps to Reproduce:
1. highlight any tag in Tags (center of 3 tabs when Captions/Tags is selected
at the right)
2. highlight one or more thumbnail images in central panel
3. click and hold right-mouse button, drag
4. drop on a row in Tags .

Actual Results:  
small dialog box "Assign  to Items (or Cancel)" appears.

Expected Results:  
small dialog box "Assign  to Items (or Cancel)"
appears.

Obviously not a big deal, but it reflects something that has gone wrong.
Collection dragged clearly stimulates processing when dropped onto a tag (if
you don't hit a tag, collection merely flows back to source, appropriately), so
the process clearly has knowledge of what items are in the right panel, but it
is picking up stale information before taking the step of offering an
assignment.

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

[kdenlive] [Bug 361090] Audio thumbnail incorrect

[Chris Gebhardt via KDE Bugzilla]

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

--- Comment #12 from Chris Gebhardt  ---
My versions are:
ffmpeg version 2.7.6-0ubuntu0.15.10.1   (standard Wily package)
melt  6.0.0+git201603291753~ubuntu15.10.1   (from kdenlive PPA)

With clearing the thumbnail cache properly while testing, I can say that none
of the thumbnails are generated properly when using FFmpeg. However, this
appears to be the only remaining problem I have and it may likely be a local
issue.

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

[kscreenlocker] [Bug 359680] ActiveChanged signal broken

[Janne Rönkkö via KDE Bugzilla]

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

--- Comment #4 from Janne Rönkkö  ---
Actually, I had version 5.6.2 installed but was still using 5.6.1.

After restarting KDE ActiveChanged signal works.

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

[plasmashell] [Bug 360994] expander arrow direction wrong in desktop

[andreas via KDE Bugzilla]

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

--- Comment #3 from andreas  ---
My problem is not the arrow direction. I report the bug because the arrow is
always in a new column and this look strange when there is space in the same
column.

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

[kscreenlocker] [Bug 359680] ActiveChanged signal broken

[Janne Rönkkö via KDE Bugzilla]

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

Janne Rönkkö  changed:

   What|Removed |Added

 CC||j...@iki.fi

--- Comment #3 from Janne Rönkkö  ---
I'm also seeing this issue.

I'm running Archlinux with kdescreenlocker version 5.6.2 (arch version 5.6.2-1)
which has the fix for D1314.

Also qdbus org.kde.screensaver /ScreenSaver
org.freedesktop.ScreenSaver.GetActive return false even when screen saver is
active but I guess this is due to the same reason ActiveChanged(true) is not
sent at all.

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

[Breeze] [Bug 361428] Inconsistent icons in some applications

[andreas via KDE Bugzilla]

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

--- Comment #1 from andreas  ---
Thanks for reporting the bug. Can you add a screenshot please

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

[valgrind] [Bug 354883] Valgrind-3.11.0 assertion failure on OSX 10.11 El Capitan

[Rhys Kidd via KDE Bugzilla]

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

Rhys Kidd  changed:

   What|Removed |Added

 CC||wwa...@gmail.com

--- Comment #14 from Rhys Kidd  ---
*** Bug 361351 has been marked as a duplicate of this bug. ***

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

[valgrind] [Bug 361351] Assertion failure analyzing SDL_Init()

[Rhys Kidd via KDE Bugzilla]

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

Rhys Kidd  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||rhysk...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Rhys Kidd  ---
Hello Wes,
This is a duplicate of the tracked bug #354883. Refer there for updates.

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

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

[systemsettings] [Bug 361436] Searching for "animation speed" highlights the wrong KCM

[Burkhard Lueck via KDE Bugzilla]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

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

[plasmashell] [Bug 361437] New: startkde -> startplasmacompositor -> startkde = "blackscreen"

[James via KDE Bugzilla]

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

Bug ID: 361437
   Summary: startkde -> startplasmacompositor -> startkde =
"blackscreen"
   Product: plasmashell
   Version: 5.6.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ja...@nurealm.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Arch Linux
plasma-workspace 5.6.1-1
systemd 229-3
AMD/ATI Redwood PRO Radeon HD 5570 with triple display
Intel Core2 Quad CPUQ6600

I'm not sure where this report should go. I am submitting it here only because
plasma-workspace owns startplasmacompositor. I seem to have found some kind of
workaround.

Running startplasmacompositor just once will cause a previously working X11 KDE
to fail repeatedly thereafter.  "Replacing" the socket /var/run/user/1000/bus
seems to restore normal X11 KDE functionality.  This is a problem because
anyone who just "dabbles" with Wayland KDE can make their X11 KDE unusable. 
Rebooting the machine is an extreme but effective method of "replacing" the
"bus" socket.

Problem:
1) run startx with startkde - it starts normally, with the splashscreen
disappearing quickly.
2) exit
3) run startplasmacompositor - it starts normally, but the splashscreen hangs
for about 25 seconds before fading.
4) exit
5) run startx with startkde - it starts with a splashscreen which hangs for
about 25 seconds.
Then, fade to "blackscreen".
The mouse works, X applications can be run, but the desktop is unresponsive.

After trying things like deleting ~/.cache and ~/.kde4, which made no
difference, I tried:
$ rm -R /var/run/user/1000/
which allowed startkde to produce a working desktop.

It make no difference to delete the files like
/var/run/user/1000/klauncherXM6740.1.slave-socket

And it makes no difference to kill the process like
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile
--systemd-activation

Upgrading from 5.6.0 to 5.6.1 makes no difference.

After some trial and error, I found it necessary to restart the process
/usr/lib/systemd/systemd --user

It is not enough to log out, which leaves this process running, and it is not
effective to kill it and try to run it manually, which gives permission errors.
So, it is necessary to find the process with something like "$ ps lU 1000",
then "$ kill ", then log out, then log back in. After all of that, startx
with startkde will function again.

Rebooting the machine will have an equivalent effect, but that is an extreme
remedy.

It seems odd to me that logging out will not automatically kill the "systemd
--user" process, in particular, when there are no other logins on other virtual
terminals, but I suppose that that is a systemd thing.

I notice that "systemd --user" creates the file "/var/run/user/1000/bus", so
this may be a dbus issue.

But then, killling "systemd --user" also - finally - kills other "lurking"
background user processes. Still, comparing the process list after exiting a
working startkde session and after a startplasmacompositor session, the only
change is a new process id for
/usr/bin/pulseaudio --daemonize=no
and
/usr/lib/pulse/gconf-helper
Killing these processes before startkde make no difference. So I would expect
that this is a dbus related issue.


Reproducible: Always

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

[plasmashell] [Bug 352647] Plasmoid popups don't reliably open with high focus stealing prevention

[via KDE Bugzilla]

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

r...@alum.mit.edu changed:

   What|Removed |Added

 CC||r...@alum.mit.edu

--- Comment #5 from r...@alum.mit.edu ---
Still happens in 5.6.1 (openSUSE RPMs).  FSP set to high or extreme, focus
follows mouse/mouse priority, the menu will not pop (there's a quick flash in
the taskbar, but the menu never pops up).

Oddly enough, the other day I'm quite sure I got it to pop by clicking on an
open part of the desktop (or moved to a different virtual screen) to defocus
everything and it worked, but it didn't today, and I had to run systemsettings5
in a terminal window to reset FSP to medium to be able to get the menu.  I just
tried again, and I got it to pop in high but not extreme.  So there would
appear to be something funny going on.

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

[kate] [Bug 355220] Segmentation fault if I split view, close current file, "open recent" and reopen the file.

[Marco T . via KDE Bugzilla]

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

--- Comment #2 from Marco T.  ---
Sorry, I am not using KDE anymore so I cannot reproduce.

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

[systemsettings] [Bug 361436] New: Searching for "animation speed" highlights the wrong KCM

[Thomas Pfeiffer via KDE Bugzilla]

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

Bug ID: 361436
   Summary: Searching for "animation speed" highlights the wrong
KCM
   Product: systemsettings
   Version: 5.6.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcmshell
  Assignee: kdelibs-b...@kde.org
  Reporter: colo...@autistici.org

When searching in system settings for "animation speed", the "Deskop Behavior"
group is highlighted, but one cannot find this setting there anymore.
Instead, the "Display and Monitor" group has to be highlighted, because the
setting is in the Compositor KCM now.

Reproducible: Always

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

[dolphin] [Bug 361383] Dolphin crashes frequently

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |DUPLICATE

--- Comment #2 from Christoph Feck  ---


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

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

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||dopazo.alv...@gmail.com

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

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[JS Gibson via KDE Bugzilla]

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

JS Gibson  changed:

   What|Removed |Added

 CC||jgibson...@gmail.com

--- Comment #101 from JS Gibson  ---
(In reply to Ruslan Kabatsayev from comment #0)
> Often after I suspend my machine, wait some time and resume back, I see
> sometimes black, other times corrupted screen with blinking triangles of
> distorted windows content. This happens on at least two machines I'm working
> on, both with nvidia video cards (one Quadro (can't tell details yet),
> another GeForce GTX 750 Ti with binary driver 340.46), both machines running
> 64 bit kernel.
> 
> This is a regression, and I've run git-bisect to find that the bad commit is
> commit 1f0bb6d36075b0b14c927b91d5c3df6720826afd
> Author: Fredrik Höglund 
> Date:   Thu Mar 21 23:52:03 2013 +0100
> 
> kwin: Use the new API for rendering quads
> 
> This bug sometimes doesn't reproduce, so I can only be _almost_ sure that
> previous versions don't have it. But I've tested kwin version right before
> this commit, at f709af7c7e23010293c8eb9fa67871adfdb75207, and haven't seen
> any problems for several days, so I think the above bad commit should be the
> right one.
> 
> Reproducible: Sometimes
> 
> Steps to Reproduce:
> 1. Run kwin with OpenGL compositing on an nvidia card with binary driver
> 2. Suspend to RAM
> 3. Wait several minutes (sometimes needs hours, don't know what triggers it)
> 4. Resume
> 
> Actual Results:  
> Screen is garbled with flickering triangles textured with parts of desktop
> content, or sometimes screen is just black
> 
> Expected Results:  
> Desktop should render normally
> 
> Toggling compositing off and on by double pressing Alt+Shift+F12 fixes the
> screen and lets me work normally until next suspend/resume cycle.

The same thing also happens whenever I change resolutions. If I have a game
start up in a lower res, and then change it, it also happens. I was wondering
if you have multiple monitors. I have a laptop set up with an external monitor
that I run with the lid closed. The machine always goes to  the laptop monitor
(1920x1080) when KDE starts (gonna be researching this bug next). After
entering the password (have to do it blind) it will change over to the external
(1920x1200) monitor. I was thinking it was the resolution change as it doesn't
happen when I boot up without the external monitor.

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

[k3b] [Bug 360897] When burning a DVD+RW, which should be overwritten, then "Ersetzen" is displayed

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #7 from Frederik Schwarzer  ---
I am not quite sure what to add to the discussion at this point. The 2011 one
seems still legit but the issue discussed back then is a different one than in
this report. So translation context seems like the only way to solve this.

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[via KDE Bugzilla]

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

--- Comment #16 from r...@alum.mit.edu ---
So there is still a problem: when I'm saving a document in LibreOffice, it
grabs focus away a couple of times when it's done even with focus stealing
prevention set to extreme and when I was typing into Firefox in a different
virtual desktop (which shouldn't matter -- my understanding is that with
FSP=extreme an application should *never* be able to grab focus, period).

FSP=high or extreme also renders the K menu completely useless; I had to run
systemsettings5 manually to set the FSP back to medium to be able to get the K
menu.

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

[akregator] [Bug 361435] New: Crash while going thrugh unread articles

[Shai via KDE Bugzilla]

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

Bug ID: 361435
   Summary: Crash while going thrugh unread articles
   Product: akregator
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: s...@platonix.com

Application: akregator (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.7
Operating System: Linux 4.0.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

Opened a feed with very many unread articles, and started going over them. At
some point, when moving (with KB -- right arrow, "next article"), akregator
crashed.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  GetAt (nIndex=, this=0x3be9aa0) at
../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:54
#7  c4_Column::ReleaseSegment (this=0x3be9aa0, index_=) at
../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:116
#8  0x7f4a02a98d6d in c4_Column::ReleaseAllSegments
(this=this@entry=0x3be9aa0) at
../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:124
#9  0x7f4a02a98dc1 in c4_Column::SetLocation (this=this@entry=0x3be9aa0,
pos_=pos_@entry=-228961430, size_=size_@entry=125) at
../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:142
#10 0x7f4a02aa5c03 in c4_SaveContext::CommitColumn
(this=this@entry=0x7ffd46207400, col_=...) at
../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:819
#11 0x7f4a02aa1895 in c4_FormatB::Commit (this=0x24c86f0, ar_=...) at
../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:775
#12 0x7f4a02aa5cdd in c4_SaveContext::CommitSequence
(this=this@entry=0x7ffd46207400, seq_=..., selfDesc_=selfDesc_@entry=false) at
../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:841
#13 0x7f4a02aa269a in c4_FormatV::Commit (this=0x24c4790, ar_=...) at
../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1174
#14 0x7f4a02aa5cdd in c4_SaveContext::CommitSequence
(this=this@entry=0x7ffd46207400, seq_=..., selfDesc_=selfDesc_@entry=true) at
../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:841
#15 0x7f4a02aa62aa in c4_SaveContext::SaveIt
(this=this@entry=0x7ffd46207400, root_=...,
spacePtr_=spacePtr_@entry=0x24c7170, rootWalk_=...) at
../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:709
#16 0x7f4a02aa6619 in c4_Persist::Commit (this=0x24c7170, full_=) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:933
#17 0x7f4a02aa66c1 in c4_Persist::Commit (this=,
full_=) at
../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:935
#18 0x7f4a02aab51e in c4_Storage::Commit (this=,
full_=full_@entry=false) at
../../../../akregator/plugins/mk4storage/metakit/src/store.cpp:361
#19 0x7f4a02ab0d7f in Akregator::Backend::FeedStorageMK4Impl::commit
(this=0x208c860) at
../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:181
#20 0x7f4a02ab6dd5 in Akregator::Backend::StorageMK4Impl::commit
(this=0x1f9fe00) at
../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:178
#21 0x7f4a02ab633a in Akregator::Backend::StorageMK4Impl::slotCommit
(this=0x1f9fe00) at
../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:283
#22 0x7f4a1bab038c in QMetaObject::activate (sender=sender@entry=0x9e9b6f0,
m=m@entry=0x7f4a1bdfe540 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3567
#23 0x7f4a1bab96ba in timeout (this=0x9e9b6f0) at
.moc/release-shared/qtimer.moc:96
#24 QSingleShotTimer::timerEvent (this=0x9e9b6f0) at kernel/qtimer.cpp:317
#25 0x7f4a1bab4953 in QObject::event (this=0x9e9b6f0, e=) at
kernel/qobject.cpp:1253
#26 0x7f4a1c4ba7bc in QApplicationPrivate::notify_helper
(this=this@entry=0x1cf0e80, receiver=receiver@entry=0x9e9b6f0,
e=e@entry=0x7ffd46207b10) at kernel/qapplication.cpp:4570
#27 0x7f4a1c4c12d8 in QApplication::notify (this=this@entry=0x7ffd46207f70,
receiver=receiver@entry=0x9e9b6f0, e=e@entry=0x7ffd46207b10) at
kernel/qapplication.cpp:4356
#28 0x7f4a1d2381aa in KApplication::notify (this=0x7ffd46207f70,
receiver=0x9e9b6f0, event=0x7ffd46207b10) at
../../kdeui/kernel/kapplication.cpp:311
#29 0x7f4a1ba9b36d in QCoreApplication::notifyInternal
(this=0x7ffd46207f70, receiver=0x9e9b6f0, event=event@entry=0x7ffd46207b10) at
kernel/qcoreapplication.cpp:955
#30 0x7f4a1baccffb in sendEvent (event=0x7ffd46207b10, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#31 QTimerInfoList::activateTimers (this=0x1cf61a0) at
kernel/qeventdispatcher_unix.cpp:621
#32 

[krusader] [Bug 361434] New: Krusader won't offer option to "remember password" for SSH / FTP connections

[Dan Duris via KDE Bugzilla]

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

Bug ID: 361434
   Summary: Krusader won't offer option to "remember password" for
SSH / FTP connections
   Product: krusader
   Version: 2.4.0-beta3 "Single Step"
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: kdeb...@staznosti.sk

I had KWallet first disabled, now I have reenabled it. However, Krusader now
won't offer an option to save a password, rather annoyingly asks for it every
time.

Also, another small UX bug is that once I press cancel button (not entering the
password), Krusader just loops the modal username/password dialog infinitely.
In the past version the behavior was that Krusader would disconnect the remote
connection on cancelling the username/password modal box (which is the desired
behavior IMO).

PS: I tried to check all the config files (and GUI options) of Krusader, but
there does not seem to be an option to change the password saving behavior.

Reproducible: Always

Steps to Reproduce:
1. Disable Kwallet, connect to remote server
2. Enable KWallet
3. Krusader now won't save the password or offer option to save it

Actual Results:  
No option to save passwords / passwords not saved

Expected Results:  
Option to save passwords / passwords saved

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

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

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

--- Comment #61 from Walter Nicholls  ---
I haven't seen this problem reoccur for me in the last month. Maybe a software
patch has changed behaviour:
Kernel now 4.2.0-35-generic 
plasma-workspace at  4:5.4.2-0ubuntu1.1
nvidia-352  version 352.63-0ubuntu0.15.10.1
(I'm not sure which packages are actually relevant to this).

Other family members with KDE computers haven't ever seen this, by the way,
although my wife did have a problem which toggling Alt-Ctrl-F12 fixed for her.
Something about the plasma bar getting corrupted? Could have been same issue.
Fairly old Toshiba laptop with intel video.

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

[systemsettings] [Bug 361433] New: Adding a program with no .desktop is buggy when .local/share/applications/rt doesn’t exist

[via KDE Bugzilla]

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

Bug ID: 361433
   Summary: Adding a program with no .desktop is buggy when
.local/share/applications/rt doesn’t exist
   Product: systemsettings
   Version: 5.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_autostart
  Assignee: mon...@kde.org
  Reporter: pe...@hack-libre.org

E.g. I get the error «Could not save properties. You do not have sufficient
access to write to
/home/ariasuni/.local/share/applications/rt/ibus-daemon.desktop.».

Reproducible: Always

Steps to Reproduce:
Add Program → i type «ibus-daemon» then OK → OK again → I get the error
message. It seems to be working, but I also get this message each time I click
«Properties» then «OK» for this particular Program (and the edit fail).


Expected Results:  
.local/share/applications/rt/ should be created before trying to create a file
in this directy, so that every subsequent operations succeed.

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

[okular] [Bug 162219] Adjust view to the position where you clicked into the thumbnail

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/okul
   ||ar/c183dd8bd300b39e55e3309b
   ||6b279b6e7b8e19c2
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Albert Astals Cid  ---
Git commit c183dd8bd300b39e55e3309b6b279b6e7b8e19c2 by Albert Astals Cid, on
behalf of Miklós Máté.
Committed on 05/04/2016 at 22:31.
Pushed by aacid into branch 'Applications/16.04'.

Set viewport to the position clicked on the thumbnail list

Also fix the mouse cursor shape
REVIEW: 127526

M  +29   -21   ui/thumbnaillist.cpp

http://commits.kde.org/okular/c183dd8bd300b39e55e3309b6b279b6e7b8e19c2

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

[plasma-nm] [Bug 356342] Size of popup of plasma-nm inside panel or desktop is very small

[Xavier Corredor Llano via KDE Bugzilla]

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

--- Comment #5 from Xavier Corredor Llano  ---
Created attachment 98263
  --> https://bugs.kde.org/attachment.cgi?id=98263=edit
Example size of plasma-nm

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

[plasma-nm] [Bug 356342] Size of popup of plasma-nm inside panel or desktop is very small

[Xavier Corredor Llano via KDE Bugzilla]

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

Xavier Corredor Llano  changed:

   What|Removed |Added

 CC||xavier.corredor.llano@gmail
   ||.com

--- Comment #4 from Xavier Corredor Llano  ---
This bug is still present in the latest version (see attachment) using
Archlinux and plasma-nm v5.6.2. My display is 1080p in 14 inch size. HiDPI
problem?

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

[okular] [Bug 323213] [frameworks] Okular could not render FB2 (Fiction Book) format properly

[Albert Astals Cid via KDE Bugzilla]

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

--- Comment #7 from Albert Astals Cid  ---
In the future, don't reuse a bug that was fixed 3 years ago, it doesn't make
sense thinking that code that was added 3 years ago somehow vanished.

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

[okular] [Bug 323213] [frameworks] Okular could not render FB2 (Fiction Book) format properly

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

Summary|Okular could not render FB2 |[frameworks] Okular could
   |(Fiction Book) format   |not render FB2 (Fiction
   |properly|Book) format properly

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

[kate] [Bug 350535] Ctrl-Shift-U fails for inputting unicode

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

--- Comment #2 from Weng Xuetian  ---
No, I don't think it's related. 2022 is not a over U+1 character.

The underline u is a feature provided by ibus. You should check whether you
have ibus's qt5 input context installed and configured correctly.

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

[okular] [Bug 361158] Rotating page should not change magnification

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||aa...@kde.org
 Resolution|--- |INVALID

--- Comment #1 from Albert Astals Cid  ---
Sorry but it's not a bug, you had fit width, and then you rotated the document,
fit width kept applying, if you didn't want fit width you should not have
chosen it.

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

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #60 from Franco Pellegrini  ---
Also, to confirm, going to EGL in favor of GLX, does not seem to help at all
for me... I have to Alt+Shift+F12 to disable effects in order to restore
drawing

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

[kate] [Bug 330843] Support .editorconfig config files

[Samat Jain via KDE Bugzilla]

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

Samat Jain  changed:

   What|Removed |Added

 CC||b...@samat.org

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

[okular] [Bug 361408] Okular crashed while zooming vectorial image

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Albert Astals Cid  ---
Can you reproduce the problem?

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

[ktorrent] [Bug 357160] KTorrent GUI freezes randlomly and stops torrent downloads

[Amichai Rothman via KDE Bugzilla]

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

Amichai Rothman  changed:

   What|Removed |Added

 CC||amich...@amichais.net

--- Comment #3 from Amichai Rothman  ---
Duplicate of bug #354633 ?

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

[digikam] [Bug 361339] Album auto-creation creates nameless subalbums and corrupts album hierarchy

[via KDE Bugzilla]

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

--- Comment #14 from kram...@web.de ---
I'm setting up a new family picture server via NFS V3, server is BTRFS. This
used to work approx. 4 weeks ago, don't know which update broke it.

Latests tests were done on a laptop on ext4 (DB and picture folders). Can also
reproduce on XFS and on Samba mounts, so I don't think it's FS related.

Latest output:

[...]
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
>AlbumManager::createPAlbum--1--> "New Album"
>AlbumManager::createPAlbum--2--> (".", "..", "Folder")
>AlbumManager::createPAlbum--3-->
QUrl("file:///mufu/transfer/test-local5/Folder/New Album")
digikam.general: QFileSystemWatcher detected change at
"/mufu/transfer/test-local5/Folder//"
digikam.general: Detected change, triggering rescan of directory
"/mufu/transfer/test-local5/Folder//"
>AlbumManager::createPAlbum--4--> (".", "..", "Folder")
digikam.database: Starting scan!
digikam.dimg: "/mufu/transfer/test-local5/Folder//Subfolder/user-manager.png" 
: PNG file identified
digikam.database: Adding new item
"/mufu/transfer/test-local5/Folder//Subfolder/user-manager.png"
digikam.database: Recognized
"/mufu/transfer/test-local5/Folder//Subfolder/user-manager.png" as identical to
item 11
digikam.database: Scanning took 1 ms
digikam.database: Finishing took 5 ms
digikam.geoiface: 
digikam.general: Cancel Main Thread
[...]

Heinz (afk for today)

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

[digikam] [Bug 361378] Tags are not being removed from files metadata

[wildcowboy via KDE Bugzilla]

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

--- Comment #3 from wildcowboy  ---
(In reply to Maik Qualmann from comment #2)
> The problem here is with digiKam-5.0.0-beta5 not to reproduce. The writing
> of image tags must of course be activated in the metadata settings.
> Otherwise old tags are not updated and with a new reading of the metadata
> appear again.
> 
> Maik

Hello Maik 
Thanks for looking into that. I am pretty sure the setting "white Metadata into
files" is being switched on. I will double check when I am back in front of the
desktop though and will let you know.

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

[plasmashell] [Bug 361432] New: plasmashell crashes when it runs out of memory

[Tim Goodwin via KDE Bugzilla]

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

Bug ID: 361432
   Summary: plasmashell crashes when it runs out of memory
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: t...@eekageek.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org

Using neon unstable version 5.6.90 memory usage of plasmashell increases until
plasmashell crashes and restarts. This has been happening for a couple of weeks
now.

Reproducible: Always

Steps to Reproduce:
1.Reboot
2.Plasmashell starts taking up memory
3.Crashes.

Actual Results:  
Plasmashell crashes and restarts

Expected Results:  
Plasmashell should be stable.

Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fce693d97c0 (LWP 1562))]

Thread 33 (Thread 0x7fce55690700 (LWP 1563)):
#0  0x7fce63a3c88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce67b5abd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fce67b5c74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fce57e42a49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce632186aa in start_thread (arg=0x7fce55690700) at
pthread_create.c:333
#6  0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 32 (Thread 0x7fce4e8d8700 (LWP 1587)):
#0  0x7fce63a3c88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce607731ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce607732fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce643764fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce6431d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce64139ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce66a0e105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fce632186aa in start_thread (arg=0x7fce4e8d8700) at
pthread_create.c:333
#9  0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 31 (Thread 0x7fce416b8700 (LWP 1607)):
#0  0x7fce607b7884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fce60772c19 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce60773190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce607732fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fce643764fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce6431d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce64139ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce66a0e105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fce632186aa in start_thread (arg=0x7fce416b8700) at
pthread_create.c:333
#10 0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 30 (Thread 0x7fce3b580700 (LWP 1624)):
#0  0x7fce63a3c88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce607731ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce607732fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce643764fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce6431d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce64139ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce66a0e105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fce632186aa in start_thread (arg=0x7fce3b580700) at
pthread_create.c:333
#9  0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 29 (Thread 0x7fce39a70700 (LWP 1652)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fce68e0f194 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fce68e0f1d9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fce632186aa in start_thread (arg=0x7fce39a70700) at
pthread_create.c:333
#4  

[plasmashell] [Bug 361431] New: plasmashell crashes when it runs out of memory

[Tim Goodwin via KDE Bugzilla]

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

Bug ID: 361431
   Summary: plasmashell crashes when it runs out of memory
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: t...@eekageek.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org

Using neon unstable version 5.6.90 memory usage of plasmashell increases until
plasmashell crashes and restarts. This has been happening for a couple of weeks
now.

Reproducible: Always

Steps to Reproduce:
1.Reboot
2.Plasmashell starts taking up memory
3.Crashes.

Actual Results:  
Plasmashell crashes and restarts

Expected Results:  
Plasmashell should be stable.

Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fce693d97c0 (LWP 1562))]

Thread 33 (Thread 0x7fce55690700 (LWP 1563)):
#0  0x7fce63a3c88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce67b5abd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fce67b5c74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fce57e42a49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce632186aa in start_thread (arg=0x7fce55690700) at
pthread_create.c:333
#6  0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 32 (Thread 0x7fce4e8d8700 (LWP 1587)):
#0  0x7fce63a3c88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce607731ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce607732fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce643764fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce6431d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce64139ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce66a0e105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fce632186aa in start_thread (arg=0x7fce4e8d8700) at
pthread_create.c:333
#9  0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 31 (Thread 0x7fce416b8700 (LWP 1607)):
#0  0x7fce607b7884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fce60772c19 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce60773190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce607732fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fce643764fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce6431d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce64139ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce66a0e105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fce632186aa in start_thread (arg=0x7fce416b8700) at
pthread_create.c:333
#10 0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 30 (Thread 0x7fce3b580700 (LWP 1624)):
#0  0x7fce63a3c88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce607731ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce607732fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce643764fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce6431d50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce64139ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce66a0e105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fce6413ea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fce632186aa in start_thread (arg=0x7fce3b580700) at
pthread_create.c:333
#9  0x7fce63a47e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 29 (Thread 0x7fce39a70700 (LWP 1652)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fce68e0f194 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fce68e0f1d9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fce632186aa in start_thread (arg=0x7fce39a70700) at
pthread_create.c:333
#4  

[kdeconnect] [Bug 361430] New: no headers installed for custom plugins

[Ben Boeckel via KDE Bugzilla]

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

Bug ID: 361430
   Summary: no headers installed for custom plugins
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: maths...@gmail.com

It would be nice if the headers that could be used to create custom plugins for
communicating with other systems (I'm thinking of eventd[1] personally) were
installed so that there was something to compile against.

[1]https://www.eventd.org/

Reproducible: Always

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

[kscreenlocker] [Bug 181554] Screen keyboard when screen is locked

[Hannes Schniepp via KDE Bugzilla]

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

Hannes Schniepp  changed:

   What|Removed |Added

 CC||why...@nurfuerspam.de

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

[kde] [Bug 361429] Plasma 5 not usable on tablets: no virtual keyboard option to log in or unlock screen locker

[Hannes Schniepp via KDE Bugzilla]

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

--- Comment #2 from Hannes Schniepp  ---
It is also related to this bug:
https://bugs.kde.org/show_bug.cgi?id=181554

However, 181554 only addresses the screen locker component and not the SDDM
component of the problem.

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

[kde] [Bug 361429] Plasma 5 not usable on tablets: no virtual keyboard option to log in or unlock screen locker

[Hannes Schniepp via KDE Bugzilla]

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

Hannes Schniepp  changed:

   What|Removed |Added

 CC||why...@nurfuerspam.de

--- Comment #1 from Hannes Schniepp  ---
This is related to this older bug filed for kdm:
https://bugs.kde.org/show_bug.cgi?id=200732

However, kdm is not part of most linux-based plasma 5 installations any longer;
therefore, a new bug was filed.

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

[digikam] [Bug 361339] Album auto-creation creates nameless subalbums and corrupts album hierarchy

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #13 from Maik Qualmann  ---
Created attachment 98262
  --> https://bugs.kde.org/attachment.cgi?id=98262=edit
test2Debug.patch

Strange problem, please give me the ouput from this patch. What for a  file
system you use?

Maik

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

[kde] [Bug 361429] New: Plasma 5 not usable on tablets: no virtual keyboard option to log in or unlock screen locker

[Hannes Schniepp via KDE Bugzilla]

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

Bug ID: 361429
   Summary: Plasma 5 not usable on tablets: no virtual keyboard
option to log in or unlock screen locker
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: why...@nurfuerspam.de

As far as I can tell, there is no virtual keyboard implemented for SDDM, which
is the recommended display manager of Plasma 5. Same for the plasma 5 screen
locker. This makes the entire plasma 5 completely unusable for anyone who wants
to do serious business on a tablet. After a lot of googling, I haven't found
any signs that this is being worked on.


Reproducible: Always

Steps to Reproduce:
1. Install any KDE/plasma 5 distribution on a tablet.
2. Boot and wait until display manager shows.
3. It is impossible to log in, since no virtual keyboard is implemented to put
in login credentials.

Actual Results:  
No virtual (onscreen) keyboard shows up for the SDDM greeter by default, nor is
this functionality installable later via systemsettings or other means. Same
for the screen locker, which has currently no option to install a virtual
(onscreen) keyboard.

Expected Results:  
The SDDM greeter should either have the default functionality to invoke an
onscreen keyboard, or it should be possible to install or enable such
functionality. Same for the screen locker. The screen locker looks identical to
the SDDM greeter, but under the hood there are likely different
mechanisms/components creating the same optical results. (I know that in KDE4
these were implemented by KDM/LightDM and kscreenlocker.)

In KDE4, it took me quite a bit of hacking to get this implemented by fiddling
around with the KDM scripts to invoke kvkbd, and with the kscreenlocker to
invoke "onboard" (slightly more convenient to use than kvkbd).

Many distros will soon end support for KDE4 (i.e. Kubuntu), so if I want to
keep operating my device safely and patched, I will have to migrate to plasma
5. The latter does currently not work with my device, so I would have to switch
to something like Unity, but I would prefer to stay on KDE.

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

[digikam] [Bug 361339] Album auto-creation creates nameless subalbums and corrupts album hierarchy

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

  Attachment #98247|0   |1
is obsolete||

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

[digikam] [Bug 361339] Album auto-creation creates nameless subalbums and corrupts album hierarchy

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

  Attachment #98257|0   |1
is obsolete||

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

[okular] [Bug 360974] Shift+click does not work for some PDF files

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[Breeze] [Bug 361428] New: Inconsistent icons in some applications

[Marcelo Escobal via KDE Bugzilla]

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

Bug ID: 361428
   Summary: Inconsistent icons in some applications
   Product: Breeze
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: marcelo.esco...@gmail.com
CC: kain...@gmail.com

Breeze icons are inconsistent in some applications (ie Kontact: side bar icons
of different style -> some icons in color, some in b).

Reproducible: Always

Steps to Reproduce:
1. Open Kontact
2. Set left column icons to any size
3. 

Actual Results:  
Some icons are in color and some are b (with different size).

Expected Results:  
Al icons in same style.

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

[kate] [Bug 355220] Segmentation fault if I split view, close current file, "open recent" and reopen the file.

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Dominik Haumann  ---
Cannot reproduce, probably got fixed meanwhile. If you can provide a proper
backtrace, please do so.

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

[digikam] [Bug 361339] Album auto-creation creates nameless subalbums and corrupts album hierarchy

[via KDE Bugzilla]

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

--- Comment #12 from kram...@web.de ---
Created attachment 98261
  --> https://bugs.kde.org/attachment.cgi?id=98261=edit
Console output after mkdirTest.patch

Sorry, no progress. issue still exists.

Heinz

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

[kdm] [Bug 200732] Integrated onscreen keyboard into login dialog

[Hannes Schniepp via KDE Bugzilla]

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

Hannes Schniepp  changed:

   What|Removed |Added

 CC||why...@nurfuerspam.de

--- Comment #6 from Hannes Schniepp  ---
It's worse in plasma 5, where there is no onscreen keyboard/virtual keyboard at
all for both the screen locker, and the display manager. This makes plasma 5
unusable on tablet computers.

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

[plasmashell] [Bug 360226] Desktop icons in Folder View sometimes doesnt snap to the dragged destination

[Mike via KDE Bugzilla]

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

--- Comment #8 from Mike  ---
Created attachment 98260
  --> https://bugs.kde.org/attachment.cgi?id=98260=edit
Screen Recording of the "rubberband" effect

I tried to show the problem with locked desktop widgets ( German:
Miniprogramme) and the rubberband effect. Hope that makes it clear.

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

[kate] [Bug 354958] Little used feature causes crash when used...

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Dominik Haumann  ---
Cannot reproduce, may be fixed meanwhile.

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

[kate] [Bug 350972] Kate segfault when providing a faulty syntax file

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Dominik Haumann  ---
Recursive use of IncludeRules.

We probably should have a guard against this...

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

[plasmashell] [Bug 360226] Desktop icons in Folder View sometimes doesnt snap to the dragged destination

[Mike via KDE Bugzilla]

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

--- Comment #7 from Mike  ---
Hi Eike,  Vokoscreen is a wonderful tool - thanks for the tip ;-) I just
recorded the effect on my desktop. Hope that makes it clear ...and yes -
English is not my native language ;-))

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

[kde] [Bug 361427] New: Crash when resizing the window after adding a view

[Ovidiu-Florin BOGDAN via KDE Bugzilla]

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

Bug ID: 361427
   Summary: Crash when resizing the window after adding a view
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ovidiu@gmail.com

Application: kdenlive (16.07.70)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-34-generic x86_64
Distribution: Ubuntu 15.10

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

I've added the Audio waveform view and it didn't appear, so I tried to move
views around, and then de-maximized the window and maximized it. I did this a
few times because the GUI had frozen.

I'm using the build from kde Kdenlive master ppa, updated yesterday.

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

Thread 118 (Thread 0x7fce10e9e700 (LWP 5753)):
#0  0x7fce1eccf88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce19bf4bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fce19bf674f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fce131eb7e9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fce1f6cda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce1d8b86aa in start_thread (arg=0x7fce10e9e700) at
pthread_create.c:333
#6  0x7fce1ecdae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 117 (Thread 0x7fcdef33f700 (LWP 5754)):
#0  0x7fce1eccf88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fcdf726e12c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7fce1d8b86aa in start_thread (arg=0x7fcdef33f700) at
pthread_create.c:333
#3  0x7fce1ecdae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 116 (Thread 0x7fcdeaa26700 (LWP 5755)):
#0  0x7fce1eccb44d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce1bef34e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce1beafcd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce1beb0190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fce1beb02fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fce1f90550b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce1f8ac50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce1f6c8ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fce2047cc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fce1f6cda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fce1d8b86aa in start_thread (arg=0x7fcdeaa26700) at
pthread_create.c:333
#11 0x7fce1ecdae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 115 (Thread 0x7fcde9224700 (LWP 5757)):
#0  0x7fce1eccf88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fce1beb01ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce1beb02fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce1f90550b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce1f8ac50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce1f6c8ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce2047cc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fce1f6cda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fce1d8b86aa in start_thread (arg=0x7fcde9224700) at
pthread_create.c:333
#9  0x7fce1ecdae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 114 (Thread 0x7fcdda6b7700 (LWP 5762)):
#0  0x7fce1bef4869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fce1beaf789 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fce1beb011b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fce1beb02fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fce1f90550b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fce1f8ac50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fce1f6c8ac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce1f6cda6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  

[kdenlive] [Bug 361374] 16.04-62fa29e SIGABRT when detaching / rejoining project and clip monitor with movit enabled

[Paul Konecny via KDE Bugzilla]

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

--- Comment #5 from Paul Konecny  ---
Created attachment 98259
  --> https://bugs.kde.org/attachment.cgi?id=98259=edit
Backtrace #2 16.04-3936976

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

[digikam] [Bug 361378] Tags are not being removed from files metadata

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
The problem here is with digiKam-5.0.0-beta5 not to reproduce. The writing of
image tags must of course be activated in the metadata settings. Otherwise old
tags are not updated and with a new reading of the metadata appear again.

Maik

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

[kdenlive] [Bug 361374] 16.04-62fa29e SIGABRT when detaching / rejoining project and clip monitor with movit enabled

[Paul Konecny via KDE Bugzilla]

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

--- Comment #4 from Paul Konecny  ---
Created attachment 98258
  --> https://bugs.kde.org/attachment.cgi?id=98258=edit
Screencast of the issue #2

Unfortunately I still get the issue with 16.04-3936976
This is without any project loaded. Just opening kdenlive and messing with the
monitor.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

 CC||swatilodh...@gmail.com

--- Comment #63 from swatilodh...@gmail.com ---
Hello Richard.

I'm Swati, currently working on digiKam MySQL database support project. I read
this open bug for MySQL Schema improvements and thought of a plausible solution
to handle the tags (rename, move or delete)

An image can have many tags and a tag can belong to multiple image. So to
handle this many-many relationship between the two, we could take use of the
following tables:

 Table: Image
Columns: Image_ID, Image_Title

Table: Tag
Columns: Tag_ID, Tag_Title

Table: Image_Tag
Columns: Tag_ID, Image_ID

Setting the Image_ID and Tag_ID as foreign keys would help in linking the
tables.

Maybe this will help. 

Regards
Swati

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

[kate] [Bug 350535] Ctrl-Shift-U fails for inputting unicode

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||wen...@gmail.com
  Latest Commit||http://commits.kde.org/ktex
   ||teditor/a9892ac1f34b5639b4b
   ||144b49b12b5cee42f71ad
 Resolution|--- |FIXED
   Version Fixed In||KDE Frameworks 5.20

--- Comment #1 from Dominik Haumann  ---
This looks like https://git.reviewboard.kde.org/r/127026/

If so, this is fixed since March 2016, please update.

@Weng Xuetian: Can you confirm?

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

[kate] [Bug 346507] kate window is invisible after closing window when minimized and then reopening window

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Dominik Haumann  ---
Sorry, this looks like a graphics driver bug or maybe issue with compiz. We
never experienced such an issue before, so we cannot really solve this.

If you still have this issue, or have further infos, please let us know.

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

[plasmashell] [Bug 361425] crashed while update system in Konsole

[RJ via KDE Bugzilla]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

[drkonqi] [Bug 361426] New: crashed when back<-back<-back was pressed

[RJ via KDE Bugzilla]

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

Bug ID: 361426
   Summary: crashed when back<-back<-back was pressed
   Product: drkonqi
   Version: 5.5.5
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ogldel...@mail.ru

Tried to post bug report but at the final step I changed my mind and pressed
back, back and back and then it crashed.


Application: drkonqi (drkonqi), signal: Bus error
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4964800 (LWP 3224))]

Thread 2 (Thread 0xae291b40 (LWP 3253)):
#0  0xb77d9f3d in __kernel_vsyscall ()
#1  0xb584ba2b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb5d624dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb00fc75a in cnd_wait (mtx=0x8aca93c, cond=0x8aca954) at
../../../../../include/c11/threads_posix.h:159
#4  pipe_semaphore_wait (sema=0x8aca93c) at
../../../../../src/gallium/auxiliary/os/os_thread.h:259
#5  radeon_drm_cs_emit_ioctl (param=0x8aca6d8) at radeon_drm_winsys.c:653
#6  0xb00fbe55 in impl_thrd_routine (p=0x8a76e08) at
../../../../../include/c11/threads_posix.h:87
#7  0xb58462f5 in start_thread () from /lib/libpthread.so.0
#8  0xb5de in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4964800 (LWP 3224)):
[KCrash Handler]
#7  0xb584931c in pthread_mutex_timedlock () from /lib/libpthread.so.0
#8  0xb72b7598 in pthreadTimedLock::lock (this=0x8974750) at
/usr/src/debug/kcoreaddons-5.20.0/src/lib/caching/kshareddatacache_p.h:248
#9  0xb72bbea0 in KSharedDataCache::Private::lock (this=0x8977fc8) at
/usr/src/debug/kcoreaddons-5.20.0/src/lib/caching/kshareddatacache.cpp:1216
#10 KSharedDataCache::Private::CacheLocker::cautiousLock (this=)
at /usr/src/debug/kcoreaddons-5.20.0/src/lib/caching/kshareddatacache.cpp:1239
#11 KSharedDataCache::Private::CacheLocker::CacheLocker (this=0xbfeff7e4,
_d=0x8977fc8) at
/usr/src/debug/kcoreaddons-5.20.0/src/lib/caching/kshareddatacache.cpp:1289
#12 0xb72b2832 in KSharedDataCache::find (this=0x897a200, key=...,
destination=0xbfeff838) at
/usr/src/debug/kcoreaddons-5.20.0/src/lib/caching/kshareddatacache.cpp:1577
#13 0xb20d7bd6 in KIconLoaderPrivate::findCachedPixmapWithPath (this=0x8978030,
key=..., data=..., path=...) at
/usr/src/debug/kiconthemes-5.20.0/src/kiconloader.cpp:835
#14 0xb20d7fe0 in KIconLoader::loadIcon (this=0xb20f45e0 <(anonymous
namespace)::Q_QGS_globalIconLoader::innerFunction()::holder>, _name=...,
group=KIconLoader::Desktop, size=64, state=0, overlays=..., path_store=0x0,
canReturnNull=false) at
/usr/src/debug/kiconthemes-5.20.0/src/kiconloader.cpp:1142
#15 0xb20cdd15 in KIconEngine::pixmap (this=0x8c9dfa0, size=...,
mode=QIcon::Normal, state=QIcon::Off) at
/usr/src/debug/kiconthemes-5.20.0/src/kiconengine.cpp:98
#16 0xb65a6e7e in QIcon::pixmap (this=0xbfeffc74, window=0x0, size=...,
mode=QIcon::Normal, state=QIcon::Off) at image/qicon.cpp:839
#17 0xb65a6f96 in QIcon::pixmap (this=0xbfeffc74, size=..., mode=QIcon::Normal,
state=QIcon::Off) at image/qicon.cpp:775
#18 0xb74ab206 in QIcon::pixmap (state=QIcon::Off, mode=QIcon::Normal,
extent=, this=0xbfeffc74) at /usr/include/qt5/QtGui/qicon.h:79
#19 KMessageBox::createKMessageBox (dialog=0x8e28a88, buttons=0x8dd5d58,
icon=..., text=..., strlist=..., ask=..., checkboxReturn=0xbfeffd03,
options=..., details=..., notifyType=QMessageBox::Information) at
/usr/src/debug/kwidgetsaddons-5.20.0/src/kmessagebox.cpp:223
#20 0xb74ab59b in KMessageBox::createKMessageBox (dialog=0x8e28a88,
buttons=0x8dd5d58, icon=QMessageBox::Information, text=..., strlist=...,
ask=..., checkboxReturn=0xbfeffd03, options=..., details=...) at
/usr/src/debug/kwidgetsaddons-5.20.0/src/kmessagebox.cpp:197
#21 0xb74ac266 in KMessageBox::questionYesNoCancelInternal (dialog=0x8e28a88,
dialog@entry=0x8dc1860, text=..., caption=..., buttonYes_=..., buttonNo_=...,
buttonCancel_=..., dontAskAgainName=..., options=...) at
/usr/src/debug/kwidgetsaddons-5.20.0/src/kmessagebox.cpp:546
#22 0xb74ac654 in KMessageBox::questionYesNoCancel (parent=0xbfeffd74,
text=..., caption=..., buttonYes=..., buttonNo=..., buttonCancel=...,
dontAskAgainName=..., options=...) at
/usr/src/debug/kwidgetsaddons-5.20.0/src/kmessagebox.cpp:575
#23 0x0809f4c0 in ReportAssistantDialog::closeEvent (this=0x8cca8b0,
event=0xbff00024) at
/usr/src/debug/plasma-workspace-5.5.5/drkonqi/bugzillaintegration/reportassistantdialog.cpp:351
#24 0xb6b1b32a in QWidget::event (this=0x8cca8b0, event=0xbff00024) at
kernel/qwidget.cpp:9047
#25 0xb6ad550a in QApplicationPrivate::notify_helper (this=0x89162e8,
receiver=0x8cca8b0, e=0xbff00024) at kernel/qapplication.cpp:3716
#26 0xb6ada936 in QApplication::notify (this=0xbff00f40, receiver=0x8cca8b0,
e=0xbff00024) at kernel/qapplication.cpp:3499
#27 0xb61f81ef in QCoreApplication::notifyInternal 

[kate] [Bug 349500] Quit command behaves strangely and might cause crash in vi mode

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kdenlive] [Bug 361357] git master - issues with new Clip Properties Widget

[farid via KDE Bugzilla]

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

--- Comment #5 from farid  ---
fixed.

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

[plasmashell] [Bug 361425] New: crashed while update system in Konsole

[RJ via KDE Bugzilla]

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

Bug ID: 361425
   Summary: crashed while update system in Konsole
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: other
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ogldel...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

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

Thread 8 (Thread 0xb002ab40 (LWP 2319)):
#0  0xb4483a5d in g_main_context_check (context=0xaf7004d8,
max_priority=2147483647, fds=0xaf702738, n_fds=1) at gmain.c:3663
#1  0xb4484081 in g_main_context_iterate (context=context@entry=0xaf7004d8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3837
#2  0xb4484224 in g_main_context_iteration (context=0xaf7004d8, may_block=1) at
gmain.c:3901
#3  0xb52b1a84 in QEventDispatcherGlib::processEvents (this=0xaf700468,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0xb52594c3 in QEventLoop::processEvents (this=0xb002a1d8, flags=...) at
kernel/qeventloop.cpp:128
#5  0xb52598fa in QEventLoop::exec (this=0xb002a1d8, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb508d855 in QThread::exec (this=0x88123f8) at thread/qthread.cpp:503
#7  0xb68aa48f in QQmlThreadPrivate::run (this=0x88123f8) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0xb5092c00 in QThreadPrivate::start (arg=0x88123f8) at
thread/qthread_unix.cpp:331
#9  0xb4c652f5 in start_thread () from /lib/libpthread.so.0
#10 0xb4dba55e in clone () from /lib/libc.so.6

Thread 7 (Thread 0xac773b40 (LWP 2320)):
#0  0xb773bf3d in __kernel_vsyscall ()
#1  0xb4c6aa2b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4dc74dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xae60575a in cnd_wait (mtx=0x895f26c, cond=0x895f284) at
../../../../../include/c11/threads_posix.h:159
#4  pipe_semaphore_wait (sema=0x895f26c) at
../../../../../src/gallium/auxiliary/os/os_thread.h:259
#5  radeon_drm_cs_emit_ioctl (param=0x895f008) at radeon_drm_winsys.c:653
#6  0xae604e55 in impl_thrd_routine (p=0x88d00a8) at
../../../../../include/c11/threads_posix.h:87
#7  0xb4c652f5 in start_thread () from /lib/libpthread.so.0
#8  0xb4dba55e in clone () from /lib/libc.so.6

Thread 6 (Thread 0xaa7ecb40 (LWP 2330)):
#0  0xb773bf3d in __kernel_vsyscall ()
#1  0xb4db017b in poll () from /lib/libc.so.6
#2  0xb4492980 in poll (__timeout=-1, __nfds=1, __fds=0xa9e02938) at
/usr/include/bits/poll2.h:46
#3  g_poll (fds=0xa9e02938, nfds=1, timeout=-1) at gpoll.c:124
#4  0xb44840ec in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0xa9e02938, timeout=, context=0xa9e004d8) at gmain.c:4135
#5  g_main_context_iterate (context=context@entry=0xa9e004d8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#6  0xb4484224 in g_main_context_iteration (context=0xa9e004d8, may_block=1) at
gmain.c:3901
#7  0xb52b1a84 in QEventDispatcherGlib::processEvents (this=0xa9e00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#8  0xb52594c3 in QEventLoop::processEvents (this=0xaa7ec1d8, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb52598fa in QEventLoop::exec (this=0xaa7ec1d8, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb508d855 in QThread::exec (this=0x8814440) at thread/qthread.cpp:503
#11 0xb68aa48f in QQmlThreadPrivate::run (this=0x8814440) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#12 0xb5092c00 in QThreadPrivate::start (arg=0x8814440) at
thread/qthread_unix.cpp:331
#13 0xb4c652f5 in start_thread () from /lib/libpthread.so.0
#14 0xb4dba55e in clone () from /lib/libc.so.6

Thread 5 (Thread 0xa9468b40 (LWP 2337)):
#0  0xb52b101a in postEventSourcePrepare (s=0x8a6cd48, timeout=0xa946803c) at
kernel/qeventdispatcher_glib.cpp:253
#1  0xb448365b in g_main_context_prepare (context=0x8a62430,
priority=0xa9468098) at gmain.c:3442
#2  0xb4483ffc in g_main_context_iterate (context=context@entry=0x8a62430,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3820
#3  0xb4484224 in g_main_context_iteration (context=0x8a62430, may_block=1) at
gmain.c:3901
#4  0xb52b1a84 in QEventDispatcherGlib::processEvents (this=0x8a75dc0,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0xb52594c3 in QEventLoop::processEvents (this=0xa94681d8, flags=...) at
kernel/qeventloop.cpp:128
#6  0xb52598fa in QEventLoop::exec (this=0xa94681d8, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb508d855 in QThread::exec (this=0x8a7fa98) at thread/qthread.cpp:503
#8  0xb68aa48f in QQmlThreadPrivate::run (this=0x8a7fa98) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#9  0xb5092c00 in QThreadPrivate::start 

[kdenlive] [Bug 361357] git master - issues with new Clip Properties Widget

[Jesse via KDE Bugzilla]

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

--- Comment #4 from Jesse  ---
Farid, can you use the latest git master build and test? Now that it uses a
scrollbar, the layout doesn't resize when you double-click to open the clip
properties widget.

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

[frameworks-ktexteditor] [Bug 339627] vi input mode: Kate 3.14.1 (kubuntu 4.14.1 backport) crashes when saving files

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

Summary|Kate 3.14.1 (kubuntu 4.14.1 |vi input mode: Kate 3.14.1
   |backport) crashes when  |(kubuntu 4.14.1 backport)
   |saving files|crashes when saving files

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

[frameworks-ktexteditor] [Bug 339627] Kate 3.14.1 (kubuntu 4.14.1 backport) crashes when saving files

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

Product|kate|frameworks-ktexteditor
  Component|general |general
Version|3.14.0  |unspecified

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

[kate] [Bug 333517] Kate crashes when you try to replace characters in large files

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||piotrekg2s...@gmail.com

--- Comment #3 from Dominik Haumann  ---
*** Bug 343979 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 343979] Kwrite hangs when replacing strings in long lines.

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---


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

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

[frameworks-kcodecs] [Bug 357341] kate .gnupg/secring.gpg crashes kate

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||kdespam34fb987@weg-werf-ema
   ||il.de

--- Comment #6 from Dominik Haumann  ---
*** Bug 343261 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 343261] kwrite/kate crashes when opening a specific binary file

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
I fixed that in KCodecs last week: The fix will be shipped with KDE Frameworks
5.21.
See: https://git.reviewboard.kde.org/r/127488/

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

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

[yakuake] [Bug 307441] split window open in same path

[via KDE Bugzilla]

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

kajokeji.2...@gmail.com changed:

   What|Removed |Added

 CC||kajokeji.2...@gmail.com

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

[okular] [Bug 361424] New: Add option to put tabs sideways

[Victor Porton via KDE Bugzilla]

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

Bug ID: 361424
   Summary: Add option to put tabs sideways
   Product: okular
   Version: 0.23.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: por...@narod.ru

Please add configuration option to show tabs of open documents vertically at
the left of the document, rather than on the top of the document. (The text of
the tabs could be 90 degrees rotated.)

Vertical space is often much more precious than horizontal one.

Reproducible: Always

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

[kate] [Bug 356813] kwrite crashes if it is closed when the print dialog is open

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/ktex
   ||teditor/a8d31664a5319c86328
   ||ed09471e37a8d977e5962
 Resolution|--- |FIXED

--- Comment #3 from Dominik Haumann  ---
Git commit a8d31664a5319c86328ed09471e37a8d977e5962 by Dominik Haumann.
Committed on 05/04/2016 at 19:41.
Pushed by dhaumann into branch 'master'.

Fix crash when closing Kate through dbus while the print dialog is open

See infos:
https://blogs.kde.org/2009/03/26/how-crash-almost-every-qtkde-application-and-how-fix-it
CHANGELOG: Fix crash when closing Kate through dbus while the print dialog is
open (bug #356813)

M  +5-1src/printing/kateprinter.cpp

http://commits.kde.org/ktexteditor/a8d31664a5319c86328ed09471e37a8d977e5962

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

[konqueror] [Bug 361423] New: Konquerer crashing

[Paul Schloemer via KDE Bugzilla]

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

Bug ID: 361423
   Summary: Konquerer crashing
   Product: konqueror
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: schl...@alumni.nd.edu

Application: konqueror (4.14.18)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Almost every time I click on a link, Konquerer crashes. I was on comicmad.com,
reading a comic, and as soon as I click on a page, the browser shuts down.

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

Thread 13 (Thread 0x7fc29ea00700 (LWP 22862)):
#0  0x7fc2b5f8b03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc2a39d6eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7fc2a39d6ee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fc25d4b3700 (LWP 22863)):
#0  0x7fc2b4c71bbd in poll () at /lib64/libc.so.6
#1  0x7fc2b1d81e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc2b1d81f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc2b634bfde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fc2b631dd4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fc2b631e045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fc2b621b4df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fc2b621dbbf in  () at /usr/lib64/libQtCore.so.4
#8  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fc257fff700 (LWP 22864)):
#0  0x7fc2b5f8b03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc2a3749b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7fc2a39fea06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fc2496ad700 (LWP 22867)):
#0  0x7fc2b5f8b03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc249714d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fc249715819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fc248eac700 (LWP 22868)):
#0  0x7fc2b5f8b03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc249714d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fc249715819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fc2486ab700 (LWP 22869)):
#0  0x7fc2b5f8b03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc249714d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7fc249715819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc23f7fe700 (LWP 22966)):
#0  0x7fc2b5f8b3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc2b621e084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7fc2b6211bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7fc2b621dbbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7fc2b5f870a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7fc2b4c79fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc2479aa700 (LWP 22981)):
#0  0x7fc2b5f8da7d in read () at /lib64/libpthread.so.0
#1  0x7fc2b1dc2b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc2b1d81999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc2b1d81df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc2b1d81f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fc2b634bfde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7fc2b631dd4f in

[krita] [Bug 361415] Krita 2.9: crash on opening Gimp image

[Lukas via KDE Bugzilla]

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

--- Comment #5 from Lukas  ---
(Temporary) solution: in GIMP save as with 'maximum compatibility' checked.

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

[kate] [Bug 271063] kate crash when missing a lot of opening files while restarting

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Dominik Haumann  ---
This is finally fixed in the upcoming KDE Applications 16.04 release.

This is what happened: Since the QList m_mainWindows; is the
last member variable, this list is destroyed first in ~KateApp. Only then is
the pluginmanager deleted, which unfortunately calls certain functions in its
destructor that finally query the mainWindows. As result, already freed memory
is read, which results in a crash.

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

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

[kate] [Bug 348604] Crash when switching tab

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||korod...@gmail.com

--- Comment #2 from Dominik Haumann  ---
*** Bug 361217 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 361217] Kate crashes when no files are open and "Open recent" function is used

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #2 from Dominik Haumann  ---
Can you please update to either the Applications 15.12 release, or maybe even
to upcoming 16.04?

We haven't been able to reproduce, unfortunately... Further details would maybe
help.

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

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

[kdenlive] [Bug 361399] Can't type volume effect parameter during playback (but dragging slider is ok)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 393697681fbc69127ac5999dcd08ae5d69f757f7 by Jean-Baptiste Mardelle.
Committed on 05/04/2016 at 19:24.
Pushed by mardelle into branch 'Applications/16.04'.

Fix editing effect value when playing and effect has only 1 keyframe

M  +6-0src/effectstack/dragvalue.cpp
M  +3-1src/effectstack/dragvalue.h
M  +5-1src/effectstack/widgets/animationwidget.cpp
M  +5-0src/effectstack/widgets/doubleparameterwidget.cpp
M  +2-0src/effectstack/widgets/doubleparameterwidget.h

http://commits.kde.org/kdenlive/393697681fbc69127ac5999dcd08ae5d69f757f7

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

[kate] [Bug 356277] Kate crashes when too many files are open.

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
Fixed in Applications 15.12 release, please update.

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

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

[kate] [Bug 349558] Kate Segfaults on startup

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #5 from Dominik Haumann  ---
*** Bug 356277 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 356815] Crash if you close kate when the print dialog is open

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---


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

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

[kate] [Bug 356813] kwrite crashes if it is closed when the print dialog is open

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #2 from Dominik Haumann  ---
*** Bug 356815 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 354343] regexp processing allocates whole available RAM and halts the system

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
   Priority|NOR |VHI

--- Comment #2 from Dominik Haumann  ---
There is definitely something wrong. I get "620 matches found", even though
there are just 26...

Needs investigation.

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

[kate] [Bug 349558] Kate Segfaults on startup

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #4 from Dominik Haumann  ---
*** Bug 354947 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 354947] Kate segfaults when opening session with too many files

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #3 from Dominik Haumann  ---
Fixed in the KDE Applications 15.12 release.

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

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

[konsole] [Bug 360360] Paste-special from Konsole in LibreOffice vaporizes Desktop Session

[Martin van Es via KDE Bugzilla]

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

Martin van Es  changed:

   What|Removed |Added

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

--- Comment #2 from Martin van Es  ---
Seems fixed in Ubuntu Xenial 16.04

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

[kate] [Bug 356473] Crashes after trying to open c/c++ files

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||manuel_songo...@yahoo.it

--- Comment #3 from Dominik Haumann  ---
*** Bug 359754 has been marked as a duplicate of this bug. ***

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

[Baloo] [Bug 361422] New: baloo crashing then QTCreator Run

[Alexander K via KDE Bugzilla]

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

Bug ID: 361422
   Summary: baloo crashing then QTCreator Run
   Product: Baloo
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: janus...@mail.ru
CC: pinak.ah...@gmail.com

Application: baloo_file (5.16.0)

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

-- Information about the crash:
- baloo crash then I make new project for Window aplication in QTCreator5

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff1d15d38c0 (LWP 2034))]

Thread 2 (Thread 0x7ff0852e4700 (LWP 2470)):
#0  0x7ff1cf11e20d in poll () at /lib64/libc.so.6
#1  0x7ff1cba89264 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff1cba8936c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff1cfd3b52b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff1cfce563a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x004216b0 in Baloo::FileContentIndexer::run() ()
#6  0x7ff1cfb13533 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ff1cfb1694f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff1ce14c4a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff1cf126b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff1d15d38c0 (LWP 2034)):
[KCrash Handler]
#6  0x7ff1cce1c418 in mdb_get () at /usr/lib64/liblmdb-0.9.16.so
#7  0x7ff1d03ce39d in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x7ff1d03cb080 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x7ff1d03ddc71 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x00429860 in
Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) ()
#11 0x0042a202 in Baloo::MetadataMover::moveFileMetadata(QString
const&, QString const&) ()
#12 0x7ff1cfd14e17 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x0042ab4a in KInotify::moved(QString const&, QString const&) ()
#14 0x0042cb54 in KInotify::slotEvent(int) ()
#15 0x7ff1cfd14e17 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7ff1cfd9039e in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
#17 0x7ff1cfd20d0b in QSocketNotifier::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7ff1cfce7ccc in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#19 0x7ff1cfd3b9bd in  () at /usr/lib64/libQt5Core.so.5
#20 0x7ff1cba89097 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#21 0x7ff1cba892c8 in  () at /usr/lib64/libglib-2.0.so.0
#22 0x7ff1cba8936c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#23 0x7ff1cfd3b50f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#24 0x7ff1cfce563a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#25 0x7ff1cfced2fd in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#26 0x00417906 in main ()

Possible duplicates by query: bug 359672, bug 355210, bug 353223.

Reported using DrKonqi

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

[kate] [Bug 359754] kwrite

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
Can you debug this further on your system? Could you try the Kate5 version?

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

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

[kate] [Bug 333329] Kate crash on IPython console check

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||g.gumicsi...@gmail.com

--- Comment #12 from Dominik Haumann  ---
*** Bug 359787 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 359787] Kate python module IPython crash

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---


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

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