[Breeze] [Bug 355676] Many plasmoids missing icon in panel

[andreas_k via KDE Bugzilla]

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

andreas_k  changed:

   What|Removed |Added

 CC||andrea...@abwesend.de

--- Comment #4 from andreas_k  ---
thank you very much I'm not an coding expert and forget to add the new folder
to the cmake file. thanks for your replay. the change was added to master.

https://quickgit.kde.org/?p=breeze-icons.git=commit=5b3a64f22c5b5c2db569b04b5e6c7792b92dfbfe

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

[telepathy] [Bug 356268] Some contacts still shown as online when going offline

[Ondřej Kučera via KDE Bugzilla]

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

--- Comment #1 from Ondřej Kučera  ---
Created attachment 95894
  --> https://bugs.kde.org/attachment.cgi?id=95894=edit
Screenshot

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

[kwin] [Bug 356205] Applications are minimized and Windows decorations disappear after monitor turned off

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=341497,
   ||https://bugs.kde.org/show_b
   ||ug.cgi?id=353428

--- Comment #2 from Thomas Lübking  ---
I bet on bug #341497 + bug #353428

The output is removed, plasmashell resizes to 0,0 - the strutted workspace with
it, KWin shrinks the windows accordingly and Qt happily crashes because of
341497 and kwin doesn't restart as it fails to claim selection because of
353428 (plasmashell may or may not crash because of 341497, but will have less
trouble restarting)

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

[plasmashell] [Bug 356023] Enable "Press and hold" even when widgets are locked

[Gregor Mi via KDE Bugzilla]

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

--- Comment #2 from Gregor Mi  ---
My intuitive impression of the purpose of locking was to prevent _accidental_
changes to the desktop configuration, although I did not find this in writing
(e.g. https://userbase.kde.org/Plasma/Panels#Locking only tells that there is
locking but not why).

I can imagine that locking might have security relevance in kiosk mode
scenarios, has it? Please clarify.

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

[kdenlive] [Bug 356187] icons missing in 15.11.80

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 6981a199975eec13a7db17fa0992c2d83491694a by Jean-Baptiste Mardelle.
Committed on 02/12/2015 at 09:33.
Pushed by mardelle into branch 'Applications/15.12'.

Fix missing larger / smaller track icons

M  +2-2src/timeline/timeline.cpp

http://commits.kde.org/kdenlive/6981a199975eec13a7db17fa0992c2d83491694a

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

[kstart] [Bug 277775] KDE Autostart / kstart starts 2 apps in wrong desktop (mixed up)

[via KDE Bugzilla]

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

dd...@samba.org changed:

   What|Removed |Added

 CC||dd...@samba.org

--- Comment #2 from dd...@samba.org ---
I see the same issue with using autostart with KDE Plasma 5.4.3 (openSUSE Leap
42.1).
"kstart --desktop X" is ineffective - all autostart programs start on desktop 1

This bug has also been discussed in the forums:
https://forum.kde.org/viewtopic.php?f=66=101023

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

[kontact] [Bug 356271] New: Kontact closes when I click on New Message

[clivejo via KDE Bugzilla]

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

Bug ID: 356271
   Summary: Kontact closes when I click on New Message
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: cliv...@aol.com

Every-time I click on New Message, Kontact closes.  However, the system doesn't
seem to recognise it as a crash.  To send a new message, I have to reply to an
old message and change all the fields.  

My system is Kubuntu 16.04 (Xenial) running Kontact 5.0.2 (I cant find this
version in the Scroll box above).  Please advice how to get a proper bug
report.

Reproducible: Always

Steps to Reproduce:
1. Open Kontact
2. Click on the "New Message" button

Actual Results:  
Kontact terminates

Expected Results:  
Display a window were I can write a new email message

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

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

[Daniel Trebbien via KDE Bugzilla]

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

--- Comment #5 from Daniel Trebbien  ---
I contacted Apple Developer Relations about the crash and they informed me that
unlike gdb, lldb does not have an initial target definition set, and relies on
the gdbserver to tell it which registers the gdbserver supports.  This can be
done either by responding to 'qRegisterInfo XX' packets or to
'qXfer:features:read:target.xml'.

They also informed me about the
plugin.process.gdb-remote.target-definition-file LLDB setting and the example
target definitions at
http://llvm.org/svn/llvm-project/lldb/trunk/examples/python/
I can confirm that using either x86_64_linux_target_definition.py or
x86_64_target_definition.py fixes the segfault issue.

I have posted a message to lldb-dev to ask if anyone can see why the XML target
definition sent back by the embedded gdbserver might be causing the crash:
http://lists.llvm.org/pipermail/lldb-dev/2015-December/009011.html

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

[kdenlive] [Bug 356100] Image Sequence is default Render profile

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from qubo...@gmail.com ---
Persists (re-introduced?) in v15.11.80-53-g0918054

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

[ark] [Bug 320806] ark extract corrupted files (which actually are not corrupt)

[Damian Ivanov via KDE Bugzilla]

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

--- Comment #3 from Damian Ivanov  ---
Maybe next time on a bug where a file archiver/extracter corrupts data you
respond earlier than 2 and a half years? :)

BUG persists:
http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/frozen-bubble-2.212-11.1.x86_64.rpm

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

[ark] [Bug 320806] ark extract corrupted files (which actually are not corrupt)

[Damian Ivanov via KDE Bugzilla]

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

Damian Ivanov  changed:

   What|Removed |Added

 CC||damianator...@gmail.com

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

[digikam] [Bug 287405] BQM AdjustCurves tool : Load curves settings file

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.0.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/e2c2cca610a5833a7bb45b7
   ||5315fdff10e6c54aa
 Resolution|--- |FIXED

--- Comment #3 from Maik Qualmann  ---
Git commit e2c2cca610a5833a7bb45b75315fdff10e6c54aa by Maik Qualmann.
Committed on 04/12/2015 at 11:35.
Pushed by mqualmann into branch 'master'.

add button for load settings file to the BQM adjust curves tool
FIXED-IN: 5.0.0

M  +2-2NEWS
M  +26   -5utilities/queuemanager/basetools/color/curvesadjust.cpp
M  +2-1utilities/queuemanager/basetools/color/curvesadjust.h

http://commits.kde.org/digikam/e2c2cca610a5833a7bb45b75315fdff10e6c54aa

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

[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal

[Villu Ruusmann via KDE Bugzilla]

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

--- Comment #23 from Villu Ruusmann  ---
Has any work been done on this? I've been applying all Fedora 23 updates, and I
just realized that my issue has probably gone away - there has been no need to
kill drkonqi during last sessions.

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

[kdeplasma-addons] [Bug 356269] New: Can't directly type Chinese.

[via KDE Bugzilla]

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

Bug ID: 356269
   Summary: Can't directly type Chinese.
   Product: kdeplasma-addons
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Dashboard
  Assignee: h...@kde.org
  Reporter: laichiah...@outlook.com
CC: plasma-b...@kde.org

I can't directly type Chinese to search applications

Reproducible: Always

Steps to Reproduce:
1.open the dashboard
2.try to type Chinese
3.it is English

Actual Results:  
I have to type 1 letter and switch the input method, and I have to do it every
time.

Expected Results:  
I can directly type Chinese in the Dashboard.

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

[kmail2] [Bug 220209] Make it possible to edit the source of a HTML mail

[Phil Schaf via KDE Bugzilla]

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

Phil Schaf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||flying-sh...@web.de
 Ever confirmed|0   |1

--- Comment #6 from Phil Schaf  ---
a very annoying thing is e.g. that you can’t break out of a blockquote to reply
inline.

pressing backspace or dedent while on a blank line inside of a blockquote
should basically insert  and place the cursor on
the blank line.

but until then i at least need *any* way to do it – e.g. a way to edit the
source.

and don’t get me wrong: that functionality is also necessary after the composer
became perfect – some things will never be possible otherwise

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

[Leon via KDE Bugzilla]

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

--- Comment #18 from Leon  ---
Hi Leslie,
thanks for the link. I have found FolderView.qml (on my system it was here:
/usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/) and added
the else if clause.

But the file foldermodel.h does not seem to be on my system. 
Without those changes STRG+X and STRG+C do not work.
What should I do now?

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

[amarok] [Bug 356267] File organizer scheme preset doesn't save

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
  Component|Collections/Local   |Collections/Organize Files
   ||Dialog

--- Comment #1 from Myriam Schweingruber  ---
known issue

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

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

[digikam] [Bug 356282] New: DIGIKAM SE CIERRA AL EXPORTAR FOTO AL CORREO ELECTRONICO

[Emilio O via KDE Bugzilla]

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

Bug ID: 356282
   Summary: DIGIKAM SE CIERRA AL EXPORTAR FOTO AL CORREO
ELECTRONICO
   Product: digikam
   Version: 4.0.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: emilioo...@hotmail.com

Application: digikam (4.0.0)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-38-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed: He reiniciado la aplicación y
funciona con normalidad. En el momento del cierre tenía abierto darktable.

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

Thread 7 (Thread 0x7fee366ef700 (LWP 2601)):
#0  0x7fee549fb12d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fee3ae4f248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7fee50ecf182 in start_thread (arg=0x7fee366ef700) at
pthread_create.c:312
#3  0x7fee54a0847d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7fee2b6a5700 (LWP 2602)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fee566e1816 in wait (time=18446744073709551615, this=0xec5a30) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0xf2a630, mutex=mutex@entry=0xf2a628,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x005e3d9e in Digikam::ScanController::run (this=0xef6220) at
/build/buildd/digikam-4.0.0/core/digikam/database/scancontroller.cpp:725
#4  0x7fee566e132f in QThreadPrivate::start (arg=0xef6220) at
thread/qthread_unix.cpp:349
#5  0x7fee50ecf182 in start_thread (arg=0x7fee2b6a5700) at
pthread_create.c:312
#6  0x7fee54a0847d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fee2aea4700 (LWP 2603)):
#0  __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7fee1c000a80) at
pthread_mutex_unlock.c:51
#1  __GI___pthread_mutex_unlock (mutex=0x7fee1c000a80) at
pthread_mutex_unlock.c:310
#2  0x7fee4d96f9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fee4d92e0f6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fee568107be in QEventDispatcherGlib::processEvents
(this=0x7fee1c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7fee567e20af in QEventLoop::processEvents
(this=this@entry=0x7fee2aea3ae0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7fee567e23a5 in QEventLoop::exec (this=this@entry=0x7fee2aea3ae0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fee566dec5f in QThread::exec (this=this@entry=0xe8e660) at
thread/qthread.cpp:537
#8  0x7fee567c3823 in QInotifyFileSystemWatcherEngine::run (this=0xe8e660)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7fee566e132f in QThreadPrivate::start (arg=0xe8e660) at
thread/qthread_unix.cpp:349
#10 0x7fee50ecf182 in start_thread (arg=0x7fee2aea4700) at
pthread_create.c:312
#11 0x7fee54a0847d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fee2a6a3700 (LWP 2607)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fee566e1816 in wait (time=18446744073709551615, this=0x1814010) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x10891b0,
mutex=mutex@entry=0x10891a8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7fee58f228aa in Digikam::ParkingThread::run (this=0x1089190) at
/build/buildd/digikam-4.0.0/core/libs/threads/threadmanager.cpp:119
#4  0x7fee566e132f in QThreadPrivate::start (arg=0x1089190) at
thread/qthread_unix.cpp:349
#5  0x7fee50ecf182 in start_thread (arg=0x7fee2a6a3700) at
pthread_create.c:312
#6  0x7fee54a0847d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fee28ea2700 (LWP 2608)):
#0  0x7fee4d92b3e3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fee4d92d9bb in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fee4d92df7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fee4d92e0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fee568107be in QEventDispatcherGlib::processEvents
(this=0x7fee140008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7fee567e20af in QEventLoop::processEvents
(this=this@entry=0x7fee28ea1ae0, flags=...) at kernel/qeventloop.cpp:149

[systemsettings] [Bug 356281] New: Once a different scheme is selected via "Window Decorations" and hit OK, if you try to get back to the same "Window Decorations" subsection of "Application Style", t

[smihaila via KDE Bugzilla]

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

Bug ID: 356281
   Summary: Once a different scheme is selected via "Window
Decorations" and hit OK, if you try to get back to the
same "Window Decorations" subsection of "Application
Style", the "System Settings" config app will crash,
all the time
   Product: systemsettings
   Version: 5.4.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: kcm_style
  Assignee: tibi...@kde.org
  Reporter: smiha...@gmail.com

1. Open System Settings.
2. Go to "Application Style".
3. Select "Window Decorations".
4. Download additional scheme/theme, such as Oxygen KDE4.2.2 or Oxygen DLS
(can't recall exact name because I can't go there anymore without crash)
5. Select the newly installed scheme. Hit ok.
6. Get back to "System Settings" main window.
7. Try to get back to "Window Decorations." The "System Settings" app will
crash.

This has happened due to selecting a mix of settings, or clicking the "fine
tune" tab of "Window Decorations" but not actually changing anything. Can't
recall 100% how I got into this state.

The bottom line is that now I can no longer invoke the "Window Decorations".

Reproducible: Always

Steps to Reproduce:
See "Details" section of this bug report.

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

[kmail2] [Bug 308968] certificate is not remembered

[Mark Stanton via KDE Bugzilla]

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

--- Comment #10 from Mark Stanton  ---
I should add that this happens every time KMail checks mail, not just once a
session.

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

[kdesvn] [Bug 345892] KDESVN crashes when trying to see the whole history entries.

[Christian Ehrlicher via KDE Bugzilla]

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

Christian Ehrlicher  changed:

   What|Removed |Added

 CC||ch.ehrlic...@gmx.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Christian Ehrlicher  ---
Duplicate of 325074
Fixed with c1adde451dfac202ef63aded5b2a7adfa9e26f9b and already integrated in
the official opensuse rpms

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

[plasmashell] [Bug 356280] Option to disable panel transparency

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk
 Resolution|--- |WONTFIX

--- Comment #1 from David Edmundson  ---
Transparency or not is a choice of the theme. 
There are plenty of themes without transparency which you can choose on
kde-look.org

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

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

[Ivo Raisr via KDE Bugzilla]

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

--- Comment #9 from Ivo Raisr  ---
Yes, '&&' seems misplaced. I attached another patch which fixes this style
issues.

As regards possible additional merges in canonicaliseLoctab() - preliminary
investigation shows that some gains are possible. However I would like to
tackle this separately, to avoid combining too many things in one commit.

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

[Planet KDE] [Bug 356274] New: sucede todo el tiempo es molesto aparte cada rato me pide clave de cartera kde y tengo que ponerle la contraseña mi wifi eh intentado resolver problemas pero no eh podid

[Domingo Brandt via KDE Bugzilla]

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

Bug ID: 356274
   Summary: sucede todo el tiempo es molesto aparte cada rato me
pide clave de cartera kde y tengo que ponerle la
contraseña mi wifi eh intentado resolver problemas
pero no eh podido es buen sistema operativo y me gusta
pero es una pena que tengas esos errores  mejor
   Product: Planet KDE
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: ranveeraggar...@gmail.com
  Reporter: brandtye...@gmail.com

Created attachment 95896
  --> https://bugs.kde.org/attachment.cgi?id=95896=edit
informe de errores

sucede todo el tiempo es molesto aparte cada rato me pide clave de cartera kde
y tengo que ponerle la contraseña mi wifi eh intentado resolver problemas pero
no eh podido es buen sistema operativo y me gusta pero es una pena que tengas
esos errores  mejor que el ubuntu este sistema operativo pero en cuanto errores
ubuntu no presenta

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

[kdenlive] [Bug 356187] icons missing in 15.11.80

[farid via KDE Bugzilla]

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

--- Comment #3 from farid  ---
just finished compiling and nothing changed.

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

[yakuake] [Bug 356272] New: Yakuake crashed

[Germano Massullo via KDE Bugzilla]

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

Bug ID: 356272
   Summary: Yakuake crashed
   Product: yakuake
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: germano.massu...@gmail.com

Application: yakuake (2.9.9+)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.2.6-301.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed:
I was looking at a very big output when Yakuake crashed.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x7fb119e19030 in QRegExpMatchState::prepareForMatch(QRegExpEngine*)
(this=0x55d974ff0ce8) at tools/qvector.h:137
#7  0x7fb119e19030 in QRegExpMatchState::prepareForMatch(QRegExpEngine*)
(this=this@entry=0x55d975631f50, eng=0x55d974ff0ce0) at tools/qregexp.cpp:1371
#8  0x7fb119e2601d in prepareEngineForMatch(QRegExpPrivate*, QString
const&) (priv=0x55d975631f20, str=...) at tools/qregexp.cpp:3731
#9  0x7fb119e2616b in QRegExp::lastIndexIn(QString const&, int,
QRegExp::CaretMode) const (this=0x55d974fefc58, str=..., offset=-1,
caretMode=QRegExp::CaretAtZero) at tools/qregexp.cpp:4155
#10 0x7fb0fd7965ca in
Konsole::SearchHistoryTask::executeOnScreenWindow(QPointer,
QPointer) () at /lib64/libkonsoleprivate.so
#11 0x7fb0fd7969f2 in Konsole::SearchHistoryTask::execute() () at
/lib64/libkonsoleprivate.so
#12 0x7fb0fd794167 in Konsole::SessionController::beginSearch(QString
const&, int) () at /lib64/libkonsoleprivate.so
#13 0x7fb0fd7942be in Konsole::SessionController::findNextInHistory() () at
/lib64/libkonsoleprivate.so
#14 0x7fb0fd798a5d in
Konsole::SessionController::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) [clone .part.98] () at /lib64/libkonsoleprivate.so
#15 0x7fb119f08a80 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=0x55d9743ce880, m=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3567
#16 0x7fb0fd759433 in
Konsole::IncrementalSearchBar::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) [clone .part.4] () at /lib64/libkonsoleprivate.so
#17 0x7fb119f08a80 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55d9743d0750, m=m@entry=0x7fb119893880
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd7ac039f0)
at kernel/qobject.cpp:3567
#18 0x7fb11941f8e2 in QAbstractButton::clicked(bool)
(this=this@entry=0x55d9743d0750, _t1=false) at
.moc/release-shared/moc_qabstractbutton.cpp:219
#19 0x7fb119154cf3 in QAbstractButtonPrivate::emitClicked()
(this=this@entry=0x55d9743d1800) at widgets/qabstractbutton.cpp:548
#20 0x7fb11915561d in QAbstractButton::click() (this=0x55d9743d0750) at
widgets/qabstractbutton.cpp:985
#21 0x7fb0fd759d23 in Konsole::IncrementalSearchBar::eventFilter(QObject*,
QEvent*) () at /lib64/libkonsoleprivate.so
#22 0x7fb119ef4a46 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*)
(this=this@entry=0x55d973f7dbe0, receiver=receiver@entry=0x55d9743cf410,
event=event@entry=0x7ffd7ac03dc0) at kernel/qcoreapplication.cpp:1065
#23 0x7fb118d7e91c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x55d973f7dbe0, receiver=0x55d9743cf410, e=0x7ffd7ac03dc0) at
kernel/qapplication.cpp:4561
#24 0x7fb118d86ae3 in QApplication::notify(QObject*, QEvent*)
(this=this@entry=0x7ffd7ac0e000, receiver=receiver@entry=0x55d9743cf410,
e=e@entry=0x7ffd7ac03dc0) at kernel/qapplication.cpp:4006
#25 0x7fb11a9ac54a in KApplication::notify(QObject*, QEvent*)
(this=0x7ffd7ac0e000, receiver=0x55d9743cf410, event=0x7ffd7ac03dc0) at
../../kdeui/kernel/kapplication.cpp:311
#26 0x7fb119ef48dd in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x7ffd7ac0e000, receiver=receiver@entry=0x55d9743cf410,
event=event@entry=0x7ffd7ac03dc0) at kernel/qcoreapplication.cpp:955
#27 0x7fb118d7d2e6 in qt_sendSpontaneousEvent(QObject*, QEvent*)
(event=event@entry=0x7ffd7ac03dc0, receiver=receiver@entry=0x55d9743cf410) at
../../src/corelib/kernel/qcoreapplication.h:234
#28 0x7fb118d7d2e6 in qt_sendSpontaneousEvent(QObject*, QEvent*)
(receiver=receiver@entry=0x55d9743cf410, event=event@entry=0x7ffd7ac03dc0) at
kernel/qapplication.cpp:5563
#29 0x7fb118e24463 in QKeyMapper::sendKeyEvent(QWidget*, bool,
QEvent::Type, int, QFlags, QString const&, bool, int,
unsigned int, unsigned int, unsigned int, bool*)
(keyWidget=keyWidget@entry=0x55d9743cf410, grab=grab@entry=217,
type=QEvent::KeyPress, code=16777220, modifiers=..., 

[muon] [Bug 354462] Tray Icon do not change if updates are done.

[Martin Droessler via KDE Bugzilla]

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

Martin Droessler  changed:

   What|Removed |Added

 CC||m...@martindroessler.de

--- Comment #2 from Martin Droessler  ---
Confirmed. Happens on my machine too - version 5.4.3

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

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

[Vit Pelcak via KDE Bugzilla]

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

Bug ID: 356277
   Summary: Kate crashes when too many files are open.
   Product: kate
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: v...@pelcak.org

kate 15.08.3

Reproducible: Always

Steps to Reproduce:
1. Open Plenty of files in Kate
2. It will crash



Program received signal SIGSEGV, Segmentation fault.
QWidget::hide (this=0x0) at kernel/qwidget.cpp:7922
7922kernel/qwidget.cpp: Adresář nebo soubor neexistuje.
(gdb) bt
#0  0x74264e90 in QWidget::hide() (this=0x0) at kernel/qwidget.cpp:7922
#1  0x77b8f7da in KateTabBar::removeTab(int) (this=0xb59040, id=0)
at /usr/src/debug/kate-15.08.3/kate/src/katetabbar.cpp:178
#2  0x77b86146 in KateViewSpace::removeTab(KTextEditor::Document*,
bool) (this=this@entry=0x10e03f0, doc=0x1691110,
documentDestroyed=documentDestroyed@entry=false) at
/usr/src/debug/kate-15.08.3/kate/src/kateviewspace.cpp:366
#3  0x77b86fcc in
KateViewSpace::registerDocument(KTextEditor::Document*, bool)
(this=this@entry=0x10e03f0, doc=doc@entry=0x1a69e10, append=append@entry=true)
at /usr/src/debug/kate-15.08.3/kate/src/kateviewspace.cpp:443
#4  0x77b88363 in KateViewSpace::restoreConfig(KateViewManager*,
KConfigBase const*, QString const&) (this=0x10e03f0,
viewMan=viewMan@entry=0x95b390, config=config@entry=0x774040, groupname=...)
at /usr/src/debug/kate-15.08.3/kate/src/kateviewspace.cpp:635
#5  0x77b8202b in KateViewManager::restoreSplitter(KConfigBase const*,
QString const&, QSplitter*, QString const&) (this=this@entry=0x95b390,
configBase=0x774040, group=..., parent=parent@entry=0x95b390, viewConfGrp=...)
at /usr/src/debug/kate-15.08.3/kate/src/kateviewmanager.cpp:1095
#6  0x77b82367 in
KateViewManager::restoreViewConfiguration(KConfigGroup const&) (this=0x95b390,
config=...)
at /usr/src/debug/kate-15.08.3/kate/src/kateviewmanager.cpp:998
#7  0x77b771f3 in KateMainWindow::readProperties(KConfigGroup const&)
(this=this@entry=0x837660, config=...)
at /usr/src/debug/kate-15.08.3/kate/src/katemainwindow.cpp:991
#8  0x77b93fc2 in
KateSessionManager::loadSession(QExplicitlySharedDataPointer
const&) const (this=this@entry=0x7ea140, session=...) at
/usr/src/debug/kate-15.08.3/kate/src/session/katesessionmanager.cpp:202
#9  0x77b94deb in
KateSessionManager::activateSession(QExplicitlySharedDataPointer,
bool, bool) (this=this@entry=0x7ea140, session=...,
closeAndSaveLast=closeAndSaveLast@entry=true, loadNew=loadNew@entry=true)
at /usr/src/debug/kate-15.08.3/kate/src/session/katesessionmanager.cpp:161
#10 0x77b95356 in KateSessionManager::activateSession(QString const&,
bool, bool) (this=0x7ea140, name=...,
closeAndSaveLast=closeAndSaveLast@entry=true, loadNew=loadNew@entry=true)
at /usr/src/debug/kate-15.08.3/kate/src/session/katesessionmanager.cpp:223
#11 0x77b918b2 in KateSessionsAction::openSession(QAction*)
(this=0x93ce90, action=)
at /usr/src/debug/kate-15.08.3/kate/src/session/katesessionsaction.cpp:69
#12 0x77bac02c in KateSessionsAction::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=)
at /usr/src/debug/kate-15.08.3/build/kate/src/moc_katesessionsaction.cpp:80
#13 0x72e6dd79 in QObject::event(QEvent*) (this=0x93ce90, e=) at kernel/qobject.cpp:1239
#14 0x74232e41 in QAction::event(QEvent*) (this=,
e=) at kernel/qaction.cpp:1094
#15 0x742398cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=
0x628880, receiver=receiver@entry=0x93ce90, e=e@entry=0x817e60) at
kernel/qapplication.cpp:3716
#16 0x7423e9d6 in QApplication::notify(QObject*, QEvent*)
(this=0x7fffdba0, receiver=0x93ce90, e=0x817e60)
at kernel/qapplication.cpp:3499
#17 0x72e3fcf3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x7fffdba0, receiver=0x93ce90, event=event@entry=0x817e60) at
kernel/qcoreapplication.cpp:965
#18 0x72e42016 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (event=0x817e60, receiver=) at
kernel/qcoreapplication.h:224
#19 0x72e42016 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x61fdd0) at kernel/qcoreapplication.cpp:1593
#20 0x72e424f8 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#21 0x72e93103 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x6c9410)
at kernel/qeventdispatcher_glib.cpp:271
#22 0x7fffeeb39097 in g_main_context_dispatch (context=0x7fffdc0016f0) at
gmain.c:3154
#23 

[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)

[Georgy via KDE Bugzilla]

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

--- Comment #24 from Georgy  ---
(In reply to Martin Klapetek from comment #22)
> Georgy - yes, this patch is spot on. Good work! Do you have commit access?
> Otherwise I'll push it for you (I just need your full name for the commit,
> you can send that in private).

Hi Martin, i don't have commit access yet, my full name is Georgy Kirichenko

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

[frameworks-solid] [Bug 346517] Plasmashell crashed after starting gparted

[anselmolsm]

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

--- Comment #26 from Anselmo L. S. Melo (anselmolsm)  ---
(In reply to David Edmundson from comment #25)
> log above didn't have what I needed.
> 
> Can someone give me a reliable way to 100% reproduce this. Ideally with
> docker or some such.

https://bugs.kde.org/355476 has a bt generated when plasmashell crashed after
starting docker. Hope it helps somehow.

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

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

[via KDE Bugzilla]

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

--- Comment #17 from p.v.niek...@hccnet.nl ---
We keep seeing this behaviour every day, quite annoying.
Despite that, we have not found what actually triggers it.

Not sure if it's related, but one thing we noticed is that whenever we use the
word "connect" in a python file, it is always rendered Bold in a blue-ish
color, independent of how and when the word is used. Expectation would be that
only the definition would be bold, and that there would be variation in the
colour used. Is there a reason for this special treatment?

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

[kdeconnect] [Bug 354333] after kubuntu upgrade of October 18+ kdeconnect loops and cannot be used

[Erike Magegere via KDE Bugzilla]

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

--- Comment #2 from Erike Magegere  ---
the previous comment does not show so as a repeat and additional:
After installing system upgrades that included linux-image-3.13.0-68-generic
kde connect worked again - except for the large file transfer showing completed
successfully but the file truncated at random lengths
after upgrading to linux-image-3.13.0-71-generic again KDE Connect fails to
where android can not find the Kubuntu system.  It does not loop as in
linux-image-3.13.0-66-generic

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

[Akonadi] [Bug 356275] akonadi-backend-sqlite requires virtual package qtbase-abi-5-4-2 but libqt5core5a now provides qtbase-abi-5-5-1

[amirsan via KDE Bugzilla]

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

amirsan  changed:

   What|Removed |Added

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

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

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

[Ivo Raisr via KDE Bugzilla]

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

Ivo Raisr  changed:

   What|Removed |Added

  Attachment #95828|0   |1
is obsolete||

--- Comment #8 from Ivo Raisr  ---
Created attachment 95895
  --> https://bugs.kde.org/attachment.cgi?id=95895=edit
patch with formatting fixed

Patch with fixed formatting.

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

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

[Ivo Raisr via KDE Bugzilla]

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

Ivo Raisr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||r15741

--- Comment #10 from Ivo Raisr  ---
Fixed in SVN commit r15741.

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

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

[Ivo Raisr via KDE Bugzilla]

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

--- Comment #11 from Ivo Raisr  ---
See also:
Bug 356273 - conserve memory by merging adjacent DiLoc entries in the debug
info location table

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

[kate] [Bug 356276] New: Kate crashes when opened file is changed by external program

[Vit Pelcak via KDE Bugzilla]

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

Bug ID: 356276
   Summary: Kate crashes when opened file is changed by external
program
   Product: kate
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: v...@pelcak.org

I have Kate 15.08.3

When I have file opened and changed in it and it gets changed by other program,
Kate crashes.

Reproducible: Always

Steps to Reproduce:
1) Open file in kate and change it, (without saving).
2) Then, edit that file in different program. 
3) Kate will ask you to reload that file. Confirm it.
4) Kate will ask you to save changes. Reject it.
5) Kate segfaults.

Actual Results:  
Segfault

Expected Results:  
Kate should continue working.

(gdb) bt
#0  0x77b8b857 in KateMwModOnHdDialog::handleSelected(int)
(this=0xb24140, action=2)
at /usr/src/debug/kate-15.08.3/kate/src/katemwmodonhddialog.cpp:214
#1  0x72e6ce17 in QMetaObject::activate(QObject*, int, int, void**)
(a=0x7fffc530, r=0xb24140, this=)
at ../../src/corelib/kernel/qobject_impl.h:124
#2  0x72e6ce17 in QMetaObject::activate(QObject*, int, int, void**)
(sender=sender@entry=0xe19430, signalOffset=,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffc530)
at kernel/qobject.cpp:3698
#3  0x72e6d787 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0xe19430, m=m@entry=0x74935bc0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffc530)
at kernel/qobject.cpp:3578
#4  0x745acf92 in QAbstractButton::clicked(bool)
(this=this@entry=0xe19430, _t1=false)
at .moc/moc_qabstractbutton.cpp:303
#5  0x74330e04 in QAbstractButtonPrivate::emitClicked()
(this=this@entry=0xd7b830) at widgets/qabstractbutton.cpp:534
#6  0x74332309 in QAbstractButtonPrivate::click()
(this=this@entry=0xd7b830) at widgets/qabstractbutton.cpp:527
#7  0x7433245c in QAbstractButton::mouseReleaseEvent(QMouseEvent*)
(this=0xe19430, e=0x7fffc9c0)
at widgets/qabstractbutton.cpp:1132
#8  0x74279df8 in QWidget::event(QEvent*) (this=0xe19430,
event=0x7fffc9c0) at kernel/qwidget.cpp:9047
#9  0x742398cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x628880, receiver=receiver@entry=0xe19430,
e=e@entry=0x7fffc9c0) at kernel/qapplication.cpp:3716
#10 0x7423f511 in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0xe19430, e=0x7fffc9c0)
at kernel/qapplication.cpp:3276
#11 0x72e3fcf3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x7fffdba0, receiver=receiver@entry=0xe19430,
event=event@entry=0x7fffc9c0) at kernel/qcoreapplication.cpp:965
#12 0x7423e082 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
(event=0x7fffc9c0, receiver=0xe19430) at
../../src/corelib/kernel/qcoreapplication.h:227
#13 0x7423e082 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
(receiver=receiver@entry=0xe19430, event=event@entry=0x7fffc9c0,
alienWidget=alienWidget@entry=0xe19430, nativeWidget=0xb24140,
buttonDown=buttonDown@entry=0x749446a0 ,
lastMouseReceiver=..., spontaneous=true)
at kernel/qapplication.cpp:2770
#14 0x74293dd3 in QWidgetWindow::handleMouseEvent(QMouseEvent*)
(this=this@entry=0xd56a10, event=event@entry=0x7fffcdc0) at
kernel/qwidgetwindow.cpp:555
#15 0x7429633b in QWidgetWindow::event(QEvent*) (this=0xd56a10,
event=0x7fffcdc0) at kernel/qwidgetwindow.cpp:210
#16 0x742398cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x628880, receiver=receiver@entry=0xd56a10,
e=e@entry=0x7fffcdc0) at kernel/qapplication.cpp:3716
#17 0x7423e9d6 in QApplication::notify(QObject*, QEvent*)
(this=0x7fffdba0, receiver=0xd56a10, e=0x7fffcdc0)
at kernel/qapplication.cpp:3499
#18 0x72e3fcf3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x7fffdba0, receiver=receiver@entry=0xd56a10,
event=event@entry=0x7fffcdc0) at kernel/qcoreapplication.cpp:965
#19 0x73a9979e in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
(event=0x7fffcdc0, receiver=0xd56a10) at
../../src/corelib/kernel/qcoreapplication.h:227
#20 0x73a9979e in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
(e=0xf68f40)
at kernel/qguiapplication.cpp:1789
#21 0x73a9b305 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
(e=e@entry=0xf68f40) at kernel/qguiapplication.cpp:1581
#22 0x73a809f8 in

[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||emilioo...@hotmail.com

--- Comment #149 from caulier.gil...@gmail.com ---
*** Bug 356282 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 345480] Kdevelop 4.7 crashes when clicking "Stop All" as soon as a project has been imported

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

   Target Milestone|--- |4.7.3
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Priority|NOR |VHI

--- Comment #1 from Milian Wolff  ---
probably happens when the ParseProjectJob is killed in the nested eventloop -
ouch.

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

[kate] [Bug 354258] The cursor is inactive after Alt+Tab

[Victor Porton via KDE Bugzilla]

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

Victor Porton  changed:

   What|Removed |Added

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

--- Comment #2 from Victor Porton  ---
Without updating Kate (remains Kate 15.08.2), this bugs resolved magically. I
close it.

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

[kdevelop] [Bug 355099] Crash when expanding project folder in Projects tab

[Milian Wolff via KDE Bugzilla]

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

--- Comment #11 from Milian Wolff  ---
I have strange painting issues with the gsmartcontrol project, i.e. expanding a
folder does not update the tree immediately. But no crash and valgrind is also
not reporting anything about a broken QTransform :(

So I'm out of luck in fixing it myself.

@Alexander: Any chance you could compile Qt from sources in debug mode and
retrigger this issue? Then the backtrace would show us more details (i.e. file
+ line into Qt sources).

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

[kdenlive] [Bug 352418] kdenlive 15.04.2 crashes randomly

[Joshua Dunamis via KDE Bugzilla]

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

--- Comment #5 from Joshua Dunamis  ---
(In reply to Joshua Dunamis from comment #4)
> It crashes randomly also to me on Manjaro Linux KDE: Plasma 5.4.3 - kdenlive
> 18.08.3

Sorry, kdenlive 15.08.3

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

[kdevelop] [Bug 350916] The debugger component does not stop on interrupt button and doesn't insert BP in running app

[Milian Wolff via KDE Bugzilla]

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

--- Comment #16 from Milian Wolff  ---
Fernando, sorry for the late reply. Did I apply your latest patch now or is
this still pending?

Again, very sorry for the mess and lack of interaction from my side...

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

[kdevelop] [Bug 355099] Crash when expanding project folder in Projects tab

[Milian Wolff via KDE Bugzilla]

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

--- Comment #12 from Milian Wolff  ---
One more idea: what happens when you move the following line down to where it
is being used:

 QString branchNameData =
index.data(VcsOverlayProxyModel::VcsStatusRole).toString();

and/or what happens if you replace it by


 QString branchNameData; // =
index.data(VcsOverlayProxyModel::VcsStatusRole).toString();

I ask b/c this potentially spins up a nested eventloop leading to all kinds of
funny issues... If this "fixes" the issue, then we at least know where to look
for a fix.

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

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

[Sven Brauch via KDE Bugzilla]

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

--- Comment #18 from Sven Brauch  ---
That is not related, that's just kate's Qt highlighting. It's a bit weird, but
you can ignore it, it is harmless.

I'm sorry for the inconvenience, but without a way to reproduce I can't really
fix it.
If you need a quick workaround, delete line 57 in duchain/unsuretype.cpp. You
will lose a bit of type tracking accuracy but probably not much.

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

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

[Sven Brauch via KDE Bugzilla]

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

--- Comment #19 from Sven Brauch  ---
sorry, duchain/types/unsuretype.cpp is the file name. The line is
  results.append(resolved.cast()->typesRecursive());
That apparently runs into a (near?) infinite recursion, but I'm not sure how.
To find out I'd need some example code which creates a type which triggers this
behaviour.

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

[kdenlive] [Bug 352418] kdenlive 15.04.2 crashes randomly

[Joshua Dunamis via KDE Bugzilla]

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

Joshua Dunamis  changed:

   What|Removed |Added

 CC||joshua.duna...@gmail.com

--- Comment #4 from Joshua Dunamis  ---
It crashes randomly also to me on Manjaro Linux KDE: Plasma 5.4.3 - kdenlive
18.08.3

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

[kdevelop] [Bug 345480] Kdevelop 4.7 crashes when clicking "Stop All" as soon as a project has been imported

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.0.0
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/bcdd01a4abc003fee4
   ||d8376a2c1226d8c896ea68

--- Comment #2 from Milian Wolff  ---
Git commit bcdd01a4abc003fee4d8376a2c1226d8c896ea68 by Milian Wolff.
Committed on 04/12/2015 at 17:49.
Pushed by mwolff into branch '5.0'.

Guard against reentrancy issues that may trigger a crash.

When the nested eventloop handles a "stop all jobs" action the
job itself may get deleted and subsequently we'd run on a deleted
`this` leading to crashes.
FIXED-IN: 5.0.0

M  +13   -2language/backgroundparser/parseprojectjob.cpp

http://commits.kde.org/kdevplatform/bcdd01a4abc003fee4d8376a2c1226d8c896ea68

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

[amarok] [Bug 355986] freezes when opened

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |DUPLICATE

--- Comment #5 from Myriam Schweingruber  ---
Thank you. Unfortunately this is a known bug, and since our devs are rather
busy I doubt this will be fixed before the next Qt4 based release. We will
definitely keep this in mind and in high priority for the Qt5 port.

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

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

[plasmashell] [Bug 356280] Option to disable panel transparency

[Ken Vermette via KDE Bugzilla]

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

Ken Vermette  changed:

   What|Removed |Added

 CC||verme...@gmail.com

--- Comment #2 from Ken Vermette  ---
Additionally, disabling compositing will remove several distractions, including
animations, as well as removing transparency. 

One thing we could do is add an intensity option slider to the Kwin "Background
Contrast" effect; with the extreme intensity effectively drowning out the
background completely, only picking up a small amount of colour.

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

[kmail2] [Bug 356283] New: Any message contents that shows in the message preview bottom pane shows <<< Grantlee theme "" is not valid >>> prefixed to the actual msg body

[smihaila via KDE Bugzilla]

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

Bug ID: 356283
   Summary: Any message contents that shows in the message preview
bottom pane shows <<< Grantlee theme "" is not valid
>>> prefixed to the actual msg body
   Product: kmail2
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: smiha...@gmail.com

For any message that is currently selected in the message view pane, the
message preview/reader pane will always show this text affixed BEFORE the
actual message body:

Grantlee theme "" is not valid

The same thing happens whenever I double click on the message to open the
composer in "E-mail Forward" mode.

When I hit reply/reply all though, the odd Grantlee theme bogus text does NOT
show up.

Please advise smiha...@gmail.com when this is fixed - it's unbearable and it
makes me downgrade back to what i was having before - K/Ubuntu 10.x WAS
P-E-R-F-E-C-T.

Reproducible: Always

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

[plasmashell] [Bug 356280] Option to disable panel transparency

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #3 from Kai Uwe Broulik  ---
Note that disabling composting takes away many benefits of offloading graphical
computations to the GPU; it also is not possible on Wayland. 

Additionally, background contrast intensity is also a determined by the theme.

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

[plasmashell] [Bug 355016] Plasma crash after wake up system

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||tuomas.ka...@gmail.com

--- Comment #2 from David Edmundson  ---
*** Bug 356264 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 356264] Plasma crash when disconnecting external screens (docking station)

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 356287] New: Icon-only Task Manager dynamic size is too big

[via KDE Bugzilla]

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

Bug ID: 356287
   Summary: Icon-only Task Manager dynamic size is too big
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
   URL: https://goo.gl/photos/vCzW3GdUZg99kecx6
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: q.chatel...@gmx.fr
CC: plasma-b...@kde.org

I have a panel which expands and shrinks depending on its components size.
However the icon-only task manager is demanding to the panel a bigger space
than it needs. For each open app, the task manager is expanding a lot, leaving
a blank space on the right.

Note : with the others task managers, it works as expected.

Reproducible: Always

Steps to Reproduce:
1. Put an Icon-only Task Manager onto a panel
2. Open one or more apps

Actual Results:  
The task manager is taking too much space.

Expected Results:  
The task manager should be as long as the total size of the icons.

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

[kdesvn] [Bug 329836] Add a menu entry to edit properties

[Christian Ehrlicher via KDE Bugzilla]

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

Christian Ehrlicher  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||ch.ehrlic...@gmx.de
 Resolution|--- |WORKSFORME

--- Comment #1 from Christian Ehrlicher  ---
In current git head there is a menu entry in the context menu and in the main
menu - default shortcut on both is CTRL+P

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

[muon] [Bug 356284] New: password dialog closes before password can be entered, error message can not continue as permission not granted

[Doug Taylor via KDE Bugzilla]

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

Bug ID: 356284
   Summary: password dialog closes before password can be entered,
error message can not continue as permission not
granted
   Product: muon
   Version: 2.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: updater
  Assignee: echidna...@kubuntu.org
  Reporter: doug.tay...@taymade.co.uk
CC: aleix...@kde.org, sit...@kde.org

problem also occurs with software updater

Reproducible: Always




waited for entry of data

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

[frameworks-solid] [Bug 346517] Plasmashell crashed after starting gparted

[David Edmundson via KDE Bugzilla]

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

--- Comment #27 from David Edmundson  ---
I'm not after a backtrace, I want guided steps on making my system crash.

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

[konsole] [Bug 356286] New: Allow scrollback buffer to be greater than 100000 lines

[Noé Rubinstein via KDE Bugzilla]

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

Bug ID: 356286
   Summary: Allow scrollback buffer to be greater than 10
lines
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: history
  Assignee: konsole-de...@kde.org
  Reporter: noe.rubinst...@gmail.com

Currently, Konsole offers three options in the "Scrolling" setting:
* No scrollback
* Fixed size scrollback
* Unlimited scrollback

The "unlimited scrollback" can sometimes fill up your FS when running programs
that output very large quantities of text (such as a build log for large
software). However, the "fixed size" scrollback is configurable only up to
10 lines, which is sometimes not enough.

I would like to be able to configure at least 10 times more scrollback.

Reproducible: Always

Steps to Reproduce:
1. Right-click your terminal
2. Click "Edit current profile"
3. Go to tab "Scrolling"
4. Select "Fixed size scrollback"
5. Input "100" (one million) in the text field

Actual Results:  
The scrollback size is 100 000 (a hundred thousands)

Expected Results:  
The scrollback size is 1 000 000 (one million)

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

[frameworks-solid] [Bug 346517] Plasmashell crashed after starting gparted

[anselmolsm]

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

--- Comment #28 from Anselmo L. S. Melo (anselmolsm)  ---
355476 was generated after a systemctl start docker.service

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

[okular] [Bug 356285] Not enough space for page number

[LtWorf]

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

--- Comment #1 from Salvo "LtWorf" Tomaselli  ---
Created attachment 95897
  --> https://bugs.kde.org/attachment.cgi?id=95897=edit
image of the problem

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

[kdevelop] [Bug 355099] Crash when expanding project folder in Projects tab

[Alexander via KDE Bugzilla]

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

--- Comment #13 from Alexander  ---
Moving the line helped, no crash and so far it looks like everything is OK!
Must be the event loop then...

Commenting it out also helps (obviously).

Finally, I can use KDevelop 5 properly, thanks!

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

[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org

--- Comment #3 from Martin Klapetek  ---
I think this https://git.reviewboard.kde.org/r/125773/ could/would fix it.

Are you able to test patches? Could you test this one?

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

[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

[Alexander via KDE Bugzilla]

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

Alexander  changed:

   What|Removed |Added

 CC||ober...@gmail.com

--- Comment #13 from Alexander  ---
OpenSuse Tumbleweed.
Konsole no close
System not shutdown. KsmServer cpu usage.

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

[kwin] [Bug 356263] Desktop wallpaper doesn't display on KDE login when using OpenGL v3.1 with EGL on Intel cards

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #6 from Thomas Lübking  ---
(In reply to Xavion from comment #5)
> My main panel is set to "auto-hide" mode.
Ah, ok. Just a guess ;-)

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

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

[plasmashell] [Bug 351180] plasma crash after activating second monitor using xrandr

[Ben Bloom via KDE Bugzilla]

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

Ben Bloom  changed:

   What|Removed |Added

 CC||benbloo...@gmail.com

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

[plasmashell] [Bug 356261] everything crashes on X session startup after Upgrading Fedora from 20 to 23

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

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

--- Comment #13 from Martin Klapetek  ---
> Xlib:  extension "GLX" missing on display ":0".

Please try reinstalling your graphics driver, you have likely a broken
configuration.

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

[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)

[george via KDE Bugzilla]

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

--- Comment #27 from george  ---
Not sure how this propagates so I would like to ask: When can we expect to have
the fixed version in openSUSE 42.1 Leap repo?

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

[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #28 from Martin Klapetek  ---
I'm sorry but you'll have to ask your distro packagers that question.

I've notified the KDE distro packagers that this should be backported,
if/how/when is fully up to them.

Sorry.

(everybody try nagging your distros though)

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

[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)

[george via KDE Bugzilla]

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

--- Comment #29 from george  ---
Thanks Martin!

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

[kdevplatform] [Bug 356293] New: Segfault in KDevelop::Stack while parsing projects.

[via KDE Bugzilla]

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

Bug ID: 356293
   Summary: Segfault in KDevelop::Stack while parsing projects.
   Product: kdevplatform
   Version: git master
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: util
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: bunge...@gmail.com

Built kdevelop and kdevplatform at current 5.0 branch. Ran with 'gdb -ex run
~/kdevelop5/bin/kdevelop' and opened Skia, kdevelop, and kdevplatform projects
(Skia one probably isn't a problem as currently KDevelop doesn't see any of its
files since all the files are in sibling directories to the CMakeLIsts.txt).
After a while (at about 10% complete) KDevelop segfaults with the following
message

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc4d56700 (LWP 19575)]
0x7fffced5800b in QVarLengthArray::append (
this=0x746efc10 ,
t=@0x7fffc4d559b4: 58) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvarlengtharray.h:126
126 ptr[idx] = t;
(gdb) bt
#0  0x7fffced5800b in QVarLengthArray::append (
this=0x746efc10 ,
t=@0x7fffc4d559b4: 58) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvarlengtharray.h:126
#1  0x7fffced5785f in KDevelop::Stack::push (
this=0x746efc10 ,
t=@0x7fffc4d559b4: 58) at $HOME/kdevelop5/include/kdevplatform/util/stack.h:60
#2  0x7fffced66377 in
KDevelop::TemporaryDataManager, true>::free (
this=0x746efc00 ,
index=58) at
$HOME/kdevelop5/include/kdevplatform/language/duchain/appendedlist.h:171
#3  0x7fffced6520d in KDevelop::TopDUContextData::m_problemsFree
(this=0x7fff84704f90)
at
$HOME/kdevelop5/include/kdevplatform/language/duchain/topducontextdata.h:78
#4  0x7fffced65368 in KDevelop::TopDUContextData::m_problemsFreeChain
(this=0x7fff84704f90)
at
$HOME/kdevelop5/include/kdevplatform/language/duchain/topducontextdata.h:78
#5  0x7fffced653d0 in KDevelop::TopDUContextData::freeAppendedLists
(this=0x7fff84704f90)
at
$HOME/kdevelop5/include/kdevplatform/language/duchain/topducontextdata.h:79
#6  0x7fffced64d42 in KDevelop::TopDUContextData::~TopDUContextData
(this=0x7fff84704f90, __in_chrg=)
at
$HOME/kdevelop5/include/kdevplatform/language/duchain/topducontextdata.h:61
#7  0x7fffced69c5b in
KDevelop::DUChainItemFactory,
KDevelop::TopDUContextData>::callDestructor (this=0x2d01ab0,
data=0x7fff84704f90) at
$HOME/kdevelop5/include/kdevplatform/language/duchain/duchainregister.h:70
#8  0x73913bc2 in KDevelop::DUChainItemSystem::callDestructor (
this=0x748ecf20 ,
data=0x7fff84704f90)
at ../language/duchain/duchainregister.cpp:45
#9  0x738bf41e in KDevelop::DUChainBase::setData (this=0x7fff84761aa0,
data=0x7fffc00031a8, constructorCalled=true)
at ../language/duchain/duchainbase.cpp:85
#10 0x7389a7a5 in (anonymous namespace)::saveDUChainItem (data=...,
item=..., totalDataOffset=@0x7fffc4d55bc4: 696, 
isSharedDataItem=false) at
../language/duchain/topducontextdynamicdata.cpp:86
#11 0x7389c38b in KDevelop::TopDUContextDynamicData::store
(this=0x7fff84761d90)
at ../language/duchain/topducontextdynamicdata.cpp:705
#12 0x7384110e in KDevelop::DUChainPrivate::doMoreCleanup (
this=0x740effe0 , retries=1, 
needLockRepository=true) at ../language/duchain/duchain.cpp:746
#13 0x7383e2d6 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x156afb0) at ../language/duchain/duchain.cpp:289
#14 0x757f92be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fffee9016aa in start_thread (arg=0x7fffc4d56700) at
pthread_create.c:333
#16 0x75111eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Reproducible: Always

Steps to Reproduce:
1. Build recent 5.0 kdevelop and kdevplatform in debug on Ubuntu Wily.
2. Open kdevelop and kdevplatform projects.
3. Wait a bit.

Actual Results:  
Crash.

Expected Results:  
No crash.

I did 'rm -rf ~/.cache/kdevduchain/' before running.

This is with qtbase5 package at version 5.4.2+dfsg-2ubuntu9 . While there have
been some issues with qvarlengtharray in the past, I don't see anything recent
in the blame at

[plasmashell] [Bug 356287] Icon-only Task Manager dynamic size is too big

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org

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

[systemsettings] [Bug 341885] User added SSL Certificate are lost when system settings is quit

[via KDE Bugzilla]

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

fetzt_d...@vollbio.de changed:

   What|Removed |Added

 CC||fetzt_d...@vollbio.de

--- Comment #3 from fetzt_d...@vollbio.de ---
I can absolutely confirm this for a freshly installed KUbuntu 15.10.

I can add my own CA-cert, it will then show up under user-added certificates.
Once you hit "apply", close kcm_ssl and open it again the certificate is gone.

Why is this unconfirmed for a whole year?

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

[frameworks-kdelibs4support] [Bug 342958] SSL KCM doesn't save any added certificates

[via KDE Bugzilla]

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

fetzt_d...@vollbio.de changed:

   What|Removed |Added

 CC||fetzt_d...@vollbio.de

--- Comment #2 from fetzt_d...@vollbio.de ---
Confirmed for Kubuntu 15.10
Creating ~/.local/share/kssl/userCaCertificates manually fixes this.

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

[plasmashell] [Bug 356295] New: The battery level on the icon does not seem correct

[Martin Klapetek via KDE Bugzilla]

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

Bug ID: 356295
   Summary: The battery level on the icon does not seem correct
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Theme - Breeze
  Assignee: visual-des...@kde.org
  Reporter: mklape...@kde.org
CC: plasma-b...@kde.org

Created attachment 95900
  --> https://bugs.kde.org/attachment.cgi?id=95900=edit
Screenshot

See the screenshot.

It has 53% yet the icon looks more like 20% while it should clearly be exactly~
half empty.

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

[konsole] [Bug 356294] New: After clearing, set before shortcut for profile, it still works

[Piotr Mierzwinski via KDE Bugzilla]

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

Bug ID: 356294
   Summary: After clearing, set before shortcut for profile, it
still works
   Product: konsole
   Version: 15.08.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

Accidentally I set shortcut for my "mc" profile - Ctrl+O. I clicked "Close"
button. When in running "mc" profile I used above shortcut I got new konsole
tab (with running mc). I realized that I set shortcut for it, so I closed it
and went to "Profile managing" and cleared it. I clicked "Close" button. After
that  I tried again use Ctrl+O and I was surprising when again I got new
konsole tab, despite it was already unset!

Reproducible: Always

Steps to Reproduce:
1. Run konsole
2. Go to "Profile managing"
3. Set shortcut for any profile
4. Click "Close" button
5. Use before set shortcut - you got new tab konsole
6. Close newly opened tab
7. Again go to "Profile managing"
8. Clear shortcut for this profile
9. Click "Close" button
10. Use before cleared shortcut

Actual Results:  
Profile opens

Expected Results:  
Profile (new tab) should not be open

Tested in Kubuntu 15.10 with all updates.

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

[kio] [Bug 147131] Allow user to specify thumbnail generators for arbitrary file types

[Christoph Feck via KDE Bugzilla]

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

--- Comment #3 from Christoph Feck  ---
http://kde-apps.org/content/show.php/?content=174485

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

[dolphin] [Bug 356298] New: Dolphin crashes when selecting multiple (more than 10) files

[via KDE Bugzilla]

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

Bug ID: 356298
   Summary: Dolphin crashes when selecting multiple (more than 10)
files
   Product: dolphin
   Version: 15.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: dsbor...@gmail.com

Application: dolphin (15.08.2)

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

-- Information about the crash:
Just tried to select a bunch of files. Seems like it's start crashing after 8
files were selected

The crash can be reproduced every time.

-- 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 0x7fecdc198800 (LWP 20576))]

Thread 3 (Thread 0x7fecd97be700 (LWP 20577)):
#0  0x7fecee8e58dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fece3310bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fece331274f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fecdbd0ca39 in QXcbEventReader::run (this=0x220f0f0) at
qxcbconnection.cpp:1105
#4  0x7fece97542be in QThreadPrivate::start (arg=0x220f0f0) at
thread/qthread_unix.cpp:337
#5  0x7fece5e116aa in start_thread (arg=0x7fecd97be700) at
pthread_create.c:333
#6  0x7fecee8f0eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7feccfac9700 (LWP 20578)):
#0  0x7fecee8e149d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fece571e4e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fece56dacd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece56db190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fece56db2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fece998b29b in QEventDispatcherGlib::processEvents
(this=0x7fecc80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7fece993175a in QEventLoop::exec (this=this@entry=0x7feccfac8dc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fece974f3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7fece97542be in QThreadPrivate::start (arg=0x26ab700) at
thread/qthread_unix.cpp:337
#9  0x7fece5e116aa in start_thread (arg=0x7feccfac9700) at
pthread_create.c:333
#10 0x7fecee8f0eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fecdc198800 (LWP 20576)):
[KCrash Handler]
#6  mdb_cursor_init (mc=mc@entry=0x7ffcb967a800, txn=txn@entry=0x345d170,
dbi=dbi@entry=1, mx=mx@entry=0x0) at mdb.c:7130
#7  0x7fece1febd0b in mdb_dbi_open (txn=0x345d170,
name=name@entry=0x7fece6694d75 "postingdb", flags=flags@entry=0,
dbi=dbi@entry=0x7ffcb967a9d4) at mdb.c:9167
#8  0x7fece6681507 in Baloo::PostingDB::open (txn=) at
../../../src/engine/postingdb.cpp:53
#9  0x7fece6674eb9 in Baloo::Database::open (this=this@entry=0x7fece689b3e0
<(anonymous namespace)::Q_QGS_s_db::innerFunction()::holder>,
mode=mode@entry=Baloo::Database::OpenDatabase) at
../../../src/engine/database.cpp:102
#10 0x7fecec6e9e46 in Baloo::File::load (this=this@entry=0x7ffcb967ac30) at
../../../src/lib/file.cpp:99
#11 0x7fececc78806 in Baloo::FileFetchJob::doStart (this=0x3146990) at
../../src/filefetchjob.cpp:58
#12 0x7fece9965651 in QObject::event (this=0x3146990, e=) at
kernel/qobject.cpp:1245
#13 0x7fecea411b8c in QApplicationPrivate::notify_helper
(this=this@entry=0x21f6910, receiver=receiver@entry=0x3146990,
e=e@entry=0x2f98d70) at kernel/qapplication.cpp:3720
#14 0x7fecea417230 in QApplication::notify (this=0x7ffcb967b330,
receiver=0x3146990, e=0x2f98d70) at kernel/qapplication.cpp:3503
#15 0x7fece9933f1b in QCoreApplication::notifyInternal
(this=0x7ffcb967b330, receiver=0x3146990, event=event@entry=0x2f98d70) at
kernel/qcoreapplication.cpp:935
#16 0x7fece9936057 in QCoreApplication::sendEvent (event=0x2f98d70,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x21f5aa0) at
kernel/qcoreapplication.cpp:1552
#18 0x7fece9936588 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1410
#19 0x7fece998ae73 in postEventSourceDispatch (s=0x222d720) at
kernel/qeventdispatcher_glib.cpp:271
#20 0x7fece56daff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fece56db250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fece56db2fc in g_main_context_iteration () from

[konsole] [Bug 356294] After clearing, set before shortcut for profile, still works

[Piotr Mierzwinski via KDE Bugzilla]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Summary|After clearing, set before  |After clearing, set before
   |shortcut for profile, it|shortcut for profile, still
   |still works |works
 CC||piotr.mierzwin...@gmail.com

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

[plasmashell] [Bug 347591] Icons are way too small when in vertical panel

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Klapetek  ---
Following the last comment, closing as fixed.

If you can reproduce with Plasma 5.5, please reopen this report.

Thanks.

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

[plasmashell] [Bug 355864] Icon of the battery seems always more empty that it is

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #7 from Martin Klapetek  ---
*** Bug 356295 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 356297] Settings lost on update, (LOCALE ignored)

[adimeymuc via KDE Bugzilla]

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

--- Comment #1 from adimeymuc  ---
Created attachment 95902
  --> https://bugs.kde.org/attachment.cgi?id=95902=edit
What I get after update

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

[kate] [Bug 343629] write cursor does not move when keys are pressed

[Arne Döring via KDE Bugzilla]

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

--- Comment #22 from Arne Döring  ---
There should be a test case that creates x11 events like those events emitted
from the neo layout. These events should be send to a running kate session with
some text and cursor position, and if the text did not change as expected, the
test should fail. The developers need to see when they break the compatibility,
I am a bit tired of broken compatibility, working again, broken … . I hope
someone can do this, because I have never written a test case for qt or even
kde applications.

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

[plasmashell] [Bug 352171] clipboard history in systray cannot be really disabled, security problem

[via KDE Bugzilla]

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

shaikadz...@4nakama.net changed:

   What|Removed |Added

 CC||shaikadz...@4nakama.net

--- Comment #10 from shaikadz...@4nakama.net ---
I would like to add my vote to an option to disable the clipboard widget
completely.
I really don't want this feature at my work (someone could see a password they
should not).

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

[dolphin] [Bug 356297] New: Settings lost on update, (LOCALE ignored)

[adimeymuc via KDE Bugzilla]

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

Bug ID: 356297
   Summary: Settings lost on update, (LOCALE ignored)
   Product: dolphin
   Version: 15.08.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: adimey...@gmail.com

Created attachment 95901
  --> https://bugs.kde.org/attachment.cgi?id=95901=edit
Settings as they were and are supposed to be

=== Dolphin and other settings lost ===
After updating via Yast onlineupdate (Using open Suse 13.2) 

A) Dolphin
from: "Version 15.04.0 Unter KDE 4.14.9"

to: "15.08.3
KDE Frameworks 5.16.0
Qt 5.5.1 (built against 5.5.0)
The xcb windowing system"

1) all Dolphin settings are lost
2) the main toolbar is now English only (ought to be German) 
3) all (non system) images assigened to be displayed as folder symbols (rather
the paths to them) 

B) kwrite 
1) toolbar and menues English only 
2) in systems settings .txt files not assigned to kwrite any longe, but libre
office instead

C) All .desktop files in the symbols bar (to start applications) disappeared

And that's just what I've noticed the last half hour, after reboot. Basically
existing settings are totally disregardedd an users can spend half a night
rebuilding them ...
Dejavu KDE 3 --> 4 ???

Screenshot before and after

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

[khotkeys] [Bug 356296] New: Unable to edit a custom shortcut a second time

[via KDE Bugzilla]

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

Bug ID: 356296
   Summary: Unable to edit a custom shortcut a second time
   Product: khotkeys
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@michael-jansen.biz
  Reporter: kram...@web.de

I can create and use a custom shortcut ("Global Shortcut / Command/URL")
successfully.

However, editing the "Action" after it is created is not possible.

Reproducible: Always

Steps to Reproduce:
1. Goto "System settings / Shortcuts / Custom Shortcuts" or run "kcmshell5
khotkeys"
2. Create a new "Global Shortcut" of type "Command/URL", e.g.:
- Shortcut: Meta+.
- Command/URL: xdotool type $(date +"%d.%m.%Y")
3. "Apply" and close the dialog.
4. Goto "System settings / Shortcuts / Custom Shortcuts" again.
5. Edit your Shortcut, e.g. try to change Command/URL to : xdotool type
--clearmodifiers $(date +"%d.%m.%Y")
6. "Apply" and close the dialog. (There is no error message).


Actual Results:  
The change to the shortcut action (Command/URL) never gets saved.
The custom shortcut must be deleted and recreated to apply changes.

Expected Results:  
The change to the shortcut action (Command/URL) should be saved and applied.

Fully updated Arch Linux
System Settings 5.4.3
Using KDE Frameworks 5.16.0
QT 5.5.1

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

[plasmashell] [Bug 356295] The battery level on the icon does not seem correct

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Klapetek  ---


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

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

[plasmashell] [Bug 355858] digital clock does not display anything

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |UPSTREAM

--- Comment #11 from Martin Klapetek  ---
Qt patch at https://codereview.qt-project.org/#/c/143091/

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

[wacomtablet] [Bug 347022] Unable to setup wacom tablet - widget missing

[Magnus Hoff via KDE Bugzilla]

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

Magnus Hoff  changed:

   What|Removed |Added

 CC||magh...@gmail.com

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

[kdenlive] [Bug 356299] New: Trying to import broken video causes crash

[via KDE Bugzilla]

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

Bug ID: 356299
   Summary: Trying to import broken video causes crash
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: qubo...@gmail.com

catalyst-hook 15.9-6
catalyst-libgl 15.9-2
catalyst-utils 15.9-2
mlt 0.9.8-3
qt5-base 5.5.1-3
kdenlive git describe --tags --always
v15.11.80-53-g0918054

Steps to reproduce:
1. Trying to import (drag and drop)
https://app.box.com/s/j7e9ljwpsu3cbm4v3tsvh3byaxfd5tre (2MB mp4) ...

Actual result:
1. ... causes a crash:

[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f01f4009560] Could not find codec parameters for
stream 0 (Video: h264 (avc1 / 0x31637661), none, 1920x1080, 6899 kb/s):
unspecified pixel format
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f01f40ecae0] Could not find codec parameters for
stream 0 (Video: h264 (avc1 / 0x31637661), none, 1920x1080, 6899 kb/s):
unspecified pixel format
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Assertion desc failed at libswscale/swscale_internal.h:676
/home/qubodup/.local/bin/klgit: line 4: 11197 Aborted 

The  video is a result of a working mp4 edited with a script that contains

ffmpeg -i "$1" -ss "$2" -t "$3" -acodec copy -vcodec copy -- "s.$1"

with parameters like 0 99.

The file being broken is certainly not Kdenlive's fault. Kdenlive shouldn't
crash though.

Expected result:
1. Video does not get imported with a short explanation why not.

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

[konsole] [Bug 356270] Crash report after reboot

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |konsole
  Component|general |general
   Assignee|unassigned-b...@kde.org |konsole-de...@kde.org

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

[krita] [Bug 356303] New: Overlay blend mode appears incorrect in a 16 bit image

[Chris Jones via KDE Bugzilla]

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

Bug ID: 356303
   Summary: Overlay blend mode appears incorrect in a 16 bit image
   Product: krita
   Version: 2.9.9
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Color models
  Assignee: krita-bugs-n...@kde.org
  Reporter: cjo...@chrisj.com.au

The opacity of a layer or brush set to Overlay blend mode in a 16 bit image
produces a lower level of opacity than the same layer in an 8 bit image.

Reproducible: Always

Steps to Reproduce:
1. Create a new 16 bit image
2. Paint some grey on Layer 1
3. Set Layer 2 to Overlay and paint over the grey with white.  Note that the
strokes are grey rather than white
4. Convert the image to 8 bit and see the strokes on Layer 2 turn to opaque
white



Photoshop does not exhibit this behaviour - it displays the white as opaque
white regardless of the colour depth.  Saving the 16 bit image from Krita as a
.psd and reducing the colour depth to 8 bit in Photoshop retains Layer 2's
original grey appearance however.

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

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

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||smiha...@gmail.com

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

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

[plasmashell] [Bug 356302] New: P crashed when doing nothing

[Peter Jespersen via KDE Bugzilla]

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

Bug ID: 356302
   Summary: P crashed when doing nothing
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: flywh...@illogical.dk
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

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

-- Information about the crash:
Qt-Creator 3.5.0 + Google chrome 47.0.2526.73 64-bit running flash paused for
some hours.

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

Thread 30 (Thread 0x7f297b8af700 (LWP 2282)):
#0  0x7f2989e70c1d in poll () at /lib64/libc.so.6
#1  0x7f298ed97422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f298ed9900f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f297e031c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f298a56755f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f298967a0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2989e7904d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f2978869700 (LWP 2289)):
#0  0x7f2989e70c1d in poll () at /lib64/libc.so.6
#1  0x7f2986551e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f2986551f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f298a798a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f298a73fa63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f298a56284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f298d84b5f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f298a56755f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f298967a0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f2989e7904d in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f2965e77700 (LWP 2305)):
#0  0x7f2989e4aded in nanosleep () at /lib64/libc.so.6
#1  0x7f2989e729d4 in usleep () at /lib64/libc.so.6
#2  0x7f296b645d00 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#3  0x7f296ad46332 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#4  0x7f296ad46385 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#5  0x7f298967a0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2989e7904d in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f295700 (LWP 2314)):
#0  0x7f29865275e0 in g_ptr_array_set_size () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f2986551401 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f2986551d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f2986551f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f298a798a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f298a73fa63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f298a56284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f298d84b5f8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f298a56755f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f298967a0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f2989e7904d in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f295eba0700 (LWP 2318)):
#0  0x7f2986551453 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f2986551d80 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f2986551f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f298a798a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f298a73fa63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f298a56284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f298d84b5f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f298a56755f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f298967a0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f2989e7904d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f295d22b700 (LWP 2358)):
#0  0x7f298967e05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f298fffe7eb in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f298fffe819 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f298967a0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2989e7904d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f2955b2b700 (LWP 2398)):
#0  0x7f2986593cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f29865514b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f2986551d80 in  () at 

[solid] [Bug 329958] KDE Goes to black screen with mouse pointer after plugging in HDMI monitor and powering up from sleep

[rockmen1 via KDE Bugzilla]

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

rockmen1  changed:

   What|Removed |Added

 CC||rockm...@gmail.com

--- Comment #8 from rockmen1  ---
Same here, my HTPC connects to a HDMI TV, when I turn off/on the TV, plasma
desktop will be gone, leaving only a mouse pointer.

Arch Linux 4.2.5
KDE Plasma 5.4.3

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

[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #5 from Martin Klapetek  ---
Not manual control, but better sizing of the icons. Basically David in the
review has the same problem as you with the systray icons.

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

[ark] [Bug 320806] ark extract corrupted files (which actually are not corrupt)

[Damian Ivanov via KDE Bugzilla]

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

--- Comment #6 from Damian Ivanov  ---
At the time of reporting there was no warning for that just corrupted files.
Good to hear this is partly fixed.

Currently affected by the same issue is file-roller (gnome's ark) and they have
even no warning:
https://bugzilla.gnome.org/show_bug.cgi?id=701699

Despite my criticism for the long time to response I want to thank you for your
time working on Ark/kde Elvis.

https://github.com/libarchive/libarchive/issues/621

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

[kdenlive] [Bug 348988] Title clips cause random crashes

[Vincent PINON via KDE Bugzilla]

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

Vincent PINON  changed:

   What|Removed |Added

 CC||jens.verwae...@gmail.com

--- Comment #4 from Vincent PINON  ---
*** Bug 354625 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 344599] Thumbnails sidebar always open when okular starts

[Sumit Sahrawat via KDE Bugzilla]

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

--- Comment #5 from Sumit Sahrawat  ---
I'm on archlinux using xmonad and no KDE/Plasma.

```
$ okular --version
Qt: 4.8.7
KDE Development Platform: 4.14.14
Okular: 0.23.2
```

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

[yakuake] [Bug 313841] No keyboard shortcut for "Find" action

[arcanis via KDE Bugzilla]

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

arcanis  changed:

   What|Removed |Added

 CC||darkarca...@mail.ru

--- Comment #2 from arcanis  ---
same here, using latest git build for frameworks

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