[kdevelop] [Bug 355428] KDevelop leaving zombie threads behind

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #1 from Kevin Funk  ---
Can't reproduce that any longer.

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

[kdevelop] [Bug 337893] Selectbox to choose launch target on main toolbar.

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords||junior-jobs

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

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[Eike Hein via KDE Bugzilla]

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

--- Comment #7 from Eike Hein  ---
Yeah, it is.

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

[kdevelop] [Bug 353896] kdev-cppcheck fails with multiple "Extra Parameters"

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords||junior-jobs

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

[plasmashell] [Bug 359077] icons frame size is too wide

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Flags||VisualDesign+

--- Comment #6 from Eike Hein  ---
I personally like it the way it is; this needs the VDG to chime in anyhow.

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

[systemsettings] [Bug 360284] New: Sysstem settings crashed after opening the configure google account.

[Danail via KDE Bugzilla]

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

Bug ID: 360284
   Summary: Sysstem settings crashed after opening the configure
google account.
   Product: systemsettings
   Version: 5.4.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dido.ka...@gmail.com

Application: systemsettings5 (5.4.1)

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

-- Information about the crash:
- Custom settings of the application: Sysstem settings crashed after opening
the configure google account.

-- Backtrace:
Application: Системни настройки (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f97596c3800 (LWP 1423))]

Thread 6 (Thread 0x7f9746cab700 (LWP 1424)):
#0  0x7f9755e5a88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9753b6abd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9753b6c74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f9749a44a39 in QXcbEventReader::run (this=0xafdcd0) at
qxcbconnection.cpp:1105
#4  0x7f975654d2be in QThreadPrivate::start (arg=0xafdcd0) at
thread/qthread_unix.cpp:337
#5  0x7f975247b754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7f97532f56aa in start_thread (arg=0x7f9746cab700) at
pthread_create.c:333
#7  0x7f9755e65e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f9736e2f700 (LWP 1456)):
#0  0x7f9752dd5a63 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9752dd6167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9752dd62fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f975678429b in QEventDispatcherGlib::processEvents
(this=0x7f97280c4800, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f975672a75a in QEventLoop::exec (this=this@entry=0x7f9736e2ece0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f97565483d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f9754ed1f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f975654d2be in QThreadPrivate::start (arg=0xe16190) at
thread/qthread_unix.cpp:337
#8  0x7f975247b754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#9  0x7f97532f56aa in start_thread (arg=0x7f9736e2f700) at
pthread_create.c:333
#10 0x7f9755e65e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f972278d700 (LWP 1466)):
#0  0x7f9755e5a88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9752dd61ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9752dd62fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f975678429b in QEventDispatcherGlib::processEvents
(this=0x7f971803e350, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f975672a75a in QEventLoop::exec (this=this@entry=0x7f972278cce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f97565483d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f9754ed1f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f975654d2be in QThreadPrivate::start (arg=0x161c200) at
thread/qthread_unix.cpp:337
#8  0x7f975247b754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#9  0x7f97532f56aa in start_thread (arg=0x7f972278d700) at
pthread_create.c:333
#10 0x7f9755e65e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f9709a95700 (LWP 1502)):
#0  0x7f974eda1bb8 in ?? () from
/usr/lib/nvidia-304/tls/libnvidia-tls.so.304.131
#1  0x7f9752e194e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9752dd5cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9752dd6190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9752dd62fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9752dd6339 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f9752dfc965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f975247b754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#8  0x7f97532f56aa in start_thread (arg=0x7f9709a95700) at
pthread_create.c:333
#9  0x7f9755e65e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f970867e700 (LWP 1503)):
#0  0x7f9755e5644d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f975247a73c in ?? () from /usr/lib/nvidia-304/libGL.so.1
#2  0x7f974eda1bf7 in ?? () from
/usr/lib/nvidia-304/tls/libnvidia-tls.so.304.131
#3  0x7f9752e194e0 

[kdevelop] [Bug 354461] Cannot disable autocompletion popups

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Kevin Funk  ---
Same for master. Change has been reverted => Fixed.

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

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

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #16 from Kevin Funk  ---
@op: Do you still get this crash?

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

[kdevelop] [Bug 356638] False-positive warning with addEventListener()

[Kevin Funk via KDE Bugzilla]

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

--- Comment #2 from Kevin Funk  ---
Can you reduce that to a simple test case?

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

[krita] [Bug 360253] Krita crashes on v 2.9.11

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||b...@valdyas.org

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

The issue with Trust tablets is known, but since trust no longer seems to make
their tablets we cannot get the hardware to see what they have been doing with
their drivers and Windows 10. For the same reason, we also cannot make Krita
3.0 support Trust tablets reliably. Worse, regularly Windows 10 updates break
tablet support altogether, probably by interfering with the drivers, but that
goes for all tablets.

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

[plasmashell] [Bug 360282] New: Plasma crashes when switching primary output/disabling secondary monitor

[via KDE Bugzilla]

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

Bug ID: 360282
   Summary: Plasma crashes when switching primary output/disabling
secondary monitor
   Product: plasmashell
   Version: 5.5.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: alx.ku...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

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

-- Information about the crash:
- What I was doing when the application crashed:
Switching primary output because one desktop was completely non-responsive.
It appeared that a refresh rate doesn't hold after being updated.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7f1de8476700 (LWP 13686)):
#0  0x7f1df7f58bbd in poll () at /lib64/libc.so.6
#1  0x7f1dfcea1422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f1dfcea300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f1dea5c73c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f1df865132f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f1df77620a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f1df7f60fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f1de562f700 (LWP 13693)):
#0  0x7f1df87027d6 in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f1df88823b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#2  0x7f1df8882945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f1df8883b5e in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f1df46394ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f1df4639d80 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7f1df4639f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f1df8883d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#8  0x7f1df882ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f1df864c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#10 0x7f1dfb95edf8 in  () at /usr/lib64/libQt5Qml.so.5
#11 0x7f1df865132f in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f1df77620a4 in start_thread () at /lib64/libpthread.so.0
#13 0x7f1df7f60fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f1dd3a9b700 (LWP 13741)):
#0  0x7f1df776603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1dde587a13 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f1dde587197 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f1df77620a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1df7f60fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f1dcd980700 (LWP 13807)):
#0  0x7f1df7f58bbd in poll () at /lib64/libc.so.6
#1  0x7f1df4639e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1df4639f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1df8883d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f1df882ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f1df864c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f1dfb95edf8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f1df865132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f1df77620a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1df7f60fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f1dc77ea700 (LWP 13857)):
#0  0x7f1df467bd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f1df4639d1d in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1df4639f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1df8883d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f1df882ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f1df864c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f1dfb95edf8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f1df865132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f1df77620a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1df7f60fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f1dc5eff700 (LWP 13858)):
#0  0x7f1df776603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1dfe12686b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f1dfe126899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f1df77620a4 in start_thread () at /lib64/libpthread.so.0
#4  

[Baloo] [Bug 360283] New: Baloo crashes after a short time after login

[via KDE Bugzilla]

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

Bug ID: 360283
   Summary: Baloo crashes after a short time after login
   Product: Baloo
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: alx.ku...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.19.0)

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

-- Information about the crash:
Baloo crashes after a short time after login even if no activity happens at
all.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f695babf700 (LWP 13702)):
#0  0x7f6aa45dcbbd in poll () at /lib64/libc.so.6
#1  0x7f6aa101be64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6aa101bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6aa5208d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f6aa51afd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x004152cd in Baloo::FileContentIndexer::run() (this=0x2008dc0) at
/usr/src/debug/baloo-5.19.0/src/file/filecontentindexer.cpp:71
#6  0x7f6aa4fd3382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f6aa4fd632f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f6aa36170a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f6aa45e4fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6aa6aa8780 (LWP 13679)):
[KCrash Handler]
#6  0x7f6aa230725c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x7f6aa58a44cd in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x7f6aa58a1dc0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x7f6aa58b3949 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x0041d3e3 in
Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&)
(this=this@entry=0x1fee760, tr=tr@entry=0x7ffee9372950, url=...) at
/usr/src/debug/baloo-5.19.0/src/file/metadatamover.cpp:74
#11 0x0041d49d in Baloo::MetadataMover::removeFileMetadata(QString
const&) (this=0x1fee760, file=...) at
/usr/src/debug/baloo-5.19.0/src/file/metadatamover.cpp:66
#12 0x7f6aa51e173f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x004270d5 in Baloo::PendingFileQueue::removeFileIndex(QString
const&) (this=this@entry=0x1fd1f00, _t1=...) at
/usr/src/debug/baloo-5.19.0/build/src/file/moc_pendingfilequeue.cpp:217
#14 0x0041b686 in Baloo::PendingFileQueue::processCache()
(this=0x1fd1f00) at
/usr/src/debug/baloo-5.19.0/src/file/pendingfilequeue.cpp:89
#15 0x7f6aa51e173f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7f6aa51eef22 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7f6aa51e28bc in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7f6aa51b218d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7f6aa51b1e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7f6aa520877d in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x7f6aa5208ad9 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7f6aa101bc84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7f6aa101bed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7f6aa101bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7f6aa5208d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7f6aa51afd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#27 0x7f6aa51b78f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x0040a832 in main(int, char**) (argc=1, argv=) at
/usr/src/debug/baloo-5.19.0/src/file/main.cpp:88

Possible duplicates by query: bug 359847, bug 359672, bug 359325, bug 359292,
bug 359276.

Reported using DrKonqi

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

[trojita] [Bug 360273] In message view horizontal scroll bar appears when vertical scroll bar appears

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #2 from Jan Kundrát  ---
FYI, this is definitely not a regression due to the recent changes. I've 
been seeing this on Fusion "forever".

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

[krunner] [Bug 352146] Execute and submit krunner query via dbus or cli (emulate "enter" key)

[Murz via KDE Bugzilla]

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

Murz  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #2 from Murz  ---
I want to automate opening KDE Telepathy chat window with specific contact via
command line. KDE Telepathy don't allow this via command line, but this works
easy and well via KRunner, for example - command:
qdbus org.kde.krunner /App query 'Alexey Korepov'
and click "Enter" - opens KDE Telepathy chat window with 'Alexey Korepov'
contact.
And will be good to automate some other things via this way.

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

[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

[Sergei Gureev via KDE Bugzilla]

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

--- Comment #2 from Sergei Gureev  ---
Hi, Laurent!

I've send you an email with problem mail in attach. Please review it.
Thanks!

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

[kate] [Bug 360281] New: Running latest stable kate from konsole results in BadWindow error

[k3bBug via KDE Bugzilla]

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

Bug ID: 360281
   Summary: Running latest stable kate from konsole results in
BadWindow error
   Product: kate
   Version: Git
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: erben...@comcast.net

Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id:  0x2800a5f


Reproducible: Always

Steps to Reproduce:
1. download (git download) and compile kate following the directions here:
http://kate-editor.org/get-it-kde-4-x/
2. run kate from the terminal using the run.sh info shown on the above
referenced url page
3.  Sometimes when saving a file or closing a file tab the error reported in
details above is reported on the console
4. Sometimes it is reproducible if you select "Open" icon then just click the
"cancel" button

Actual Results:  
The following info is printed on the konsole window:
Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id:  0x2800a5f



Compiled on OpenSuse 13.1 (x86_64) with gcc 4.8.1 
git cmds used:
  git clone git://anongit.kde.org/kate
  git checkout KDE/4.14

This (the above reported errors) does not cause a crash but should be
investigated

I also tried running "kate/run-tests-in-xvfb.sh" with the following results
 # ./run-tests-in-xvfb.sh  build
Waiting for Xvfb with pid 25970 to launch...
Running tests...
Test project /home/erbenton/sdb/kde/kate/build
  Start  1: katetextbuffertest
 1/48 Test  #1: katetextbuffertest ...***Failed0.06 sec
  Start  2: kate-range_test
 2/48 Test  #2: kate-range_test ..   Passed0.46 sec
  Start  3: kate-undomanager_test
 3/48 Test  #3: kate-undomanager_test    Passed0.39 sec
  Start  4: kate-plaintextsearch_test
 4/48 Test  #4: kate-plaintextsearch_test    Passed0.68 sec
  Start  5: kate-regexpsearch_test
 5/48 Test  #5: kate-regexpsearch_test ...   Passed0.80 sec
  Start  6: kate-scriptdocument_test
 6/48 Test  #6: kate-scriptdocument_test .   Passed0.52 sec
  Start  7: kate-completion_test
 7/48 Test  #7: kate-completion_test .   Passed   20.76 sec
  Start  8: kate-wordcompletion_test
 8/48 Test  #8: kate-wordcompletion_test .   Passed9.64 sec
  Start  9: kate-searchbar_test
 9/48 Test  #9: kate-searchbar_test ..   Passed3.31 sec
  Start 10: kate-vimode_test
10/48 Test #10: kate-vimode_test .   Passed   40.44 sec
  Start 11: kate-movingcursor_test
11/48 Test #11: kate-movingcursor_test ...   Passed0.18 sec
  Start 12: kate-movingrange_test
12/48 Test #12: kate-movingrange_test    Passed0.94 sec
  Start 13: kate-katedocument_test
13/48 Test #13: kate-katedocument_test ...   Passed1.04 sec
  Start 14: kate-kateview_test
14/48 Test #14: kate-kateview_test ...   Passed0.59 sec
  Start 15: kate-revision_test
15/48 Test #15: kate-revision_test ...   Passed0.13 sec
  Start 16: kate-modificationsystem_test
16/48 Test #16: kate-modificationsystem_test .   Passed0.11 sec
  Start 17: kate-templatehandler_test
17/48 Test #17: kate-templatehandler_test    Passed0.20 sec
  Start 18: codefoldingtest
18/48 Test #18: codefoldingtest ..   Passed0.57 sec
  Start 19: kate-indenttest
19/48 Test #19: kate-indenttest ..***Failed9.83 sec
  Start 20: kate-commands_test
20/48 Test #20: kate-commands_test ...   Passed0.30 sec
  Start 21: kate-scripting_test
21/48 Test #21: kate-scripting_test ..   Passed0.23 sec
  Start 22: kate-syntax_highlighting_test
22/48 Test #22: kate-syntax_highlighting_test    Passed0.23 sec
  Start 23: kate-bug286887_test
23/48 Test #23: kate-bug286887_test ..   Passed1.74 sec
  Start 24: kate-bug313759_test
24/48 Test #24: kate-bug313759_test ..   Passed0.71 sec
  Start 25: kate-bug313769_test
25/48 Test #25: kate-bug313769_test ..   Passed1.72 sec
  Start 26: kate-bug317111_test
26/48 Test #26: kate-bug317111_test ..   Passed0.25 sec
  Start 27: kte-documentcursor_test
27/48 Test #27: kte-documentcursor_test ..   Passed0.11 sec
  Start 28: kte-messageinterface
28/48 Test #28: kte-messageinterface .   Passed   26.25 sec
  Start 29: utf8.txt_create
29/48 Test #29: utf8.txt_create ..   Passed0.04 sec
  Start 30: utf8.txt_diff
30/48 Test #30: utf8.txt_diff    Passed0.00 sec
  Start 31: latin15.txt_create
31/48 Test #31: 

[kdenlive] [Bug 355987] continue crash on Ubuntu 15.10 in more situation (transform, title, move clips ....)

[via KDE Bugzilla]

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

bass...@hotmail.com changed:

   What|Removed |Added

 CC||bass...@hotmail.com

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

[muon] [Bug 360280] New: after pressing check for updates message appears Could not download packages

[Elric T via KDE Bugzilla]

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

Bug ID: 360280
   Summary: after pressing check for updates message appears Could
not download packages
   Product: muon
   Version: 5.4.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: elric.temp...@t-online.de
CC: aleix...@kde.org, sit...@kde.org

After a fresh restart
i opened the app and pressed check for updates.
The message Could not download packages appears afterwards. Details shows only
the text "Details"(which is strange enough).


Reproducible: Always

Steps to Reproduce:
1. open muon
2. click check for updates
3. message appears

Actual Results:  
"Could not download packages" message and details window shows only the text
"details".

Expected Results:  
checks for updates and downloades the list etc

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

[kdenlive] [Bug 352418] kdenlive 15.04.2 crashes randomly

[via KDE Bugzilla]

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

--- Comment #6 from bass...@hotmail.com ---
We can reproduce issue by adding a lot of Clips, including a Title Clip. Put
the cursor a bit before the Title Clip and hit play. First time it almost-never
crashes, second time it always crashes.

The project that has the issue has 6 video tracks (many MTS videos + one title
clip) and 3 Audio tracks. At least 3 videos are overlapping (including the
title clip) when the crash usually happens.

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

[kdenlive] [Bug 352418] kdenlive 15.04.2 crashes randomly

[via KDE Bugzilla]

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

bass...@hotmail.com changed:

   What|Removed |Added

 CC||bass...@hotmail.com

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

[partitionmanager] [Bug 354641] There is no "Confirm" button on "Edit mount point" window

[via KDE Bugzilla]

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

singlemanstra...@gmail.com changed:

   What|Removed |Added

 CC||singlemanstra...@gmail.com

--- Comment #2 from singlemanstra...@gmail.com ---
hi guys

I have this problem now but I'm unsure how to solve it. It's marked as fixed,
but I have no save or edit buttons at all when I edit mount info.

how do I solve this bug ?

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

[kde] [Bug 360279] New: Amarok media player-jovie-hd0

[sennhvi via KDE Bugzilla]

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

Bug ID: 360279
   Summary: Amarok media player-jovie-hd0
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sennhviw...@gmail.com

Application: plasma-desktop (4.11.11)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-37-generic x86_64
Distribution: Linux Mint 17.1 Rebecca

-- Information about the crash:
- What I was doing when the application crashed:
click Amarok to play music,uploading big file
- Unusual behavior I noticed:
jovie has been removed but ktts still alert missing.
After booting my pc,it alert some message like cannot find hd0(sorry I don't
get it).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff9d4f867c0 (LWP 2905))]

Thread 5 (Thread 0x7ff9a92a8700 (LWP 2909)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff9cdc3fffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7ff9cdc40039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7ff9c87b6182 in start_thread (arg=0x7ff9a92a8700) at
pthread_create.c:312
#4  0x7ff9d488147d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7ff91f89e700 (LWP 2910)):
#0  update_get_addr (ti=0x7ff9d178da50) at dl-tls.c:758
#1  0x7ff9d1325044 in get_thread_data () at thread/qthread_unix.cpp:188
#2  QThreadData::current () at thread/qthread_unix.cpp:219
#3  0x7ff9d1455af5 in postEventSourcePrepare (s=0x7ff918001350,
timeout=0x7ff91f89dc24) at kernel/qeventdispatcher_glib.cpp:263
#4  0x7ff9c80a468d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff9c80a4f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7ff9c80a50ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7ff9d14557be in QEventDispatcherGlib::processEvents
(this=0x7ff9180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#8  0x7ff9d14270af in QEventLoop::processEvents
(this=this@entry=0x7ff91f89dde0, flags=...) at kernel/qeventloop.cpp:149
#9  0x7ff9d14273a5 in QEventLoop::exec (this=this@entry=0x7ff91f89dde0,
flags=...) at kernel/qeventloop.cpp:204
#10 0x7ff9d1323c5f in QThread::exec (this=this@entry=0x1aaea80) at
thread/qthread.cpp:537
#11 0x7ff9d1408823 in QInotifyFileSystemWatcherEngine::run (this=0x1aaea80)
at io/qfilesystemwatcher_inotify.cpp:265
#12 0x7ff9d132632f in QThreadPrivate::start (arg=0x1aaea80) at
thread/qthread_unix.cpp:349
#13 0x7ff9c87b6182 in start_thread (arg=0x7ff91f89e700) at
pthread_create.c:312
#14 0x7ff9d488147d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7ff91d3ab700 (LWP 2912)):
#0  0x7ff9d487412d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff9c80a4fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff9c80a530a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff91dea7336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7ff9c80c9f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff9c87b6182 in start_thread (arg=0x7ff91d3ab700) at
pthread_create.c:312
#6  0x7ff9d488147d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7ff90fbb9700 (LWP 2913)):
#0  0x7ff9c80e68aa in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff9c80e6d29 in g_private_get () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff9c80ca3a0 in g_thread_self () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff9c80a50dd in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff9d14557be in QEventDispatcherGlib::processEvents
(this=0x7ff9080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7ff9d14270af in QEventLoop::processEvents
(this=this@entry=0x7ff90fbb8de0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7ff9d14273a5 in QEventLoop::exec (this=this@entry=0x7ff90fbb8de0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7ff9d1323c5f in QThread::exec (this=this@entry=0x1433210) at
thread/qthread.cpp:537
#8  0x7ff9d1408823 in QInotifyFileSystemWatcherEngine::run (this=0x1433210)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7ff9d132632f in QThreadPrivate::start (arg=0x1433210) at
thread/qthread_unix.cpp:349
#10 0x7ff9c87b6182 in start_thread (arg=0x7ff90fbb9700) at
pthread_create.c:312
#11 0x7ff9d488147d in clone () at

[kcalc] [Bug 353644] Constants buttons do not work

[Bruce via KDE Bugzilla]

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

--- Comment #8 from Bruce  ---
Thanks, Luigi!  I look forward to using the fixed version when it becomes
available on Archlinux.

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

[plasmashell] [Bug 360277] Everytime i log in Plasma crahes

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[frameworks-kded] [Bug 360245] kded crashing with Qt 5.6.0-rc

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 360278] New: Android client stops working after some time in Android 6

[Daniel via KDE Bugzilla]

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

Bug ID: 360278
   Summary: Android client stops working after some time in
Android 6
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: c...@daniel.priv.no

Clipboard sharing stops working after running on some time on Android 6.

Permanent work around:
Go to Settings: Battery: Battery Optimization, and select KDE Connect and
choose Don’t optimize.

Temporary work around:
Reopen the KDE Connect app.

Based on the work arounds, I guess that the app is prevented from running in
the background after some time due to battery policies in Android 6. 

Sony Xperia Z3 with Sony Concept Software (Android 6.0 preview), latest KDE
Connect from the Google Play Store.

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

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

[Quanah Gibson-Mount via KDE Bugzilla]

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

Quanah Gibson-Mount  changed:

   What|Removed |Added

 CC||qua...@zimbra.com

--- Comment #22 from Quanah Gibson-Mount  ---
These patches don't work with the current release:

../coregrind/libcoregrind-amd64-linux.a(libcoregrind_amd64_linux_a-image.o): In
function `get_slowcase':
/tmp/valgrind/valgrind-3.11.0/coregrind/m_debuginfo/image.c:636: undefined
reference to `tinfl_decompress_mem_to_mem'
collect2: error: ld returned 1 exit status
make[3]: *** [memcheck-amd64-linux] Error 1

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

[plasmashell] [Bug 360277] New: Everytime i log in Plasma crahes

[Rodrigo de Araujo via KDE Bugzilla]

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

Bug ID: 360277
   Summary: Everytime i log in Plasma crahes
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: araujorodrigo1...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.3-300.fc23.x86_64+debug x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
I received a message the Plasma had crashed, but nothing really happened. I
keep on using it perfectly, including the appeareance of widgets which is
untouched.

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

Thread 8 (Thread 0x7f5c2b7a5700 (LWP 2007)):
#0  0x7f5c43bdcfdd in poll () at /lib64/libc.so.6
#1  0x7f5c4a096272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f5c4a097ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f5c2e0cfda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f5c447e53de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f5c42f2060a in start_thread () at /lib64/libpthread.so.0
#6  0x7f5c43be8a4d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f5c28d54700 (LWP 2070)):
#0  0x7f5c43bdcfdd in poll () at /lib64/libc.so.6
#1  0x7f5c3f10016c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f5c3f10027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f5c44a1cecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f5c449c3eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f5c447e0434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f5c48b2d9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f5c447e53de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f5c42f2060a in start_thread () at /lib64/libpthread.so.0
#9  0x7f5c43be8a4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f5c20e71700 (LWP 2091)):
#0  0x7f5c43bdcfdd in poll () at /lib64/libc.so.6
#1  0x7f5c3f10016c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f5c3f10027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f5c44a1cecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f5c449c3eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f5c447e0434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f5c48b2d9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f5c447e53de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f5c42f2060a in start_thread () at /lib64/libpthread.so.0
#9  0x7f5c43be8a4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f5c1a1a0700 (LWP 2483)):
#0  0x7f5c43bdcfdd in poll () at /lib64/libc.so.6
#1  0x7f5c3f10016c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f5c3f10027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f5c44a1cecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f5c449c3eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f5c447e0434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f5c48b2d9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f5c447e53de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f5c42f2060a in start_thread () at /lib64/libpthread.so.0
#9  0x7f5c43be8a4d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f5c18957700 (LWP 2526)):
#0  0x7f5c42f25b10 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5c4b986514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f5c4b986559 in  () at /lib64/libQt5Script.so.5
#3  0x7f5c42f2060a in start_thread () at /lib64/libpthread.so.0
#4  0x7f5c43be8a4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f5c12768700 (LWP 2635)):
#0  0x7f5c43bdcfdd in poll () at /lib64/libc.so.6
#1  0x7f5c3f10016c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f5c3f10027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f5c44a1cecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f5c449c3eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f5c447e0434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f5c12db49f5 in QQuickXmlQueryEngine::run() () at

[trojita] [Bug 360273] In message view horizontal scroll bar appears when vertical scroll bar appears

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Thomas Lübking  ---
Affects Fusion & Gtk+ but not Breeze and Virtuality.
Either some frame or related to scrollbars in/out of the frame.

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

[yakuake] [Bug 360234] Cursor not in focus while Yakuake it is

[Leonardo Romor via KDE Bugzilla]

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

--- Comment #3 from Leonardo Romor  ---
"If you move the mouse pointer across the broken cursor you will see it gets
filled in. "
Well, for me doesn't work =(
As you can see the cursor "wrongly" toogle only when I place the mouse over the
window of yakuake otherwise it works just fine. Also, is not only a "view"
issue, since I can't copy paste with ctrl+shift+c/v until I click outside the
window and then inside again.

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

[kdenlive] [Bug 360246] git master 2016-03-08 - melt ignores rotation flag, proxy clip generator does not....

[Evert Vorster via KDE Bugzilla]

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

--- Comment #2 from Evert Vorster  ---
Created attachment 97780
  --> https://bugs.kde.org/attachment.cgi?id=97780=edit
video clip with the flag set

This is a video with the flag set... kind of difficult getting a video small
enough to go under the 4mb file limit...

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

[yakuake] [Bug 360234] Cursor not in focus while Yakuake it is

[Leonardo Romor via KDE Bugzilla]

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

--- Comment #2 from Leonardo Romor  ---
Created attachment 97779
  --> https://bugs.kde.org/attachment.cgi?id=97779=edit
Bug video

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

[kdenlive] [Bug 360246] git master 2016-03-08 - melt ignores rotation flag, proxy clip generator does not....

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

Summary|git master 2016-03-08 - |git master 2016-03-08 -
   |kdenlive ignores rotation   |melt ignores rotation flag,
   |flag on video clips, proxy  |proxy clip generator does
   |clips go nuts.  |not

--- Comment #1 from Evert Vorster  ---
Some more info on this footage. 
melt footage.mpg plays the video, with no rotation, ie: the way it was recorded
vlc footage.mpg plays it rotated, ie: honors the rotation flag

The main problem here is that the proxy generator (ffmpeg) honors the rotation
flag, while the rest of kdenlive, using mlt, does not. 

I have not noticed this issue before, as I used to edit without proxy clips on
much more powerful hardware. :D

I am able to manually strip out the rotation flag in the original footage with
ffmpeg and 
-metadata:s:v rotate="0"

But manually stripping out the rotation flag is a pain. 
So, I tried to just put the same command argument into the proxy clip generator
command line, but for some reason, it looks like kdenlive is messing with the
command line being passed to the proxy clip generator.
It does not pass this command to ffmpeg when I add it to the proxy clip
generator. 

I am also noticing something else now 
When I used to rotate these clips manually before, I was able to hit "fit to
width" and it would scale the clip so that the width fitted, or scale height so
that the entire thing fitted. 
It does not do that anymore, basically it does not look like the rotate
filters (I tried all of them) does not modify the width/height parameters of
the video clip. 

Wait, let me upload a small clip with the rotation flag set, and you can play
with it yourself.

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

[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything

[Luigi Toscano via KDE Bugzilla]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #2 from Luigi Toscano  ---
For reference:
https://blogs.kde.org/2015/09/04/konsoles-new-manage-profiles-configure-dialog

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

[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons

[John Choate via KDE Bugzilla]

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

John Choate  changed:

   What|Removed |Added

 CC||jdcho...@gmail.com

--- Comment #7 from John Choate  ---
Still seeing this in Plasma 5.5.95 :(

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

[plasmashell] [Bug 360276] Battery Plasmoid review

[andreas via KDE Bugzilla]

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

--- Comment #1 from andreas  ---
Created attachment 97778
  --> https://bugs.kde.org/attachment.cgi?id=97778=edit
battery plasmoid

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

[plasmashell] [Bug 360276] New: Battery Plasmoid review

[andreas via KDE Bugzilla]

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

Bug ID: 360276
   Summary: Battery Plasmoid review
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Battery Monitor
  Assignee: k...@privat.broulik.de
  Reporter: kain...@gmail.com
CC: plasma-b...@kde.org

the sizing is prety good maybe a link to the kinforcenter (or an kcm module) to
the battery consumtion stuff would be awesome.

don't show the user in the widget something like that:

"No screen or keeboard brightness contrast available"

maybe you can add this to the kcm where you give the user the feedback that
something is not available but not in the main plasmoid (we don't show the user
SOMETHING IS BROKEN at least not when it is only not available.

thange the widget icon to the "battery" icon please which is available in
breeze.

Reproducible: Always

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

[plasmashell] [Bug 360275] Panel lock & unlock behavior

[andreas via KDE Bugzilla]

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

--- Comment #4 from andreas  ---
Created attachment 9
  --> https://bugs.kde.org/attachment.cgi?id=9=edit
lock stuff on desktop not needed

As we have the edit mode at the panel burger menu AND on the desktop burger
menu there is no need of this lock / unlock stuff any more. In addition lock /
unlock plasmoid when right click on the desktop look out of place cause right
click is ordinary an config of the selected stuff and the user select the
desktop so not a widget. I would also remove the add widget and add panel stuff
cause they are available with the burger menu.

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

[plasmashell] [Bug 360275] Panel lock & unlock behavior

[andreas via KDE Bugzilla]

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

--- Comment #3 from andreas  ---
Created attachment 97776
  --> https://bugs.kde.org/attachment.cgi?id=97776=edit
Panel and widget mode

Panel and Widget Mode

reduce information and bring there more consistency.

Widget
-
when you use right click on Widgets you come to edit widget and remove widget
(new) if there is an alternative widget you get also this information. that's
it. Same behavior as on the desktop

Panel
---
For the panel we have the Burger Menu that opens the panel configuration mode.
There you can add widgets, move widgets, (edit and delete widgets too), add and
remove a panel and config the panel. everything done.

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

[kscreenlocker] [Bug 352650] Random white area in screen lock settings

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

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

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

[ksmserver] [Bug 355589] Theme selection not shown in the screenlocker KCM

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

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

--- Comment #1 from Wolfgang Bauer  ---
Actually this is the same as bug#352650...

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

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

[plasmashell] [Bug 360275] Panel lock & unlock behavior

[andreas via KDE Bugzilla]

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

--- Comment #2 from andreas  ---
Created attachment 97775
  --> https://bugs.kde.org/attachment.cgi?id=97775=edit
panel widget right click

Right click on widget


as you can see in the screenshot there are different behaviours on right click
to an widget. In addition there are a lot of informations most of the time
different if you lock or unlock widgets. In addition there are sometimes
submenues with ONE entry so an additional click with no additional information.

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

[plasmashell] [Bug 360275] Panel lock & unlock behavior

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

  Flags||Usability+

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

[plasmashell] [Bug 360275] Panel lock & unlock behavior

[andreas via KDE Bugzilla]

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

--- Comment #1 from andreas  ---
Created attachment 97774
  --> https://bugs.kde.org/attachment.cgi?id=97774=edit
panel configuration

Panel configuration
--
Panel configuration is available if the widget is unlocked. when you look at
the screenshot PanelConfiguration.png on the right click you have in addition
the add panel stuff so to be consistent it would be nice to add it in the more
settings of panel config too.

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

[trojita] [Bug 360249] Optimize compile flag is used without concern for the variable CMAKE_BUILD_TYPE

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #11 from Jan Kundrát  ---
> I wish to know how to disable tests. I sought the information 
> but did not find it.

Probably something like -DCMAKE_DISABLE_FIND_PACKAGE_Qt5Test=true (or 
Qt5Tests?) should do the trick.

Or just do not run `make all` (which is a default target executed by 
`make`), but `make trojita`, that's even easier.

> -fvisibility=hidden -fvisibility-inlines-hidden -O2 -g -DNDEBUG 
> -fPIC   -fPIC

Trojita's build system never specifies this particular chunk of CXXFLAGS 
directly. I've tried grepping my /usr/lib64/cmake, but I don't see an 
obvious culprit in there.

We might workaround by carefuly placing user's CXXFLAGS after any 
library-provided CXXFLAGS, but in order to fix this, we need to know which 
module injects these flags.

Anyway, this worked for me:

  $ cd clean/build/dir
  $ cmake -DCMAKE_CXX_FLAGS="-O0 -march=native" -DCMAKE_BUILD_TYPE=Debug 
~/work/prog/trojita
  $ make -j4 VERBOSE=1
  ...
  /usr/bin/c++   -DQT_CORE_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_TO_ASCII -DQT_STRICT_ITERATORS -DQT_USE_FAST_CONCATENATION 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -Wall -Wsign-compare 
-O2 -O0 -march=native -std=c++11 -fvisibility=hidden 
-fvisibility-inlines-hidden -Werror -g -fPIC 
-I/home/jkt/work/prog/trojita/src 
-I/home/jkt/work/prog/_trojita-build/cxxflags -isystem /usr/include/qt5 
-isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore 
-isystem /usr/lib64/qt5/mkspecs/linux-g++-fPIC -o 
CMakeFiles/Streams.dir/src/Streams/DeletionWatcher.cpp.o -c 
/home/jkt/work/prog/trojita/src/Streams/DeletionWatcher.cpp

> So, the optimization level is '-O2' even though I specified 
> '-O0'. The CXXFLAGS
> variable in the shell when cmake was called also had '-pipe -march=native'
> which are missing, so we see that the variable from the shell 
> passed to CMake was not used.

Considering that you specified both an env var and an explicit option to 
cmake when configuring, it makes sense that the -DCMAKE_CXX_FLAGS has won. 
That's not a bug.

> I don't see where it is getting double '-O2' from. It is not coming from my
> CXXFLAGS or CFLAGS environment variable.  It could be
> - the line adding -O2 to CMAKE_CXX_FLAGS is being called twice.
> - there is some rule where CMAKE_CXX_FLAGS is used twice.
> This could happen by being used once directly as CMAKE_CXX_FLAGS and another
> being appended to CXXFLAGS.

I'm willing to bet that this comes from some external library cmake config. 
As I wrote above, it's apparently build-type-dependant, so add a 
-DCMAKE_BUILD_TYPE=Debug and be done with it.

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

[plasmashell] [Bug 360275] New: Panel lock & unlock behavior

[andreas via KDE Bugzilla]

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

Bug ID: 360275
   Summary: Panel lock & unlock behavior
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: kain...@gmail.com

Some ideas to bring more consistency into the widgets an panels and reduce
duplicated information.

Reproducible: Always

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

[kdevelop] [Bug 357585] ASSERT: "offset >= start" in clangutils.cpp

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords|release_blocker |

--- Comment #11 from Kevin Funk  ---
No longer a release blocker, I've guarded the code.

I'm assuming a bug in libclang here, there's not a lot we can do I'm afraid.

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

[kdevelop] [Bug 357585] ASSERT: "offset >= start" in clangutils.cpp

[Kevin Funk via KDE Bugzilla]

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

--- Comment #10 from Kevin Funk  ---
Git commit cf87a91c1ae37d61d912448665208d6360701be5 by Kevin Funk.
Committed on 08/03/2016 at 23:15.
Pushed by kfunk into branch '5.0'.

ClangUtils: Bail out after assert in relmode

Make sure we never crash here.

M  +7-1languages/clang/util/clangutils.cpp

http://commits.kde.org/kdevelop/cf87a91c1ae37d61d912448665208d6360701be5

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

[kdevelop] [Bug 335470] Build Directory change is ignored

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/b79b903762afde553bed0d
   ||aa06bde19bf42f7298
 Resolution|--- |FIXED

--- Comment #4 from Kevin Funk  ---
Git commit b79b903762afde553bed0daa06bde19bf42f7298 by Kevin Funk.
Committed on 08/03/2016 at 23:15.
Pushed by kfunk into branch '5.0'.

Notify settings about build dir change.

Summary:
Notify settings about build dir change.

Reviewers: kfunk

Reviewed By: kfunk

Subscribers: kdevelop-devel, coopht

Projects: #kdevelop

Differential Revision: https://phabricator.kde.org/D1089

M  +2-0projectmanagers/custom-buildsystem/configwidget.cpp

http://commits.kde.org/kdevelop/b79b903762afde553bed0daa06bde19bf42f7298

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

[kdevelop] [Bug 335470] Build Directory change is ignored

[Kevin Funk via KDE Bugzilla]

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

--- Comment #3 from Kevin Funk  ---
Unrelated to your patch though. Will push your patch for now.

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

[kdevelop] [Bug 335470] Build Directory change is ignored

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Kevin Funk  ---
While your patch fixes the issue with the build directory, I'm now getting a
crash when I reopen the Configuration dialog a second time. Sigh.

Trace:
=
==6091==ERROR: AddressSanitizer: heap-use-after-free on address 0x611001ccded8
at pc 0x7f81def8a6a2 bp 0x7ffd71abd790 sp 0x7ffd71abd788
READ of size 1 at 0x611001ccded8 thread T0
#0 0x7f81def8a6a1 in ConfigWidget::setTool(CustomBuildSystemTool const&)
/home/kfunk/devel/src/kf5/kdevelop-stable/projectmanagers/custom-buildsystem/configwidget.cpp:85:40
#1 0x7f81def88690 in ConfigWidget::changeAction(int)
/home/kfunk/devel/src/kf5/kdevelop-stable/projectmanagers/custom-buildsystem/configwidget.cpp:100:9
#2 0x7f81def89e8e in ConfigWidget::loadConfig(CustomBuildSystemConfig)
/home/kfunk/devel/src/kf5/kdevelop-stable/projectmanagers/custom-buildsystem/configwidget.cpp:70:5
#3 0x7f81def9284f in
CustomBuildSystemConfigWidget::changeCurrentConfig(int)
/home/kfunk/devel/src/kf5/kdevelop-stable/projectmanagers/custom-buildsystem/custombuildsystemconfigwidget.cpp:164:5
#4 0x7f81def95e09 in CustomBuildSystemConfigWidget::loadFrom(KConfig*)
/home/kfunk/devel/src/kf5/kdevelop-stable/projectmanagers/custom-buildsystem/custombuildsystemconfigwidget.cpp:111:5
#5 0x7f81def9b83c in CustomBuildSystemKCModule::reset()
/home/kfunk/devel/src/kf5/kdevelop-stable/projectmanagers/custom-buildsystem/kcm_custombuildsystem.cpp:47:5
#6 0x7f821b73fa4a in
KDevelop::ConfigDialog::addConfigPageInternal(KPageWidgetItem*,
KDevelop::ConfigPage*)
/home/kfunk/devel/src/kf5/kdevplatform-stable/shell/configdialog.cpp:173:5
#7 0x7f821b73c33f in
KDevelop::ConfigDialog::addConfigPage(KDevelop::ConfigPage*,
KDevelop::ConfigPage*)
/home/kfunk/devel/src/kf5/kdevplatform-stable/shell/configdialog.cpp:157:9
#8 0x7f821b73ab3d in
KDevelop::ConfigDialog::ConfigDialog(QVector const&,
QWidget*, QFlags)
/home/kfunk/devel/src/kf5/kdevplatform-stable/shell/configdialog.cpp:51:9
#9 0x7f821b2e698f in
KDevelop::ProjectControllerPrivate::projectConfig(QObject*)
/home/kfunk/devel/src/kf5/kdevplatform-stable/shell/projectcontroller.cpp:149:32
#10 0x7f821b2be080 in
KDevelop::ProjectController::configureProject(KDevelop::IProject*)
/home/kfunk/devel/src/kf5/kdevplatform-stable/shell/projectcontroller.cpp:974:5
#11 0x7f81eb33bc3b in ProjectTreeView::openProjectConfig()
/home/kfunk/devel/src/kf5/kdevplatform-stable/plugins/projectmanagerview/projecttreeview.cpp:368:9
#12 0x7f81eb34df5d in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (ProjectTreeView::*)()>::call(void
(ProjectTreeView::*)(), ProjectTreeView*, void**)
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501:13
#13 0x7f81eb34dae1 in void QtPrivate::FunctionPointer::call, void>(void
(ProjectTreeView::*)(), ProjectTreeView*, void**)
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520:13
#14 0x7f81eb34d20b in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:143:17
#15 0x7f8215a44e1e in QMetaObject::activate(QObject*, int, int, void**)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2b4e1e)
#16 0x7f82162ff411 in QAction::triggered(bool)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x151411)
#17 0x7f8216301897 in QAction::activate(QAction::ActionEvent)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x153897)
#18 0x7f8216483df1  (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2d5df1)
#19 0x7f821648a08b  (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2dc08b)
#20 0x7f821648dfff in QMenu::mouseReleaseEvent(QMouseEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2d)
#21 0x7f821634bf87 in QWidget::event(QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x19df87)
#22 0x7f821648ea52 in QMenu::event(QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2e0a52)
#23 0x7f821630905b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15b05b)
#24 0x7f821630ec18 in QApplication::notify(QObject*, QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x160c18)
#25 0x7f8215a165ba in QCoreApplication::notifyInternal(QObject*, QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2865ba)
#26 0x7f821630db31 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15fb31)
#27 

[trojita] [Bug 356865] Sent messages with Bcc receipients does not list Bcc

[Erik Quaeghebeur via KDE Bugzilla]

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

--- Comment #3 from Erik Quaeghebeur  ---
(In reply to Jan Kundrát from comment #2)
>
> 1) Generate the plaintext of the message, place the Bcc header into a 
> well-known place (end of all headers sounds like a trivial fix, if it's 
> legal),

It is legal to place Bcc at the end. It is also legal to place it at the top,
which would result in only having to remember one offset, I think.

> 2) Remember the offsets of the beginning and end of this sensitive area,
> 3) Change the code to not treat the just-saved message as a single entity, 
> but rather as a pair of (stuff before the whitened-out, stuff after), and 
> pass this pair to BURL.

I have tried to wrap my head around the code, but I'm not there yet.

Orthogonal to that, I wonder whether it would make more sense to instead split
the message in (header, body), have header+bcc and header. I guess that would
essentially mean uploading the header twice, which may still be acceptable
bandwidth-wise, and seems simpler and more generic (also applicable to other
cases where the header should be different for the sent-out and for the stored
version, e.g., Resent-Bcc, which cannot appear at the end of the header...
although it could appear at the top).

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

[kphotoalbum] [Bug 360196] can't open Kphotoalbum ("error reading next element"): found duplicate attributes in tags in index.xml photos database

[Johannes Zarl-Zierl via KDE Bugzilla]

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

--- Comment #11 from Johannes Zarl-Zierl  ---
Git commit 1d32f069207ddbf044f379f057ac51405b3b016e by Johannes Zarl-Zierl.
Committed on 08/03/2016 at 22:53.
Pushed by johanneszarl into branch 'master'.

Prevent duplication of special categories.

Take care that a category in the index.xml file cannot have the same
name as the "Folder" or "Media type" category.
This prevents the creation of an ill-formed xml file in these cases.

M  +8-2XMLDB/FileReader.cpp

http://commits.kde.org/kphotoalbum/1d32f069207ddbf044f379f057ac51405b3b016e

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Søren Holm via KDE Bugzilla]

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

--- Comment #51 from Søren Holm  ---
Removing dbus-update-activation-environment from startkde did not solve it or
me. skipping "--systemd" was no luck either.

Interestingly enough, the first login running completely without
dbus-update-activation-environment but with
/usr/lib/x86_64-linux-gnu/libexec/ksyncdbusenv instead work well for ONE login.
After that it made no difference.

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

[krunner] [Bug 360268] KRunner autocomplete should not override the typed character case

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 360274] activity pager review

[andreas via KDE Bugzilla]

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

--- Comment #1 from andreas  ---
Created attachment 97773
  --> https://bugs.kde.org/attachment.cgi?id=97773=edit
activity pager

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

[plasmashell] [Bug 360274] activity pager review

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

  Flags||Usability+, VisualDesign+

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

[plasmashell] [Bug 360274] New: activity pager review

[andreas via KDE Bugzilla]

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

Bug ID: 360274
   Summary: activity pager review
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Pager
  Assignee: plasma-b...@kde.org
  Reporter: kain...@gmail.com

Settings:
-
- Display Texty
  Activity number, Activity name, No text

the activity size scall according to the activity name but only after an
restart of plasma. but well done. maybe the text color of the selected activity
change to the selected text color.

- Display Icon
is only available if the pager is bigger (as I expect to work also for the
settings in Display Text.

- Slecting current desktop: 
  Does nothing, Show desktop, show the dashboard

I did not find out what this feature is used for. As fare as I know is that the
dashboard stuff was removed anywhere. Maybe an additional information is needed
(if this setting is needed)

-
at the general icon in preferences I would prefere the icon
preferences-desktop-plasma instead of the desktop icon.
-

Right click to the activity icon
-
works usefull maybe an remove widget entry would be nice but therefore I make
an global bug report. will add the number here.

Reproducible: Always

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[Søren Holm via KDE Bugzilla]

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

Søren Holm  changed:

   What|Removed |Added

 CC||s...@sgh.dk

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

[kdevplatform] [Bug 358776] per-project tab colors not updated on palette change

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords|release_blocker |

--- Comment #2 from Kevin Funk  ---
I would not consider this a release blocker though -> dropping the keyword.

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

[trojita] [Bug 360273] New: In message view horizontal scroll bar appears when vertical scroll bar appears

[Erik Quaeghebeur via KDE Bugzilla]

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

Bug ID: 360273
   Summary: In message view horizontal scroll bar appears when
vertical scroll bar appears
   Product: trojita
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Desktop GUI
  Assignee: trojita-b...@kde.org
  Reporter: kdeb...@equaeghe.nospammail.net

Since the new envelope design (I think), whenever a message is (vertically) too
long for the window so that a vertical scroll bar appears, also a horizontal
scroll bar appears. I guess this is due to the horizontal size of the vertical
scroll bar not being taken into account in some width calculation somewhere.

Reproducible: Always

Steps to Reproduce:
1. look at message in some message view (wide, compact, one at a time, window)
2. manipulate window size so that content does not fit vertically

Actual Results:  
vertical scroll bar appears and horizontal scroll bar appears

Expected Results:  
vertical scroll bar appears and horizontal scroll bar does not appear

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

[kphotoalbum] [Bug 360196] can't open Kphotoalbum ("error reading next element"): found duplicate attributes in tags in index.xml photos database

[Tobias Leupold via KDE Bugzilla]

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

--- Comment #10 from Tobias Leupold  ---
Just for the moment:

A workaround would be: open the v6 database with KPA 4.7.1. You get doubled
"Folder" and "Media Type" categories, one is the real one one is empty for
each. Delete the empty ones (the "real" ones are not shown in the category
settings and can't be deleted). Save the database.

Doing so, the read error does not occur anymore here.

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

[www.kde.org] [Bug 360272] New: Broken link to KF5.5.0 sources

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 360272
   Summary: Broken link to KF5.5.0 sources
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: aspotas...@gmail.com

https://www.kde.org/announcements/kde-frameworks-5.5.0.php links to
http://download.kde.org/stable/frameworks/5.5/ which returns error 404.

Reproducible: Always

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

[kcalc] [Bug 353644] Constants buttons do not work

[Luigi Toscano via KDE Bugzilla]

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

Luigi Toscano  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kcal
   ||c/a4dfbe234f8a6d1a052c36e53
   ||5be60f030bf35ca
   Version Fixed In||15.12.3
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Luigi Toscano  ---
Git commit a4dfbe234f8a6d1a052c36e535be60f030bf35ca by Luigi Toscano.
Committed on 08/03/2016 at 22:19.
Pushed by ltoscano into branch 'Applications/15.12'.

Fix click event for constant buttons

It looks like the new style of "connect" tries to use the clicked
signal as defined inside the function, which does not trigger
slotClicked(). This change explicitly use the clicked signal from
the (grand)parent class and the expected chain of signal/slots
triggering is restored.
REVIEW: 127017
FIXED-IN: 15.12.3

M  +1-1kcalc_const_button.cpp

http://commits.kde.org/kcalc/a4dfbe234f8a6d1a052c36e535be60f030bf35ca

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

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

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

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

[kinfocenter] [Bug 360271] New: KInfoCenter crashes after clicking Energy Information

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 360271
   Summary: KInfoCenter crashes after clicking Energy Information
   Product: kinfocenter
   Version: 5.5.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: aspotas...@gmail.com

KInfoCenter crashes immediately after loading the Energy Information view.

=

aspotashev@cell ~ $ gdb kinfocenter 
GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kinfocenter...Reading symbols from
/usr/lib64/debug//usr/bin/kinfocenter.debug...(no debugging symbols
found)...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/kinfocenter 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Qt: gdb: -nograb added to command-line options.
 Use the -dograb option to enforce grabbing.
[New Thread 0x7fffe7be5700 (LWP 24609)]
kf5.kservice.sycoca: Opening ksycoca from
"/home/aspotashev/.cache/ksycoca5_ru_EoKFmqbKC+uh8_5YVTRGFRshero="
kf5.kservice.sycoca: checking file timestamps
Error loading plugin "kcm_energyinfo" "Динамическая библиотека не найдена." 
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin",
"/usr/lib64/kde4/plugins") 
The environment variable QT_PLUGIN_PATH might be not correctly set
[New Thread 0x7fffdaf32700 (LWP 24700)]
org.kde.kwindowsystem: Loaded plugin
"/usr/lib64/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so"
for platform "xcb"
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
QQmlExpression: Expression
file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:447:43
depends on non-NOTIFYable properties:
Solid::Battery::serial
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:221:9: QML Binding:
Binding loop detected for property "value"
file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/Graph.qml:64:
TypeError: Cannot read property 'x' of undefined
kf5.kservice.sycoca: checking file timestamps
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
QMetaObject::indexOfSignal: signal visibleChanged() from QQuickItem redefined
in ToolTip
Start of DAVE debug
no role explicitly changed, notifying all the properties
we want to emit  8 signals
signal ids are  QVector(6, 7, 8, 9, 10, 11, 12, 13)
listing items
QQmlDMAbstractItemModelData(0x273abe0)
QQmlDMAbstractItemModelData(0x273cb80)
QQmlDMAbstractItemModelData(0x27f73c0)
QQmlDMAbstractItemModelData(0x2155130)
QQmlDMAbstractItemModelData(0x273e8a0)
QQmlDMAbstractItemModelData(0x2150900)
QQmlDMAbstractItemModelData(0x276d2b0)
QQmlDMAbstractItemModelData(0x281c570)
QQmlDMAbstractItemModelData(0x276b170)
QQmlDMAbstractItemModelData(0x2774100)
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE notifying delegates
DAVE 

[plasmashell] [Bug 360270] activity widget wrong text padding

[andreas via KDE Bugzilla]

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

--- Comment #1 from andreas  ---
Created attachment 97772
  --> https://bugs.kde.org/attachment.cgi?id=97772=edit
activity plasmoid

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

[plasmashell] [Bug 359833] Have option in Pager Settings to enable/disable tooltip?

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

  Flags||Usability?

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

[plasmashell] [Bug 360270] activity widget wrong text padding

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

  Flags||Usability+

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

[plasmashell] [Bug 360270] New: activity widget wrong text padding

[andreas via KDE Bugzilla]

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

Bug ID: 360270
   Summary: activity widget wrong text padding
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Activity Switcher
  Assignee: ivan.cu...@kde.org
  Reporter: kain...@gmail.com
CC: plasma-b...@kde.org

activities don't use the plasmoid style for selected elements like the task
manager in the panel was use. In addition it is not possible to use a vertical
activitie bar and the text scaling and padding is not well when use it on the
desktop.

Reproducible: Always

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

[kwin] [Bug 360269] New: Build failure with Qt 5.7 branch

[Christoph Feck via KDE Bugzilla]

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

Bug ID: 360269
   Summary: Build failure with Qt 5.7 branch
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: cf...@kde.org

kwin/plugins/qpa/abstractplatformcontext.h:42:22:
error:
'void (* KWin::QPA::AbstractPlatformContext::getProcAddress(const
QByteArray&))()' marked override, but does not override

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

[krunner] [Bug 360268] New: KRunner autocomplete should not override the typed character case

[Weng Xuetian via KDE Bugzilla]

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

Bug ID: 360268
   Summary: KRunner autocomplete should not override the typed
character case
   Product: krunner
   Version: 5.5.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: wen...@gmail.com

For example, if I have typed "KSYSGUARD" before. next time krunner will already
replace what I have type with upper case even I type lowercase.

Reproducible: Always

Steps to Reproduce:
1. Make sure history is empty
2. Type KSYSGUARD to start ksysguard
3. type "ksys"

Actual Results:  
ksys is replaced by "KSYS".

Expected Results:  
it should still keep what user have typed exactly.

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

[kdevelop] [Bug 360209] Crash with 'Overriders possible, show all'

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #9 from Kevin Funk  ---
Just verified: I can reproduce with v4.90.91, but not with 5.0 anymore. =>
Issue was fixed in the meantime.

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

[kdenlive] [Bug 356499] Consider changing interface display when moving effects in stack up and down in Properties Widget

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|Issues and suggestions with |Consider changing interface
   |the "Properties" widget |display when moving effects
   |(video example included)|in stack up and down in
   ||Properties Widget
   Severity|normal  |wishlist

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

[kdenlive] [Bug 359218] 15.13.0 git master - Using split mode in clip monitor after applying the rotate effect creates monitor glitches (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #1 from Jesse  ---
This issue seems to be resolved/fixed in the latest git builds of kdenlive.
Thanks!

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

[plasmashell] [Bug 283501] wish: OSDs for Wireless on/off, 3G on/off, GPS on/off and (un)docking

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #7 from Kai Uwe Broulik  ---
That issue is fixed in Wayland.

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

[kdenlive] [Bug 359213] 15.13.0 git master - "open file dialog" in Render Widget (under gnome) doesn't work right. (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 356499] Issues and suggestions with the "Properties" widget (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #5 from Jesse  ---
UPDATE: Issues #1 and #3 seem to be resolved/fixed in the latest git master
builds of Kdenlive. Thanks JB!

The final item in this report is merely a suggestion. If not found best, feel
free to close this bug. :)

Thanks.

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

[plasmashell] [Bug 283501] wish: OSDs for Wireless on/off, 3G on/off, GPS on/off and (un)docking

[Igor Poboiko via KDE Bugzilla]

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

--- Comment #6 from Igor Poboiko  ---
(In reply to Kai Uwe Broulik from comment #5)
> It does here, when I press Ctrl+Alt+K to switch layouts.

Oh! Surprise. Works for me as well.
Apparently it works only with "Alternative shortcut", but doesn't work with
xkb_group:ctrl_shift_toggle (the "Ctrl+Shift" main shortcut option in layouts
KCM).
Should I fill a new bugreport then? I guess the logic can be changed (from
"show OSD on shortcut" to "show OSD on layout change")

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

[kdenlive] [Bug 356498] Several workflow and design improvement suggestions for timeline widget (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #3 from Jesse  ---
Looks like issue #4 has been resolved/fixed in latest git master builds.
Thanks!

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

[kdenlive] [Bug 356501] Capitalize all items in Transitions & Effects widgets, and categorize items in the "Transitions" widget?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|Suggest capitalizing all|Capitalize all items in
   |items in Transitions &  |Transitions & Effects
   |Effects widgets, and|widgets, and categorize
   |categorize items in |items in the "Transitions"
   |transition widget?  |widget?

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

[kdenlive] [Bug 346608] Use Breeze Dark theme as program's default look?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|SUGGESTION: Breeze dark |Use Breeze Dark theme as
   |theme by default?   |program's default look?

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

[ark] [Bug 335716] Incorrect displaying file names in .zip cp2151

[Alexander Potashev via KDE Bugzilla]

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

--- Comment #16 from Alexander Potashev  ---
I have zip-3.0 and unzip-6.0 from http://www.info-zip.org/

> ZipInfo 3.00 of 20 April 2009, by Greg Roelofs and the Info-ZIP group.

And it works correctly:

aspotashev@cell ~ $ zipinfo -l -T -z Downloads/cyrilic_bug.zip 
Archive:  Downloads/cyrilic_bug.zip
Zip file size: 390 bytes, number of entries: 2
drwx--- 3.1 fat0 bx0 stor 20140818.145236 папка/
-rw-a-- 3.1 fat0 bx0 stor 20140818.145234 папка/файл.txt
2 files, 0 bytes uncompressed, 0 bytes compressed:  0.0%


May be it depends on the locale. I have ru_RU.UTF-8.

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

[konsole] [Bug 360267] New: Konsole Crash

[James Haydon via KDE Bugzilla]

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

Bug ID: 360267
   Summary: Konsole Crash
   Product: konsole
   Version: 15.12.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: haydon.ja...@gmail.com

Application: konsole (15.12.2)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-pv x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I was using Heimdall to
attempt to get a print of the pit file off my phone

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

Thread 2 (Thread 0x7efcd2abf700 (LWP 2634)):
#0  0x7efce061879c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7efce0614489 in _L_lock_918 () at /lib64/libpthread.so.0
#2  0x7efce06142b0 in pthread_mutex_lock () at /lib64/libpthread.so.0
#3  0x7efce0a35644 in  () at /usr/lib64/libxcb.so.1
#4  0x7efce0a3700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#5  0x7efcd4e1c3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#6  0x7efce56a232f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7efce06120a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7efce92d5fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7efce9992840 (LWP 2630)):
[KCrash Handler]
#6  0x7efce0a36460 in  () at /usr/lib64/libxcb.so.1
#7  0x7efce0a36d74 in  () at /usr/lib64/libxcb.so.1
#8  0x7efce0a36ed2 in xcb_wait_for_reply64 () at /usr/lib64/libxcb.so.1
#9  0x7efce24121f0 in _XReply () at /usr/lib64/libX11.so.6
#10 0x7efcd49d40e2 in XIQueryDevice () at /usr/lib64/libXi.so.6
#11 0x7efcd4e3c0c3 in QXcbConnection::xi2SetMouseGrabEnabled(unsigned int,
bool) () at /usr/lib64/libQt5XcbQpa.so.5
#12 0x7efce6564fc2 in QApplicationPrivate::closePopup(QWidget*) () at
/usr/lib64/libQt5Widgets.so.5
#13 0x7efce659d5be in QWidgetPrivate::hide_helper() () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7efce65a19e8 in QWidget::setVisible(bool) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7efce659d66b in
QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7efce66d7dee in  () at /usr/lib64/libQt5Widgets.so.5
#17 0x7efce66d88c9 in  () at /usr/lib64/libQt5Widgets.so.5
#18 0x7efce66dc5c8 in QMenu::mousePressEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#19 0x7efce65a23ba in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7efce66dd3db in QMenu::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#21 0x7efce6561e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#22 0x7efce65672cb in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7efce587de95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#24 0x7efce6566191 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQt5Widgets.so.5
#25 0x7efce65bae76 in  () at /usr/lib64/libQt5Widgets.so.5
#26 0x7efce65bd353 in  () at /usr/lib64/libQt5Widgets.so.5
#27 0x7efce6561e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#28 0x7efce6566cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#29 0x7efce587de95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#30 0x7efce5dcf964 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib64/libQt5Gui.so.5
#31 0x7efce5dd1175 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /usr/lib64/libQt5Gui.so.5
#32 0x7efce5db6268 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib64/libQt5Gui.so.5
#33 0x7efcd4e47200 in  () at /usr/lib64/libQt5XcbQpa.so.5
#34 0x7efcdfedec84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#35 0x7efcdfedeed8 in  () at /usr/lib64/libglib-2.0.so.0
#36 0x7efcdfedef7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#37 0x7efce58d4d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#38 0x7efce587bd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#39 0x7efce66d7a20 in QMenu::exec(QPoint const&, QAction*) () at
/usr/lib64/libQt5Widgets.so.5
#40 0x7efce8f6e1d2 in
Konsole::SessionController::showDisplayContextMenu(QPoint const&) () at
/usr/lib64/libkonsoleprivate.so.15
#41 0x7efce58ad73f in 

[kdenlive] [Bug 356492] When widgets are popped out, suggest that they don't affect the rest of program layout. (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 358599] 15.13.0 git master - adding title clip to timeline above clip causes flicking issue during playback. (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #3 from Jesse  ---
This issue doesn't seem to be present anymore in latest builds.

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

[kdenlive] [Bug 351723] 15.13.0 git master - Layout (widget size & position) doesn't load at program start-up when program window is maximized

[Jesse via KDE Bugzilla]

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

--- Comment #12 from Jesse  ---
I can confirm this issue is still present in Kdenlive 15.13.0 git master
development branch, Kubuntu 15.10 x64 w/ KDE Plasma 5.5.4 & KDE Frameworks
5.18.0.

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

[kdenlive] [Bug 351723] 15.13.0 git master - Layout (widget size & position) doesn't load at program start-up when program window is maximized

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|Doesn't load layout (widget |15.13.0 git master - Layout
   |size & position) at program |(widget size & position)
   |start-up when window is |doesn't load at program
   |maximized   |start-up when program
   ||window is maximized

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

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

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 358172] Kdenlive-git - Importing clip causes clip monitor to play previous clip highlighted without prompting (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #3 from Jesse  ---
After switching back to Kubuntu, this issue naturally resolved itself. While I
think it would be helpful to look into it later, for now, it works for me.

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

[kdenlive] [Bug 358175] Implement feature in Title Editor widget to adjust letter spacing (kerning) between letters in title text

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|Kdenlive-git - Title|Implement feature in Title
   |editor, implement feature   |Editor widget to adjust
   |to adjust letter spacing|letter spacing (kerning)
   |between letters in titles   |between letters in title
   ||text
   Platform|Archlinux Packages  |Kubuntu Packages

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

[kdenlive] [Bug 358173] 15.13.0 git master - Folder icons in Project Bin are not the same size as Clips. Doesn't look uniform.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|Kdenlive-git - Folder icons |15.13.0 git master - Folder
   |in Project Bin are not the  |icons in Project Bin are
   |same size as Clips. Doesn't |not the same size as Clips.
   |look uniform.   |Doesn't look uniform.
   Platform|Archlinux Packages  |Kubuntu Packages

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

[kdenlive] [Bug 357758] 15.13.0 git master - New render widget: double-clicking profile headers both opens save profile window and THEN expands category list -- should do either or.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|kdenlive-git - New render   |15.13.0 git master - New
   |widget: double-clicking |render widget:
   |profile header both opens   |double-clicking profile
   |save profile window and |headers both opens save
   |then expands list -- should |profile window and THEN
   |do either or.   |expands category list --
   ||should do either or.

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

[kdenlive] [Bug 357758] kdenlive-git - New render widget: double-clicking profile header both opens save profile window and then expands list -- should do either or.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

   Platform|Archlinux Packages  |Kubuntu Packages
 CC||j...@kdenlive.org,
   ||jesse.dub...@gmail.com

--- Comment #1 from Jesse  ---
This issue is still present in the latest git master build.

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

[kdenlive] [Bug 357757] kdenlive-git - New render widget shows "Invalid Profile" when a header is selected... misleading.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #2 from Jesse  ---
This has been fixed in later versions of Kdenlive, specifically 15.13.0
development branch.

Thanks! Marking this bug as fixed.

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

[kdenlive] [Bug 346606] SUGGESTION: Consider somehow highlighting active section/module in use?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #2 from Jesse  ---
The more I look at it, and move my mouse over the current 15.13.0 git master
interface, it is rather self-revealing as to what function is being highlighted
or used. So I'm gonna mark this wishlist bug as invalid.

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

[kdenlive] [Bug 346607] Implement the ability to have multiple timeline edits/sequences in a single Kdenlive project

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com
Summary|SUGGESTION: Create the  |Implement the ability to
   |ability to have multiple|have multiple timeline
   |timeline edits/sequences in |edits/sequences in a single
   |a single project, perhaps   |Kdenlive project
   |placed or created in|
   |Project Bin widget  |

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

[kdenlive] [Bug 346607] Implement the ability to have multiple timeline edits/sequences in a single Kdenlive project

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

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

[kdenlive] [Bug 346607] Implement the ability to have multiple timeline edits/sequences in a single Kdenlive project

[Jesse via KDE Bugzilla]

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

--- Comment #4 from Jesse  ---
@JB, I think you said in another post that this is what the Library widget is
meant for?

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

[kdenlive] [Bug 353291] Have a color gradient option for title clips, not just one solid color only for text

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

Summary|FEATURE REQUEST - Add   |Have a color gradient
   |option for color gradient   |option for title clips, not
   |for title text, not just|just one solid color only
   |one solid color?|for text
 CC||jesse.dub...@gmail.com,
   ||vpi...@kde.org

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