[kmail2] [Bug 363085] kmail window fails to display/load on second start

[via KDE Bugzilla]

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

--- Comment #8 from bl...@vivaldi.net ---
Ryein Goddard, please check this
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1584288
Click on "Does this bug affect you?" -> "Yes, it affects me".

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

[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again

[Ben Tilford via KDE Bugzilla]

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

--- Comment #27 from Ben Tilford  ---
This happens with every laptop I use. I'm unable to use any workaround like
xrandr because it doesn't even detect the laptop display.

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

[kmail2] [Bug 363085] kmail window fails to display/load on second start

[via KDE Bugzilla]

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

--- Comment #7 from bl...@vivaldi.net ---
It's really hard to debug this stuff in kubuntu because package kdepim-dbg is
missing. Why?

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

[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again

[Ben Tilford via KDE Bugzilla]

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

Ben Tilford  changed:

   What|Removed |Added

 CC||b...@tilford.info

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

[kmail2] [Bug 363085] kmail window fails to display/load on second start

[via KDE Bugzilla]

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

--- Comment #6 from bl...@vivaldi.net ---
KMailSettings::self()->emptyTrashOnExit() just reads settings and returns
"true" or "false". That's not it.

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

[kolourpaint] [Bug 363353] version 4.14.1 No toolbar/toolbox

[Martin Koller via KDE Bugzilla]

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

Martin Koller  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||kol...@aon.at

--- Comment #1 from Martin Koller  ---
Use Menu -> Settings -> Toollbars Shown and check "Tool Box"

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

[krusader] [Bug 363360] New: Password of net connection is not saved, if add the NAS server location

[George Getejanc via KDE Bugzilla]

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

Bug ID: 363360
   Summary: Password of net connection is not saved, if add the
NAS server location
   Product: krusader
   Version: Git
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: net-connection
  Assignee: m...@fork.pl
  Reporter: silwa...@gmail.com

I can connect to my NAS server on lan, with or without password. The difference
is, that, if i connect without password, i can't change, delete or add
anything, just browse, or watch.

Therefore, i need to attach the location "with" password. And, it works well on
first adding the location with pass, but, if i add this location to Bookmarks,
next time i start the Krusader 15.08- Beta, it wont attach the location with
password, just location with username, but, the password is not saved, and i
can't adding or changing the password anywhere. I must go to new net
connection, and readd the location, name and password, to able to have the
location on my NAS with password.

My Linux distro is KaOS Linux 16.04 (KDE Plasma 5.6.4, Qt 5.6.0, Kernel
4.4.5-1) x64

Reproducible: Always

Steps to Reproduce:
1. Create new smb Net Connection with name and password
2. Add the location to Bookmarks
3.Try to reconnect next time you open Krusader - it will connect, but without
password, just as annonymous - the password is not saved.

Actual Results:  
password of net connection (smb) is not saved on Bookmarking the location.

Expected Results:  
Password should saved, if added on new net connection, and the location is
added on Bookmarks.

On Editing Bookmarks, it should have option to be possible to change the actual
password, if any.

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

[plasmashell] [Bug 363359] New: Plasma keeps crashing randomly

[Slaughter via KDE Bugzilla]

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

Bug ID: 363359
   Summary: Plasma keeps crashing randomly
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slaughterho...@hotmail.ca
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
In this particular case, I had just finished watching a program using VLC. When
I went to close the window, Plasma crashed. After it happens once, the problems
happens more frequently especially with using VLC. The upgrade to 16.04 is when
all of the problems I've been having with Plasma have occured (hanging screens
at login forcing several reboots, crashes when transferring files to a USB
stick, etc)

-- 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 0x7f045a0ba8c0 (LWP 4784))]

Thread 12 (Thread 0x7f04453dc700 (LWP 4787)):
#0  0x7f04547cbe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0458890c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f04588928d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f044752a629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f0454ec184e in QThreadPrivate::start (arg=0x1fdf8a0) at
thread/qthread_unix.cpp:331
#5  0x7f0453fae6fa in start_thread (arg=0x7f04453dc700) at
pthread_create.c:333
#6  0x7f04547d7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f043eb46700 (LWP 4789)):
#0  0x7f04547cbe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f045156131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f045156142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f04550f8a9b in QEventDispatcherGlib::processEvents
(this=0x7f04380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f045509fdea in QEventLoop::exec (this=this@entry=0x7f043eb45ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f0454ebc8a4 in QThread::exec (this=this@entry=0x20c1640) at
thread/qthread.cpp:503
#6  0x7f04577643c5 in QQmlThreadPrivate::run (this=0x20c1640) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f0454ec184e in QThreadPrivate::start (arg=0x20c1640) at
thread/qthread_unix.cpp:331
#8  0x7f0453fae6fa in start_thread (arg=0x7f043eb46700) at
pthread_create.c:333
#9  0x7f04547d7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f043405f700 (LWP 4794)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0437957aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f0437957907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f0453fae6fa in start_thread (arg=0x7f043405f700) at
pthread_create.c:333
#4  0x7f04547d7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f043385e700 (LWP 4795)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0437957aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f0437957907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f0453fae6fa in start_thread (arg=0x7f043385e700) at
pthread_create.c:333
#4  0x7f04547d7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f043305d700 (LWP 4796)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0437957aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f0437957907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f0453fae6fa in start_thread (arg=0x7f043305d700) at
pthread_create.c:333
#4  0x7f04547d7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f043285c700 (LWP 4797)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0437957aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f0437957907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f0453fae6fa in start_thread (arg=0x7f043285c700) at
pthread_create.c:333
#4  0x7f04547d7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f042e029700 (LWP 4798)):
#0  0x7f04515a5a49 in g_mutex_lock () 

[kio] [Bug 362762] Unable to create io-slave: Could not find the 'kio_kamera' plugin.

[via KDE Bugzilla]

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

ipatrol6...@yahoo.com changed:

   What|Removed |Added

 CC||ipatrol6...@yahoo.com

--- Comment #5 from ipatrol6...@yahoo.com ---
Confirming that this problem also exists with the iPhone 6. I suggest that the
importance of this bug be raised, since it is potentially a major UX
deficiency.

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

[frameworks-baloo] [Bug 333037] Search for filenames requires first characters, cannot start in the middle

[nuju via KDE Bugzilla]

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

nuju  changed:

   What|Removed |Added

 CC||nujucob...@gmail.com

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

[kdenlive] [Bug 363354] git master: error during compile

[Massimo Stella via KDE Bugzilla]

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

Massimo Stella  changed:

   What|Removed |Added

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

--- Comment #1 from Massimo Stella  ---
I'm sorry for the mistake in signaling this bug.
I didn't read there was to update a library.
I did it and everything worked.
I guess we can close and delete this bug signalisation.

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

[plasmashell] [Bug 363351] plasmashell fails to start rendering system unusable when using kernel 4.5 and higher. It works fine on kernel 4.4.

[Chao Feng via KDE Bugzilla]

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

Chao Feng  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM
 CC||chaofeng...@gmail.com

--- Comment #1 from Chao Feng  ---
The "k" here means kernel, not KDE :)

So please seek help from downstream Arch. See below link for bug reporting in
Arch. https://wiki.archlinux.org/index.php/Reporting_bug_guidelines

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

[dolphin] [Bug 363358] New: copying files over 16GB over smb causes disk is full error

[illumilore via KDE Bugzilla]

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

Bug ID: 363358
   Summary: copying files over 16GB over smb causes disk is full
error
   Product: dolphin
   Version: 15.12.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: illumil...@gmail.com

When using dolphin to copy files over 16GB to or from the client, dolphin will
give a disk is full error. This happens everytime.

Reproducible: Always

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

[plasmashell] [Bug 363357] New: After transferring files, copying dialogue stays in system tray notifications

[illumilore via KDE Bugzilla]

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

Bug ID: 363357
   Summary: After transferring files, copying dialogue stays in
system tray notifications
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: illumil...@gmail.com

After moving and copying files in dolphin using copy and cut, the notification
in the system tray that shows the progress won't go away. It just shows a bunch
of blank entries that never finish until I manually hit the stop icon, even
though the actually copying and pasting would have taken less than a second.

Reproducible: Always

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

[dolphin] [Bug 363356] New: slow drag and drop

[illumilore via KDE Bugzilla]

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

Bug ID: 363356
   Summary: slow drag and drop
   Product: dolphin
   Version: 15.12.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: illumil...@gmail.com

Whenenver transferring files over smb, dragging folders and files around in
dolphin becomes extremely slow. The icon animation that would normally follow
the mouse lags behind.

Reproducible: Always

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

[plasma-pa] [Bug 363355] New: volume settings for event sounds ignored

[illumilore via KDE Bugzilla]

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

Bug ID: 363355
   Summary: volume settings for event sounds ignored
   Product: plasma-pa
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: illumil...@gmail.com
CC: plasma-b...@kde.org

In the volume sliders, I have event sounds set to 0%, but whenever something
like dolphin has an error or does something that would normally make a noise,
that noise is at 100% volume. This seems to only happen for the first time,
subsequent errors or things that cause event sounds seem to go back to the
normal volume for a while.

Reproducible: Always

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

[valgrind] [Bug 348924] MIPS: Load doubles through memory so the code compiles with the FPXX ABI

[Petar Jovanovic via KDE Bugzilla]

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

--- Comment #3 from Petar Jovanovic  ---
Committed in VEX r3219.
Thank you.

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

[kdenlive] [Bug 363354] New: git master: error during compile

[Massimo Stella via KDE Bugzilla]

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

Bug ID: 363354
   Summary: git master: error during compile
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Installation
  Assignee: vpi...@kde.org
  Reporter: maxs...@tin.it

After the latest modify
https://git.launchpad.net/kdenlive/commit/?id=4e4870bbb16b0c83cade0eff3aeeedda190e3be6
it's no more possible to compile Kdenlive.
The error is this one:
mainwindow.cpp:244:36: error: ‘GroupedDragging’ is not a member of
‘QMainWindow’

Reproducible: Always

Steps to Reproduce:
1.Open the terminal and write
2.git clone https://git.launchpad.net/kdenlive
3.cd kdenlive
4.mkdir build
5.cd build
6.cmake .. -DCMAKE_INSTALL_PREFIX=/install/path
7.make -j4

Actual Results:  
Compiling operation stops at 98% with error:
mainwindow.cpp:244:36: error: ‘GroupedDragging’ is not a member of
‘QMainWindow’

Expected Results:  
Compiling operations end successfully at 100%

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

[Akonadi] [Bug 349549] KMail crashes after asking multiple times at once for certificate

[via KDE Bugzilla]

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

--- Comment #2 from noucam...@hotmail.com ---
Created attachment 99108
  --> https://bugs.kde.org/attachment.cgi?id=99108=edit
New crash information added by DrKonqi

akonadi_imap_resource (4.14) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:
Accepting an SSL certificate for this session only. Computer had just
restarted. Two windows popped up asking for the same. The crash occur after
accepting the second one.

-- Backtrace (Reduced):
#7  0x7f95e384bf38 in invokeMethod (val9=..., val8=..., val7=..., val6=...,
val5=..., val4=..., val3=..., val2=..., val1=..., val0=...,
member=0x7f95e386e06e "doSslErrorHandlerResponse", obj=) at
/usr/include/qt4/QtCore/qobjectdefs.h:434
#8  KIMAP::SessionThread::sslErrorHandlerResponse (this=,
response=true) at ../../kimap/sessionthread.cpp:274
#9  0x7f95e5bd6c1e in QObject::event (this=0x18b52f0, e=) at
kernel/qobject.cpp:1194
#10 0x7f95e4f57e2c in QApplicationPrivate::notify_helper
(this=this@entry=0x1643150, receiver=receiver@entry=0x18b52f0,
e=e@entry=0x7f95cc0ee1b0) at kernel/qapplication.cpp:4567
#11 0x7f95e4f5e4a0 in QApplication::notify (this=this@entry=0x7ffee178b850,
receiver=receiver@entry=0x18b52f0, e=e@entry=0x7f95cc0ee1b0) at
kernel/qapplication.cpp:4353

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

[Akonadi] [Bug 349549] KMail crashes after asking multiple times at once for certificate

[via KDE Bugzilla]

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

noucam...@hotmail.com changed:

   What|Removed |Added

 CC||noucam...@hotmail.com

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

[kolourpaint] [Bug 363353] New: version 4.14.1 No toolbar/toolbox

[Uli via KDE Bugzilla]

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

Bug ID: 363353
   Summary: version 4.14.1   No toolbar/toolbox
   Product: kolourpaint
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: uli...@yahoo.com

Linux Mint 17.3 Rosa 64-bit
When opening the program, the toolbar on the left side is missing. No way to
select pencil, line, eraser etc.


Reproducible: Always

Steps to Reproduce:
1. Open KolourPaint4 on Linux Mint 17.
2.
3.

Actual Results:  
KolourPaint opens without tools.

Expected Results:  
KolourPaint opens with a toolbar on the left side.

Sometimes from Menu/Software Manager,Kolourpaint4, if you press install-button:
Nothing happens. You gotta use Menu/Package Manager, this works.
In Linux Mint 13 32-bit KolourPaint worked very well.

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

[kde] [Bug 363352] New: previewing some libreoffice files in folder view

[Phil Terry via KDE Bugzilla]

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

Bug ID: 363352
   Summary: previewing some libreoffice files in folder view
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: p...@terryism.com

Application: plasma-desktop (4.11.16)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.15-desktop-2.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed: If the mouse hovers over a
libreoffice file in the Downloads folder displayed on the desktop in the Folder
View plasmoid the desktop crashes and restarts

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff74de97780 (LWP 14089))]

Thread 3 (Thread 0x7ff71be4f700 (LWP 14091)):
#0  0x7ff74b492f5d in poll () at /lib64/libc.so.6
#1  0x7ff748578eb4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7ff748578fbc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7ff74cae3e3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7ff74cab5931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7ff74cab5c45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7ff74c9b3899 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7ff74ca973d3 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#8  0x7ff74c9b5fff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7ff74c7265bd in start_thread () at /lib64/libpthread.so.0
#10 0x7ff74b49e81d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff71b64e700 (LWP 14092)):
#0  0x7ff74c72b67f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff73870573a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQtScript.so.4
#2  0x7ff738705769 in  () at /lib64/libQtScript.so.4
#3  0x7ff74c7265bd in start_thread () at /lib64/libpthread.so.0
#4  0x7ff74b49e81d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff74de97780 (LWP 14089)):
[KCrash Handler]
#5  0x7ff67f481541 in mov_probe () at /lib64/libavformat.so.56
#6  0x7ff6809986a5 in FFMPEGEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () at /usr/lib64/strigi/strigiea_ffmpeg.so
#7  0x7ff73c7af6a8 in
Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0
#8  0x7ff73c786bf5 in Strigi::AnalysisResult::indexChild(std::string
const&, long, Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0
#9  0x7ff73c7ca753 in OdfEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0
#10 0x7ff73c7af6a8 in
Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0
#11 0x7ff73ce17471 in KFileMetaInfoPrivate::init(QIODevice&, KUrl const&,
long, QFlags) () at /usr/lib64/libkio.so.5
#12 0x7ff73ce1795a in KFileMetaInfo::KFileMetaInfo(QString const&, QString
const&, QFlags) () at /usr/lib64/libkio.so.5
#13 0x7ff73ce0495f in KFileItem::metaInfo(bool, int) const () at
/usr/lib64/libkio.so.5
#14 0x7ff724173f6c in ToolTipWidget::metaInfo() const () at
/usr/lib64/kde4/plasma_applet_folderview.so
#15 0x7ff7241767fb in ToolTipWidget::setContent() () at
/usr/lib64/kde4/plasma_applet_folderview.so
#16 0x7ff724176aee in ToolTipWidget::toolTipAboutToShow() () at
/usr/lib64/kde4/plasma_applet_folderview.so
#17 0x7ff74cabea72 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () at
/lib64/libQtCore.so.4
#18 0x7ff74cac0d2e in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at
/lib64/libQtCore.so.4
#19 0x7ff73b0ce69a in Plasma::ToolTipManagerPrivate::showToolTip() () at
/usr/lib64/libplasma.so.3
#20 0x7ff73b0cf069 in Plasma::ToolTipManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.25] () at
/usr/lib64/libplasma.so.3
#21 0x7ff74caca88a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#22 0x7ff74cacec2b in 

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

[Paolo Carlini via KDE Bugzilla]

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

Paolo Carlini  changed:

   What|Removed |Added

 CC|pcarl...@gmail.com  |

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

[kdelibs] [Bug 279592] Allow per-application color scheme

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

  Flags||Usability?
 CC||k...@privat.broulik.de

--- Comment #13 from Kai Uwe Broulik  ---
If, and only if, we were to add something like that, we could add it to KXmlGui
and have it provide a settings dialog in the settings menu where you also find
eg. "Configure Toolbars".

The infrastructure is already there, KWin can even follow the colorscheme of an
application to colorize the title bar accordingly. However, with
KColorSchemeManager there's an easy-to-use class that applications that want to
provide such functionality (eg. Krita, KDevelop, Gwenview, Dragon Player) can
add to their settings without further complicating the already insane
customizability of our applications.

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

[plasmashell] [Bug 363351] New: plasmashell fails to start rendering system unusable when using kernel 4.5 and higher. It works fine on kernel 4.4.

[via KDE Bugzilla]

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

Bug ID: 363351
   Summary: plasmashell fails to start rendering system unusable
when using kernel 4.5 and higher. It works fine on
kernel 4.4.
   Product: plasmashell
   Version: 5.6.4
  Platform: Archlinux Packages
   URL: https://bbs.archlinux.org/viewtopic.php?id=212427
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arnold.bal...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Messages appear while on kernel 4.5 when on command line:

systemd[1]: Journal service failed to start appear and kworker process is
blocked.

INFO: task kworker/u8:0:6 blocked for more than 120 seconds Tainted: G 0
4.5.2-1-ARCH #1 "echo bla bla bla" disables this message.

Sometimes it also I get this output as I am about to decrypt my home folder and
log in:
[18.783662] ata2.00: exception Emask 0x0 SAct 0x0 Serr 0x0 action 0x6 frozen
[18.783937] ata2.00: cmd a0/00:00:00:00:00:00:/a0 tag 15 pio 16392 in
[18.783937] opcode-0x4a 4a 01 00 00 10 00 00 00 08 00res 50/00:03:00 ... Emask
0x4 (timeout)
[18.783941] ata2.00: status: { DRDY }
[21.687301] usb 1-3: device descriptor read/64, error -110

I never get these errors when I am in kernel 4.4.5-1

Reproducible: Always

Steps to Reproduce:
1. Upgrade from linux 4.4.5-1 to 4.5.2-1 in KDE Plasma 5.6.4
2. Restart machine
3. Boot normally
4. Blank screen (sometimes I can see my desktop wallpaper but rarely and
nothing else)
5. Restart machine
6. Boot in level 3 so you have command line instead of gui and these messages
appear sporadically from time to time.

Actual Results:  
Blank screen and when on command line only the messages described in the
details appear.


Expected Results:  
It should have shown the shell normally without the messages and everything
should have worked fine just like in kernel 4.4.5


The laptop runs hot as if trying to complete a heavy task. I think its caused
by the kworker not being able to run or something else that its not running
properly.

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

[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload

[Stas Fomin via KDE Bugzilla]

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

Stas Fomin  changed:

   What|Removed |Added

Summary|Command line option to  |Disable warning "The
   |disable presentation mode   |document requested to be
   |and warning "The document   |launched in presentation
   |requested to be launched in |mode" on document reload
   |presentation mode"" |

--- Comment #2 from Stas Fomin  ---
OK. 

I will try to patch it.

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

[dolphin] [Bug 363349] Video duration in Details Mode

[kiran via KDE Bugzilla]

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

kiran  changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Archlinux Packages
   Severity|wishlist|normal

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

[dolphin] [Bug 363349] Video duration in Details Mode

[kiran via KDE Bugzilla]

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

--- Comment #1 from kiran  ---
Created attachment 99107
  --> https://bugs.kde.org/attachment.cgi?id=99107=edit
Dolphin details view of video files in KDE 5.6.0

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

[kwin] [Bug 363350] New: Window sometimes not getting redrawn with EGL compositing enabled

[via KDE Bugzilla]

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

Bug ID: 363350
   Summary: Window sometimes not getting redrawn with EGL
compositing enabled
   Product: kwin
   Version: 5.6.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: egl
  Assignee: kwin-bugs-n...@kde.org
  Reporter: linus.kardell+kdeb...@gmail.com

Windows sometimes do not seem to be redrawn properly when EGL composititing is
used. For example in Firefox if you highlight some text and then click
somewhere it unhighlights the text. However the the text still looks
highlighted. If you scroll afterwords it seems to force it to redraw. It
happens elsewhere as well. It's most noticeable when editing text as your edits
do not appear on the screen immediately. It does not seem to happen with GLX
compositing.

Reproducible: Always

Steps to Reproduce:
1. Enable EGL compsiting
2. Highlight text in Firefox
3. Click somewhere on the page
4. Scroll

Actual Results:  
The highlight does not seem to disappear until you scroll.

Expected Results:  
The highlight should immediately disappear when you click.

openSUSE Leap 42.1
KDE from KDE:frameworks5 BuildService repo
Intel Core-i5 3230M with Intel HD Graphics 4000
Mesa 11.0.8

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

[dolphin] [Bug 363349] Video duration in Details Mode

[kiran via KDE Bugzilla]

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

kiran  changed:

   What|Removed |Added

URL|https://plus.google.com/u/0 |
   |/107970213369875035288/post |
   |s/AkJW7zV2wKg   |

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

[kwin] [Bug 348270] Cannot scroll properly in GTK3 apps after focus switching

[Allan via KDE Bugzilla]

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

Allan  changed:

   What|Removed |Added

 CC||kdeb...@metalight.dk

--- Comment #30 from Allan  ---
While I realise this has nothing to do with KDE. A workaround would be awesome
as this GTK3 bug (Opera, pavucontrol..) is still here anno 2016 with gtk
3.20.4. When mouse leaves the gtk window and comes back - first scroll event is
ignored. :-o

As unbelievable as it may sound - it even happens in pure Gnome..
- Defective by design nearly on par with scrollbar snapback in Chrome
https://bugs.chromium.org/p/chromium/issues/detail?id=377191 (Gnome folks tried
to implement this too, once.. Malice I say.. Malice!).

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

[dolphin] [Bug 363349] New: Video duration in Details Mode

[kiran via KDE Bugzilla]

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

Bug ID: 363349
   Summary: Video duration in Details Mode
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
   URL: https://plus.google.com/u/0/107970213369875035288/post
s/AkJW7zV2wKg
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: skirankumar...@gmail.com
CC: anandrk...@gmail.com, m...@vhanda.in,
ponchorat1...@hotmail.com, skirankumar...@gmail.com

+++ This bug was initially created as a clone of Bug #322023 +++

Video duration in Details Mode not available. Can not view duration file
without opening and cannot sort bu duration as well.

Reproducible: Always

Steps to Reproduce:
1. Open Dolphin
2. Navigate to any folder containing videos
Actual Results:  
Duration details not available.

Expected Results:  
Like Audio, we need a category for video and should display video specific
attributes such as Duration, Chapter, Etc.

I tried 'Duration' attribute under Audio but it does not display values for
video files.

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

[dolphin] [Bug 322023] Video duration in Details Mode

[kiran via KDE Bugzilla]

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

--- Comment #13 from kiran  ---
Why is this bug resolved ?. This is a new functionality request.

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

[extra-cmake-modules] [Bug 363348] New: Include KDEInstallDirs in ECMGeneratePriFile ?

[Antonio Rojas via KDE Bugzilla]

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

Bug ID: 363348
   Summary: Include KDEInstallDirs in ECMGeneratePriFile ?
   Product: extra-cmake-modules
   Version: 5.22.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alex.me...@kde.org
  Reporter: aro...@archlinux.org
CC: ecm-bugs-n...@kde.org

>From commit a2d184bb it is not necessary to pass
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON explicitely if the install prefix coincides
with the Qt one, since it is set automatically in KDEInstallDirs. 
 This variable is used in ECMGeneratePriFile to determine the mkspecs path. If
a project includes ECMGeneratePriFile before KDEInstallDirs (eg. like
kdepim-apps-libs or kmailtransport do) then the variable will still not be set
when importing ECMGeneratePriFile and the pri files will be installed in the
wrong path.
 Not sure if this should be fixed in ECM (by including KDEInstallDirs in
ECMGeneratePriFile) or in the projects by making sure that KDEInstallDirs is
included befora ECMGeneratePriFile.

Reproducible: Always

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

[frameworks-kdoctools] [Bug 362849] meinproc5.exe searches the wrong path for kdoctools

[Jasem Mutlaq via KDE Bugzilla]

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

--- Comment #2 from Jasem Mutlaq  ---
Any update on this issue? Was this tested on Win10? under powershell?

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

[kdevelop] [Bug 363341] Crashed unmarking breakpoint

[Leozito via KDE Bugzilla]

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

--- Comment #2 from Leozito  ---
Yeah it looks like a Qt issue. Couldn't reproduce though. Thanks for the
review!

On Fri, May 20, 2016, 18:17 Kevin Funk via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=363341
>
> Kevin Funk  changed:
>
>What|Removed |Added
>
> 
>  Status|UNCONFIRMED |RESOLVED
>  Resolution|--- |UPSTREAM
>
> --- Comment #1 from Kevin Funk  ---
> Backtrace indicates this is an issue somewhere in the Qt modules; nothing
> we
> can do about.
>
> Is this crash reproducible?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[kdevelop] [Bug 363341] Crashed unmarking breakpoint

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Kevin Funk  ---
Backtrace indicates this is an issue somewhere in the Qt modules; nothing we
can do about.

Is this crash reproducible?

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

[dolphin] [Bug 363343] New: Dolphin se cierra inesperadamente

[Etzel via KDE Bugzilla]

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

Bug ID: 363343
   Summary: Dolphin se cierra inesperadamente
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: iet...@outlook.com

Application: dolphin (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed: El explorador de archivos
Dolphin se cerró al abrir la carpeta de archivos de un disco duro externo
toshiba de 2TB que recién había conectado.

The crash can be reproduced sometimes.

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

Thread 4 (Thread 0x7f50ae9ec700 (LWP 4883)):
#0  0x7f50c2a4161a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f50c2a419a9 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f50c29ff680 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f50c29fff03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f50c2a000ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f50c78177be in QEventDispatcherGlib::processEvents
(this=0x7f50a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f50c77e90af in QEventLoop::processEvents
(this=this@entry=0x7f50ae9ebde0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f50c77e93a5 in QEventLoop::exec (this=this@entry=0x7f50ae9ebde0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f50c76e5c5f in QThread::exec (this=this@entry=0xd5afb0) at
thread/qthread.cpp:537
#9  0x7f50c77ca823 in QInotifyFileSystemWatcherEngine::run (this=0xd5afb0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f50c76e832f in QThreadPrivate::start (arg=0xd5afb0) at
thread/qthread_unix.cpp:349
#11 0x7f50c2edf182 in start_thread (arg=0x7f50ae9ec700) at
pthread_create.c:312
#12 0x7f50cb7b647d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f50ae19b700 (LWP 4884)):
#0  0x7f50cb7a912d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f50c29fffe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f50c2a000ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f50c78177be in QEventDispatcherGlib::processEvents
(this=0x7f50a8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f50c77e90af in QEventLoop::processEvents
(this=this@entry=0x7f50ae19ae20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f50c77e93a5 in QEventLoop::exec (this=this@entry=0x7f50ae19ae20,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f50c76e5c5f in QThread::exec (this=) at
thread/qthread.cpp:537
#7  0x7f50c76e832f in QThreadPrivate::start (arg=0xb249a0) at
thread/qthread_unix.cpp:349
#8  0x7f50c2edf182 in start_thread (arg=0x7f50ae19b700) at
pthread_create.c:312
#9  0x7f50cb7b647d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f50ad2ff700 (LWP 4885)):
#0  0x7f50c29fd3e7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f50c29ff9bb in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f50c29fff7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f50c2a000ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f50c78177be in QEventDispatcherGlib::processEvents
(this=0x7f50a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7f50c77e90af in QEventLoop::processEvents
(this=this@entry=0x7f50ad2fede0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f50c77e93a5 in QEventLoop::exec (this=this@entry=0x7f50ad2fede0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f50c76e5c5f in QThread::exec (this=this@entry=0xead0e0) at
thread/qthread.cpp:537
#8  0x7f50c77ca823 in QInotifyFileSystemWatcherEngine::run (this=0xead0e0)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f50c76e832f in QThreadPrivate::start (arg=0xead0e0) at
thread/qthread_unix.cpp:349
#10 0x7f50c2edf182 in start_thread (arg=0x7f50ad2ff700) at
pthread_create.c:312
#11 0x7f50cb7b647d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f50cbeee7c0 (LWP 4882)):
[KCrash Handler]
#6  0x7f50c932138b in QDomNode::isElement (this=this@entry=0x7de13540)
at dom/qdom.cpp:2823
#7  0x7f50c9324a28 in QDomNode::firstChildElement
(this=this@entry=0x7de136c0, tagName=...) at dom/qdom.cpp:2951
#8  0x7f50c96fa967 in 

[kleopatra] [Bug 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

[via KDE Bugzilla]

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

ipatrol6...@yahoo.com changed:

   What|Removed |Added

 CC||ipatrol6...@yahoo.com

--- Comment #14 from ipatrol6...@yahoo.com ---
(In reply to Ralf Jung from comment #13)
> > gpg2 is not the problem. But the lack of a separate config file by default 
> > is.
> I would argue that the bug is in gpgconf (KWatchGnuPG does not touch the
> configfile itself): It should not write options to configfiles which are
> later read by programs not understanding these options. This problem is
> tracked upstream as https://bugs.g10code.com/gnupg/issue1448 .

Except GPG has denied that bug report, and instead says that it is not
recommended to install both gpg1 and gpg2 on the same system during normal
operation.

So now the ball is back in our court. We can either continue complaining about
it, or come up with a workaround. In the mean time, I will consult with the
Debian project about trying to resolve the gpg1 dependencies and declare the
packages in conflict with each other.

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

[Baloo] [Bug 363342] New: Baloo crashes when writing/generating file

[Arnout Boelens via KDE Bugzilla]

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

Bug ID: 363342
   Summary: Baloo crashes when writing/generating file
   Product: Baloo
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: a.m.p.boel...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.16.0)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
When writing or creating a new file, Baloo crashes very often. The backtrace is
attached to this email.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f76f58900 (LWP 9622))]

Thread 2 (Thread 0x7f1e2b4d6700 (LWP 13262)):
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:116
#7  0x7f1f761497ea in memcpy (__len=604058256, __src=,
__dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f1e2b4d59af, arr=...) at
../../../src/codecs/postingcodec.cpp:42
#9  0x7f1f76135f74 in Baloo::PostingDB::get
(this=this@entry=0x7f1e2b4d5a90, term=...) at
../../../src/engine/postingdb.cpp:100
#10 0x7f1f76146b26 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:277
#11 0x7f1f7613e852 in Baloo::Transaction::commit
(this=this@entry=0x7f1e2b4d5b90) at ../../../src/engine/transaction.cpp:262
#12 0x0041c939 in Baloo::NewFileIndexer::run (this=0x127c5e0) at
../../../src/file/newfileindexer.cpp:75
#13 0x7f1f75a5a2f3 in QThreadPoolThread::run (this=0x12b48c0) at
thread/qthreadpool.cpp:93
#14 0x7f1f75a5d7fe in QThreadPrivate::start (arg=0x12b48c0) at
thread/qthread_unix.cpp:331
#15 0x7f1f746f3454 in start_thread (arg=0x7f1e2b4d6700) at
pthread_create.c:334
#16 0x7f1f7507ee5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1f76f58900 (LWP 9622)):
#0  0x7f1f75071dad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f72295740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f72251e84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f72252340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1f722524ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f1f75c94a3f in QEventDispatcherGlib::processEvents (this=0x11932f0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#6  0x7f1f75c3bd6a in QEventLoop::exec (this=this@entry=0x7ffdf0a41da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f1f75c43e0c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#8  0x0041698c in main (argc=1, argv=) at
../../../src/file/main.cpp:88

Possible duplicates by query: bug 356445.

Reported using DrKonqi

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

[kdevelop] [Bug 363341] New: Crashed unmarking breakpoint

[Leozito via KDE Bugzilla]

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

Bug ID: 363341
   Summary: Crashed unmarking breakpoint
   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.18
Qt Version: 4.8.7
Operating System: Linux 4.5.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160422) (x86_64)"

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

I was debugging a c++ code session then i unmarked a Breakpoint at the editor
and it crashed!

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

Thread 19 (Thread 0x7ff01a412700 (LWP 19558)):
#0  0x7ff03160903f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff0312d6a5a in  () at /usr/lib64/libQtScript.so.4
#2  0x7ff0312d6a89 in  () at /usr/lib64/libQtScript.so.4
#3  0x7ff031603424 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff0338e9add in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fef98fe9700 (LWP 19559)):
#0  0x7ff0338dd04d in read () at /lib64/libc.so.6
#1  0x7ff02dc1d400 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff02dbdae94 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff02dbdb308 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7ff02dbdb46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7ff0340d919e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7ff0340a9361 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7ff0340a9675 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x7ff033fa2a29 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x7ff03408a443 in  () at /usr/lib64/libQtCore.so.4
#10 0x7ff033fa520c in  () at /usr/lib64/libQtCore.so.4
#11 0x7ff031603424 in start_thread () at /lib64/libpthread.so.0
#12 0x7ff0338e9add in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7fef93d49700 (LWP 19561)):
#0  0x7ff0316093e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff033fa5702 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7ff0328bd656 in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0x2adc0b0) at
/usr/src/debug/kdevplatform-1.7.3/language/duchain/duchain.cpp:283
#3  0x7ff033fa520c in  () at /usr/lib64/libQtCore.so.4
#4  0x7ff031603424 in start_thread () at /lib64/libpthread.so.0
#5  0x7ff0338e9add in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fef922e7700 (LWP 19562)):
#0  0x7ff02dc1e6a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff02dbda999 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff02dbdb293 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff02dbdb46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff0340d919e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7ff0340a9361 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7ff0340a9675 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7ff033fa2a29 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7ff033fa520c in  () at /usr/lib64/libQtCore.so.4
#9  0x7ff031603424 in start_thread () at /lib64/libpthread.so.0
#10 0x7ff0338e9add in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fef8383e700 (LWP 19563)):
#0  0x7ff0338e107d in poll () at /lib64/libc.so.6
#1  0x7ff02dbdb364 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff02dbdb46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff0340d919e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7ff0340a9361 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7ff0340a9675 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7ff033fa2a29 in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7ff033fa520c in  () at /usr/lib64/libQtCore.so.4
#8  0x7ff031603424 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff0338e9add in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fef7315f700 (LWP 19570)):
#0  0x7ff02dc1e6c4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff02dbdaa10 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff02dbdb293 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff02dbdb46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff0340d919e 

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC|simg...@gmail.com   |

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

[kmail2] [Bug 363085] kmail window fails to display/load on second start

[Ryein Goddard via KDE Bugzilla]

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

--- Comment #5 from Ryein Goddard  ---
Does that mean a problem exists in the emptyTrashOnExit() function?  Because it
works while using the context menu right click.  Are they that different, or
does the trash empty program move the process to an external application
because the application closes before doing the empty process?

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

[kdenlive] [Bug 363340] Text outline thickness adjustment in titling module not saving.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kden |http://commits.kde.org/kden
   |live/2b8f8a59615f394fff52ed |live/d36a5e0dd81472f41f3545
   |2cc6a1c96dd60255e4  |e35462bb33d4e50ad6

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit d36a5e0dd81472f41f3545e35462bb33d4e50ad6 by Jean-Baptiste Mardelle.
Committed on 20/05/2016 at 20:33.
Pushed by mardelle into branch 'Applications/16.04'.

Fix text outline width incorrectly loaded on title editing

M  +1-1src/titler/titledocument.cpp

http://commits.kde.org/kdenlive/d36a5e0dd81472f41f3545e35462bb33d4e50ad6

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

[kdenlive] [Bug 363340] Text outline thickness adjustment in titling module not saving.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kden
   ||live/2b8f8a59615f394fff52ed
   ||2cc6a1c96dd60255e4
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 2b8f8a59615f394fff52ed2cc6a1c96dd60255e4 by Jean-Baptiste Mardelle.
Committed on 20/05/2016 at 20:32.
Pushed by mardelle into branch 'master'.

Fix text outline width incorrectly loaded on title editing

M  +1-1src/titler/titledocument.cpp

http://commits.kde.org/kdenlive/2b8f8a59615f394fff52ed2cc6a1c96dd60255e4

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #19 from Thomas Pfeiffer  ---
How about something like this?
http://www.iconarchive.com/show/windows-8-icons-by-icons8/Network-Disconnected-icon.html
That clearly shows that it's an unplugged plug and cannot be confused for a
speaker

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

[kmail2] [Bug 363085] kmail window fails to display/load on second start

[via KDE Bugzilla]

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

--- Comment #4 from bl...@vivaldi.net ---
This is the actual problematic piece of code

KSharedConfig::Ptr config =  KMKernel::config();
Akonadi::Collection trashCollection =
CommonKernel->trashCollectionFolder();
if (trashCollection.isValid()) {
if (KMailSettings::self()->emptyTrashOnExit()) {
Akonadi::CollectionStatisticsJob *jobStatistics = new
Akonadi::CollectionStatisticsJob(trashCollection);
if (jobStatistics->exec()) {
if (jobStatistics->statistics().count() > 0) {
mFolderCollectionMonitor->expunge(trashCollection, true
/*sync*/);
}
}
}
}

from kmkernel.cpp file.

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

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Stijn Tintel via KDE Bugzilla]

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

Stijn Tintel  changed:

   What|Removed |Added

 CC||stijn+b...@linux-ipv6.be

--- Comment #23 from Stijn Tintel  ---
(In reply to David Rosca from comment #19)
> Git commit d2f3147fd27ddb6b49f98592d4148fff306b0ebe by David Rosca.
Applied this diff to plasma-workspace-5.5.5. It seems to fix this problem for
me. Thanks!

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

[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below

[Allan via KDE Bugzilla]

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

--- Comment #14 from Allan  ---
Just testing closing a window on middle click in Enlightenment WM above
Konsole, as expected - nothing is passed down to Konsole.

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

[okular] [Bug 363326] Cannot change printing settings

[Krzysztof Tataradziński via KDE Bugzilla]

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

Krzysztof Tataradziński  changed:

   What|Removed |Added

 CC||ktatar...@gmail.com

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

[kdenlive] [Bug 363340] New: Text outline thickness adjustment in titling module not saving.

[Phillip Sear via KDE Bugzilla]

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

Bug ID: 363340
   Summary: Text outline thickness adjustment  in titling module
not saving.
   Product: kdenlive
   Version: 16.04.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: pccs...@gmail.com

The titling module allows the thickness of text outlining to be adjusted on a
scale of 0-10.  When adjustments are made using the module, they show up on the
module screen, but will only save as 0 or 10 (eg, if I choose thickness '5',
when I hit the OK button the thickness is saved as 10.  Incidentally I am using
v16.04.1, but it did not show as an option on the version menu.

Reproducible: Always

Steps to Reproduce:
1. New title clip from Project menu
2. Add text
3. Adjust Outline setting to 5
4. Hit OK to save
5.  Double click title clip in tree view, and click on text to edit


Actual Results:  
Outline size has defaulted to 10

Expected Results:  
Outline size should be 5

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

[krita] [Bug 362868] [AIPTEK] Krita crashes upon putting the stylus back onto the tablet

[- via KDE Bugzilla]

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

--- Comment #9 from -  ---
Good that I looked up similar bugs, before I submited a Bug Report.
(Krita Version: krita-3.0-RC-1-master-6f75b0f-x64)
First I want to confirm that this Bug also happens on the "Slim Tablet 600U"
from Aiptek as well. (with the same driver)

The Bug is easily reproducable following the instructions on Win7 Pro (x64)
with Service Pack 1

Following your experiments on the compatibility mode, I found out that it works
seemingly fine even on the "Win7-mode (without SP1)"

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

[krita] [Bug 362868] [AIPTEK] Krita crashes upon putting the stylus back onto the tablet

[- via KDE Bugzilla]

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

-  changed:

   What|Removed |Added

 CC||dr.prof.a...@gmail.com

--- Comment #8 from -  ---
Good that I looked up similar bugs, before I submited a Bug Report.

First I want to confirm that this Bug also happens on the "Slim Tablet 600U"
from Aiptek as well. (with the same driver)

The Bug is easily reproducable following the instructions on Win7 Pro (x64)
with Service Pack 1

Following your experiments on the compatibility mode, I found out that it works
seemingly fine even on the "Win7-mode (without SP1)"

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #18 from Kai Uwe Broulik  ---
Looks like a "muted" icon to me

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

[krita] [Bug 363320] Very bad performances on large files (can't draw)

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #15 from Camille Bissuel  ---
Another idea : the original very rought sketch in this file was done  with
mypaint in the .ora format.
I add it to the Drive (named "croquis-mlle-solange-4.ora"). So one layer in the
kra file is coming from ora. 
I tried to remove it with Krita 2.9 and open it again in Krita 3, but it
doesn't fix the bug.

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[andreas via KDE Bugzilla]

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

--- Comment #17 from andreas  ---
Created attachment 99105
  --> https://bugs.kde.org/attachment.cgi?id=99105=edit
mount unmount icons

better?

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

[systemsettings] [Bug 363325] KDE Systems setting crashes on exit - duplicate

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Already reported as bug 363323.

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||jwi...@gmail.com

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

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

[systemsettings] [Bug 363323] KDE Systems settings crashes on close

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 363339] New: plasmashell crashing after login

[Marlon Rodriguez via KDE Bugzilla]

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

Bug ID: 363339
   Summary: plasmashell crashing after login
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rac_swo...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Logged in, closed bug reports, restarted plasmashell.  Same crash.

The crash can be reproduced every time.

-- 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 0x7f9f7a6668c0 (LWP 3166))]

Thread 8 (Thread 0x7f9f65989700 (LWP 3169)):
#0  0x7f9f74d77e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9f78e3cc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9f78e3e8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f9f67ad7629 in QXcbEventReader::run (this=0xa2a4d0) at
qxcbconnection.cpp:1253
#4  0x7f9f7546d84e in QThreadPrivate::start (arg=0xa2a4d0) at
thread/qthread_unix.cpp:331
#5  0x7f9f7455a6fa in start_thread (arg=0x7f9f65989700) at
pthread_create.c:333
#6  0x7f9f74d83b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f9f5efc9700 (LWP 3171)):
#0  0x7f9f71b52a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f71b0d31e in g_main_context_acquire () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f71b0e1d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f71b0e42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f756a4a9b in QEventDispatcherGlib::processEvents
(this=0x7f9f580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f9f7564bdea in QEventLoop::exec (this=this@entry=0x7f9f5efc8ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f9f754688a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f9f77d103c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f9f7546d84e in QThreadPrivate::start (arg=0xaf99f0) at
thread/qthread_unix.cpp:331
#9  0x7f9f7455a6fa in start_thread (arg=0x7f9f5efc9700) at
pthread_create.c:333
#10 0x7f9f74d83b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f9f54782700 (LWP 3173)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9f5c725213 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f9f5c724937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f9f7455a6fa in start_thread (arg=0x7f9f54782700) at
pthread_create.c:333
#4  0x7f9f74d83b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f9f4fe77700 (LWP 3174)):
#0  0x7f9f71b52a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f71b0dd49 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f71b0e2c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f71b0e42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f756a4a9b in QEventDispatcherGlib::processEvents
(this=0x7f9f480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f9f7564bdea in QEventLoop::exec (this=this@entry=0x7f9f4fe76ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f9f754688a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f9f77d103c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f9f7546d84e in QThreadPrivate::start (arg=0xd9eb50) at
thread/qthread_unix.cpp:331
#9  0x7f9f7455a6fa in start_thread (arg=0x7f9f4fe77700) at
pthread_create.c:333
#10 0x7f9f74d83b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f9f4de2a700 (LWP 3175)):
#0  0x7f9f71b52a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f71b0e436 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f756a4a9b in QEventDispatcherGlib::processEvents
(this=0x7f9f48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7f9f7564bdea in QEventLoop::exec (this=this@entry=0x7f9f4de29ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f9f754688a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#5  0x7f9f77d103c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  

[KScreen] [Bug 356884] kscreen messes with original xrandr config, does not respect saved config, and apply defined config only on the second try.

[Allan via KDE Bugzilla]

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

Allan  changed:

   What|Removed |Added

 CC||kdeb...@metalight.dk

--- Comment #20 from Allan  ---
I'm also affected by this. Running KDE 5.6.4 on Arch Linux on nvidia gtx970.

Regardless if I setup my two monitors in the xorg.conf or with display and
monitor in systemsettings - the setup seems not to be respected on reboot.

Workaround: set monitors up in xorg.conf and disable kscreen2 in
startup systemsettings.

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

[plasmashell] [Bug 363338] Configuration of icons (Automatic/Show/Hide) won't work

[Diego Rubert via KDE Bugzilla]

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

--- Comment #1 from Diego Rubert  ---
Created attachment 99104
  --> https://bugs.kde.org/attachment.cgi?id=99104=edit
The system tray options (in brazilian portuguese)

The system tray options (in brazilian portuguese)

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

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

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #103 from Thomas Lübking  ---
Probably. There're mentions it'd only fire on FBOs, but since those would
likely go alongside.
Unfortunately it's not even (yet) linked in
https://developer.nvidia.com/nvidia-opengl-specs so far (bleeding edge beta
feature)

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

[konsole] [Bug 340031] vim cursorline not cleared properly

[Nick via KDE Bugzilla]

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

Nick  changed:

   What|Removed |Added

 CC||futurepi...@gmx.us

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

[plasmashell] [Bug 363338] New: Configuration of icons (Automatic/Show/Hide) won't work

[Diego Rubert via KDE Bugzilla]

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

Bug ID: 363338
   Summary: Configuration of icons (Automatic/Show/Hide) won't
work
   Product: plasmashell
   Version: 5.6.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: diegorub...@gmail.com

When I set options to automatic, show or hide icons, select OK and return to
the same screen, all items are set to Automatic and just clipboard icon is set
to Show (maybe the word isn't "show", my environment is in brazilian
portuguese). I can't control what items I want to see and what items I want to
be hidden.

Reproducible: Always

Steps to Reproduce:
1. Right click on the widget
2. Configurations
3. Change options at proper tab

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

[krita] [Bug 363334] Memory full when working with large files

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #3 from Boudewijn Rempt  ---
Also, don't hesitate to test-drive the 3.0 builds -- they are appimages, so
it's just a download, make executable and execute. No installation needed!

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

[systemsettings] [Bug 301622] Mouse pointer gets huge if a second large screen is connected

[José Tomás Atria via KDE Bugzilla]

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

José Tomás Atria  changed:

   What|Removed |Added

 CC||jtat...@gmail.com

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

[krita] [Bug 363320] Very bad performances on large files (can't draw)

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #14 from Boudewijn Rempt  ---
> Are there any change in the file format between 2.9 and 3 ?

Only for the animation support.

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

[krita] [Bug 363320] Very bad performances on large files (can't draw)

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #13 from Camille Bissuel  ---
Your last comment made me do one last test : Open other big files in Krita 3
RC1 (based on the same 8K template).
Interestingly, only the file created today with Krita 3 triggered this bug.
Older files created with Krita 2.9 or Krita 2.8 are not.
But the bigger one I found ("radical-dreaming.kra" made with Krita 2.9) crashed
Krita 3 when my pen was close enough to be detected. Reopening once again it
worked.

I'm uploading big files here (upload will take two or three hours), so you can
test :
https://drive.google.com/open?id=0B-5J--XsvWh-Z3lWVksyVlJwMzA
"D12.kra" and "radical-dreaming.kra" are 2.9 files
"illustration-mlle-solangel.kra" and "illustration-mlle-solange-final.kra" are
new files created a few days ago and finished today with Krita 3.

Are there any change in the file format between 2.9 and 3 ?

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

[plasmashell] [Bug 363337] New: Recent docs/history shortcuts in kicker/kickoff fail when clicked with "Could not find any application or handler..." error

[Rik Mills via KDE Bugzilla]

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

Bug ID: 363337
   Summary: Recent docs/history shortcuts in kicker/kickoff fail
when clicked with  "Could not find any application or
handler..." error
   Product: plasmashell
   Version: master
  Platform: unspecified
   URL: http://i.imgur.com/twoUpUZ.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: rik.mill...@gmail.com
CC: plasma-b...@kde.org

Recent docs/history shortcuts in kicker/kickoff fail when clicked with  "Could
not find any application or handler..." for the file; error in a plasma error
popup (see url link).

Seems to be associated with running plasma with latest frameworks 5.22. Testing
with previous frameworks 5.21 with same plasma version does not produce the
error. 

Reproducible: Always

Steps to Reproduce:
1. Install plasma 5.6.4 or above with frameworks v 5.22
2. Activate kicker/kickoff menu and navigate to history/recent document lists 
3. Click desired recent item of ANY type

Actual Results:  
Error "Could not find any application or handler..." for the file, in a plasma
error popup (see url link)

Expected Results:  
Should launch application for file association, and load recent document.

Tested on.

With bug occurring:
- kubuntu plasma 5.6.4 backport testing packages with frameworks 5.22
- kde-neon user and dev editions with plasma 5.6.4 and 5.6.90, and frameworks
5.22
- archlinux plasma 5.6.4, with frameworks 5.22 from their 'testing' repo

Without bug occurring:
- archlinux plasma 5.6.4 with frameworks 5.21

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

[Akonadi] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1

[Jay Ambee via KDE Bugzilla]

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

--- Comment #18 from Jay Ambee  ---
Hello again --- Good to see I am not the only one with this problem, with which
I had a few interesting days (up to today ...).
After installing Framework 5.22 and Plasma 5.6.4 and a restart akonadi
miraculously started working again (I swear, I didn't change anything in my
config). I had - finally - the time to move my emails to my imap server. Took
some time, though, but now I have access to everything through thunderbird
(which in my is hot quite as powerful as kontact would be). Because ... after
installing KDE Apps 16.04.1 and some further tweaking on my side (see the
following points) all the splendour has vanished again... but not directly - a
few strange things happened:
1. After I changed the Inboxes of my external Email-Accounts to the Inbox of
the IMAP Server, the complete local-mail folder structure "disappeared" (from
kontact - it still exists on my harddrive) for no apparent reason. I later
found out that there had been created an new ".local-mail" folder without me
requesting it. I can live with that for now, but would really like to know how
that happens, and why.

2. Interestingly my calendars and contacts where completely gone from kontact
(and akonadi) - not the data, but all the configs, which makes sense in the
light of the following:

3.  As I have my calendars and my contacts on a dav-server (Owncloud at my
hosting provider, which has been working like a charm until the problem with
akonadi/kontact started (and still does, as far as my mobile devices are
concerned), I wanted to keep it that way, but move to the builtin servers on my
synology nas. This seemed to be working fine (with some minor glitches which I
would have tolerated), but when I was "nearly done", (having my calendars
working and imported my contacts) as something "blocked" plasma (I could not
switch programs or anything) and I had to reboot the system. After that, I was
back with my friend "akonadi not working properly" and had to return to
Thunderbird as my PIM system (which is not my first choice for numerous
reasons).

My "educated guess" now is, that there is something wrong with the akonadi
infrastructure for korganizer/kaddressbook, not necessarily with relation to
the DAV subsystem (since this seems to have worked). 
But that´s just a guess. Maybe all this is still just a config problem, but to
solve it, I would like to start from scratch for a test (at least everything
seems to work "in principle"). Which parts of the akonadi data an the config do
I have to delete for that??

Thanks, still, for your help.

Jay

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

[partitionmanager] [Bug 363294] KDE Partition Manager crashes on exit if QFileDialog is used

[Andrius Štikonas via KDE Bugzilla]

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

--- Comment #1 from Andrius Štikonas  ---
Bug 356700 has very similar backtrace

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

[kdebugsettings] [Bug 356700] Segmentation fault after saving to a file and pressing OK

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||andr...@stikonas.eu

--- Comment #1 from Andrius Štikonas  ---
Note that this looks very similar to bug 363294

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

[dolphin] [Bug 355870] Drag and Drop severely slows down when dragging icons (51.12 Beta)

[Joe via KDE Bugzilla]

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

Joe  changed:

   What|Removed |Added

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

--- Comment #3 from Joe  ---
Closing out as it no longer does this in the latest Dolphin release.

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

[kmix] [Bug 355706] Kmix Random Crashes

[Joe via KDE Bugzilla]

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

Joe  changed:

   What|Removed |Added

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

--- Comment #1 from Joe  ---
I am going to close this out as it hasn't crashed on me for a couple of
releases now.

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

[krita] [Bug 363334] Memory full when working with large files

[SylviaRitter via KDE Bugzilla]

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

--- Comment #2 from SylviaRitter  ---
Hello :).

Thanks for the fast reply. I've updated Krita to 2.9.11 and i will let you know
during the next six days if the memory consumption is still a huge problem. I'm
on a 64 bits version of Ubuntu.
I've also updated the other bug reports for 2.9.11.

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

[kwin] [Bug 361241] Double click to maximize does not work in some situations

[Allan via KDE Bugzilla]

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

Allan  changed:

   What|Removed |Added

 CC||kdeb...@metalight.dk

--- Comment #5 from Allan  ---
A similar scenario, KDE 5.6.4 (Archlinux).

Double click titlebar to lower, is configured, i find that:

- Triple click is needed in 5.6.4 when just entering the window and not
manipulating it beforehand.
- Not in 5.5.5, so a regression.
- Funnily double click to lower works- when the window is first dragged or has
it’s border clicked once (not titlebar).

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

[plasmashell] [Bug 363336] Since upgrading to 16.04 three weeks ago I have been plagued with numerous plasma panel system tray crashes

[Ralph Green via KDE Bugzilla]

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

Ralph Green  changed:

   What|Removed |Added

 CC||rocky1...@comcast.net

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

[krita] [Bug 363335] Lock for the mirror tool.

[SylviaRitter via KDE Bugzilla]

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

SylviaRitter  changed:

   What|Removed |Added

Version|2.9.7   |2.9.11

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

[krita] [Bug 363327] "Set horizontal/vertical mirror mode" button, reset option

[SylviaRitter via KDE Bugzilla]

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

--- Comment #1 from SylviaRitter  ---
I've updated Krita to 2.9.11. When I'm opening a new file now the mirror axis
in the middle of the canvas, perfect! It would still be great to be able to
reset it at any time, in case it changed the position. Or a lock would be very
helpful: Bug 363335 - Lock for the mirror tool
https://bugs.kde.org/show_bug.cgi?id=363335. Thanks :).

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

[plasmashell] [Bug 363336] New: Since upgrading to 16.04 three weeks ago I have been plagued with numerous plasma panel system tray crashes

[Ralph Green via KDE Bugzilla]

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

Bug ID: 363336
   Summary: Since upgrading to 16.04 three weeks ago I have been
plagued with numerous plasma panel system tray crashes
   Product: plasmashell
   Version: master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rocky1...@comcast.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Created attachment 99103
  --> https://bugs.kde.org/attachment.cgi?id=99103=edit
Crash report

Crashes start shortly after boot up and starting Thunderbird.  These crashes
happen hundreds of times a day and seem to be triggered by dropping the cursor
into the task manager bar  area.
It seems starting Thunderbird sets the stage and shutting it down seems to
lessen the crashes.

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 0x7f975ef078c0 (LWP 3117))]

Thread 12 (Thread 0x7f974a04d700 (LWP 3120)):
#0  0x7f97595a0e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f975d6afc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f975d6b18d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f974c1c7629 in QXcbEventReader::run (this=0x1c74670) at
qxcbconnection.cpp:1253
#4  0x7f9759ca384e in QThreadPrivate::start (arg=0x1c74670) at
thread/qthread_unix.cpp:331
#5  0x7f9758d756fa in start_thread (arg=0x7f974a04d700) at
pthread_create.c:333
#6  0x7f97595acb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f97435ed700 (LWP 3122)):
#0  0x7f975959c9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f975630b6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f97562c7e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f97562c82c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f97562c842c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9759edaa9b in QEventDispatcherGlib::processEvents
(this=0x7f973c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f9759e81dea in QEventLoop::exec (this=this@entry=0x7f97435ecce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f9759c9e8a4 in QThread::exec (this=this@entry=0x1d4c930) at
thread/qthread.cpp:503
#8  0x7f975c5673c5 in QQmlThreadPrivate::run (this=0x1d4c930) at
qml/ftw/qqmlthread.cpp:141
#9  0x7f9759ca384e in QThreadPrivate::start (arg=0x1d4c930) at
thread/qthread_unix.cpp:331
#10 0x7f9758d756fa in start_thread (arg=0x7f97435ed700) at
pthread_create.c:333
#11 0x7f97595acb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f9738b85700 (LWP 3127)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9740ce4aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f9740ce4907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f9758d756fa in start_thread (arg=0x7f9738b85700) at
pthread_create.c:333
#4  0x7f97595acb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f9738384700 (LWP 3128)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9740ce4aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f9740ce4907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f9758d756fa in start_thread (arg=0x7f9738384700) at
pthread_create.c:333
#4  0x7f97595acb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f9737b83700 (LWP 3129)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9740ce4aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f9740ce4907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f9758d756fa in start_thread (arg=0x7f9737b83700) at
pthread_create.c:333
#4  0x7f97595acb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f9737382700 (LWP 3130)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9740ce4aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f9740ce4907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f9758d756fa in start_thread (arg=0x7f9737382700) at
pthread_create.c:333
#4  0x7f97595acb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f9732b0d700 (LWP 3131)):
#0  0x7f97595a0e8d in poll () at 

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[Simon Lewis via KDE Bugzilla]

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

Simon Lewis  changed:

   What|Removed |Added

 CC||simon.le...@slnet-online.de

--- Comment #18 from Simon Lewis  ---
Fixed version of breeze-gtk that works with apps built against gtk-3.20 can
found at:

https://github.com/FadeMind/breeze-gtk

Works perfectly when installed on my manjaro / kde desktop installation. ..

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

[kate] [Bug 284474] Kate doesn't open 1 instance per activity

[Todd via KDE Bugzilla]

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

Todd  changed:

   What|Removed |Added

 CC||toddrme2...@gmail.com

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

[krita] [Bug 363331] Feature request: Krita restores settings after restart.

[SylviaRitter via KDE Bugzilla]

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

SylviaRitter  changed:

   What|Removed |Added

Version|2.9.7   |2.9.11

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

[yakuake] [Bug 363333] Processes started in yakuake terminals block indefinitely some time after switching to a different VT

[Jaak Ristioja via KDE Bugzilla]

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

Jaak Ristioja  changed:

   What|Removed |Added

Summary|Processes started in|Processes started in
   |yakuake terminals block |yakuake terminals block
   |indefinitely ~45s after |indefinitely some time
   |switching to a different VT |after switching to a
   ||different VT

--- Comment #2 from Jaak Ristioja  ---
I think the ~45s period might be mplayer specific. Probably some OS buffer gets
full because the other end (Yakuake) is not reading.

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

[krita] [Bug 363335] New: Lock for the mirror tool.

[SylviaRitter via KDE Bugzilla]

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

Bug ID: 363335
   Summary: Lock for the mirror tool.
   Product: krita
   Version: 2.9.7
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: sylvia.rit...@duangle.com

I often accidentally move the mirror tool while painting. 

Reproducible: Always

Steps to Reproduce:
1. Set mirror mode and try to lock it.
2.
3.

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

[krita] [Bug 363334] Memory full when working with large files

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hi Silvia,

Thanks for your bug reports! Unfortunately, Ubuntu 16.04 only comes with Krita
2.9.7, which is pretty old -- the 2.9 series is now at 2.9.11, and memory
consumption is one of the things that got improved along the road, though Krita
is still quite hungry for memory. We're now working towards the first release
of Krita 3.0. Are you on a 32 or 64 bits version of Ubuntu?

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

[yakuake] [Bug 363333] Processes started in yakuake terminals block indefinitely ~45s after switching to a different VT

[Jaak Ristioja via KDE Bugzilla]

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

--- Comment #1 from Jaak Ristioja  ---
More information:
* Only happens when Yakuake is left visible (i.e. "dropped down") when leaving
the VT.
* Switching back to the VT with Yakuake immediately resumes the blocked
process, even if VT is locked.
* Bug does not occur when process is launched in Konsole instead of Yakuake.

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

[krita] [Bug 363327] "Set horizontal/vertical mirror mode" button, reset option

[SylviaRitter via KDE Bugzilla]

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

SylviaRitter  changed:

   What|Removed |Added

   Severity|normal  |major

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

[kmail2] [Bug 363027] KMail 16.04.0: Per folder HTML settings are not working

[Laurent Montel via KDE Bugzilla]

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

--- Comment #6 from Laurent Montel  ---
(In reply to Till Schäfer from comment #5)
> cool/THX! I was just checking out kdepim.git to try to fix it myself :-) 
> 
> Regarding the "load external ref" option: I am not sure if it was there.
> Maybe i just was used to it from the contact editor. 
> Background: I only moved to the per folder settings because of Bug 363024
> (both above mentioned html option were removed from the contact settings).

I know it was removed as I didn't find a good area to put it in new interface.
It's still on my todo list.

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

[krita] [Bug 363331] Feature request: Krita restores settings after restart.

[SylviaRitter via KDE Bugzilla]

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

SylviaRitter  changed:

   What|Removed |Added

   Severity|normal  |major

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

[krita] [Bug 363334] Memory full when working with large files

[SylviaRitter via KDE Bugzilla]

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

SylviaRitter  changed:

   What|Removed |Added

   Severity|major   |grave

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

[krita] [Bug 363334] Memory full when working with large files

[SylviaRitter via KDE Bugzilla]

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

SylviaRitter  changed:

   What|Removed |Added

   Severity|normal  |major

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

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

[Fahad Alduraibi via KDE Bugzilla]

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

--- Comment #57 from Fahad Alduraibi  ---
(In reply to Troy Volin from comment #56)
> Created attachment 99093 [details]
> attachment-29857-0.html
> 

> Fedora doesn't present a "save session" on the Leave menu, but I can do it
> through qdbus. I guess I'll give that a try, and use "saved session" from
> kdm.

Actually it does, I just tried the manual restore and a new item shows right
below logout and called "Save Session" and it doesn't have an icon too.

The manual option restores the kde apps I tested it with (no GTK), while the
auto "restore previous ..." doesn't restore any thing at all, and I get a clean
desktop even though ksmserverrc has them listed even after I login

restartCommand1=kwin_x11,-session,10b4dad3da00014637604640111720001_1463760707_7673
restartCommand2=/usr/bin/owncloud,-session,10b4dad3da00014637604640111720007_1463760706_950741
restartCommand3=/usr/bin/kwalletd5,-session,10b4dad3da00014637604640111720009_1463760706_952608
restartCommand4=/usr/bin/konsole,-session,10b4dad3da00014637604820111720012_1463760706_957934
restartCommand5=/usr/bin/dolphin,-session,10b4dad3da00014637604940111720013_1463760706_952905
restartCommand6=/usr/bin/dolphin,-session,10b4dad3da00014637606890120380011_1463760706_953994
restartCommand7=/usr/bin/konsole,-session,10b4dad3da00014637606970120380012_1463760706_956747


that is on my laptop, on the desktop i haven't tested the manual option, but
the auto way only restores Konsole windows and their current paths are reset to
the default which means it is restarting it fresh.

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

[krita] [Bug 363320] Very bad performances on large files (can't draw)

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #12 from Boudewijn Rempt  ---
Hm, on my mac, I can confirm that everything is really slow, and the file
crashes Krita in my Linux vm. So my first guess was that there were lots of
pixels outside the image, but that's not true either. On the other hand, Krita
2.8 in another VM also couldn't load the file at all... I guess I need to
investigate on my desktop, back at home.

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

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

[Nick Guletskii via KDE Bugzilla]

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

--- Comment #102 from Nick Guletskii  ---
Could the new NV_robustness_video_memory_purge extension be used to detect when
to trigger an update?

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

[krita] [Bug 363334] New: Memory full when working with large files

[SylviaRitter via KDE Bugzilla]

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

Bug ID: 363334
   Summary: Memory full when working with large files
   Product: krita
   Version: 2.9.7
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: sylvia.rit...@duangle.com

I often need to create large files (~9500x4500px) to print large artworks.
With lots of layers Krita gets quickly slowly and then I get a memory problem.
Every 15-20 minutes it freezes and the screen turns grey-black. I have to wait
3-5 minutes till I can continue with my work and this can be very distracting. 
It would be great to know what is going on. The grey-black screen doesn't give
me any information. Maybe a box could answer these questions: How long do I
have to wait? What is the problem and how can I fix it? I would like to avoid
closing Krita if this problem occurs. Mostly because Krita doesn't restores all
of my settings: Bug 363331 - Feature request: Krita restores settings after
restart - https://bugs.kde.org/show_bug.cgi?id=363331
I hope the performance will improve in the future.


Reproducible: Always

Steps to Reproduce:
1.Not easy to reproduce ;). Paint a ~9500x4500px file with many details like
this one http://sylviaritter.deviantart.com/art/Quantal-Quetzal-609390302.
2.
3.

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

[kmail2] [Bug 363027] KMail 16.04.0: Per folder HTML settings are not working

[Till Schäfer via KDE Bugzilla]

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

--- Comment #5 from Till Schäfer  ---
cool/THX! I was just checking out kdepim.git to try to fix it myself :-) 

Regarding the "load external ref" option: I am not sure if it was there. Maybe
i just was used to it from the contact editor. 
Background: I only moved to the per folder settings because of Bug 363024 (both
above mentioned html option were removed from the contact settings).

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

[yakuake] [Bug 363333] New: Processes started in yakuake terminals block indefinitely ~45s after switching to a different VT

[Jaak Ristioja via KDE Bugzilla]

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

Bug ID: 36
   Summary: Processes started in yakuake terminals block
indefinitely ~45s after switching to a different VT
   Product: yakuake
   Version: 3.0.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: j...@ristioja.ee

This seems to be a regression after upgrading from kde-misc/yakuake-2.9.9-r3 to
kde-misc/yakuake-3.0.2 together with the upgrade from KDE4 to KF5.

Reproducible: Always

Steps to Reproduce:
1. Open two KDE sessions with yakuake
2. Run mplayer somemusicfile.mp3
3. Switch to another VT using Ctrl+Alt+F1, for example.
4. Wait ~45s

Actual Results:  
The application wanting to write something to stdout blocks:

  gdb:
#0  0x688bef0b3610 in __write_nocancel () at
../sysdeps/unix/syscall-template.S:84
  strace:
write(1, "A: 245.1 (04:05.1) of 346.8 (05:"..., 48
  # ls /proc/`pidof mplayer`/fd/1 -lhd
lrwx-- 1 myser mygroup 64 mai   20 19:13 /proc/4550/fd/1 -> /dev/pts/4

Expected Results:  
Process does not block.

Backtrace of yakuake during block:

(gdb) thread apply all bt full

Thread 2 (Thread 0x78c72a55f700 (LWP 3354)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
No locals.
#1  0x78c7346f0f09 in _xcb_conn_wait (c=c@entry=0x69552506800,
cond=cond@entry=0x69552506840, vector=vector@entry=0x0, count=count@entry=0x0)
at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:427
ret = 
fd = {fd = 603994464, events = 30919, revents = 0}
#2  0x78c7346f30df in xcb_wait_for_event (c=0x69552506800) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
ret = 0x0
#3  0x78c72bd26899 in QXcbEventReader::run (this=0x69552510e90) at
qxcbconnection.cpp:1229
event = 
#4  0x78c7368ffc1c in QThreadPrivate::start (arg=0x69552510e90) at
thread/qthread_unix.cpp:331
__clframe = {__cancel_routine = 0x78c7368fe8e0
, __cancel_arg = 0x69552510e90, __do_it = 1,
__cancel_type = }
thr = 0x69552510e90
data = 0x695525111f0
objectName = {static null = {}, d = 0x78c736bd9660
}
#5  0x78c732f5464c in start_thread (arg=0x78c72a55f700) at
pthread_create.c:334
__res = 
pd = 0x78c72a55f700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {132796804101888,
7985632438364207210, 135822295332368, 135822295332127, 0, 132796804101888,
7985632438318069866, 7985615675874539626}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#6  0x78c7361e183d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
No locals.

Thread 1 (Thread 0x78c72bfed780 (LWP 3352)):
#0  0x78c7361d7a4d in poll () at ../sysdeps/unix/syscall-template.S:84
No locals.
#1  0x78c7346f0c6a in poll (__timeout=-1, __nfds=1, __fds=0x7b8797aa7090)
at /usr/include/bits/poll2.h:46
No locals.
#2  _xcb_conn_wait (c=c@entry=0x69552506800, cond=cond@entry=0x7b8797aa71c0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
ret = 
fd = {fd = 3, events = 1, revents = 0}
#3  0x78c7346f2d5f in wait_for_reply (c=c@entry=0x69552506800,
request=4247, e=e@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:516
cond = {__data = {__lock = 0, __futex = 2, __total_seq = 1,
__wakeup_seq = 1, __woken_seq = 1, __mutex = 0x69552506818, __nwaiters = 0,
__broadcast_seq = 0}, __size =
"\000\000\000\000\002\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\030hPR\225\006\000\000\000\000\000\000\000\000\000",
__align = 8589934592}
reader = {request = 4247, data = 0x7b8797aa71c0, next = 0x0}
ret = 0x0
#4  0x78c7346f2e98 in xcb_wait_for_reply (c=0x69552506800, request=4247,
e=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:546
ret = 
#5  0x78c72bd1f8b0 in QXcbConnection::sync (this=0x69552505210) at
qxcbconnection.cpp:1839
cookie = 
#6  0x78c72bd46705 in QXcbShmImage::preparePaint (this=0x69552524810,
region=...) at qxcbbackingstore.cpp:286
region = 
this = 0x69552524810
#7  0x78c72bd46ae8 in QXcbBackingStore::beginPaint (this=0x695526307d0,
region=...) at qxcbbackingstore.cpp:324
dpr = 
windowDpr = 
#8  0x78c737466c25 in QWidgetBackingStore::beginPaint
(toCleanIsInTopLevelCoordinates=true, returnInfo=,
backingStore=, widget=, toClean=...,
this=0x69552747090) at 

[plasmashell] [Bug 362509] Plasna crashes on clicking on tasks panel

[Ralph Green via KDE Bugzilla]

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

Ralph Green  changed:

   What|Removed |Added

 CC||rocky1...@comcast.net

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