[kwin] [Bug 364689] New: Prevent/delay focus stealing while typing

[ned via KDE Bugzilla]

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

Bug ID: 364689
   Summary: Prevent/delay focus stealing while typing
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: naught...@gmail.com

I have focus stealing prevention turned off, generally, because I like to be
notified if something requires my attention (e.g. password inputs, chat
messages etc). However, when multiple things are happening at once, it can
happen that you're half way through typing something, focus is stolen, and you
end up typing the rest in the wrong window. This can be problematic at times:
for example, accidentally pressing the wrong ok/cancel button in a new dialogue
window, or accidentally sexting your grandmother...

It would be great if there was an option to turn focus stealing prevention on
only while typing - so, for example, if I press any key, focus stealing is
prevented for the next 1000ms (configurable). It would be ideal if focus
stealing was optionally delayed, instead of prevented: so one second after I
stop typing, and I'm looking at the screen, thinking, and the new window pops
up, and I can react intentionally, instead of accidentally.

Reproducible: Always

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

[kontact] [Bug 364670] kmail crash on search

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
could you add more debug info (package debug info) please ?

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

[krita] [Bug 363574] Edit Brushes either don't work at all or mysteriously stop working

[aK via KDE Bugzilla]

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

aK  changed:

   What|Removed |Added

 CC||oneb7...@gmail.com

--- Comment #2 from aK  ---
If you manage to accidently press a combination of right/left/middle mouse
together at the same time in the scratch pad, the scratch pad will break.

#363080 i think is what your experiencing maybe.

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

[krita] [Bug 363080] scratchpad stops working when clicking right/middle mb while painting

[aK via KDE Bugzilla]

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

aK  changed:

   What|Removed |Added

 CC||oneb7...@gmail.com

--- Comment #5 from aK  ---
Confirmed i can do the same , 64bit windows vista.

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

[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available

[Evert Vorster via KDE Bugzilla]

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

--- Comment #10 from Evert Vorster  ---
We're not sure that this is even an error with kdenlive, it could very well be
with the distrobution that you are running, your specific system, or even just
the setup on your system. 

Kdenlive runs fine for me with vbox drivers, intel drivers and nvidia drivers,
both free and proprietary.  

My advice: use the binary nvidia drivers until the next release of kdenlive on
your distribution, and be patient.

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

[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available

[Yueqi Li via KDE Bugzilla]

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

--- Comment #9 from Yueqi Li  ---
When can you fix it?

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

[kdenlive] [Bug 364655] git master 2016-06-22 - re-creation of proxy files...

[Evert Vorster via KDE Bugzilla]

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

--- Comment #2 from Evert Vorster  ---
Hi there, JB. 

My /home is rather small, and I would symlink out any cache directory to a
larger faster disk if not given the option to configure it in the UI. 

I did not mean that the proxy clip should match the project resolution, but
that the proxy name should be what the proxy generator is called in Kdenlive. 
I have my proxy generators labelled to what size video they will produce, and I
can easily see how the miscommunication happened. My apologies. 

Say I have a 1080p project, with proxies enabled. My proxy generator is called
720p, but it could also have been called MPEGTS... a proxy generated with it
should just have the source clip name, and the name of the proxy generator, and
maybe the string "proxy" in the name. 

It's good to be careful about deleting stuff. If you filter carefully, and
catch empty variables, your chances of actually deleting source footage is
quite small. 
When deleting en masse, give a list of files up for deletion, and give the
option to cancel as a final check. 

In the end, Kdenlive is mostly your project, and whatever you do with it is
fine. If I don't like it I will either learn to live with it, or get a
workaround. :)

I think I have an ancient open bug about proxies not being re-created when the
proxy generator profile changes. With my scheme, you would not have to delete
proxies at all, unless you modified the parameters of a proxy generator. 

Deleting really needs it's own UI, where you can filter and select files,
rather than trying to do it automatically. 

Thanks for some awesome software!

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

[krita] [Bug 364688] New: Krita randomly crashes, and makes it impossible to retrieve my work

[Ednie Saint Eloi via KDE Bugzilla]

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

Bug ID: 364688
   Summary: Krita randomly crashes, and makes it impossible to
retrieve my work
   Product: krita
   Version: 3.0
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: edniesainte...@gmail.com

When I am painting, Krita randomly crashes, and my work is always gone. By
doing the slightest bit of movement can cause it to crash. My work is always
getting lost, which means every 2 minutes into painting, I have to constantly
save so if it do crashes, I can at least have a bit of my painting back, and
when I do open it, Krita merges ALL my layers together, which makes it REALLY
frustrating.

Reproducible: Always

Steps to Reproduce:
1.Open up Krita and start painting for a good amount of time
2. Out of nowhere, my brush turns into a blue, circles, resembling the ones you
get when you click on too many things on a computer
3. A message pops up saying there is something wrong with krita, then it closes

Actual Results:  
I have not tried to reproduced those steps in fear my work will be deleted.

Expected Results:  
The software shouldn't have to crash, randomly oh so often, but if it did,
there should have been a way to get your image AND your layers  back.
SEPERATLELY

I'm starting to regret updating krita, The previous version worked
effortlessly.

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

[krunner] [Bug 363421] krunner crash/restart when starting iceweasel from alt-F2

[via KDE Bugzilla]

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

m...@nightrealms.com changed:

   What|Removed |Added

 CC||m...@nightrealms.com

--- Comment #1 from m...@nightrealms.com ---
Created attachment 99671
  --> https://bugs.kde.org/attachment.cgi?id=99671=edit
Stack trace of crash, as generated by Dr Konqi

I've also been intermittently getting this crash, though only once did Dr Konqi
catch it and generate a bug report.

Additional info: in .xsession-errors, right before the KCrash text about
krunner is a series of XCB errors about "BadWindow" and "BadDrawable"; might be
related.

(The automatic bug reporter was itself bugged in respect to attaching a stack
trace to existing bugs, so I'm doing it manually.)

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

[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

[Andreas Hartmetz via KDE Bugzilla]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 CC||ahartm...@gmail.com

--- Comment #24 from Andreas Hartmetz  ---
I'm with Martin. We should make sure that our processes terminate to avoid
wasting resources. Independent of that, systemd is wrong to change behavior
because the way it used to work was good. Logout - end the session, leave
detached processes alone. Shutdown / reboot - kill everything that still lives
and only wait for a very short time. It is not hard to understand why that is
the right behavior.

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

[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #10 from Andreas Hartmetz  ---
Note: "some processes" is not precise enough, I take this to be about Kate.
There is still a known (to me at least) problem with shutdown because indeed
"some processes" don't terminate voluntarily and systemd (unlike other init
systems) waits for them for a full two minutes.

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

[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly

[Andreas Hartmetz via KDE Bugzilla]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Andreas Hartmetz  ---
Assuming it's fixed, please reopen if it's not fixed in a recent version.

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

[kaffeine] [Bug 364683] Change channels or try selecting a recording results in an immediate crash.

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

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

--- Comment #1 from Mauro Carvalho Chehab  ---
Looking from the trace, I suspect that it has something to do with libVLC.
Maybe you had some upgrades at VLC side.

Yet, we're not supporting Kaffeine 1.3 upstream anymore. There are simply too
many changes from it to Kaffeine 2.x, including the migration to Qt5, and
several fixes at playlist (where the code hanged).

Please either report this bug to Mageia or upgrade to the latest version
(2.0.3) or to the git one (I'm about to release a 2.0.4 from the current git
tree - I'm just giving some time to i18n people for translations).

If the bug happens with Kaffeine 2.0.3(or -git), please re-open, with Kaffeine
logs (those are enabled with the new --debug option).

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

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

[Jonatan Cloutier via KDE Bugzilla]

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

Jonatan Cloutier  changed:

   What|Removed |Added

 CC||cloutier...@gmail.com

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

[kaffeine] [Bug 364517] Kaffeine can't tune in RTL (dvb-c / german television)

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #7 from Mauro Carvalho Chehab  ---
(In reply to boris64 from comment #6)
> FYI: i tried up2date vlc-3 (git-whatever) + vlc-clang-git and it turned out
> that RTL was ok (for now), but another channel showed video only and no
> sound anymore. Ahhrr crap.

heh...

> So this really seems to be some kind of _vlc issue_. Too bad there is no way
> of choosing the backend used in kaffeine. In (s)mplayer everything is really
> ok (but on the other hand it's really slow when switching channels because
> of buffering).

It used to have for a while, with Kaffeine 1.0.x, I guess... The mplayer
backend code is still there (and the libxine/gst at the logs), but putting
those backends work again is painful.

If someone would write the patches to re-enable mplayer as another backend
option and/or to add support for gst, I may end applying it upstream.
> 
> Ok, thanks for your help anyway ;)

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

[krita] [Bug 364184] Navigating Canvas is slow (Pan, Rotate, Zoom)

[via KDE Bugzilla]

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

--- Comment #8 from katearche...@yandex.ru ---
(In reply to eliotJ from comment #7)
> @katearche...@yandex.ru
> 
> Hmmm... Sad news... Can you try also these testing on version of Krita with
> the same settings what you using (these version of Krita also has Instant
> Preview - would be cool if you will try with enabled and with disabled
> Instant Preview) ?:
> http://files.kde.org/krita/windows/krita_2.9.10.2ae_beta_x64.zip

Well. I have tried all three versions and results are pretty same:
2.9.11:  nice and smooth
2.9.10 beta: nice and smooth without Instant Preview, with it it become a
little laggy but barely noticeable.
3.0: not smooth at all with or without IP(without a little better but not that
much to make a difference)

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

[amarok] [Bug 364354] Amarok stutters and hangs system before crashing

[Myriam Schweingruber via KDE Bugzilla]

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

--- Comment #5 from Myriam Schweingruber  ---
so no crash anymore or should we still wait for a backtrace? Even if this is a
pulseaudio issue, a backtrace would still be nice to have as it makes cornering
the problem easier.

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

[amarok] [Bug 360540] Amarok does not read the "albumartist" ID3 tag in my ID3v2.4 tagged MP3 Files

[Myriam Schweingruber via KDE Bugzilla]

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

--- Comment #13 from Myriam Schweingruber  ---
Well, kid3 is a tag editor, which shows both id3 v1 and v2 tags, might give you
an insight on where the tag comes from

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

[kdenlive] [Bug 364306] git master: moving a group containing transition corrupts project by creating multiple copies of transitions

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
Git commit 8d25df8b34caea01d37903070b660e6af9ecf0f9 by Jean-Baptiste Mardelle.
Committed on 23/06/2016 at 23:06.
Pushed by mardelle into branch 'master'.

Fix transition corruption on group move

M  +5-5src/timeline/customtrackview.cpp
M  +2-2src/timeline/customtrackview.h
M  +1-1src/timeline/managers/movemanager.cpp

http://commits.kde.org/kdenlive/8d25df8b34caea01d37903070b660e6af9ecf0f9

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

[kdenlive] [Bug 364585] git master: after moving a set of clips using the spacer tool clips cannot be moved anymore

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Cannot reproduce... is it still a problem for you ?

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

[kdenlive] [Bug 364106] git master - Preview render not working & Adding preview zone makes in-out zone area real small

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #10 from Jean-Baptiste Mardelle  ---
Should be fixed now. For HD 1920x1080 projects it will use the DNxHD profiles,
and default to MJPEG if no matching frames size / fps is found. When trying on
an existing project you might need to change the timeline preview profile (in
project settings), MJPEG should work on all profiles

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

[kdenlive] [Bug 364106] git master - Preview render not working & Adding preview zone makes in-out zone area real small

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #9 from Jean-Baptiste Mardelle  ---
Git commit 94bd2ac37c17183f2ef619d2d4bd0c5585080bb9 by Jean-Baptiste Mardelle.
Committed on 23/06/2016 at 22:40.
Pushed by mardelle into branch 'master'.

Fix timeline preview encoding parameter detection

M  +5-5data/encodingprofiles.rc
M  +11   -12   src/doc/kdenlivedoc.cpp
M  +3-2src/effectstack/effectstackview2.cpp
M  +2-0src/timeline/timeline.cpp

http://commits.kde.org/kdenlive/94bd2ac37c17183f2ef619d2d4bd0c5585080bb9

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

[plasma-pa] [Bug 364687] Default device is not remembered

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #2 from Weng Xuetian  ---
(In reply to David Rosca from comment #1)
> Hm, that's kind of to be expected actually. All it does is to change the
> default device in pulseaudio, so ideally pulseaudio should remember it.

If you know about start-pulseaudio-kde, you'll know that in the past, kde uses
different pulseaudio mechanism to select default device. (by using
/usr/bin/pactl load-module module-device-manager "do_routing=1" > /dev/null )

So that the old kcm phonon will be able to set a list of device to pa. I don't
think it uses the same "default" device mechanism  like other desktop. And
actually select default device from kcm doesn't do anything on my desktop. It
doesn't change application to use another device.

I think you probably want to pick up the same mechanism used by kcm phonon to
decide the real default device.

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

[plasmashell] [Bug 359570] Icons cannot be positioned freely on desktop (folder view), snap to grid instead

[Roman Bysh via KDE Bugzilla]

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

--- Comment #2 from Roman Bysh  ---
Follow Up

Problem still exists in Plasma 5.6.4.

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

[plasmashell] [Bug 359570] Icons cannot be positioned freely on desktop (folder view), snap to grid instead

[Roman Bysh via KDE Bugzilla]

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

Roman Bysh  changed:

   What|Removed |Added

 CC||rb03...@gmail.com

--- Comment #1 from Roman Bysh  ---
This folder view widget has the icons locked using "snap to grid". This is
broken by design.
I would recommend bringing back what we had in KDE4.

KDE4 allowed us to place the icons where we wanted in whatever order or row
that we liked.
Plasma 5's folder plasmoid is a step backward. Please fix.

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

[plasma-pa] [Bug 364687] Default device is not remembered

[David Rosca via KDE Bugzilla]

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

--- Comment #1 from David Rosca  ---
Hm, that's kind of to be expected actually. All it does is to change the
default device in pulseaudio, so ideally pulseaudio should remember it.

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

[digikam] [Bug 363697] Album visible even after deletion [patch]

[Johannes Hirte via KDE Bugzilla]

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

--- Comment #13 from Johannes Hirte  ---
Patch works for me with MySQL/MariaDB.

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[Steve via KDE Bugzilla]

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

Steve  changed:

   What|Removed |Added

 CC||stephenrn...@gmail.com

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

[krita] [Bug 220180] Remember selection action setting on switching selection tool

[Michael via KDE Bugzilla]

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

Michael  changed:

   What|Removed |Added

 CC||miabr...@gmail.com

--- Comment #4 from Michael  ---
Six and a half years later this is implemented (=

https://phabricator.kde.org/rKRITAd850ff238bd6b34aa6e5c7438d27d0f9791f3529

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

[digikam] [Bug 364563] digiKam crashes when browsing albums, only for images in portrait format

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #3 from caulier.gil...@gmail.com ---
bugzilla file storage is very limited in size. Use a cloud web service to share
a file.

But as you said previously, it sound like a bug in Exiv2. It's difficult to
confirm, as the GDB backtrace is uncomplete.

Gilles Caulier

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

[plasma-pa] [Bug 364687] New: Default device is not remembered

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 364687
   Summary: Default device is not remembered
   Product: plasma-pa
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: wen...@gmail.com
CC: plasma-b...@kde.org

I have a bluetooth headphone and I set it as default device in plasma-pa's kcm
after I first use it.

After I close it and reopen it, the default device is still the builtin-analog,
instead of the bluetooth device.

Reproducible: Always

Steps to Reproduce:
1. Connect bluetooth head set
2. Set it as default in plasma-pa's kcm
3. Close the headset
4. reopen and connect the headset

Actual Results:  
builtin-analog is default device.

Expected Results:  
Bluetooth headset becomes default device when it's available.

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

[plasma-pa] [Bug 364686] Change volume with global hotkey doesn't "unmute" the device.

[David Rosca via KDE Bugzilla]

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

David Rosca  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[plasma-pa] [Bug 364686] New: Change volume with global hotkey doesn't "unmute" the device.

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 364686
   Summary: Change volume with global hotkey doesn't "unmute" the
device.
   Product: plasma-pa
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: wen...@gmail.com
CC: plasma-b...@kde.org

My sound card is muted, and press volume up/down doesn't unmute it. Using
plasma-pa 5.6.95

Reproducible: Always

Steps to Reproduce:
1. Mute the device
2. use volume up and down to change it

Actual Results:  
volume changes, but it's still muted

Expected Results:  
volume changes and device is unmuted.

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

[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

--- Comment #8 from Jean-Baptiste Mardelle  ---
This really looks like a duplicate of bug #364278

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

[kdenlive] [Bug 364655] git master 2016-06-22 - re-creation of proxy files...

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
In my recent move to more standard XDG data location, I moved the proxy clips
inside the project's cache folder. This effectively means that a proxy created
in one project will not be available in another project. I agree that depending
on your workflow that might not be a good idea.

However I am not really comfortable with putting the proxy clips in the source
clip folder. Proxy clips are in my opinion temporary data (more valuable than
thumbnails I agree). For example, if the proxy profile is changed in the
project, existing proxies should be deleted (just tested this and changing
project's proxy profile is in fact not working :-( ). I don't want to start
deleting stuff that is mixed with original source clips.

So I would rather put them like we did before all in one folder, maybe
$HOME/.cache/kdenlive/proxies/.

This would make proxy clips available cross project. Also not sure keeping
different proxy copies is really needed. Proxy clips are not supposed to match
the project resolution, they are supposed to be low resolution copies allowing
a faster workflow so I don't think it makes sense to have 720P proxies and
1080P proxies.

Would the change to a cross project folder be ok for you?

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

[krita] [Bug 364149] I was working on an art piece and I saved it as a new krita file. I try and open the file the next day and it comes up with a message that says that the file cannot be opened beca

[via KDE Bugzilla]

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

--- Comment #12 from khadic...@gmail.com ---
All the files in the folder had the same thing happen to them

On Thu, Jun 23, 2016 at 10:38 AM, Boudewijn Rempt via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=364149
>
> --- Comment #11 from Boudewijn Rempt  ---
> Okay, downloading now.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[plasmashell] [Bug 362677] Crashes on changing activity

[Aayush Agarwal via KDE Bugzilla]

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

--- Comment #2 from Aayush Agarwal  ---
I get that it's a duplicate but which version of Plasma has this been fixed in?
I'm still getting this bug as of 5.6.4.

Application: plasmashell (5.6.4)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.6.2-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160621) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Using meta+tab to switch between activities.
- Unusual behavior I noticed:
One of my activities was missing

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 0x7fe1c85c58c0 (LWP 2761))]

Thread 35 (Thread 0x7fe1b2785700 (LWP 2770)):
#0  0x7fe1c19d5a1d in poll () at /lib64/libc.so.6
#1  0x7fe1c69bc410 in  () at /usr/lib64/libxcb.so.1
#2  0x7fe1c69be1a9 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fe1b5119ef9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fe1c20d2868 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fe1c11d8474 in start_thread () at /lib64/libpthread.so.0
#6  0x7fe1c19de3ed in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7fe1abfff700 (LWP 2775)):
#0  0x7fe1c19d5a1d in poll () at /lib64/libc.so.6
#1  0x7fe1be068186 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe1be06828c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe1c22feedb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe1c22a6b3a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe1c20cd963 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe1c30a1815 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fe1c20d2868 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fe1c11d8474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe1c19de3ed in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7fe1aadee700 (LWP 2860)):
#0  0x7fe1be067a4e in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fe1be068100 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe1be06828c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe1c22feedb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe1c22a6b3a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe1c20cd963 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe1c5468ac5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fe1c20d2868 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fe1c11d8474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe1c19de3ed in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7fe197ce1700 (LWP 2877)):
#0  0x7fe1be0aad69 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fe1be068278 in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fe1c22feedb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7fe1c22a6b3a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7fe1c20cd963 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7fe1c5468ac5 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7fe1c20d2868 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe1c11d8474 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe1c19de3ed in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7fe196481700 (LWP 2885)):
#0  0x7fe1be0aad84 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fe1be068142 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe1be06828c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe1c22feedb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe1c22a6b3a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe1c20cd963 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe1c5468ac5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fe1c20d2868 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fe1c11d8474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe1c19de3ed in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7fe194b51700 (LWP 2916)):
#0  0x7fe1c11de09f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe1c7ca4fc4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fe1c7ca5009 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fe1c11d8474 in start_thread () at /lib64/libpthread.so.0
#4  0x7fe1c19de3ed in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fe18df32700 (LWP 2951)):
#0  0x7fe1c19d5a1d in poll () at /lib64/libc.so.6
#1  0x7fe1be068186 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe1be06828c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe1c22feedb in

[plasmashell] [Bug 363909] After suspend plasmashell and X use about 2 cpus

[via KDE Bugzilla]

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

vindica...@live.com changed:

   What|Removed |Added

 CC||vindica...@live.com

--- Comment #4 from vindica...@live.com ---
Just adding myself to this report since it basically mirrors my issue as well.
It's been happening for well over a month and I looked into it a little before,
but now it's really bugging me and I want to see it get resolved.

I'm using Archlinux, single display, 5 KDE widgets on the side to keep tabs on
resources.
I don't know when it happens, I'll just suddenly notice my mouse cursor
skip/jitter and then note my cpu widget much higher while at "idle".

I will also confirm killing plasmashell and restarting it brings the cpu usage
back to normal.

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

[konsole] [Bug 364685] New: Kconsole crashs - maybe becuase started from PyQt5 app

[Barry Scott via KDE Bugzilla]

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

Bug ID: 364685
   Summary: Kconsole crashs - maybe becuase started from PyQt5 app
   Product: konsole
   Version: 16.04.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: ba...@barrys-emacs.org

Application: konsole (16.04.1)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.7-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I run a PyQt5 application that allows Konsole processes to be created.

Maybe this is related to the crash.

I am happy to test patches that investigate the problem of may fix it.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f967a79e980 (LWP 13230))]

Thread 2 (Thread 0x7f967a593700 (LWP 13231)):
#0  0x7f9688bee32d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f968472fa46 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f96740033b0, timeout=, context=0x7f9674001600)
at gmain.c:4135
#2  0x7f968472fa46 in g_main_context_iterate
(context=context@entry=0x7f9674001600, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f968472fb5c in g_main_context_iteration (context=0x7f9674001600,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f96899f265b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f96740008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f96899a1a6a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f967a592c00, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f9689801a03 in QThread::exec() (this=this@entry=0x7f968fb82060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#7  0x7f968fb0d3b9 in QDBusConnectionManager::run() (this=0x7f968fb82060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7f968980603a in QThreadPrivate::start(void*) (arg=0x7f968fb82060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#9  0x7f9686f655ca in start_thread (arg=0x7f967a593700) at
pthread_create.c:333
#10 0x7f9688bf9ead in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f967a79e980 (LWP 13230)):
[KCrash Handler]
#6  0x7f9688b2b6f5 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f9688b2d2fa in __GI_abort () at abort.c:89
#8  0x7f96897f2321 in QMessageLogger::fatal(char const*, ...) const
(context=..., message=) at global/qlogging.cpp:1610
#9  0x7f96897f2321 in QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffec5ad59a0, msg=msg@entry=0x7f968fb69dd0 "Internal error:
got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") at
global/qlogging.cpp:784
#10 0x7f968fb190ed in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) (this=,
object=, msg=..., metaTypes=..., slotIdx=) at
qdbusintegrator.cpp:940
#11 0x7f96899cc059 in QObject::event(QEvent*) (this=0x55d3cc06c550,
e=) at kernel/qobject.cpp:1256
#12 0x7f968a23434c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55d3cc06c550, e=0x7f9674015560) at
kernel/qapplication.cpp:3714
#13 0x7f968a23952f in QApplication::notify(QObject*, QEvent*)
(this=0x7ffec5ad60d0, receiver=0x55d3cc06c550, e=0x7f9674015560) at
kernel/qapplication.cpp:3495
#14 0x7f96899a2bfa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55d3cc06c550, event=event@entry=0x7f9674015560) at
kernel/qcoreapplication.cpp:1015
#15 0x7f96899a4c9f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (event=0x7f9674015560, receiver=) at
kernel/qcoreapplication.h:227
#16 0x7f96899a4c9f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x55d3cbcc30b0) at kernel/qcoreapplication.cpp:1650
#17 0x7f96899a51b8 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1508
#18 0x7f96899f25c3 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=s@entry=0x55d3cbd4a930) at kernel/qeventdispatcher_glib.cpp:270
#19 0x7f968472f703 in g_main_context_dispatch (context=0x7f9674001710) at
gmain.c:3154
#20 0x7f968472f703 in g_main_context_dispatch
(context=context@entry=0x7f9674001710) at gmain.c:3769

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

[Stefan via KDE Bugzilla]

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

--- Comment #12 from Stefan  ---
Today a was working on the write access. The deletion of an note works now, but
the resource blocks after this operation and is then unusable.

Adding and modifying don't work at the moment. The note data seems not to be
available as payload.

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #12 from Wolfgang Bauer  ---
I had a look at the problem today, and this should fix it:
https://git.reviewboard.kde.org/r/128279

Ideally, kmahjongg would try to adjust the path though IMHO, e.g. try to load
$XDG_DATA_DIRS/kmahjongg/layouts/FILENAME_WITHOUT_PATH before falling back to
the default.
Currently, the KDE4 migration basically resets the layout, background and
tileset because the paths have changed.

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

[digikam] [Bug 364563] digiKam crashes when browsing albums, only for images in portrait format

[Hans-Peter via KDE Bugzilla]

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

--- Comment #2 from Hans-Peter  ---
I can provide a sample, but how? Just attach it here in the bugs.kde.org ?

Additional info: it seems that it crashes only with portrait mode images from
my new Sony A77ii, older images can be browsed without crash. I just
de-installed exiv2 from Phillip Johnsons ppa and installed the older
libgexif2-2 from Ubuntu repos instead, this seem to work stable.

HP

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

[cantor] [Bug 363560] Sage backend is not working with Sage 7.2 version

[jackdyson31 via KDE Bugzilla]

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

--- Comment #6 from jackdyson31  ---
just for info : downloaded and built the 16.04 updated Cantor Version 16.07.70
on Kubuntu 16.04 - doesn't seem to work, opens a sage window : typing commands
hangs it or displays nothing as output.

Only solution I got running was mathcals' suggestion here:
https://bugs.kde.org/show_bug.cgi?id=348128
The LaTeX doesn't work however (it does on the old Cantor in Kubuntu 14.04)

thanks for all the hard work!

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

[kdenlive] [Bug 364278] kdenlive crashes whilst starting

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

--- Comment #6 from Jean-Baptiste Mardelle  ---
Some of the OpenGL changes I made in git master were backported to the 16.04.2
version and I guess this is the reason for your crash. The problem is that
OpenGL's is highly tied to the graphic card / driver that you are using. So
depending on your hardware/driver config, things might work or crash... Not
sure how to handle this issue.

Can you tell us which graphic card / drivers you are using ?

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

[kdenlive] [Bug 360039] Movie from hell crashes kdenlive

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from Wegwerf  ---
eezacque, can you please test with melt and ffmpeg if the same or similar
problem happens when you try to play your particular movie file? As Kdenlive
uses ffmpeg for decoding and MLT for playing av media, it is probably a general
issue out of scope of Kdenlive. Which MLT and ffmpeg versions do you have
installed. Also, without the concrete movie file, it is impossible to reproduce
your problem. The report at this time is not extemely useful, I'm afraid.

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Frederik Schwarzer via KDE Bugzilla]

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

--- Comment #11 from Frederik Schwarzer  ---
I am sorry about this problem. It did not occur on my box when I ported
KMahjongg.

Two months ago I tried to debug this but got confused by all the locations
stuff can be put to (by CMake) and looked for (by Qt). Currenty I am in the
process of finding a flat in another city and starting a new job so in the
coming weeks (or small number of months) I am likely not able to sit down for
this again.

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

[kaffeine] [Bug 364517] Kaffeine can't tune in RTL (dvb-c / german television)

[boris64 via KDE Bugzilla]

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

--- Comment #6 from boris64  ---
FYI: i tried up2date vlc-3 (git-whatever) + vlc-clang-git and it turned out
that RTL was ok (for now), but another channel showed video only and no sound
anymore. Ahhrr crap.
So this really seems to be some kind of _vlc issue_. Too bad there is no way of
choosing the backend used in kaffeine. In (s)mplayer everything is really ok
(but on the other hand it's really slow when switching channels because of
buffering).

Ok, thanks for your help anyway ;)

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

[digikam] [Bug 364563] digiKam crashes when browsing albums, only for images in portrait format

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
I can not reproduce this problem with digikam-5.0.0-beta7. Can you upload a
test image in portrait format?

Maik

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #8 from Andreas Hartmetz  ---
Git commit 2946faa9a4e1fa2eb85d67f0bb11bd3f62f331aa by Andreas Hartmetz.
Committed on 23/06/2016 at 19:06.
Pushed by ahartmetz into branch 'master'.

Revert "Remove legacy session management support."

This reverts commit 5f0ca1305db4a925dbdbf927f541497be334feff.

Firefox and some GTK+ 2 applications still seem to use the old way.
For shame.

Cherry-picked from 5.6.

M  +1-0ksmserver/CMakeLists.txt
A  +419  -0ksmserver/legacy.cpp [License: UNKNOWN]  *
M  +1-0ksmserver/server.cpp
M  +26   -2ksmserver/server.h
M  +11   -1ksmserver/shutdown.cpp
M  +2-0ksmserver/startup.cpp

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/plasma-workspace/2946faa9a4e1fa2eb85d67f0bb11bd3f62f331aa

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #9 from Andreas Hartmetz  ---
Git commit 03f0dc51d72ba0ad55fe077a519e1041c937ac6d by Andreas Hartmetz.
Committed on 23/06/2016 at 19:07.
Pushed by ahartmetz into branch 'master'.

Revert "Remove saving and loading (and client matching by) WM_COMMAND."

This reverts commit 2eac7634cc524bf5e425cf081a639a6b6407e380.

Cherry-picked from 5.6.

M  +1-1activities.cpp
M  +17   -4sm.cpp
M  +1-0sm.h
M  +13   -0toplevel.cpp
M  +1-0toplevel.h

http://commits.kde.org/kwin/03f0dc51d72ba0ad55fe077a519e1041c937ac6d

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #7 from Andreas Hartmetz  ---
Git commit bdf555bbcb277566d5901de9902990024f680dfe by Andreas Hartmetz.
Committed on 23/06/2016 at 18:59.
Pushed by ahartmetz into branch 'Plasma/5.7'.

Revert "Remove saving and loading (and client matching by) WM_COMMAND."

This reverts commit 2eac7634cc524bf5e425cf081a639a6b6407e380.

Cherry-picked from 5.6.

M  +1-1activities.cpp
M  +17   -4sm.cpp
M  +1-0sm.h
M  +13   -0toplevel.cpp
M  +1-0toplevel.h

http://commits.kde.org/kwin/bdf555bbcb277566d5901de9902990024f680dfe

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #6 from Andreas Hartmetz  ---
Git commit aee734e126b16db3be510a46ead9134c987fc97b by Andreas Hartmetz.
Committed on 23/06/2016 at 19:00.
Pushed by ahartmetz into branch 'Plasma/5.7'.

Revert "Remove legacy session management support."

This reverts commit 5f0ca1305db4a925dbdbf927f541497be334feff.

Firefox and some GTK+ 2 applications still seem to use the old way.
For shame.

Cherry-picked from 5.6.

M  +1-0ksmserver/CMakeLists.txt
A  +419  -0ksmserver/legacy.cpp [License: UNKNOWN]  *
M  +1-0ksmserver/server.cpp
M  +26   -2ksmserver/server.h
M  +11   -1ksmserver/shutdown.cpp
M  +2-0ksmserver/startup.cpp

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/plasma-workspace/aee734e126b16db3be510a46ead9134c987fc97b

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

[digikam] [Bug 363697] Album visible even after deletion [patch]

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

Summary|Album visible even after|Album visible even after
   |deletion|deletion [patch]

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

[digikam] [Bug 363697] Album visible even after deletion

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #12 from Maik Qualmann  ---
Created attachment 99669
  --> https://bugs.kde.org/attachment.cgi?id=99669=edit
foreignKeyChecks.patch

I think a temporary disabling is fine here. Please test the patch.

Maik

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

[amarok] [Bug 364354] Amarok stutters and hangs system before crashing

[Be via KDE Bugzilla]

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

--- Comment #4 from Be  ---
Hm, so this may have something to do with PulseAudio. It happened again and I
left my computer for a while (after unplugging my speakers from my sound card).
When I came back, Amarok had not crashed, but my system was taking a long time
to respond to anything until I quit Amarok. I restarted Amarok and got a
warning from Phonon saying that various outputs could not be found, including
PulseAudio. Amarok wouldn't output any sound (maybe it was playing to my
onboard sound card?) so I started pavucontrol to check if my USB sound card (an
RME Babyface Pro in class compliant mode) got disconnected and PulseAudio
wasn't detecting it, but pavucontrol showed the error in the attached
screenshot. I ran 'pulseaudio -D' and restarted Amarok, then Amarok worked
fine.

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

[amarok] [Bug 364354] Amarok stutters and hangs system before crashing

[Be via KDE Bugzilla]

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

--- Comment #3 from Be  ---
Created attachment 99668
  --> https://bugs.kde.org/attachment.cgi?id=99668=edit
error when starting pavucontrol after quitting Amarok

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

[kdenlive] [Bug 348938] 15.04.1 Unusable - extremely slow timeline

[Torsten Römer via KDE Bugzilla]

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

Torsten Römer  changed:

   What|Removed |Added

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

--- Comment #4 from Torsten Römer  ---
Sorry for being a bit unresponsive - I just tested 15.12.3 which is installed
on my system and already there it works just fine.

So I am marking as solved.

Thanks!

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

[peruse] [Bug 364684] New: Two-page view

[via KDE Bugzilla]

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

Bug ID: 364684
   Summary: Two-page view
   Product: peruse
   Version: 1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: bode...@gmail.com

Comics often have landscapes that span two pages. A two-page view could show
the full picture.

Mangas, read from right to left, would need the two pages merged from right to
left: [-2-][-1-]

Reproducible: Always




An issue you would likely run into is mismatched pages. For example, the cover
page should not be merged with the first page. Complicating matters is the fact
that some comics may have alternate covers included. I do not think there is an
easy where to deal with this.

Because of this, you may need to include an option to manually offset which
pages are merged.

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

[kaffeine] [Bug 364683] New: Change channels or try selecting a recording results in an immediate crash.

[Alan via KDE Bugzilla]

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

Bug ID: 364683
   Summary: Change channels or try selecting  a recording results
in an immediate crash.
   Product: kaffeine
   Version: unspecified
  Platform: Mandriva RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: pinner...@gmail.com

I am using Mageia 5 and Kaffeine 1.3-git.
This has been comoletely stable until today.

Reproducible: Always

Steps to Reproduce:
1.Execute kaffeine
2.click on new channel; or
3.Go to file->~/videos. Click on video title - crash.


Expected Results:  
See bug trace at additional info

Application: kaffeine (1.3-git)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.4.13-desktop-1.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:


-- Backtrace:
Application: Kaffeine (kaffeine), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2359cd9780 (LWP 5907))]

Thread 5 (Thread 0x7f233e5e0700 (LWP 5908)):
#0  0x7f2355d87d6d in poll () at /lib64/libc.so.6
#1  0x7f2340325c81 in poll_func () at /lib64/libpulse.so.0
#2  0x7f2340317891 in pa_mainloop_poll () at /lib64/libpulse.so.0
#3  0x7f2340317ece in pa_mainloop_iterate () at /lib64/libpulse.so.0
#4  0x7f2340317f80 in pa_mainloop_run () at /lib64/libpulse.so.0
#5  0x7f2340325c33 in thread () at /lib64/libpulse.so.0
#6  0x7f23400ca198 in internal_thread_func () at
/usr/lib64/pulseaudio/libpulsecommon-5.0.so
#7  0x7f23573215bd in start_thread () at /lib64/libpthread.so.0
#8  0x7f2355d9362d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f233dddf700 (LWP 5909)):
#0  0x7f2352492fe4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f235244ef5e in g_main_context_acquire () at /lib64/libglib-2.0.so.0
#2  0x7f235244fd85 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f235244ffbc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f23576dee3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#5  0x7f23576b0931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f23576b0c45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#7  0x7f23575ae899 in QThread::exec() () at /lib64/libQtCore.so.4
#8  0x7f23576923d3 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#9  0x7f23575b0fff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#10 0x7f23573215bd in start_thread () at /lib64/libpthread.so.0
#11 0x7f2355d9362d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f233c604700 (LWP 5924)):
[KCrash Handler]
#5  0x7f2355ccf547 in raise () at /lib64/libc.so.6
#6  0x7f2355cd0cda in abort () at /lib64/libc.so.6
#7  0x7f2355d0e393 in  () at /lib64/libc.so.6
#8  0x7f2355d160c8 in _int_free () at /lib64/libc.so.6
#9  0x7f2355d19798 in free () at /lib64/libc.so.6
#10 0x7f230f19630f in mad_stream_finish () at /lib64/libmad.so.0
#11 0x7f230f3b3b06 in CloseFilter () at
/usr/lib64/vlc/plugins/audio_filter/libmpgatofixed32_plugin.so
#12 0x7f23541b2902 in vlc_module_unload () at /lib64/libvlccore.so.8
#13 0x7f23541a3157 in aout_FiltersDelete () at /lib64/libvlccore.so.8
#14 0x7f23541a11d2 in aout_DecDelete () at /lib64/libvlccore.so.8
#15 0x7f23541641b5 in DeleteDecoder () at /lib64/libvlccore.so.8
#16 0x7f235416c793 in EsUnselect () at /lib64/libvlccore.so.8
#17 0x7f2354170c64 in EsOutControl () at /lib64/libvlccore.so.8
#18 0x7f2354172fbc in es_out_Control () at /lib64/libvlccore.so.8
#19 0x7f2354174b5e in Control () at /lib64/libvlccore.so.8
#20 0x7f235417692c in es_out_Control () at /lib64/libvlccore.so.8
#21 0x7f235417b613 in End () at /lib64/libvlccore.so.8
#22 0x7f235417dd0d in Run () at /lib64/libvlccore.so.8
#23 0x7f23573215bd in start_thread () at /lib64/libpthread.so.0
#24 0x7f2355d9362d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f230c11a700 (LWP 5928)):
#0  0x7f2357326a28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f23541ce2d7 in vlc_cond_timedwait () at /lib64/libvlccore.so.8
#2  0x7f2354189eec in vout_control_Pop () at /lib64/libvlccore.so.8
#3  0x7f2354191c42 in Thread () at /lib64/libvlccore.so.8
#4  0x7f23573215bd in start_thread () at /lib64/libpthread.so.0
#5  0x7f2355d9362d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f2359cd9780 (LWP 5907)):
#0  0x7f2357322665 in pthread_join () at /lib64/libpthread.so.0
#1  0x7f235417dfef in input_Close () at /lib64/libvlccore.so.8
#2  0x7f2358a41677 in libvlc_media_player_set_media () at
/lib64/libvlc.so.5
#3  0x0048874b in VlcMediaWidget::play(MediaSource const&) ()
#4  

[partitionmanager] [Bug 364645] Partitionmanager crashs when trying to import partition table

[Fabian via KDE Bugzilla]

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

--- Comment #3 from Fabian  ---
Hi, I am using a mixture of English and German localization. Means the
underlying Arch is localized in German, but Plasma and all other KDE related
applications are localized in English.

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

[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional

[Marco Parillo via KDE Bugzilla]

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

--- Comment #26 from Marco Parillo  ---
With Plasma 5.6.5. I can hide the panel, show the desktop, click the K kicker,
and move the mouse pointer up to one of my favorites? It seems to me that the
bottom of the kicker menu is too high, where the panel should have been, but is
now hidden.

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

[peruse] [Bug 364682] New: Manga (AKA right-to-left) page navigation

[via KDE Bugzilla]

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

Bug ID: 364682
   Summary: Manga (AKA right-to-left) page navigation
   Product: peruse
   Version: 1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: bode...@gmail.com

Mangas are read from right to left, so pages should slide in from the left.

Ideally, this should be a per-comic option so that you don't have to switch the
navigation modes each time that you read a comic after a manga, or vice versa.

Reproducible: Always

Steps to Reproduce:
1. Open Manga
2. Tap left arrow or swipe page to the right

Actual Results:  
Nothing, or we return to the Welcome screen

Expected Results:  
Next page of manga slides in from the left.

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

[plasmashell] [Bug 364681] New: plasmall digital clock calendar shows month in wrong language when LC_TIME uses a different language

[Allan via KDE Bugzilla]

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

Bug ID: 364681
   Summary: plasmall digital clock calendar shows month in wrong
language when LC_TIME uses a different language
   Product: plasmashell
   Version: 5.6.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: mklape...@kde.org
  Reporter: al...@azic.ca
CC: plasma-b...@kde.org

When LC_TIME is set to a zone with a different language, the following gets
translated:

- digital clock tooltip
- digital clock's calendar weekday

but not the digital clock's calendar month.

Reproducible: Always

Steps to Reproduce:
1. change LC_TIME to different zone that uses a different language than LANG
2.
3.

Actual Results:  
see that digital clock calendar translation is incomplete

Expected Results:  
translate the month to LC_TIME's langauge like other translated elements

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

[okular] [Bug 364680] feature request: restore previous session

[Peter via KDE Bugzilla]

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

Peter  changed:

   What|Removed |Added

 CC||pmli...@free.fr

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

[okular] [Bug 364680] New: feature request: restore previous session

[Peter via KDE Bugzilla]

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

Bug ID: 364680
   Summary: feature request: restore previous session
   Product: okular
   Version: unspecified
  Platform: Other
   URL: https://mail.kde.org/pipermail/okular-devel/2014-Decem
ber/019851.html
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: pmli...@free.fr

Hi,

It would be nice, if Okular could restore the previous session (like Firefox).

TIA for your efforts,
Peter

Reproducible: Always

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #5 from Andreas Hartmetz  ---
Git commit 59740e7416bb2b3a9852212fa4b213e5ba76deb7 by Andreas Hartmetz.
Committed on 23/06/2016 at 17:40.
Pushed by ahartmetz into branch 'Plasma/5.6'.

Revert "Remove saving and loading (and client matching by) WM_COMMAND."

This reverts commit 2eac7634cc524bf5e425cf081a639a6b6407e380.

M  +1-1activities.cpp
M  +17   -4sm.cpp
M  +1-0sm.h
M  +13   -0toplevel.cpp
M  +1-0toplevel.h

http://commits.kde.org/kwin/59740e7416bb2b3a9852212fa4b213e5ba76deb7

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Andreas Hartmetz via KDE Bugzilla]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/e4a76cd947759f
   ||d723935965ca30c00021601a45
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Andreas Hartmetz  ---
Git commit e4a76cd947759fd723935965ca30c00021601a45 by Andreas Hartmetz.
Committed on 23/06/2016 at 17:36.
Pushed by ahartmetz into branch 'Plasma/5.6'.

Revert "Remove legacy session management support."

This reverts commit 5f0ca1305db4a925dbdbf927f541497be334feff.

Firefox and some GTK+ 2 applications still seem to use the old way.
For shame.

M  +1-0ksmserver/CMakeLists.txt
A  +419  -0ksmserver/legacy.cpp [License: UNKNOWN]  *
M  +1-0ksmserver/server.cpp
M  +26   -2ksmserver/server.h
M  +11   -1ksmserver/shutdown.cpp
M  +2-0ksmserver/startup.cpp

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/plasma-workspace/e4a76cd947759fd723935965ca30c00021601a45

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

[kontact] [Bug 364663] Crash after importing Thunderbird mails

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org
 Resolution|--- |FIXED

--- Comment #1 from Laurent Montel  ---
Fixed in 5.2.x

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

[Piotr Mierzwinski via KDE Bugzilla]

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

--- Comment #66 from Piotr Mierzwinski  ---
@Wolfgang Bauer
Thanks for explanation.
On begin I can say that happened what I supposed. So today after first login to
Plasma, konsole has not been restored, at all. Maybe this is some bug in
konsole. Yesterday, before shutting down the system I also run okular, and
kate. Today all of them have been restored.

> restoring them should work (or not) the same for both
> But in the end it's the client's (i.e. the application's) job to save its 
> state correctly
I know that in the moment of closing application its destructor are calling,
actually QApplication/KApplication. So what is the difference in type of
shutting (by server). When I log off (calling log off in Plasma) or shut down
system (calling "turn of" in Plasma) then shutting should work the same. in
This is my suspicion.
The only one job what can do application in shutting down moment is saving it's
state into some configuration file. Every other actions are managed by
Qt/KF/ksmsever. As I suppose.  And this is doing correct for login off and
restart.

For me it should just work for both (konsole and kwrite) the same.
Sorry I repeat my self. Yesterday I reloged couple of times, also I restarted
system. And konsole was restored every time. When yesterday  I shut down the
system and run it today,  konsole has not been restored. I don't understand
this.
I don't know how exactly Plasma closing/shutting down its session, I suppose is
using some qdbus command (example of shutting down: "qdbus org.kde.ksmserver
/KSMServer logout 0 2 2"). Is this implemented by distribution or in K menu?

And on end. You are comparing two Qt versions. Why openSuse doesn't use the
newest Qt version, only its developers backported some fixes? Maybe in last Qt
still persists some bug related with closing applications. 

@Chris
I don't know what situation you meant, saying "konsole never ever get restored
for me."?
If this is just rerun of konsole thats OK. For me either konsole wasn't
restored.
If this is relogin/restart/shut down and run then in my opinion konsole should
be restored every times when Plasma session is starting and proper option is
turned on in Plasma setting (for example: "Restore previous session" in System
settings).

Maybe this is distro related. I don know. :/. I'll try to report it.

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

[krita] [Bug 364237] When user switches to a subwindow of other saved document , the window reverts to previous subwindow

[Quiralta via KDE Bugzilla]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #2 from Quiralta  ---
I can reproduce the same issue, also on archlinux.

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

[systemsettings] [Bug 182847] Phonon-4.3.0 not all alsa pcm listed

[Andrew Gaydenko via KDE Bugzilla]

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

Andrew Gaydenko  changed:

   What|Removed |Added

 CC|a...@gaydenko.com  |

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||toralf.foers...@gmx.de

--- Comment #10 from Wolfgang Bauer  ---
*** Bug 364646 has been marked as a duplicate of this bug. ***

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

[kmahjongg] [Bug 364646] new kmahjongg won't start if an too old rc file is there

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Wolfgang Bauer  ---
The problem is not that the kmahjonggrc file is "too old", but that it
specifies a non-existing Layout_file which causes kmahjongg to enter an endless
loop apparently.

Just removing (or correcting) that one line should fix it too.

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

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

[Phonon] [Bug 329476] no sound device found but it is present

[Andreas Hartmetz via KDE Bugzilla]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 CC||ahartm...@gmail.com
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Andreas Hartmetz  ---
Peter, do you have a custom alsa configuration? This might be a duplicate of
bug 182847.

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

[systemsettings] [Bug 182847] Phonon-4.3.0 not all alsa pcm listed

[Andreas Hartmetz via KDE Bugzilla]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 CC||ahartm...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #14 from Andreas Hartmetz  ---
This is probably due to an upstream bug that was fixed by yours truly in VLC
2.2.2. If the default device was created in an .asoundrc / alsa.conf, it could
not be selected in VLC.

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

[kdeconnect] [Bug 343235] SFTP: Dolphin is unresponsive when copying file via directory browse

[EMR_Kde via KDE Bugzilla]

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

--- Comment #2 from EMR_Kde  ---
Notably, it does not happen in a file chooser (Start Kate, File -> Open,
sftp://servername). I could click around forever and it doesn't get hung up.

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

[dolphin] [Bug 364642] 16.04.1: kio_sftp is broken

[EMR_Kde via KDE Bugzilla]

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

--- Comment #1 from EMR_Kde  ---
I am getting the same error. I think we might have the same bug, even if the
symptoms are different. See my bug #364677. It just hangs when I navigate more
than four clicks on a remote system. But if I open file -> new window, I can
get four more clicks before it hanging.

fileSystemFreeSpace() did not call finished() or error()! Please fix the KIO
slave.

If I leave the window open it just keeps printing: log_kio_sftp: special():
polling

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

[dolphin] [Bug 364642] 16.04.1: kio_sftp is broken

[EMR_Kde via KDE Bugzilla]

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

EMR_Kde  changed:

   What|Removed |Added

 CC||emre...@gmail.com

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

[plasmashell] [Bug 364679] New: Plasma hangs and crash when connect external monitor

[alien via KDE Bugzilla]

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

Bug ID: 364679
   Summary: Plasma hangs and crash when connect external monitor
   Product: plasmashell
   Version: 5.6.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 27...@alunos.isel.ipl.pt
CC: bhus...@gmail.com, plasma-b...@kde.org

If connect an external project on VGA the plasma hangs first by locking the
computer and mouse get stuck for log time, and then crash. After some time both
screens get black and the panels disappear and the computer start respond.

Reproducible: Always

Steps to Reproduce:
1. Connect a projector or monitor to vga or hdmi
2.
3.

Actual Results:  
hang the computer and crash the plasmashell

Expected Results:  
Show the image on both screens and don't crash plasmashell

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

[kaddressbook] [Bug 364678] New: kaddressbook does not sync contacts

[Peter Gückel via KDE Bugzilla]

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

Bug ID: 364678
   Summary: kaddressbook does not sync contacts
   Product: kaddressbook
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pguec...@gmail.com
CC: to...@kde.org

kaddressbook-15.12.3-1.fc24.x86_64
akonadi-1.13.0-102.fc24.x86_64

I had a contacts vcard file.vcf with all of my contacts. Whenever I made
changes to the information in kaddressbook, the akonadi database was correctly
updated, but the updates were not written to my master file resource! I then
converted the contacts.vcf file to individual vcard4 files, one for each
contact, and made a contacts directory. Again, kaddressbook read all of my
contacts into the akonadi database, but, when making updates to the contact
information, the revised data was not correspondingly updated in my master
vcard file collection.

As a result of this bug, I have irretrievably lost much information.

Why do the updates not get written to the master resources?

Reproducible: Always


Actual Results:  
Edit a contact. Akonadi is updated, but the master file is not. When
transferring the master file to a clean install of fedora or to another distro,
there is data loss.

Expected Results:  
My updates to my saved contact information must be preserved!

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

[dolphin] [Bug 364677] Dolphin hangs during sftp url access

[EMR_Kde via KDE Bugzilla]

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

--- Comment #1 from EMR_Kde  ---
Note, I sent it the SEGV signal to get a dump. Otherwise dolphin just hangs
there. If you open another one, it would be a separate process. Also, the
sockets are not where the second local:// is.

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

[dolphin] [Bug 364677] Dolphin hangs during sftp url access

[EMR_Kde via KDE Bugzilla]

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

EMR_Kde  changed:

   What|Removed |Added

   Severity|crash   |major
 CC||emre...@gmail.com

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

[dolphin] [Bug 364677] New: Dolphin hangs during sftp url access

[EMR_Kde via KDE Bugzilla]

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

Bug ID: 364677
   Summary: Dolphin hangs during sftp url access
   Product: dolphin
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: emre...@gmail.com

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.21-14-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I repeated this twice, and it happens all the time:
1) open dolphin
2) enter sftp://servername 
3) change the url to sftp://servername/usr/local/src
4) click on a subdirectory 4-5 times
Result: 
It just says "Loading..." at bottom right and nothing shows up.
Expected Result:
Display lists of folders.

Extra info:
 1705 ?Tl 0:02 /usr/bin/dolphin -session
1013a1a61b11ab00014666917790015980050_1466693648_956992
 5069 ?Tl 0:03 /usr/bin/dolphin
 5153 ?Sl 0:00 /usr/lib64/libexec/drkonqi -platform xcb -display :0
--appname dolphin --apppath /usr/bin --signal 11 --pid 1705 --appversion
15.12.3 --programname Dolphin --bugaddress sub...@bugs.kde.org --startupid 0
 5154 ?Sl 0:04 /usr/lib64/libexec/drkonqi -platform xcb -display :0
--appname dolphin --apppath /usr/bin --signal 11 --pid 5069 --appversion
15.12.3 --programname Dolphin --bugaddress sub...@bugs.kde.org --startupid 0
 5227 ?Sl 0:16 /usr/bin/dolphin
 5241 ?S  0:00 sftp.so [kdeinit5] sftp
local:/run/user/1001/klauncherXM1611.1.slave-socket
local:/run/user/1001/dolphinBC5227.5.slave-socket
 5242 ?S  0:00 sftp.so [kdeinit5] sftp
local:/run/user/1001/klauncherXM1611.1.slave-socket
local:/run/user/1001/dolphinHf5227.6.slave-socket
 5243 ?S  0:00 sftp.so [kdeinit5] sftp
local:/run/user/1001/klauncherXM1611.1.slave-socket
local:/run/user/1001/dolphinyJ5227.7.slave-socket
 5245 ?S  0:00 sftp.so [kdeinit5] sftp
local:/run/user/1001/klauncherXM1611.1.slave-socket
local:/run/user/1001/dolphinFW5227.8.slave-socket
 5251 ?S  0:00 sftp.so [kdeinit5] sftp
local:/run/user/1001/klauncherXM1611.1.slave-socket
local:/run/user/1001/dolphinwX5227.9.slave-socket

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f717b34c700 (LWP 5070)):
#0  0x7f7191bfabbd in poll () at /lib64/libc.so.6
#1  0x7f7184c06422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f7184c0800f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f717d6a13c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f718bd0a32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f71877b80a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f7191c02fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f71923477c0 (LWP 5069)):
[KCrash Handler]
#6  0x7f7191bfabbd in poll () at /lib64/libc.so.6
#7  0x7f7186c32e64 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7186c32f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f718bf3cd6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f718bee3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f718beeb8f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#12 0x7f7191f26427 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#13 0x7f7191b3fb05 in __libc_start_main () at /lib64/libc.so.6
#14 0x004007ee in _start ()

Reported using DrKonqi

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

[okular] [Bug 364676] New: Okular turns off/on HDMI external monitor

[alien via KDE Bugzilla]

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

Bug ID: 364676
   Summary: Okular turns off/on HDMI external monitor
   Product: okular
   Version: 0.24.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: 27...@alunos.isel.ipl.pt

If we open a pdf document from firefox or thunderbird the okular open the
document and turns off the hdmi external monitor. After that sometimes it will
turn on if you open another document from thunderbird or firefox. 

When it turns off, you can not detect the presence of the monitor although it's
attached.
The if you open a document with the same process for example in thunderbird it
will turn on the external monitor

Reproducible: Sometimes

Steps to Reproduce:
1. Download a pdf document,
2. On saves as dialog select open with Okular
3. Do OK

Actual Results:  
Open the document and turns off the  external monitor.

Expected Results:  
Don't turn on/off the external monitor

Lenovo E530c
Graphic card Intel 4000

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

[kdenlive] [Bug 364278] kdenlive crashes whilst starting

[Frits Spieker via KDE Bugzilla]

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

--- Comment #5 from Frits Spieker  ---
6.2.0-70.4

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

[kinfocenter] [Bug 364675] New: KInfoCenter crashed when I was quickly reviewing infos

[via KDE Bugzilla]

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

Bug ID: 364675
   Summary: KInfoCenter crashed when I was quickly reviewing infos
   Product: kinfocenter
   Version: 5.6.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: kevi...@zaclys.net

Application: kinfocenter (5.6.4)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.7-300.fc24.x86_64+debug x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed: I was quickly reviewing all
the informations in the app when it suddently crashed

-- Backtrace:
Application: Info Center (kinfocenter), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7feb52ab9940 (LWP 4727))]

Thread 4 (Thread 0x7feb397bc700 (LWP 4733)):
#0  0x7feb61b0e32d in poll () at /lib64/libc.so.6
#1  0x7feb5de61a46 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7feb5de61b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7feb6291265b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7feb628c1a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7feb62721a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7feb612ed145 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7feb6272603a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7feb5f6695ca in start_thread () at /lib64/libpthread.so.0
#9  0x7feb61b19ead in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7feb3bfff700 (LWP 4732)):
#0  0x7feb61b0e32d in poll () at /lib64/libc.so.6
#1  0x7feb5de61a46 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7feb5de61b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7feb6291265b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7feb628c1a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7feb62721a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7feb612ed145 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7feb6272603a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7feb5f6695ca in start_thread () at /lib64/libpthread.so.0
#9  0x7feb61b19ead in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7feb43dc3700 (LWP 4729)):
#0  0x7feb61b0e32d in poll () at /lib64/libc.so.6
#1  0x7feb5de61a46 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7feb5de61b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7feb6291265b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7feb628c1a6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7feb62721a03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7feb684ed3b9 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7feb6272603a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7feb5f6695ca in start_thread () at /lib64/libpthread.so.0
#9  0x7feb61b19ead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7feb52ab9940 (LWP 4727)):
[KCrash Handler]
#5  0x7feb5eb9db3c in xcb_send_request64 () at /lib64/libxcb.so.1
#6  0x7feb5eb9dc79 in xcb_send_request () at /lib64/libxcb.so.1
#7  0x7feb5eba5ad0 in xcb_free_pixmap () at /lib64/libxcb.so.1
#8  0x7feb4b6f9ffb in dri3_free_render_buffer.isra () at /lib64/libEGL.so.1
#9  0x7feb4b6fa303 in loader_dri3_drawable_fini () at /lib64/libEGL.so.1
#10 0x7feb4b6f954e in dri3_destroy_surface () at /lib64/libEGL.so.1
#11 0x7feb4b6f09bf in dri2_make_current () at /lib64/libEGL.so.1
#12 0x7feb4b6e64f3 in eglMakeCurrent () at /lib64/libEGL.so.1
#13 0x7feb31ecfa1d in GetInfo_OpenGL(QTreeWidget*) () at
/usr/lib64/qt5/plugins/kcm_opengl.so
#14 0x7feb31ed0b11 in KCMOpenGL::KCMOpenGL(QWidget*, QList
const&) () at /usr/lib64/qt5/plugins/kcm_opengl.so
#15 0x7feb31ed1bf8 in QObject* KPluginFactory::createInstance(QWidget*, QObject*, QList const&) () at
/usr/lib64/qt5/plugins/kcm_opengl.so
#16 0x7feb63b962a4 in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) () at
/lib64/libKF5CoreAddons.so.5
#17 0x7feb681f3fc7 in KCModuleLoader::loadModule(KCModuleInfo const&,
KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () at
/lib64/libKF5KCMUtils.so.5
#18 0x7feb681fcfcf in KCModuleProxyPrivate::loadModule() () at
/lib64/libKF5KCMUtils.so.5
#19 0x7feb681fdbc5 in KCModuleProxy::realModule() const () at
/lib64/libKF5KCMUtils.so.5
#20 0x7feb681fdd64 in 

[krita] [Bug 364096] Scml spriter export fails to properly crop the layers, fails to export animation frames

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #6 from Boudewijn Rempt  ---
Git commit 85bcf05c4c1839ba9db58cb8f8580c39c2c1fa80 by Boudewijn Rempt.
Committed on 23/06/2016 at 14:58.
Pushed by rempt into branch 'video-export-rebased'.

M  +3-3plugins/impex/spriter/kis_spriter_export.cpp

http://commits.kde.org/krita/85bcf05c4c1839ba9db58cb8f8580c39c2c1fa80

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

[amarok] [Bug 360540] Amarok does not read the "albumartist" ID3 tag in my ID3v2.4 tagged MP3 Files

[Daniil Vasin via KDE Bugzilla]

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

--- Comment #12 from Daniil Vasin  ---
What do you mean?

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

[frameworks-baloo] [Bug 362255] Searching through menu crashed kde

[Reuben Peterkin via KDE Bugzilla]

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

Reuben Peterkin  changed:

   What|Removed |Added

 CC||reube...@yahoo.com

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

[frameworks-baloo] [Bug 362773] after type word in menu search

[Reuben Peterkin via KDE Bugzilla]

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

Reuben Peterkin  changed:

   What|Removed |Added

 CC||reube...@yahoo.com

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

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

[Wolfgang Lorenz via KDE Bugzilla]

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

Wolfgang Lorenz  changed:

   What|Removed |Added

 CC||wl-c...@gmx.de

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

[korganizer] [Bug 364674] attendee auto completion does not work

[via KDE Bugzilla]

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

--- Comment #1 from jacob.bec...@uni-konstanz.de ---
the openSUSE tumbleweed kontact (5.1.3) shows the same issue.

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

[korganizer] [Bug 364674] New: attendee auto completion does not work

[via KDE Bugzilla]

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

Bug ID: 364674
   Summary: attendee auto completion does not work
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: invitations
  Assignee: korganizer-de...@kde.org
  Reporter: jacob.bec...@uni-konstanz.de

The attendees tab in the "new event ..." dialog offers  auto completion while
typing known addresses in the "Name" filed. However the names selected in the
appearing suggestion list are not filled in the name field, even when selected.

Reproducible: Always

Steps to Reproduce:
1. create new event
2. open attendees tab
3. typ an email address in the name filed known to akonadi so the suggestions
appear.
select a suggested attendee.

Actual Results:  
the string in the name filed showing only the user input not the selected
suggestion 

Expected Results:  
the selected attendee should be filled in the name field

kontact 5.1.3 with kde neon

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

[plasmashell] [Bug 364673] New: Widget explorer flickers between opaque and semi-transparent when dragging a widget over it

[Thomas Pfeiffer via KDE Bugzilla]

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

Bug ID: 364673
   Summary: Widget explorer flickers between opaque and
semi-transparent when dragging a widget over it
   Product: plasmashell
   Version: 5.6.95
  Platform: Neon Packages
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Widget Explorer
  Assignee: plasma-b...@kde.org
  Reporter: thomas.pfeif...@kde.org

When dragging a widget over the widget explorer, it's supposed to go
semi-transparent so that one can place a widget under it.
However, when doing so, it flickers between opaque and semi-transparent, and
then goes semi-transparent when you move the widget away from it again.

Reproducible: Always

Steps to Reproduce:
1. Click on "Add Widgets"
2. Drag a widget
3. Move the cursor over the widget explorer

Actual Results:  
Explorer flickers

Expected Results:  
Explorer goes semi-transparent

I can see it both on an AMD GPU and an Intel GPU with 5.6.5 on Manjaro and on
5.6.95 on Neon.

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

[Lucky via KDE Bugzilla]

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

Lucky  changed:

   What|Removed |Added

 CC||n...@southview.biz

--- Comment #45 from Lucky  ---
Same here, except I can see photos and videos on my SD card in a folder named
"Camera pictures(SD card 2)".  I can't see anything else on the SD Card.  There
are two folders named "SD card" and "SD card 2", but they are seemingly empty. 
I can see the contents of my phone in a folder named "Internal storage".

When I right-click on a file in Dophin, I get the option "Send to [phone] via
KDE connect".  When I click on on it, the file starts transferring immediately,
without other choices.  It then lands up in a folder "kdeconnect" on the
internal storage.  I'd like the option of transferring it to the SD card.

My set-up is Fedora 23 and a Hisence Pureshot phone running Android 5.0.2.

Thanks for a great program!

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

[Akonadi] [Bug 364114] moving a folder within one maildir resource is extremely slow and inefficient

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[digikam] [Bug 363697] Album visible even after deletion

[via KDE Bugzilla]

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

--- Comment #11 from caulier.gil...@gmail.com ---
Swati,

A patch will be welcome here to be able to test this solution, if Johannes is
favorable to use this way of course...

Also, what's about the bug #237878 ?

Gilles Caulier

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

[digikam] [Bug 363697] Album visible even after deletion

[via KDE Bugzilla]

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

--- Comment #10 from swatilodh...@gmail.com ---
Johannes,

Your second solution seems to fit here. Temporary disabling referential
constraints might work 'cause we've parent-child tables. 

In the function makeStaleAlbum(), there's an update query which doesn't work.
(Reason why Albums table is not updated)
We could use:
//
SET FOREIGN_KEY_CHECKS = 0;
UPDATE.
SET FOREIGN_KEY_CHECKS = 1;
//
I think this should work...

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

[kdevelop] [Bug 364672] New: Loked on an initialization crash loop!

[Leozito via KDE Bugzilla]

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

Bug ID: 364672
   Summary: Loked on an initialization crash loop!
   Product: kdevelop
   Version: 4.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: independent.scient...@gmail.com

Application: kdevelop (4.7.3)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.7.0-rc3-1.g59af2d0-default x86_64
Distribution: "openSUSE Tumbleweed (20160619) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Just opened the editor and it's crashing every time. Did not change anything on
the editor last time it was opened successfuly.

The crash can be reproduced every time.

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

Thread 12 (Thread 0x7fbef39c1700 (LWP 3930)):
#0  0x7fbf0acde09f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbf0a9a6e0a in  () at /usr/lib64/libQtScript.so.4
#2  0x7fbf0a9a6e39 in  () at /usr/lib64/libQtScript.so.4
#3  0x7fbf0acd8474 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbf0d0803ed in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fbe72565700 (LWP 3931)):
#0  0x7fbf0d077a1d in poll () at /lib64/libc.so.6
#1  0x7fbf0728d186 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbf0728d28c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbf0d88382e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fbf0d851b8f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fbf0d851ef5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fbf0d7408d9 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fbf0d831973 in  () at /usr/lib64/libQtCore.so.4
#8  0x7fbf0d7431aa in  () at /usr/lib64/libQtCore.so.4
#9  0x7fbf0acd8474 in start_thread () at /lib64/libpthread.so.0
#10 0x7fbf0d0803ed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fbe71a28700 (LWP 3933)):
#0  0x7fbf0acde448 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbf0d7436f4 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7fbf0c0282ee in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0x2bafcb0) at
/usr/src/debug/kdevplatform-1.7.3/language/duchain/duchain.cpp:283
#3  0x7fbf0d7431aa in  () at /usr/lib64/libQtCore.so.4
#4  0x7fbf0acd8474 in start_thread () at /lib64/libpthread.so.0
#5  0x7fbf0d0803ed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fbe6bdb7700 (LWP 3934)):
#0  0x7fbf0d077a1d in poll () at /lib64/libc.so.6
#1  0x7fbf0728d186 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbf0728d28c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbf0d88382e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fbf0d851b8f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fbf0d851ef5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fbf0d7408d9 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fbf0d7431aa in  () at /usr/lib64/libQtCore.so.4
#8  0x7fbf0acd8474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbf0d0803ed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fbe5d4f4700 (LWP 3935)):
#0  0x7fbf0d077a1d in poll () at /lib64/libc.so.6
#1  0x7fbf0728d186 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbf0728d28c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbf0d88380e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7fbf0d851b8f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7fbf0d851ef5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fbf0d7408d9 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7fbf0d7431aa in  () at /usr/lib64/libQtCore.so.4
#8  0x7fbf0acd8474 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbf0d0803ed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fbe5ccf3700 (LWP 3936)):
#0  0x7fbf0d0790a3 in select () at /lib64/libc.so.6
#1  0x7fbf0d82de7a in  () at /usr/lib64/libQtCore.so.4
#2  0x7fbf0d7431aa in  () at /usr/lib64/libQtCore.so.4
#3  0x7fbf0acd8474 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbf0d0803ed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fbe4ce4b700 (LWP 3942)):
#0  0x7fbf0d077a1d in poll () at /lib64/libc.so.6
#1  0x7fbf0728d186 in  () at /usr/lib64/libglib-2.0.so.0
#2  

[kdevelop] [Bug 360707] KDevelop crashes during parsing a project when it is compiled with GCC 6.0

[fantaz via KDE Bugzilla]

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

fantaz  changed:

   What|Removed |Added

 CC||ski...@riteh.hr

--- Comment #19 from fantaz  ---
Please, 
Where on earth can one install/download version 4.7.4? Don't see it on
http://download.kde.org/stable/kdevelop/, nor it is in opensuse's tumbleweed
repo...

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