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

[Andreas Hartmetz via KDE Bugzilla]

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

--- Comment #11 from Andreas Hartmetz  ---
Note: sub-session support in the session manager is basically support for
activities. Session restore of activities has never worked well enough to be
useful for me.

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

[Baloo] [Bug 353342] Crash - mdb_txn_begin

[via KDE Bugzilla]

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

--- Comment #15 from andreas.sturmlech...@gmail.com ---
Created attachment 96073
  --> https://bugs.kde.org/attachment.cgi?id=96073=edit
plasmashell-20151214-070254.kcrash.txt

In that case I'll attach my backtrace from after upgrade to kde-frameworks-5.17
(I think it's related).

Please also note that I have baloo file search disabled.

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

[kio] [Bug 356662] dolphin 15.08 does not know the camera protocol

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|konq-b...@kde.org   |mar...@jet.franken.de
 CC||cf...@kde.org
  Component|kioslave|kamera

--- Comment #2 from Christoph Feck  ---
The kio-kamera slave was only recently ported to Qt5 and is now part of the KDE
Applications 15.12 release. Please check if this version works.

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

[plasmashell] [Bug 356428] Plasmashell crash when minimizing app and then hovering mouse over taskmanager

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE
 CC||mklape...@kde.org

--- Comment #2 from Martin Klapetek  ---
Thanks for the report

Could you please install debug package for libKF5Plasma and then
post an updated backtrace? Would help with pinpointing this bug.
If you get the updated backtrace, it's enough if you copy-paste just
the "Thread 1" or whichever has the "[KCrash Handler]" in it.

Thanks

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

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

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #12 from Leslie Zhai  ---
Hi Andreas, 

Thanks for your patch! I do not have Qt developer's account, so I could not +1
for your great job.
Hope Qt5.x will integrate your patch to fix the restore session relative issue.

About ksmserver session management improvement, as you said make it robust
http://marc.info/?l=kde-core-devel=144832700109449=1 is there someone else
to work together to make ksmserver better, make KDE5 better ;-)

Thanks again for your great job!

Regards,
Leslie Zhai

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

[klipper] [Bug 343519] Klipper systray widget is not closed automatically once a user has selected an item

[Ricardo J . Barberis via KDE Bugzilla]

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

Ricardo J. Barberis  changed:

   What|Removed |Added

 CC||ricardo.barbe...@gmail.com

--- Comment #6 from Ricardo J. Barberis  ---
I haven't used Plasma 5 so I'm probably not the best to judge it, but my vote
goes for closing klipper after selecting an entry.

While I agree that consistency is important, I think the principle of least
surprise is important too, especially when you're changing a behaviour that is
expected and maybe even part of muscular memory for many.

I'm a heavy user of klipper and I can see this being very annoying for my
workflow, since I'm mostly a keyboard person.

That said, I'm also a KDE/Plasma veteran user, so an option to change the
default (i.e., stay open) behavior is fine for me.

My €0.02

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

[valgrind] [Bug 356611] vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xC9 0x3 0x1D 0x0

[via KDE Bugzilla]

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

muell...@gmx.net changed:

   What|Removed |Added

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

--- Comment #1 from muell...@gmx.net ---
Ooops. Just found it now. Sorry.

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

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

[plasmashell] [Bug 356711] New: XembedSNIProxy prevents KWin from unredirecting fullscreen SDL2 apps

[Danni H via KDE Bugzilla]

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

Bug ID: 356711
   Summary: XembedSNIProxy prevents KWin from unredirecting
fullscreen SDL2 apps
   Product: plasmashell
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: XembedSNIProxy
  Assignee: plasma-b...@kde.org
  Reporter: dannihf...@fastmail.fm

I was trying to figure out why I was getting microstutters in some games after
upgrading to 5.5. I then toggled compositing a few times and at some point I
managed to get a black square to appear where Dropbox usually is in the system
tray. That I was in a fullscreen game and this window was trying to draw itself
above the game seemed suspicious. I killed xembedsniproxy and sure enough the
problem was resolved.

Reproducible: Always

Steps to Reproduce:
1. Ensure KWin is set to "Suspend compositor for full screen windows"
2. Ensure xembedsniproxy is running
3. Open an SDL2 app in fullscreen mode (example: latest version of Quakespasm)
4. Notice lots of microstuttering regardless of whether the in-game vsync is
enabled or disabled
5. Kill xembedsniproxy
6. Reopen the same SDL2 app and notice that it runs smoothly now.

Actual Results:  
Lots of microstutter, running without in-game vsync gives uneven framerate and
no tearing

Expected Results:  
In-game vsync off should give tearing, in-game vsync on should be butter smooth

I tried forcing xembedsniproxy to Keep Below in the KWin rules but no dice.

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

[plasmashell] [Bug 356707] New: Plama crashes without reason

[Chris Taylor via KDE Bugzilla]

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

Bug ID: 356707
   Summary: Plama crashes without reason
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: chrismar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-19-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Operating pc on multiple screens, watching youtube

- Unusual behavior I noticed:
the bar went missing and was redrawn

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

Thread 16 (Thread 0x7fa49c94f700 (LWP 2105)):
#0  0x7fa4abc0f8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa4afc56bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fa4afc5874f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fa49ec99a39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7fa4ac3022be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa4ab3f16aa in start_thread (arg=0x7fa49c94f700) at
pthread_create.c:333
#6  0x7fa4abc1aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fa49620e700 (LWP 2135)):
#0  0x7fa4abc0f8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa4a89bc1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa4a89bc2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa4ac53929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa4ac4df75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa4ac2fd3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa4aeb25f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa4ac3022be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa4ab3f16aa in start_thread (arg=0x7fa49620e700) at
pthread_create.c:333
#9  0x7fa4abc1aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fa48ae96700 (LWP 2149)):
#0  0x7fa4ac3b33a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa4ac536d29 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa4ac537295 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa4ac53867e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa4a89bb77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa4a89bc11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fa4a89bc2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fa4ac53929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa4ac4df75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa4ac2fd3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa4aeb25f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7fa4ac3022be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fa4ab3f16aa in start_thread (arg=0x7fa48ae96700) at
pthread_create.c:333
#13 0x7fa4abc1aeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fa483fff700 (LWP 2153)):
#0  0x7fa4ac537212 in QTimerInfoList::repairTimersIfNeeded() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa4ac5372a3 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa4ac53867e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa4a89bb77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa4a89bc11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa4a89bc2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fa4ac53929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa4ac4df75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa4ac2fd3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa4aeb25f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 

[kde] [Bug 356682] xdg-open url -- socket operation timed out error

[via KDE Bugzilla]

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

pnewc...@gmail.com changed:

   What|Removed |Added

Summary|xdg-open url - scoket   |xdg-open url -- socket
   |operation timed out error   |operation timed out error

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

[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

[andy via KDE Bugzilla]

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

--- Comment #33 from andy  ---
while I was  overstating in my criticism to windows 10, it is surely a very
complex system but it by far does not put the user in the center as kde4,
plasma5 does. The one dimensional structure of unity does leave no power to the
user wishes, you can take it or live it, like choosing between grey and grey. 
Very simple. The effort creating such a sophisticated system as kde4 and
plasma5 is far more higher and demands far more work. I remember as kde4 took
its baby steps, many people laughed about and criticised and left. KDE4 turned
out to be the best along with time, as  I held on to it because it still left
me so much freedom...  you are working on the best, most userfriendly desktop I
know so far, and the results are promissing even now the old and matured and
good xfce has not so much simplicity and beauty as plasma5 does, so keep on,
dont let discourage yourself building it.

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

[plasmashell] [Bug 354490] plasmashell Freezes Momentarily Then Notification Center Goes Crazy

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org

--- Comment #2 from Martin Klapetek  ---
In addition to the above, please also type "thread apply all bt" after "bt" and
post both outputs.

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

[plasmashell] [Bug 356631] Plasma crash

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---


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

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

[valgrind] [Bug 328357] vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xEF 0x3 0x5 0x0

[via KDE Bugzilla]

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

muell...@gmx.net changed:

   What|Removed |Added

 CC||muell...@gmx.net

--- Comment #7 from muell...@gmx.net ---
*** Bug 356611 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 350060] Device notification and use

[Max Sydorenko via KDE Bugzilla]

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

Max Sydorenko  changed:

   What|Removed |Added

 CC||maxim.starga...@gmail.com

--- Comment #4 from Max Sydorenko  ---
I want to confirm this issue with Plasma 5.5.
Also, probably related problem. Sometimes, after notification popped, I can not
open the menu by simply clicking on the icon. When it happens I have to click
first on Battery and Brightness icon (for example) to "unfreeze" Device
notification.

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

[muon] [Bug 356709] New: You should change the way addons/plugin selection list looks

[via KDE Bugzilla]

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

Bug ID: 356709
   Summary: You should change the way addons/plugin selection list
looks
   Product: muon
   Version: 5.4.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: madpootismaster5...@gmail.com
CC: echidna...@kubuntu.org, sit...@kde.org

Whenever I go to install a new program, I see the list of addons. Let's take
Geany for example. When I go to the Geany install page, I see the list of
addons I can choose to install. (THERE ARE A Lot..) But the checklist so so
crowded! Its hard to distinguish which addon name leads to the correct
checkbox. It takes a while to figure out which is which.

Reproducible: Always




I really think you should change it to where the text in italics comes right
after the addon/plugin name and not in a separate line.

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #11 from Thomas Lübking  ---
To gain less flexibility?
Despite Martins concern, the scripting overhead is neglectable - switching
fullscreen state doesn't happen that often (and far more expensive things than
a string comparism happen in that moment anyway - let alone the plasmashell
overhead when you suspend the compositor and it reloads its theme...)

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

[kdenlive] [Bug 356661] New: Visual jitter in statusbar when move cursor over timeline

[Egor via KDE Bugzilla]

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

Bug ID: 356661
   Summary: Visual jitter in statusbar when move cursor over
timeline
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: e.vakhromt...@gmail.com

Proportional font used fore "timstamps" on status bar provides visual jitter.
Example video:
https://dl.dropboxusercontent.com/u/59794362/kdenlive-bugs/timestamp-jitter/kdenlive-timestamp-jitter.mp4

Reproducible: Always

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

[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup

[Leszek Lesner via KDE Bugzilla]

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

--- Comment #37 from Leszek Lesner  ---
(In reply to Weng Xuetian from comment #36)
> ...
> 
> diff --git a/applets/systemtray/plugin/host.cpp
> b/applets/systemtray/plugin/host.cpp
> index 27ca227..61e8705 100644
> --- a/applets/systemtray/plugin/host.cpp
> +++ b/applets/systemtray/plugin/host.cpp
> @@ -99,7 +99,7 @@ Host::Host(QObject* parent) :
>  QObject(parent),
>  d(new HostPrivate(this))
>  {
> -QTimer::singleShot(0, this, SLOT(init()));
> +QTimer::singleShot(0, this, ::init);
>  }
> 

You are my personal hero man ;) 
Yes indeed reverting that patch fixes the issue for me too. 
So changing from Plasma 5.5 defaults
> QTimer::singleShot(0, this, ::init);
to 
> QTimer::singleShot(0, this, SLOT(init()));
and I get my plasma-pa icon on every boot :)

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

[krita] [Bug 356592] crash when menu "settings -> configure krita" (win64)

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #6 from Boudewijn Rempt  ---
Probably not, though Krita is built on Qt, which uses freetype too for font
rendering, so there might be something weird going on.

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

[KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason

[bzi]

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

b...@samadhi-institute.org  changed:

   What|Removed |Added

 CC||samadhi.0...@gmail.com

--- Comment #2 from b...@samadhi-institute.org  ---
It happens very frequently with nvidea 

Dez 12 12:00:19 osiris org.kde.KScreen[9196]: kscreen: Primary output changed
from KScreen::Output(Id: 176 , Name: "HDMI-1" ) ( "HDMI-1" ) to KScreen

... and so on

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

[plasmashell] [Bug 356668] New: Plasma crashes when resuming from suspend with different screen

[Massimiliano via KDE Bugzilla]

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

Bug ID: 356668
   Summary: Plasma crashes when resuming from suspend with
different screen
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: leoni.massimilia...@gmail.com
CC: plasma-b...@kde.org

I use my laptop with an external monitor through DisplayPort, and I often
suspend it and unplug the monitor to go somewhere, or the other way around.
When I later resume from this situation, I get bug report assistants for
crashes in kdeinit and plasma5. 

Most of the times the whole shell crashed and I am thrown back to login screen
[sddm].

This worked fine with KDE4.

Reproducible: Always

Steps to Reproduce:
1. Connect external monitor, configured as primary
2. Suspend
3. Unplug monitor
4. Resume

Actual Results:  
Plasma crashes and eventually takes me back to login

Expected Results:  
Plasma detects screen configuration changes and resumes on the correct screen.

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

[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory

[René Krell via KDE Bugzilla]

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

--- Comment #1 from René Krell  ---
Created attachment 96058
  --> https://bugs.kde.org/attachment.cgi?id=96058=edit
cat /proc/`pidof plasmashell`/smaps (output)

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

[plasmashell] [Bug 356670] New: Plasma shell memory leak let subsequent applications run out of memory

[René Krell via KDE Bugzilla]

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

Bug ID: 356670
   Summary: Plasma shell memory leak let subsequent applications
run out of memory
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: renda.kr...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

After the most recent system updates I encounter a heavy memory leak which lets
applications like Chromium, Chrome, Firefox, Maven builds etc. run out of
memory. It is jard for me to analyze, but I try to collect the necessary
information.

OS: OpenSUSE Tumbleweed 20151209
uname -a: Linux rkrell 4.3.0-2-default #1 SMP PREEMPT Sat Nov 14 16:19:19 UTC
2015 (734b32c) x86_64 x86_64 x86_64 GNU/Linux

I opened the Gnome System Monitor to get an idea of a suspicious application -
the most common one for all failure situations which consumes most memory is

plasmashell:
- Virtual Memory: 10 GB
- Resident Memory: 435,2 MB
- Shared Memory 204,4 MB
- X-Server memory: 2,3 MB

followed by baloo:
- Virtual Memory: 5,3 GB
- Resident Memory: 88,5 MB
- Shared Memory 17,2 MB
- X-Server memory: 0 kBytes

Several weeks ago with previous KDE versions this didn't happen.
I'll append several output I get from my system, if you're interested please
tell me what else to provide, I'm not sure.


Reproducible: Always

Steps to Reproduce:
1. Logon to KDE
2. Open Chromium/Chrome (or whatever app usually consuming a bit more memory)

Actual Results:  
Most of the tabs of about 20 open tabs don't open.

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

[kipiplugins] [Bug 356673] New: MediaWiki export doesn't work

[Sergei S . Rublёv via KDE Bugzilla]

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

Bug ID: 356673
   Summary: MediaWiki export doesn't work
   Product: kipiplugins
   Version: 4.14.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: MediaWiki
  Assignee: kde-imag...@kde.org
  Reporter: kde-b...@ssr.host.ru

I cannot upload any file to Wikimedia Commons with KIPI "Export to MediaWiki"
plugin.

In the past, this worked. From some time, this stopped working. Relatively long
ago, several months. I tried this in several Linux installations, the same
everywhere — this time in latest Fedora with latest updates.

I pick a file, successfully login to Commons in the plugin, fill out forms.
When I click "Upload", it starts "uploading", but eternally sticks at 0%, never
upload. I have to interrupt this, and DigiKam status bar then sticks at
"Aborting" (with 0%).

Reproducible: Always

Steps to Reproduce:
1. Pick a file, start the plugin, login to Commons
2. Fill out basical forms (maybe not all) 
3. Press upload button

Actual Results:  
No upload

Expected Results:  
Upload to Commons

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

[plasmashell] [Bug 356660] New: Notification pop-up from left side sometimes

[via KDE Bugzilla]

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

Bug ID: 356660
   Summary: Notification pop-up from left side sometimes
   Product: plasmashell
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: hkz85825...@gmail.com
CC: plasma-b...@kde.org

Notifications usually pops on the bottom-right, but since 5.5.0, it sometimes
come from bottom-right.

Reproducible: Sometimes

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[via KDE Bugzilla]

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

--- Comment #56 from ric...@nakts.net ---
another thing that seems to be lost - ability to set locale to a region (to get
the defaults for all the settings) and override interface language. pretty much
all of the previously available overrides were very useful.

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

[plasmashell] [Bug 356660] Notification pop-up from left side sometimes

[Sudhir Khanger via KDE Bugzilla]

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

Sudhir Khanger  changed:

   What|Removed |Added

 CC||sud...@sudhirkhanger.com

--- Comment #1 from Sudhir Khanger  ---
Created attachment 96062
  --> https://bugs.kde.org/attachment.cgi?id=96062=edit
notification on bottom left

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

[plasmashell] [Bug 356656] All KDE Plasma 5.5.0 sometimes freeze after press-and-holding folder widget

[via KDE Bugzilla]

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

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
After restarting plasmashell, Folder widget no longer exist

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

[phonon-backend-gstreamer] [Bug 356527] Plasma Crash

[Harald Sitter via KDE Bugzilla]

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

Harald Sitter  changed:

   What|Removed |Added

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

--- Comment #2 from Harald Sitter  ---
Actually most likely you had some bad third party repository. The plasma crash
you had was pretty much the result of GStreamer trying to load an incompatible
plugin which made it blow up. Why or how it was incompatible I unfortunately
can't say from the backtrace.

If a new Fedora 23 works again I think we're best served simply forgetting
about this :)

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

[i18n] [Bug 356630] [Gwenview] wrong German translation for metadata/lens

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

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

--- Comment #1 from Frederik Schwarzer  ---
SVN commit 1447264 by schwarzer:

Translation fix.

Lens: Linse -> Objektiv


 M  +44 -40digikam.po  


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

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

[plasmashell] [Bug 356415] Multiple clicks are necessary in order to activate panel elements

[Christoph Erhardt via KDE Bugzilla]

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

Christoph Erhardt  changed:

   What|Removed |Added

 CC||k...@sicherha.de

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

[plasmashell] [Bug 356656] All KDE Plasma 5.5.0 sometimes freeze after press-and-holding folder widget

[via KDE Bugzilla]

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

opensuse.lietuviu.ka...@gmail.com changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[via KDE Bugzilla]

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

--- Comment #14 from jeremy9...@gmail.com ---
I really don't understand. You already do some kind of detection for the
"unredirected fullscreen window" feature...

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

[konsole] [Bug 356665] New: Konsole crash when connecting bluetooth keyboard

[Victor Mataré via KDE Bugzilla]

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

Bug ID: 356665
   Summary: Konsole crash when connecting bluetooth keyboard
   Product: konsole
   Version: 15.08.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: mat...@lih.rwth-aachen.de

Application: konsole (15.08.0)

Qt Version: 5.5.1
Operating System: Linux 4.2.6-gentoo_wald x86_64
Distribution: "Gentoo Base System release 2.2"

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

After resuming from suspend I connected my bluetooth keyboard and konsole
immediately crashed. Window was not even visible at the time.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb26ab59880 (LWP 3916))]

Thread 2 (Thread 0x7fb268daf700 (LWP 3917)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x003018a99280 in QBasicMutex::lockInternal() () from
/usr/lib64/libQt5Core.so.5
#2  0x7fb26a486c99 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#3  0x003018aa04f2 in ?? () from /usr/lib64/libQt5Core.so.5
#4  0x003000807444 in start_thread (arg=0x7fb268daf700) at
pthread_create.c:334
#5  0x0030004e96ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb26ab59880 (LWP 3916)):
[KCrash Handler]
#6  0x003000433477 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x0030004348ca in __GI_abort () at abort.c:89
#8  0x003000472728 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x3000566ba8 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x003000478016 in malloc_printerr (action=3, str=0x3000562dcd
"corrupted double-linked list", ptr=, ar_ptr=) at
malloc.c:5000
#10 0x003000479046 in _int_free (av=0x7fb26420, p=0x7fb2640059f0,
have_lock=0) at malloc.c:3999
#11 0x7fb26a486748 in QXcbConnection::processXcbEvents() () from
/usr/lib64/libQt5XcbQpa.so.5
#12 0x003018c7694a in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#13 0x7fb2724ac69c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#14 0x7fb2724b1b10 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#15 0x003018c4d65d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#16 0x003018c50423 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#17 0x003018c9afb3 in ?? () from /usr/lib64/libQt5Core.so.5
#18 0x7fb26e9d1c9d in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#19 0x7fb26e9d1f80 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x7fb26e9d202c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#21 0x003018c9b027 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#22 0x003018c4c27a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#23 0x003018c5364c in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#24 0x7fb274f990eb in kdemain () from /usr/lib64/libkdeinit5_konsole.so
#25 0x003000420620 in __libc_start_main (main=0x400790 , argc=1,
argv=0x7fffe74ab848, init=, fini=,
rtld_fini=, stack_end=0x7fffe74ab838) at libc-start.c:289
#26 0x004007c9 in _start ()

Possible duplicates by query: bug 356068, bug 355645, bug 353906, bug 352449,
bug 351908.

Reported using DrKonqi

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[via KDE Bugzilla]

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

--- Comment #16 from jeremy9...@gmail.com ---
> What exactly is your exact concern about using the script system which was 
> especially created to allow flexible and custom manipulation of the flow 
> control in kwin?

I don't have any concern about using the script but, as I didn't even know that
the script existed, I think that only a very few people will find it and use it
whereas a built in feature is more easily discoverable.

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

[kmail2] [Bug 356657] Notification popups not readable

[OlafLostViking via KDE Bugzilla]

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

--- Comment #1 from OlafLostViking  ---
Just to show how this can be a problem: the reason for me not being able to
send an email was that the new KMail uses kwallet5 which didn't provide the
correct password. But as KMail's popup told me my problem is the authtication
*method* (PLAIN not supported...) and, as written above, the message from the
server itself was not readable, I didn't expect any problems with my
credentials. After changing the password manually sending emails works again.

Oh, and the popup is shown "anywhere" but not near or even in the notification
area of Plasma. But that could also be a KWin or Plasma problem (as they both
are struggeling a lot with multiple screens). I'm just mentioning it as this
could lead to more people not even ever realising there was a message
displayed. As this is an error message a modal dialog seems more appropriate.
But that's another story ;-)

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

[krita] [Bug 356669] New: random lines appear as you draw

[Avelino De Sabbata via KDE Bugzilla]

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

Bug ID: 356669
   Summary: random lines appear as you draw
   Product: krita
   Version: 2.9.10
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: avelinodesabb...@alice.it

Hello,
This is a problem that I encounter for a long time, but it's hard to describe,
and why I never reported: I try with the help of some of the screen grab.
It seems to have already been reported in bug 355665, but I use a Wacom Intuos
5 pro tablet.
While using the tool "Freehand Brush Tool" to draw, which happens to be
randomly inserted lines longer or shorter variable directions with the brush in
use. In the attached pictures it is highlighted the problem described.
The phenomenon it happened also with other brushes, but in tests I did for you,
I could not repeat it. I use what ever preset Ave_Pencil_4B (brush I modified
from a standard) but I do not think the problem is this brush (which I
enclose), although in fact it is with it that the problem occurs more often. In
tests made for you the problem manifested itself with the preset Ink_Gpen.
In the image "ave_pencil_4b.png" the fact is very clear and it happened while I
was being typed the name of the brush.

Download zip archive with grabs from my dropbox
"https://www.dropbox.com/s/joz3olgfofwxfoj/Files_from_bug.zip?dl=0;

Thank you.

Reproducible: Sometimes

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

[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory

[René Krell via KDE Bugzilla]

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

--- Comment #3 from René Krell  ---
KDE versions:
- KDE Releases Frameworks: 5.16.0
- KDE Releases Applications 15.08.3
- Plasma: 5.4.3

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

[Akonadi] [Bug 356677] No backgrounds on notes

[Olivier Churlaud via KDE Bugzilla]

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

Olivier Churlaud  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |MOVED

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

[kdeplasma-addons] [Bug 356679] New: No background on notes

[Olivier Churlaud via KDE Bugzilla]

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

Bug ID: 356679
   Summary: No background on notes
   Product: kdeplasma-addons
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: notes
  Assignee: plasma-b...@kde.org
  Reporter: oliv...@churlaud.com

Since the last upgrade of plasma, the notes don't have any background.

It's rather hard to read and seems to be directly written on the desktop
background.

Reproducible: Always

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

[solid] [Bug 341041] Battery Monitor flashing in taskbar

[via KDE Bugzilla]

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

slartibar...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from slartibar...@gmail.com ---
does not appear any more in 5.5. closing

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[via KDE Bugzilla]

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

--- Comment #12 from jeremy9...@gmail.com ---
(In reply to Thomas Lübking from comment #11)
> To gain less flexibility?

Why ? Having a fullscreen matching feature built in Kwin don't avoid the
possible use of the script it one need it ?

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

[muon] [Bug 356568] Outdated notifier metadata.desktop

[Harald Sitter via KDE Bugzilla]

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

Harald Sitter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Harald Sitter  ---
Please hold on to https://techbase.kde.org/Contribute/Send_Patches next time.
Patches easily get lost in bug reports.

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

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Nick Cross via KDE Bugzilla]

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[plasmashell] [Bug 356666] New: Letters are randomly missing in Plasma notifications

[Roman Odaisky via KDE Bugzilla]

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

Bug ID: 35
   Summary: Letters are randomly missing in Plasma notifications
   Product: plasmashell
   Version: 5.4.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: to.roma.from.kde...@qwertty.com
CC: plasma-b...@kde.org

For me, about half the time Plasma notifications in the corner of the screen
are shown with half the letters randomly missing. Just blank spaces. For
example, see http://qwertty.com/tmp/kde-notifications-missing-letters.png : it
was supposed to say “Kopete: Connection trouble with Jabber...” but instead I
got “K p   : C n   c  r  bl  wi h Jabb r ...”.

Googling suggests this isn’t limited to Plasma notifications
(https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1510959), possibly
being a general Qt issue instead, but for me notifications are the only place
where the problem occurs.

Reproducible: Sometimes

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

[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 CC||oliv...@churlaud.com

--- Comment #13 from Bhushan Shah  ---
*** Bug 356679 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 356680] Faulty font rendering in Calendar

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

 CC||rapiteanu.cata...@gmail.com

--- Comment #1 from Viorel-Cătălin Răpițeanu  ---
Created attachment 96061
  --> https://bugs.kde.org/attachment.cgi?id=96061=edit
Faulty font rendering in Calendar popup

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

[plasmashell] [Bug 356680] New: Faulty font rendering in Calendar

[Viorel-Cătălin Răpițeanu via KDE Bugzilla]

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

Bug ID: 356680
   Summary: Faulty font rendering in Calendar
   Product: plasmashell
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Calendar
  Assignee: mklape...@kde.org
  Reporter: rapiteanu.cata...@gmail.com
CC: plasma-b...@kde.org

The numbers 6 and 7 are not rendered in the calendar created from the clock
popup.

Reproducible: Always

Steps to Reproduce:
1. Open calendar popup.


Actual Results:  
The numbers 6 and 7 are not rendered in the calendar.

Expected Results:  
All the calendar numbers should be correctly rendered.

- Attached screenshot of the described problem.

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

[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information

[Christoph Erhardt via KDE Bugzilla]

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

Christoph Erhardt  changed:

   What|Removed |Added

 CC||k...@sicherha.de

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

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[systemsettings] [Bug 356444] Fonts on the rigth side of the font manager appear without smoothed edges

[via KDE Bugzilla]

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

--- Comment #1 from slartibar...@gmail.com ---
could this be in virtualbox and vmware only?
I tested with physical hardware (intel laptop, intel graphics) and there it's
ok.
The error can still be seen in the virtualized environments.

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[via KDE Bugzilla]

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

--- Comment #10 from jeremy9...@gmail.com ---
What I mean is that it should be a built in feature of Kwin ;)

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

[kio] [Bug 356662] New: dolphin 15.08 does not know the camera protocol

[Éric Brunet via KDE Bugzilla]

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

Bug ID: 356662
   Summary: dolphin 15.08 does not know the camera protocol
   Product: kio
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kioslave
  Assignee: konq-b...@kde.org
  Reporter: eric.bru...@lps.ens.fr

When plugging my fujifilm X10 camera, which uses the PTP protocol, in a fedora
23 with kde, nothing happens. When I plug the same camera in a fedora 21, the
device notifier pops up and gives me some options. The fact that nothing
happens on the fedora 23 is an annoying bug by itself, but it is not really the
bug I want to report now.

On the fedora 21 machine, I can browse and modify the files on the camera from
within dolphin by entering the url "camera:/". On fedora 23, entering
"camera:/" gives me an "invalid protocol" error message.

Of course, fedora 21 uses dolphin 15.04.0 based on kde 4.14.11, while fedora 23
uses dolphin 15.08.1 based on kde frameworks 5.16.0. I presume that the camera
ioslave was not ported to kde 5.

As a matter of fact, if I fire good old konqueror on the fedora 23 computer, I
can access the filesystem on the camera by entering the "camera:/" url.
konqueror is still a kde 4 application.

This is a very serious regression. In 2015, one expects to have a window
popping up when plugging a camera and having no trouble browsing the files on
it. Is there any way to make dolphin5 use the kde4 kioslave ? Is there a plan
porting the kioslave to kde5 ?

For information, the relevant output from "solid-hardware5 list details" when
the camera is plugged:

udi =
'/org/kde/solid/udev/sys/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3.2'
  parent = '/org/kde/solid/udev'  (string)
  vendor = '04cb'  (string)
  product = 'USB PTP Camera'  (string)
  description = 'Appareil photo'  (string)
  Block.major = 189  (0xbd)  (int)
  Block.minor = 8  (0x8)  (int)
  Block.device = '/dev/bus/usb/001/009'  (string)
  Camera.supportedProtocols = {'ptp'}  (string list)
  Camera.supportedDrivers = {'gphoto'}  (string list)



Reproducible: Always

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

[frameworks-ktexteditor] [Bug 356585] adding menu as submenu (too?) leads to repeated "InsertNative: item is already in menu" errors

[RJVB via KDE Bugzilla]

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

--- Comment #1 from RJVB  ---
As an additional observation:

Running kate5 on OS X using the XCB plugin is possible even without all
X11-specific code included. It may not make much sense, but it does add an
interesting observation:
the application doesn't get a menubar.

Regular/simple Qt applications will get a window-based menubar instead of the
Mac-style menubar when run with the XCB QPA; if that doesn't happen that often
means that Qt::AA_DontUseNativeMenuBar is set explicitly (normally the platform
plugin does that).

I cannot find a trace of setting AA_DontUseNativeMenuBar in any of the KF5
frameworks (or Kate' s code itself), but when I set that attribute in Kate's
kdemain function something else happens. The application gets TWO menubars. And
that leads to many more of the above error messages, concerning other items.

I think that lends a lot of support to my hypothesis re: adding QWidgetAction
to multiple menus.

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

[kwin] [Bug 356600] OSD desktop switch animation text could be bigger (and configurable)

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #4 from Thomas Lübking  ---
> I agree that the current font size is too small to read at a glance.
Which would be my concern as well.
I don't think there's a global OSD font, but the item isn't sufficiently "in
your face" (and otherwise it hardly makes sense and you'd turn it off entirely
- as I personally do, I can see the current desktop in the panel)
I don't even share the size concerns given the layouted variant takes *much*
more space.

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

[plasma-pa] [Bug 356605] Audio applet not visible, only empty space with no reaction to mouse

[Michael Davies via KDE Bugzilla]

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

Michael Davies  changed:

   What|Removed |Added

 CC||michaeld2...@gmail.com

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

[plasma-nm] [Bug 356622] Cannot change the group in the login form, and specifying it in the config results in not showing the login form (openconnect)

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/plas
   ||ma-nm/c004d3563a08ed9519be2
   ||0c98861999ea72faa42
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Grulich  ---
Git commit c004d3563a08ed9519be20c98861999ea72faa42 by Jan Grulich.
Committed on 14/12/2015 at 09:18.
Pushed by grulich into branch 'master'.

Fix openconnect dialog

Previous patch removing "Show passwords" checkbox changed layout order and
we forgot to address that.

Patch from Simon Munton
Related: bug 356587

M  +3-19   vpn/openconnect/openconnectauth.cpp
M  +0-1vpn/openconnect/openconnectauth.h

http://commits.kde.org/plasma-nm/c004d3563a08ed9519be20c98861999ea72faa42

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

[plasma-nm] [Bug 356587] Connecting to openconnect vpn fails

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas
   |ma-nm/c004d3563a08ed9519be2 |ma-nm/28c4b2e1b868427201cec
   |0c98861999ea72faa42 |b6d01cdb45ebfd157a0

--- Comment #4 from Jan Grulich  ---
Git commit 28c4b2e1b868427201cecb6d01cdb45ebfd157a0 by Jan Grulich.
Committed on 14/12/2015 at 09:18.
Pushed by grulich into branch 'Plasma/5.5'.

Fix openconnect dialog

Previous patch removing "Show passwords" checkbox changed layout order and
we forgot to address that.

Patch from Simon Munton
Related: bug 356622

M  +3-19   vpn/openconnect/openconnectauth.cpp
M  +0-1vpn/openconnect/openconnectauth.h

http://commits.kde.org/plasma-nm/28c4b2e1b868427201cecb6d01cdb45ebfd157a0

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

[plasma-nm] [Bug 356622] Cannot change the group in the login form, and specifying it in the config results in not showing the login form (openconnect)

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/plas
   |ma-nm/c004d3563a08ed9519be2 |ma-nm/28c4b2e1b868427201cec
   |0c98861999ea72faa42 |b6d01cdb45ebfd157a0

--- Comment #2 from Jan Grulich  ---
Git commit 28c4b2e1b868427201cecb6d01cdb45ebfd157a0 by Jan Grulich.
Committed on 14/12/2015 at 09:18.
Pushed by grulich into branch 'Plasma/5.5'.

Fix openconnect dialog

Previous patch removing "Show passwords" checkbox changed layout order and
we forgot to address that.

Patch from Simon Munton
Related: bug 356587

M  +3-19   vpn/openconnect/openconnectauth.cpp
M  +0-1vpn/openconnect/openconnectauth.h

http://commits.kde.org/plasma-nm/28c4b2e1b868427201cecb6d01cdb45ebfd157a0

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

[plasma-nm] [Bug 356587] Connecting to openconnect vpn fails

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/plas
   ||ma-nm/c004d3563a08ed9519be2
   ||0c98861999ea72faa42

--- Comment #3 from Jan Grulich  ---
Git commit c004d3563a08ed9519be20c98861999ea72faa42 by Jan Grulich.
Committed on 14/12/2015 at 09:18.
Pushed by grulich into branch 'master'.

Fix openconnect dialog

Previous patch removing "Show passwords" checkbox changed layout order and
we forgot to address that.

Patch from Simon Munton
Related: bug 356622

M  +3-19   vpn/openconnect/openconnectauth.cpp
M  +0-1vpn/openconnect/openconnectauth.h

http://commits.kde.org/plasma-nm/c004d3563a08ed9519be20c98861999ea72faa42

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

[kmail2] [Bug 356657] New: Notification popups not readable

[OlafLostViking via KDE Bugzilla]

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

Bug ID: 356657
   Summary: Notification popups not readable
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

[This is for KMail 5.0.3, which is not selectable in the Version drop down.]

After updating to *5, KMail can no longer send out mails. I guess another
configuration setting wasn't ported correctly. But the notification popup,
which shows the server response on error, is a) too small to show the whole
message (only the text telling me that the following - not visible - message
was sent by the server is readable), b) disappears too fast/cannot be pinned to
the foreground or reread in the notification area of plasma and c) cannot be
logged to a file (I tried to log the notification of KMail and the SendLater
agent into a logfile to be able to read the message, but no file is created at
the given path).

Reproducible: Always

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

[rekonq] [Bug 356663] New: Rekonq crashes on clicking on link to RPM file

[via KDE Bugzilla]

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

Bug ID: 356663
   Summary: Rekonq crashes on clicking on link to RPM file
   Product: rekonq
   Version: 2.4.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: adj...@gmail.com
  Reporter: p...@kc.rr.com

Application: rekonq (2.4.2)
KDE Platform Version: 4.14.14
Qt Version: 4.8.6
Operating System: Linux 4.3.2-1.1 x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
On the opensuse repository site, click on a click of a (src) rpm file in order
to download it. The crash happens immediately and always.

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7efbe2908700 (LWP 10238)):
#0  0x7efbf651e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7efbfb3f6eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7efbfb3f6ee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7efbe15cf700 (LWP 10239)):
#0  0x7efbf651e428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7efbf5be5084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7efbf5bd8bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7efbf5be4bbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7efbe0dce700 (LWP 10240)):
#0  0x7efbf651e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7efbfb169b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7efbfb41ea06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7efbdbb60700 (LWP 10244)):
#0  0x7efbf651e07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7efbfa91a1cb in WebCore::IconDatabase::syncThreadMainLoop() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7efbfa91a3b4 in WebCore::IconDatabase::iconDatabaseSyncThread() () at
/usr/lib64/libQtWebKit.so.4
#3  0x7efbfb41ea06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#4  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7efbdb240700 (LWP 10245)):
#0  0x7efbf2b02344 in g_mutex_unlock () at
/opt/gnome/lib64/libglib-2.0.so.0
#1  0x7efbf2abfb0e in g_main_context_check () at
/opt/gnome/lib64/libglib-2.0.so.0
#2  0x7efbf2ac00a8 in  () at /opt/gnome/lib64/libglib-2.0.so.0
#3  0x7efbf2ac020c in g_main_context_iteration () at
/opt/gnome/lib64/libglib-2.0.so.0
#4  0x7efbf5d12fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7efbf5ce4d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7efbf5ce5045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7efbf5be24df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7efbf5be4bbf in  () at /usr/lib64/libQtCore.so.4
#9  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7efb994e2700 (LWP 10253)):
#0  0x7efbf651e428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7efbf5be5084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7efbf5bd8bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7efbf5be4bbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7efb98ce1700 (LWP 10254)):
#0  0x7efbf651e428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7efbf5be5084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7efbf5bd8bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7efbf5be4bbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7efbf65184a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7efbf500fbad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7efb7a041700 (LWP 10264)):
#0  0x7efbf500725d in poll () at /lib64/libc.so.6
#1  0x7efbf2ac0104 in  () at 

[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View

[Cyril Brosch via KDE Bugzilla]

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

--- Comment #6 from Cyril Brosch  ---
It is extremely hard to reproduce, for me it seems to happen simply from time
to time. 
I've just tested many copy situations, and when I finally got the error (I
deleted a folder, and then copied another folder from the same directory), I
could not reproduce it later after restart of dolphin, doing exactly the same
actions.

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

[Akonadi] [Bug 356677] New: No backgrounds on notes

[Olivier Churlaud via KDE Bugzilla]

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

Bug ID: 356677
   Summary: No backgrounds on notes
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: oliv...@churlaud.com

Since the last big upgrade (I'm now on plasma 5.5 and Akonadi 5.0.51) the notes
don't have any background.

It's rather hard to read and seems to be directly written on the desktop
background.



Reproducible: Always

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

[valgrind] [Bug 356678] New: unhandled arm64-linux syscall: 232 (mincore)

[Роман Донченко via KDE Bugzilla]

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

Bug ID: 356678
   Summary: unhandled arm64-linux syscall: 232 (mincore)
   Product: valgrind
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: d...@corrigendum.ru

$ valgrind --version
valgrind-3.11.0

$ uname -p
aarch64

$ cat test.c
#include 
#include 

int main() {
  unsigned char c;
  mincore(0, 1, );
}

$ gcc test.c

$ valgrind ./a.out
==10743== Memcheck, a memory error detector
==10743== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10743== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==10743== Command: ./a.out
==10743== 
--10743-- WARNING: unhandled arm64-linux syscall: 232
--10743-- You may be able to write your own handler.
--10743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--10743-- Nevertheless we consider this a bug.  Please report
--10743-- it at http://valgrind.org/support/bug_reports.html.
==10743== 
==10743== HEAP SUMMARY:
==10743== in use at exit: 0 bytes in 0 blocks
==10743==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==10743== 
==10743== All heap blocks were freed -- no leaks are possible
==10743== 
==10743== For counts of detected and suppressed errors, rerun with: -v
==10743== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

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

[plasmashell] [Bug 356653] When notification appears for first time, it appears twice

[via KDE Bugzilla]

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

--- Comment #3 from opensuse.lietuviu.ka...@gmail.com ---
Created attachment 96076
  --> https://bugs.kde.org/attachment.cgi?id=96076=edit
after `kquitapp5 plasmashell && plasmashell`: from checking for package updates

Log printed very fast and a lot of lines, I don't know exact moment of
appearing, so I attach log since checking for updates.

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

[digikam] [Bug 353789] Add new tool to apply Lut3D on image [patch]

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #11 from Maik Qualmann  ---
Git commit 537d7132117c804acc502f898ea95e588c20b20d by Maik Qualmann.
Committed on 15/12/2015 at 06:58.
Pushed by mqualmann into branch 'master'.

move Lut3D filter to the ColorFX filters

M  +0-1imageplugins/color/CMakeLists.txt
M  +1-2imageplugins/color/digikamimageplugin_color_ui.rc
M  +0-14   imageplugins/color/imageplugin_color.cpp
M  +0-1imageplugins/color/imageplugin_color.h
D  +0-201  imageplugins/color/lut3dtool.cpp
D  +0-75   imageplugins/color/lut3dtool.h
M  +11   -1imageplugins/filters/colorfxtool.cpp
M  +1-0imageplugins/filters/colorfxtool.h
M  +0-3libs/dimg/CMakeLists.txt
M  +0-3libs/dimg/filters/dimgfiltermanager.cpp
M  +270  -4libs/dimg/filters/fx/colorfxfilter.cpp
M  +15   -8libs/dimg/filters/fx/colorfxfilter.h
M  +171  -27   libs/dimg/filters/fx/colorfxsettings.cpp
M  +5-1libs/dimg/filters/fx/colorfxsettings.h
D  +0-64   libs/dimg/filters/lut3d/lut3dcontainer.cpp
D  +0-60   libs/dimg/filters/lut3d/lut3dcontainer.h
D  +0-324  libs/dimg/filters/lut3d/lut3dfilter.cpp
D  +0-94   libs/dimg/filters/lut3d/lut3dfilter.h
D  +0-234  libs/dimg/filters/lut3d/lut3dsettings.cpp
D  +0-77   libs/dimg/filters/lut3d/lut3dsettings.h
M  +0-1utilities/queuemanager/CMakeLists.txt
D  +0-126  utilities/queuemanager/basetools/color/lut3d.cpp
D  +0-72   utilities/queuemanager/basetools/color/lut3d.h
M  +11   -0utilities/queuemanager/basetools/filters/colorfx.cpp
M  +0-2utilities/queuemanager/manager/batchtoolsmanager.cpp

http://commits.kde.org/digikam/537d7132117c804acc502f898ea95e588c20b20d

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

[krita] [Bug 356256] [Krita animation beta] Copying frame offsets the image to original position

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/call |http://commits.kde.org/krit
   |igra/bc16a275413791dae90466 |a/da7dbfc1f8eacd4b8075251ee
   |a22c3cebae44ee81c9  |245e287af3551ec

--- Comment #2 from Dmitry Kazakov  ---
Git commit da7dbfc1f8eacd4b8075251ee245e287af3551ec by Dmitry Kazakov.
Committed on 14/12/2015 at 15:28.
Pushed by dkazakov into branch 'master'.

Fix initialization of the offset of the frame when it is duplicated

M  +4-2krita/image/kis_paint_device.cc

http://commits.kde.org/krita/da7dbfc1f8eacd4b8075251ee245e287af3551ec

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

[kwin] [Bug 356480] system crashes on startup , screen freezing , not recovery

[eloy via KDE Bugzilla]

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

--- Comment #3 from eloy  ---
Yeah solved , many thanks

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

[kwin] [Bug 356562] When I open windows, I see the window decoration before the window contents.

[Michael Davies via KDE Bugzilla]

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

Michael Davies  changed:

   What|Removed |Added

 CC||michaeld2...@gmail.com

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

[krita] [Bug 356592] crash when menu "settings -> configure krita" (win64)

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #4 from Boudewijn Rempt  ---
What is 'mactype'? That doesn't ring a bell. The 2.9.10 builds indeed say
they're 2.9.9, I made the builds before Cyrille updated the version number,
accidentally.

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

[kwin] [Bug 356557] Add "Fullscreen window" matching

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #15 from Thomas Lübking  ---
Which is not part of the rule system (as your request initially pointed) and
totally broken/useless to begin with (because it doesn't cover unmanaged
windows which many games actually are while otoh, you usually don't want that
when turning your browser or word processor fullscreen) - it is constant
subject to "let's remove this nonsense" discussions (also because we need to
downforce it on intel chips for causing bug #252817 - isn't it scary that I can
still remember the bug id?)

We could turn that into a "completely suspend the compositor when a window goes
fullscreen" but that would just carry the mentioned flaws as well.

What exactly is your exact concern about using the script system which was
especially created to allow flexible and custom manipulation of the flow
control in kwin?

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

[plasmashell] [Bug 348608] notifications pop up on wrong monitor

[Nick Cross via KDE Bugzilla]

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory

[René Krell via KDE Bugzilla]

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

--- Comment #2 from René Krell  ---
Created attachment 96059
  --> https://bugs.kde.org/attachment.cgi?id=96059=edit
cat /proc/`pidof baloo_file`/smaps (output)

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

[plasmashell] [Bug 356674] New: Plasma 5 Screenlocker crashes whenever I physically power off my DisplayPort Display

[Antornix via KDE Bugzilla]

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

Bug ID: 356674
   Summary: Plasma 5 Screenlocker crashes whenever I physically
power off my DisplayPort Display
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: antor...@antornix.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.3.0-2-default x86_64
Distribution: "openSUSE Tumbleweed (20151209) (x86_64)"

-- Information about the crash:
I am using SuSE Tumbleweed, I tend to be updated at all times, I am
experiencing serious regressions regarding DisplayPort under Plasma, though
this problem might be in the intel display driver.

My computer is an Intel NUC D54250WYK

If there's been a long delay since the last time I used my computer, the screen
remains off for say 3-4 minutes, then the PC comes back to life and is fully
operational. I will enable SSH to try to workaround this by triggering some
xrandr with the hope that I can resume my session faster.

Thank you all for pushing opensource computing KDE to unmatchable levels of
awesomness!!!

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f46b97ba700 (LWP 4382)):
#0  0x7f46c97bd20d in poll () at /lib64/libc.so.6
#1  0x7f46ce67a432 in  () at /usr/lib64/libxcb.so.1
#2  0x7f46ce67c007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f46bb909e29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f46c9eae94f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f46c8fc44a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f46c97c5b9d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f46b2b48700 (LWP 4383)):
#0  0x7f46c97bd20d in poll () at /lib64/libc.so.6
#1  0x7f46c5eb4264 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f46c5eb436c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f46ca0d352b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f46ca07d63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f46c9ea9b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f46cd1559a5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f46c9eae94f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f46c8fc44a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f46c97c5b9d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f46a594e700 (LWP 4384)):
#0  0x7f46c97b91ed in read () at /lib64/libc.so.6
#1  0x7f46c5ef6210 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f46c5eb3d94 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f46c5eb4208 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f46c5eb436c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f46ca0d352b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f46ca07d63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f46c9ea9b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f46cd1559a5 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f46c9eae94f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f46c8fc44a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f46c97c5b9d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f469fdca700 (LWP 4387)):
#0  0x7f46c97bd20d in poll () at /lib64/libc.so.6
#1  0x7f46c5eb4264 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f46c5eb436c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f46ca0d352b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f46ca07d63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f46c9ea9b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f46cd1559a5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f46c9eae94f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f46c8fc44a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f46c97c5b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f469e587700 (LWP 4388)):
#0  0x7f46c8fca07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f46cf8e9a84 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f46cf8e9ac9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f46c8fc44a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f46c97c5b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f460a097700 (LWP 4390)):
#0  0x7f46c97bd20d in poll () at /lib64/libc.so.6
#1  

[kwin] [Bug 356480] system crashes on startup , screen freezing , not recovery

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #4 from Thomas Lübking  ---


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

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

[kmail2] [Bug 356684] New: When default BCC or CC-address is set, no TO-Field is created.

[via KDE Bugzilla]

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

Bug ID: 356684
   Summary: When default BCC or CC-address is set, no TO-Field is
created.
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: qqq...@gmeyer.df-kunde.de

Version 5.0.80 beta1
When default BCC or CC-address is set, no TO-Field is created. Instead , the
first address-field after the automatically inserted is a CC-Field.

Reproducible: Always

Steps to Reproduce:
1. Add a default CC or BCC field in your default identity
2. Click New Mail.
3.

Actual Results:  
The first address-field after the automatically inserted is a CC-Field.

Expected Results:  
 The first address-field after the automatically inserted is a TO-Field.

Without a default CC-recipient, a TO-field is created.

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

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

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||eloy...@gmail.com

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

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

[plasmashell] [Bug 356685] New: Displaced Menue

[via KDE Bugzilla]

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

Bug ID: 356685
   Summary: Displaced Menue
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: b1mein...@aol.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
A KDE submenue was displaced (doubled) while moving the cursor with pressed
left mouse button inside main menue

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

Thread 8 (Thread 0x7fc8f8d6c700 (LWP 1489)):
#0  0x7fc908803c1d in poll () at /lib64/libc.so.6
#1  0x7fc90d72a422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc90d72c00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc8faebcc29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc908efa55f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc90800d0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc90880c04d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc8f1fed700 (LWP 1492)):
#0  0x7fff11bfc9a2 in clock_gettime ()
#1  0x7fc908818c9d in clock_gettime () at /lib64/libc.so.6
#2  0x7fc908faab06 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fc90912a089 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fc90912a615 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc90912b82e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fc904ee44ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fc904ee4d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fc904ee4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fc90912ba5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fc9090d2a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fc908ef584a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fc90c1de5f8 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7fc908efa55f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7fc90800d0a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7fc90880c04d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc8de270700 (LWP 1686)):
#0  0x7fc908ef9585 in  () at /usr/lib64/libQt5Core.so.5
#1  0x7fc90912c541 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7fc904ee48f1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc904ee4df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc904ee4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fc90912ba5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fc9090d2a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fc908ef584a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fc90c1de5f8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fc908efa55f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fc90800d0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fc90880c04d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc8d7fff700 (LWP 1692)):
#0  0x7fc9087ffced in read () at /lib64/libc.so.6
#1  0x7fc904f25b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc904ee4999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc904ee4df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc904ee4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fc90912ba5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fc9090d2a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fc908ef584a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fc90c1de5f8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fc908efa55f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fc90800d0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fc90880c04d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc8d6d4b700 (LWP 1701)):
#0  0x7fc90801105f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc90e9917eb in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fc90e991819 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fc90800d0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc90880c04d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc84f6b5700 (LWP 1785)):
#0  0x7fff11bfc9a2 in clock_gettime ()
#1  0x7fc908818c9d in clock_gettime () at /lib64/libc.so.6
#2  0x7fc908faab06 in  

[krita] [Bug 356256] [Krita animation beta] Copying frame offsets the image to original position

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/call
   ||igra/bc16a275413791dae90466
   ||a22c3cebae44ee81c9
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Dmitry Kazakov  ---
Git commit bc16a275413791dae90466a22c3cebae44ee81c9 by Dmitry Kazakov.
Committed on 14/12/2015 at 15:27.
Pushed by dkazakov into branch 'krita-animation-pentikainen'.

Fix initialization of the offset of the frame when it is duplicated

M  +4-2krita/image/kis_paint_device.cc

http://commits.kde.org/calligra/bc16a275413791dae90466a22c3cebae44ee81c9

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

[krita] [Bug 356249] [Krita animation beta] File not storing animation end frame number.

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/call |http://commits.kde.org/krit
   |igra/1a18426e977a66650846c8 |a/65766c2c886d6ec45e2877916
   |9d464e852f68de661c  |38247baae4195bb

--- Comment #4 from Dmitry Kazakov  ---
Git commit 65766c2c886d6ec45e287791638247baae4195bb by Dmitry Kazakov.
Committed on 14/12/2015 at 15:48.
Pushed by dkazakov into branch 'master'.

Fix loading of the animation playback properties

M  +10   -3krita/plugins/extensions/dockers/animation/animation_docker.cpp

http://commits.kde.org/krita/65766c2c886d6ec45e287791638247baae4195bb

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

[kwin] [Bug 318322] kickoff shadow remains

[Piotr Kloc via KDE Bugzilla]

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

--- Comment #24 from Piotr Kloc  ---
(In reply to Thomas Lübking from comment #23)
> https://git.reviewboard.kde.org/r/126323/

I have patched kwin from abs. It's not helping. Unless it's more of a long term
goal.

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

[kholidays] [Bug 356683] New: parsers/qcalendarsystem.cpp: missing breaks in switch

[via KDE Bugzilla]

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

Bug ID: 356683
   Summary: parsers/qcalendarsystem.cpp: missing breaks in switch
   Product: kholidays
   Version: git
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: dcb...@hotmail.com

../../src/parsers/qcalendarsystem.cpp:421] ->
[../../src/parsers/qcalendarsystem.cpp:434]: (warning) Variable 'dd' is
reassigned a value before the old one has been used. 'break;' missing?

Many more occurances in the same switch.

Reproducible: Always

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

[plasmashell] [Bug 348608] notifications pop up on wrong monitor

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #3 from OlafLostViking  ---
Perhaps see #356461

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

[frameworks-kio] [Bug 356667] Incorrect breadcrumb labels when navigating fish resources

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

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

--- Comment #3 from David Faure  ---
Yes already fixed. https://git.reviewboard.kde.org/r/126295/

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

[frameworks-kinit] [Bug 356614] ksmserver crashes after unlocking screens

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

Summary|kdeinit5 crashes after  |ksmserver crashes after
   |unlocking screens   |unlocking screens

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

[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 CC||virgo...@gmail.com

--- Comment #14 from Bhushan Shah  ---
*** Bug 356702 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 356495] 15.11.90+48 - When "Split" button is clicked on a clip with no effects, clip monitor still enters "split mode". Should remain in standard mode.

[Jesse via KDE Bugzilla]

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

--- Comment #3 from Jesse  ---
I just realized that the icon does change when it's clicked. I get the
direction you're going with it... but maybe consider if the button should
behave more like the edit mode in Project monitor? Would seem more congruent in
each monitor's behavior, yeah?

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

[digikam] [Bug 356704] Version 4.14 Digikam still crashes (bug not fixed) scanning a new photo directory & subdirs

[via KDE Bugzilla]

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

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

   What|Removed |Added

  Component|general |Metadata-Engine
 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Crash is always in Exiv2 RIFF video file parser.

upgrade Exiv2 shared lib to last 0.25. digiKam and libkexiv2 MUST be recompiled
(Help/Component Info dialog from digiKam must show Exiv2 to 0.25)

If problem still here with 0.25, report the problem to Exiv2 team.

Giles Caulier

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

[valgrind] [Bug 356715] New: vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x7D 0x13 0x4 0x4A 0xC5 0xFC

[Christopher Zapart via KDE Bugzilla]

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

Bug ID: 356715
   Summary: vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2
0x7D 0x13 0x4 0x4A 0xC5 0xFC
   Product: valgrind
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: chris.zap...@nao.ac.jp

valgrind 3.11.0 (tar.bz2) built from source on CentOS release 6.7 (Final)
seg-faults on the following AVX2 instructions:

_mm256_store_ps((dest + i), _mm256_cvtph_ps(_mm_load_si128((__m128i*)(cube +
i;

compiler: icpc (ICC) 15.0.2 20150121
compiler invokation: icpc -g -O3 -xCORE-AVX2 -mcmodel large

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

[plasma-nm] [Bug 356703] Plasmashell crash when is pressed "connect" on a configured VPN

[Jan Grulich via KDE Bugzilla]

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

--- Comment #1 from Jan Grulich  ---
Any backtrace? I cannot reproduce this.

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

[plasmashell] [Bug 356716] Empty line in Kicker Recent programs group after uninstalling one last used program

[via KDE Bugzilla]

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

--- Comment #2 from opensuse.lietuviu.ka...@gmail.com ---
Created attachment 96078
  --> https://bugs.kde.org/attachment.cgi?id=96078=edit
After re-installing program

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

[plasmashell] [Bug 356716] Empty line in Kicker Recent programs group after uninstalling one last used program

[via KDE Bugzilla]

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

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
Created attachment 96077
  --> https://bugs.kde.org/attachment.cgi?id=96077=edit
Empty line instead uninstalled program

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

[Baloo] [Bug 354636] baloo_file_extractor memory consuming

[Stéphane ANCELOT via KDE Bugzilla]

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

--- Comment #3 from Stéphane ANCELOT  ---
Maybe you are not using your computer to store files 

take a whole directory (almost 1g and so) of files with pictures (raw photos,
jpg high and  low densite) ,svg files,  libreoffice files, development c/c++
files , eg android source code and so on ...
a thunderbird imap account with more than 1000 messages .
There are lot of files generated , that  we can not master in our computer.
I mean a classic developer computer. 
you may have not tried using 1gb and more files.
This should easily trigger some problems

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

[ktorrent] [Bug 356717] New: Cannot switch datadir

[Petar Marinov via KDE Bugzilla]

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

Bug ID: 356717
   Summary: Cannot switch datadir
   Product: ktorrent
   Version: 4.3.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: eng.petar.mari...@gmail.com

I am trying to change my "Folder to store torrent information" from
/media/Data/Downloads/ to any existing path on my file system.
My /dev/sdd1 was mounted to /media/Data/ and then unmounted, so
/media/Data/Downloads/ does not exists now.

~/.kde/share/apps/ktorrent/log says:

вт дек. 15 09:29:58 2015: Switching to datadir
/home/wildalmighty/.kde/share/apps/ktorrent/
вт дек. 15 09:29:58 2015: Setting suspended state to 1
вт дек. 15 09:29:58 2015: /media/Data/Downloads/tor15/ ->
/home/wildalmighty/.kde/share/apps/ktorrent/tor15/
вт дек. 15 09:29:58 2015: Could not move /media/Data/Downloads/tor15/ to
/home/wildalmighty/.kde/share/apps/ktorrent/tor15/
вт дек. 15 09:29:58 2015: Error, rolling back
вт дек. 15 09:29:58 2015: Setting suspended state to 0
вт дек. 15 09:29:59 2015: Stopped update timer

The result is that I cannot use KTorrent now.

Reproducible: Always

Steps to Reproduce:
1. Umount/remove dev containing the path to the old datadir
2. Go to Settings -> Configure KTorrent -> Application
3. Change "Folder to store torrent information" with an existing path 
4. Press "Save"

Actual Results:  
"Folder to store torrent information" (datadir) is not changed.

Expected Results:  
"Folder to store torrent information" (datadir) should be changed.

KTorrent cannot be used with the old datadir, so I have to manually delete my
config file ~/.kde/share/config/ktorrentrc in order to use kTorrent again.

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

[kdenlive] [Bug 351723] 15.11.80 - Doesn't load layout (widget size & position) at program start-up

[Grzegorz Nowak via KDE Bugzilla]

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

Grzegorz Nowak  changed:

   What|Removed |Added

 CC||gno...@gmail.com

--- Comment #8 from Grzegorz Nowak  ---
Confirmed on new install of Kubuntu 15.10, Kdenlive 15.08.1

I save my layout in Layout 1 and shut down and reopen. And the original
(default) layout is loaded. I can manually load Layout 1 and it gives me the
settings I have saved.

Where can I set Layout 1 to be the default layout?

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

[kwin] [Bug 356616] kwin reports a crash when sending in Thunderbird

[Johannes Rauh via KDE Bugzilla]

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

--- Comment #4 from Johannes Rauh  ---
It seems that compositing is off:

$ qdbus org.kde.KWin /KWin supportInformation | grep omposit
compositingMode: 1
useCompositing: false
compositingInitialized: false
Compositing
Compositing is not active

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

[kontact] [Bug 356652] kmail crashes when trying to open a message

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #2 from Laurent Montel  ---
I fixed crash when kdepim-addons is not installed

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

[kwin] [Bug 356322] Black screen after login, mouse pointer visible

[Felix Miata via KDE Bugzilla]

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

Felix Miata  changed:

   What|Removed |Added

 CC||mrma...@earthlink.net

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