[kdevelop] [Bug 363707] Assert when parsing project

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/b4263571146bab54459dd0
   ||aa122fc5dc604705d5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/bef8072e620ecaac9cdaf2
   ||7c1996167caa7f75b5
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr  ---
Git commit b4263571146bab54459dd0aa122fc5dc604705d5 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 05:13.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Summary:
Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

Reviewers: apol, #kdevelop

Reviewed By: apol, #kdevelop

Subscribers: kdevelop-devel

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


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

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit bef8072e620ecaac9cdaf27c1996167caa7f75b5 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:54.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

M  +6-0projectmanagers/cmake/duchain/declarationbuilder.cpp

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

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

[kdevelop] [Bug 363707] Assert when parsing project

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/b4263571146bab54459dd0
   ||aa122fc5dc604705d5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/bef8072e620ecaac9cdaf2
   ||7c1996167caa7f75b5
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr  ---
Git commit b4263571146bab54459dd0aa122fc5dc604705d5 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 05:13.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Summary:
Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

Reviewers: apol, #kdevelop

Reviewed By: apol, #kdevelop

Subscribers: kdevelop-devel

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


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

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit bef8072e620ecaac9cdaf27c1996167caa7f75b5 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:54.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

M  +6-0projectmanagers/cmake/duchain/declarationbuilder.cpp

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

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

[digikam] [Bug 363510] Wrong filename shown in album view

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #17 from caulier.gil...@gmail.com ---
Torsten,

Thanks for your investigations.

The code in unchanged in this function with 5.0.0. The main difference is to
use Qt5 instead Qt4 to play with QHash  API to cache strings of squeezed
filename.

I close this file as resolved with 5.0.0. Don't hesitate to re-ope if
necessary.

Gilles Caulier

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

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #3 from caulier.gil...@gmail.com ---
Give me the full backtrace of configuration stage

Gilles Caulier

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

[kpat] [Bug 363826] New: Crash in KSharedDataCache in KPat

[Matthew Dawson via KDE Bugzilla]

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

Bug ID: 363826
   Summary: Crash in KSharedDataCache in KPat
   Product: kpat
   Version: 3.6
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: matt...@mjdsystems.ca
CC: kde-games-b...@kde.org

Application: kpat (3.6)
 (Compiled from sources)
Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.6.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

I was loading a game of patience, when KPat randomly crashed.  Every so often
it will do this when loading a game (the type of game doesn't seem to matter).

I looked at the result of the comparision in gdb and the memory appared to be
present and I could read the data, so I don't know why it crashed.  It did
crash reading from a register, but I don't know how to recover the value in gdb
after KCrash's signal handler has run.  Any hints regarding that would be
appreciated to help track it down.

May be related to bug #361426, which also crashed around where I did, except it
actually tried locking the lock.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
18562:movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f2609331880 (LWP 28538))]

Thread 6 (Thread 0x7f25f2df0700 (LWP 28543)):
#0  0x7f260534342d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f25fdd4ebba in poll (__timeout=-1, __nfds=1, __fds=0x7f25f2defbf0)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x24da680, cond=cond@entry=0x24da6c0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/usr/src/debug/x11-libs/libxcb-1.11.1/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7f25fdd51091 in xcb_wait_for_event (c=0x24da680) at
/usr/src/debug/x11-libs/libxcb-1.11.1/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f25f451c289 in QXcbEventReader::run (this=0x24da080) at
qxcbconnection.cpp:1313
#5  0x7f2605daca4d in QThreadPrivate::start (arg=0x24da080) at
thread/qthread_unix.cpp:340
#6  0x7f2600b51652 in start_thread (arg=0x7f25f2df0700) at
pthread_create.c:334
#7  0x7f260534cc8d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f25f1672700 (LWP 28545)):
#0  0x7f260534342d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f26003d62fd in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f25e4003020, timeout=, context=0x7f25e4000990) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f25e4000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3835
#3  0x7f26003d6433 in g_main_context_iteration (context=0x7f25e4000990,
may_block=may_block@entry=1) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3901
#4  0x7f2605ff1dab in QEventDispatcherGlib::processEvents
(this=0x7f25e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f2605f9631b in QEventLoop::exec (this=this@entry=0x7f25f1671cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f2605da7885 in QThread::exec (this=this@entry=0x7f2602712e40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:503
#7  0x7f2602692bf6 in QDBusConnectionManager::run (this=0x7f2602712e40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7f2605daca4d in QThreadPrivate::start (arg=0x7f2602712e40 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#9  0x7f2600b51652 in start_thread (arg=0x7f25f1672700) at
pthread_create.c:334
#10 0x7f260534cc8d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f25d6e1a700 (LWP 28562)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f25eb99546b in cnd_wait (mtx=0x27627b0, cond=0x27627d8) at
/usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x27627b0) at
/usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0x2762380) at
/usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:688
#4  0x7f25eb995018 in impl_thrd_routine (p=) at
/usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/include/c11/threads_posix.h:87
#5  

[konsole] [Bug 363821] Cursor position two characters to the right of where it should be as root.

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org

--- Comment #1 from Eike Hein  ---
Most likely a font issue. Try a different font.

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

[konsole] [Bug 363821] Cursor position two characters to the right of where it should be as root.

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Component|general |kpart
Product|yakuake |konsole
   Assignee|h...@kde.org|konsole-de...@kde.org

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

[Breeze] [Bug 349411] Horizontal and vertical task buttons should have consistent margin sizes

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
 CC||h...@kde.org

--- Comment #9 from Eike Hein  ---
There are no changes planned to this at this time - that's just a theme that
needs fixing.

The Breeze theme bugs mentioned in comment #7 got fixed since, I forgot to
update the bug.

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

[kde] [Bug 363825] New: kdeconnect crashed after clearing (clicked the X) a notification.

[PLX via KDE Bugzilla]

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

Bug ID: 363825
   Summary: kdeconnect crashed after clearing (clicked the X) a
notification.
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: k...@pmc.com.pt

Application: kdeconnectd (0.1)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.4.11-desktop-1.mga5 x86_64
Distribution: "Mageia 5"

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

I clicked a notification's X to remove/clear the notification. I've done this
action many times before without crashing.
The only difference this time I can see is that the phone was turned off but
was still showing in kdeconnect.

- Unusual behavior I noticed:

kdeconnect crashed.

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

Thread 3 (Thread 0x7f41fa08f700 (LWP 2436)):
#0  0x7f420ef51d6d in poll () at /lib64/libc.so.6
#1  0x7f420c18ceb4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f420c18cfbc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f420f6cee3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f420f6a0931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f420f6a0c45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f420f59e899 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f420f5a0fff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#8  0x7f420fa105bd in start_thread () at /lib64/libpthread.so.0
#9  0x7f420ef5d62d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f41f3df2700 (LWP 3172)):
#0  0x7f420ef51d6d in poll () at /lib64/libc.so.6
#1  0x7f420c18ceb4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f420c18cfbc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f420f6cee3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f420f6a0931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f420f6a0c45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f420f59e899 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f420f6823d3 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#8  0x7f420f5a0fff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7f420fa105bd in start_thread () at /lib64/libpthread.so.0
#10 0x7f420ef5d62d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4211834780 (LWP 2435)):
[KCrash Handler]
#5  0x7f4211447ab1 in QHash::findNode(QString
const&, unsigned int*) const () at /lib64/libkdeconnectcore.so.1
#6  0x7f421144713a in KdeConnectPlugin::sendPackage(NetworkPackage&) const
() at /lib64/libkdeconnectcore.so.1
#7  0x7f41f89245e5 in
NotificationsDbusInterface::dismissRequested(Notification*) () at
/usr/lib64/kde4/kdeconnect_notifications.so
#8  0x7f41f8920e6d in
NotificationsDbusInterface::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) [clone .part.7] () at /usr/lib64/kde4/kdeconnect_notifications.so
#9  0x7f420f6b588a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#10 0x7f41f892109f in Notification::dismissRequested(Notification*) () at
/usr/lib64/kde4/kdeconnect_notifications.so
#11 0x7f41f8920da6 in Notification::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at
/usr/lib64/kde4/kdeconnect_notifications.so
#12 0x7f41f892128f in Notification::qt_metacall(QMetaObject::Call, int,
void**) () at /usr/lib64/kde4/kdeconnect_notifications.so
#13 0x7f420dec0b06 in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QList const&, int) () at /lib64/libQtDBus.so.4
#14 0x7f420dec1c49 in QDBusConnectionPrivate::activateCall(QObject*, int,
QDBusMessage const&) () at /lib64/libQtDBus.so.4
#15 0x7f420dec23ed in
QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&,
QDBusMessage const&, int) () at /lib64/libQtDBus.so.4
#16 0x7f420dec281b in QDBusActivateObjectEvent::placeMetaCall(QObject*) ()
at /lib64/libQtDBus.so.4
#17 0x7f420f6b9d61 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#18 0x7f42102c879c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#19 0x7f42102cee40 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#20 0x7f4210ffb25a in KApplication::notify(QObject*, QEvent*) () at

[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert on startup

[via KDE Bugzilla]

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

--- Comment #17 from guruguru...@outlook.jp ---
Created attachment 99321
  --> https://bugs.kde.org/attachment.cgi?id=99321=edit
log file

Tested the build - Krita does seem to find Japanese locale resource, but it
still quits saying "It can't find any presets"
I attach the console log - I still think this line is looking
incorrect(incorrect XDG_DATA_DIRS setting causing preset load fail?):
Setting XDG_DATA_DIRS "/../../share"

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

[kmymoney4] [Bug 363824] New: Crash when i save a new budget report

[Fernando via KDE Bugzilla]

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

Bug ID: 363824
   Summary: Crash when i save a new budget report
   Product: kmymoney4
   Version: 4.7.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: file
  Assignee: kmymoney-de...@kde.org
  Reporter: ferna...@tele1.com.br

Crash when i save a new budget report with more than one month column

Reproducible: Always

Steps to Reproduce:
1.open a budget report in my favorite reports session
2.configure a new report based on than with more than one month, especificaly
30 past + 60 next days
3. save the report.

Actual Results:  
Crash and lost all data.

Expected Results:  
save

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

[krita] [Bug 363823] New: Error message for ambiguous key shortcuts talks about no longer existing menu entry

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Bug ID: 363823
   Summary: Error message for ambiguous key shortcuts talks about
no longer existing menu entry
   Product: krita
   Version: 3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: shortcuts
  Assignee: krita-bugs-n...@kde.org
  Reporter: kosse...@kde.org

The message is still e.g. "The key sequence 'Ctrl+Shift+N' is ambiguous. Use
'Configure Shortcuts'
 from the 'Settings' menu to solve the ambiguity." while the shortcut config is
now in the "Configure Krita" dialog in the "Keyboard Shortcuts" section.

libs/widgetutils/xmlgui/kactionconflictdetector.cpp:49 for the old string. No
time to make up a new string, so at least filing the bug which confuses users.

Reproducible: Always

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

[krita] [Bug 363822] New: krita doesn't display anything on the canvas until a few seconds after but the layer preview does.

[via KDE Bugzilla]

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

Bug ID: 363822
   Summary: krita doesn't display anything on the canvas until a
few seconds after but the layer preview does.
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: CPU Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: pottsba...@gmail.com

I have just installed Krita 3.0. When I tested it by making a few strokes, the
strokes I made did not appear on the canvas. However, the layer preview shows
it just fine. The brushes also lags a lot.

Reproducible: Always

Steps to Reproduce:
1.Open Krita.
2.Start a new project.
3.Make brush strokes.

Actual Results:  
Brush doesn't move at once, not even at all. Nothing shows on the canvas but
the layer preview shows the strokes you make.

Expected Results:  
The brush should move as you make strokes with your pen, the canvas should show
those strokes.

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

[kwin] [Bug 363804] Struts are broken with multiple screens

[Aleix Pol via KDE Bugzilla]

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

--- Comment #4 from Aleix Pol  ---
That does fix the problem.
Note that this used to work up until few weeks ago...

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

[okteta] [Bug 344322] Okteta frozen for a long time at startup

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Friedrich W. H. Kossebau  ---
Closing now, as luckily noone seems to be able to reproduce this problem
anymore with recent KF5 (and Okteta) versions.

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

[kdeplasma-addons] [Bug 361060] Configuration dialog section name "General" is not translatable

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

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

--- Comment #1 from Friedrich W. H. Kossebau  ---
Thanks for the report. The "General" entry was renamed and made translatable
before the release in Plasma 5.6, so has been fixed already.

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

[yakuake] [Bug 363821] New: Cursor position two characters to the right of where it should be as root.

[Rick Stanley via KDE Bugzilla]

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

Bug ID: 363821
   Summary: Cursor position two characters to the right of where
it should be as root.
   Product: yakuake
   Version: 3.0.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: rstan...@rsiny.com

After the latest update the cursor appears to have two spaces before the
visible cursor, only after su to root.  This does not occur as regular user, in
the [Ctrl]-[Alt]-[F1] console as root, or the XTerm terminal, as root.

Reproducible: Always

Steps to Reproduce:
1. Press [F12] to invoke Yakuake
2. su to login as root
3.

Actual Results:  
Visible Block cursor two characters to the right of where it should be.

Expected Results:  
Cursor appears as it should be immediately after the last character entered.

It becomes VERY annoying when you attempt to edit the command line.  I "Purged"
Yakuake using aptitude, then reinstalled, without success.  I have not altered
the default prompt for root or regular user.  I can provide images if that
would help.

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

[kwin] [Bug 363804] Struts are broken with multiple screens

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #3 from Thomas Lübking  ---
Wild guess, what if you left-align the lower screen?

   xrandr --output LVDS1 --pos 0x1080

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

[Breeze] [Bug 363790] slider dialog is unusable with breeze theme

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #2 from Hugo Pereira Da Costa  ---
Cannot reproduce. Neither with breeze (@kde4), nor oxygen. Christoph, can you ? 
(and they share the same code with respect to window dragging, so that I would
be surprise that the behave differently)
Otherwise, a complete test case would help

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

[kwin] [Bug 363804] Struts are broken with multiple screens

[Aleix Pol via KDE Bugzilla]

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

--- Comment #2 from Aleix Pol  ---
Sure! :)

That's xprop: https://paste.kde.org/pk9kiemwu

$ xrandr -q 
Screen 0: minimum 8 x 8, current 1920 x 1848, maximum 32767 x 32767 
LVDS1 connected primary 1366x768+554+1080 (normal left inverted right x axis y
axis) 277mm x 156mm 
   1366x768  60.02*+
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25 
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   680x384   60.00  
   640x360   60.00  
DP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x
287mm   
   1920x1080 60.00*+
   1680x1050 59.95  
   1680x945  60.02  
   1400x1050 74.8759.98 
   1600x900  60.00  
   1280x1024 75.0260.02  
   1440x900  74.9859.89  
   1280x960  60.00  
   1366x768  59.79  
   1360x768  60.02  
   1280x800  74.9359.81  
   1152x864  75.00  
   1280x768  74.8959.87  
   1280x720  60.00  
   1024x768  75.0870.0760.00  
   1024x576  59.97  
   800x600   72.1975.0060.3256.25  
   848x480   60.00  
   640x480   75.0072.8160.00  
   720x400   70.08  
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

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

[krita] [Bug 361515] [UGEE] Brush Cursor Doesn't Follow Ugee Tablet Pen on Hover

[james via KDE Bugzilla]

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

james  changed:

   What|Removed |Added

 CC||jamesonr...@gmail.com

--- Comment #5 from james  ---
I am having the same issues with my artist 22hd XP-pen tablet, including
Dmitry's issue of seeing connecting lines between strokes in Krita 3.0.

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

[dolphin] [Bug 156759] Freeze in KLockFile when trying to lock a file on mounted smbfs / cifs directory

[Ivo Steinmann via KDE Bugzilla]

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

Ivo Steinmann  changed:

   What|Removed |Added

 CC||iv...@jaison.ch

--- Comment #38 from Ivo Steinmann  ---
I even have this problem with Dolphin 16.04.1

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

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

[Lisa Miller via KDE Bugzilla]

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

Lisa Miller  changed:

   What|Removed |Added

 CC||lizajane...@gmail.com

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

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

[Simon via KDE Bugzilla]

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

Simon  changed:

   What|Removed |Added

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

--- Comment #2 from Simon  ---
With commit f1f247f1cc71e948c377ec7d1daa1389728fe88c I still get the following
output:

--  libgphoto2 found. NO  (optional)
--  digiKam will be compiled without GPhoto2 camera drivers support.
--  Please install the libgphoto2 (version >= 2.4.0) development package.
-- 

I do and did have libusb 1.0.20 and libgphoto 2.5.10 both with -dev packages
installed.

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

[krita] [Bug 363756] Empty "Tool options" docker after upgrade

[Smomu via KDE Bugzilla]

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

Smomu  changed:

   What|Removed |Added

  Attachment #99319|Empty "Tool Options" docker |Empty "Tool Options" docker
description|(Windows 10)|(Krita 3.0 / Windows 10)

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

[kmail2] [Bug 363531] TLS negotiation was unsuccessful

[Gerry Gavigan via KDE Bugzilla]

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

Gerry Gavigan  changed:

   What|Removed |Added

 CC||gerrys...@gmail.com

--- Comment #1 from Gerry Gavigan  ---
I've just suffered a similar problem - offered in case it helps 

configure kmail -> sending account ->, modify -> advanced tab, and you might
find the TLS box checked,

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

[krita] [Bug 363756] Empty "Tool options" docker after upgrade

[Smomu via KDE Bugzilla]

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

Smomu  changed:

   What|Removed |Added

  Attachment #99319|Empty tool options (Windows |Empty "Tool Options" docker
description|10) |(Windows 10)

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

[krita] [Bug 363756] Empty "Tool options" docker after upgrade

[Smomu via KDE Bugzilla]

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

--- Comment #3 from Smomu  ---
Created attachment 99319
  --> https://bugs.kde.org/attachment.cgi?id=99319=edit
Empty tool options (Windows 10)

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

[krita] [Bug 363756] Empty "Tool options" docker after upgrade

[Smomu via KDE Bugzilla]

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

Smomu  changed:

   What|Removed |Added

 CC||smo...@gmail.com

--- Comment #2 from Smomu  ---
Same bug here on Windows 10 64-bit.

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

[katomic] [Bug 363818] New: the level 28 of katomic is impossible

[via KDE Bugzilla]

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

Bug ID: 363818
   Summary: the level 28 of katomic is impossible
   Product: katomic
   Version: unspecified
  Platform: Mint (Ubuntu based)
   URL: http://www.hostingpics.net/viewer.php?id=585465Capture
du20160601231143.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dim...@gmail.com
  Reporter: vincentfali...@laposte.net
CC: kde-games-b...@kde.org

The level 28 of KAtomic is impossible.
Impossible go to next level.
Picture of the error.
http://www.hostingpics.net/viewer.php?id=585465Capturedu20160601231143.png

Reproducible: Always

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

[plasmashell] [Bug 363817] Memory status widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99318
  --> https://bugs.kde.org/attachment.cgi?id=99318=edit
Memory status widget on a panel

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

[plasmashell] [Bug 363817] New: Memory status widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

Bug ID: 363817
   Summary: Memory status widget unreadable when placed on panel
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: andy...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

Memory status widget becomes unreadable is placed on a horizontal panel because
the memory type overlaps with the consumption readings. The widget has no
settings, so there is no way to remove the memory type or adjust font settings
or anything.

Reproducible: Always

Steps to Reproduce:
1. Add a memory status widget to a horizontal panel.

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

[plasmashell] [Bug 363816] Network monitor widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99317
  --> https://bugs.kde.org/attachment.cgi?id=99317=edit
Network monitor on a panel

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

[plasmashell] [Bug 363816] New: Network monitor widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

Bug ID: 363816
   Summary: Network monitor widget unreadable when placed on panel
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: andy...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

Network monitor widget becomes unreadable is placed on a horizontal panel
because the network interface name overlaps with the bandwidth readings. The
widget has no settings, so there is no way to remove the interface name or
adjust font settings or anything.


Reproducible: Always

Steps to Reproduce:
1. Add a network monitor widget to a horizontal panel.

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

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

[via KDE Bugzilla]

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

mtihlenfi...@gmail.com changed:

   What|Removed |Added

 CC||mtihlenfi...@gmail.com

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

  Attachment #99313|0   |1
is obsolete||

--- Comment #22 from Lastique  ---
Created attachment 99316
  --> https://bugs.kde.org/attachment.cgi?id=99316=edit
Screencast showing opacity changes when opening windows

Sorry, I mixed up two of by bugs.

Here's a screencast of opacity changes when blur is enabled. Pay attention to
the panels.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

  Attachment #99314|0   |1
is obsolete||

--- Comment #13 from Lastique  ---
Created attachment 99315
  --> https://bugs.kde.org/attachment.cgi?id=99315=edit
Screencast showing undrawn decorations

Sorry, I mixed up two of by bugs.

(In reply to Lastique from comment #11)
> I put KWIN_USE_BUFFER_AGE=0 to /etc/environment a few days ago and so far I
> haven't seen any flickering textures. I can't be 100% sure this fixes the
> problem but it does make things better.
> 
> Note: My vsync mode is "Automatic".

And there you go. A few minutes later after I wrote the message I re-enabled
the Blur effect and got un-drawn window decorations. No flickering though. Also
I noticed that the decorations are affected by the nearby windows. See the
attached screencast.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #12 from Lastique  ---
Created attachment 99314
  --> https://bugs.kde.org/attachment.cgi?id=99314=edit
Screencast showing opacity changes when opening windows

Here's a screencast of opacity changes when blur is enabled. Pay attention to
the panels.

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

[Breeze] [Bug 362884] Illegible icons in Plasma taskbar / add oxygen icons to air plasma theme

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

Summary|Illegible icons in Plasma   |Illegible icons in Plasma
   |taskbar |taskbar / add oxygen icons
   ||to air plasma theme

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

[Breeze] [Bug 362884] Illegible icons in Plasma taskbar

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #21 from Lastique  ---
Created attachment 99313
  --> https://bugs.kde.org/attachment.cgi?id=99313=edit
Screencast showing undrawn decorations

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

[konqueror] [Bug 363815] New: Doesn't show play controls for HTML5

[Mikhail Rokhin via KDE Bugzilla]

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

Bug ID: 363815
   Summary: Doesn't show play controls for HTML5
   Product: konqueror
   Version: 4.14.3
  Platform: FreeBSD Ports
   URL: https://www.youtube.com/watch?v=ZIt738-eXU4
OS: FreeBSD
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: khtml
  Assignee: konq-b...@kde.org
  Reporter: mikhail.rok...@gmail.com

Doesn't show play controls for HTML5

Reproducible: Always

Steps to Reproduce:
1. Open any youtube video when on youtube html5 is enabled
2.
3.

Actual Results:  
no play controls

Expected Results:  
default html5 play controls

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #20 from Lastique  ---
(In reply to Lastique from comment #19)
> 
> I tried disabling blur and indeed opacity changes have disappeared.

And there you go. A few minutes later after I wrote the message I re-enabled
the Blur effect and got un-drawn window decorations. No flickering though. Also
I noticed that the decorations are affected by the nearby windows. See the
screencast.

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

[kaffeine] [Bug 334197] Dvb-t HD channels corrupt audio, slow video, but records fine.

[Hadrien via KDE Bugzilla]

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

--- Comment #18 from Hadrien  ---
(In reply to Hadrien from comment #17)
> The TV does not work at all, I've got this error (in a terminal) when I
> start the program:
> core libvlc error: No plugins found! Check your VLC installation.
> 01-06-16 22:45:48.202 [System  ] VlcMediaWidget::init: cannot create vlc
> instance ""

I tried to reinstall vlc and it fixed the problem:
sudo apt install vlc

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

[frameworks-kconfig] [Bug 363814] New: typedef conflict between kglobal.h and ksharedconfig.h

[Spencer Brown via KDE Bugzilla]

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

Bug ID: 363814
   Summary: typedef conflict between kglobal.h and ksharedconfig.h
   Product: frameworks-kconfig
   Version: 5.22.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: matt...@mjdsystems.ca
  Reporter: spencerbrown...@gmail.com
CC: kdelibs-b...@kde.org

WIth both kglobal.h and ksharedconfig.h included in a file, the build process
fails, complaining of a typedef conflict between 
typedef KSharedConfig::Ptr KSharedConfigPtr; (in ksharedconfig.h)
and
typedef KSharedPtr KSharedConfigPtr; (in kglobal.h)

Reproducible: Always

Steps to Reproduce:
1. #include  and  in project
2. build (cmake)

Actual Results:  
Build fails

Expected Results:  
Project should have been built sucessfully

I'm using KDevelop 4.90.92 and CMake, working on the KJots project.
Build error thrown is below.

In file included from /usr/include/kcomponentdata.h:23:0,
 from /home/spencer/projects/kjots.git/src/kjotsedit.cpp:32:
/usr/include/KF5/KConfigCore/ksharedconfig.h:90:28: error: conflicting
declaration ‘typedef KSharedConfig::Ptr KSharedConfigPtr’
 typedef KSharedConfig::Ptr KSharedConfigPtr;
^~~~
In file included from /usr/include/kstandarddirs.h:27:0,
 from /home/spencer/projects/kjots.git/src/kjotsedit.cpp:31:
/usr/include/kglobal.h:42:35: note: previous declaration as ‘typedef class
KSharedPtr KSharedConfigPtr’
 typedef KSharedPtr KSharedConfigPtr;
   ^~~~
src/CMakeFiles/kjots_common.dir/build.make:122: recipe for target
'src/CMakeFiles/kjots_common.dir/kjotsedit.cpp.o' failed
make[2]: *** [src/CMakeFiles/kjots_common.dir/kjotsedit.cpp.o] Error 1
CMakeFiles/Makefile2:214: recipe for target
'src/CMakeFiles/kjots_common.dir/all' failed
make[1]: *** [src/CMakeFiles/kjots_common.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
*** Failure: Exit code 2 ***

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

[kaffeine] [Bug 334197] Dvb-t HD channels corrupt audio, slow video, but records fine.

[Hadrien via KDE Bugzilla]

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

--- Comment #17 from Hadrien  ---
It's nice to see that the project is living.

So I tried the latest git code (commit
199edfa1c3bbcf20ce4b321e6f7dcfe288982303). Here are my remarks:
I'm on Ubuntu 16.04 so I looked in the README in the section about Debian.
Those packages were not found with apt: libqt5-sql-sqlite
libkf5kdbusaddons-dev, but I've been able to build the source anyway.

The program starts without problem but all my settings (including channels)
were lost.

The TV does not work at all, I've got this error (in a terminal) when I start
the program:
core libvlc error: No plugins found! Check your VLC installation.
01-06-16 22:45:48.202 [System  ] VlcMediaWidget::init: cannot create vlc
instance ""

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

[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments

[Gregor Mi via KDE Bugzilla]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #11 from Lastique  ---
I put KWIN_USE_BUFFER_AGE=0 to /etc/environment a few days ago and so far I
haven't seen any flickering textures. I can't be 100% sure this fixes the
problem but it does make things better.

Note: My vsync mode is "Automatic".

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #19 from Lastique  ---
(In reply to Thomas Lübking from comment #18)
> Meh - blur (next to contrast) is by it's nature still a major contender to
> be the culprit.
> => If you can reproduce it with disabled blur, it might be helpful to see a
> video of what's actually going one.

I tried disabling blur and indeed opacity changes have disappeared.

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

[gcompris] [Bug 363158] Count the items (enumerate) activity - No Virtual Keyboard

[Jazeix Johnny via KDE Bugzilla]

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

Jazeix Johnny  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/gcom |http://commits.kde.org/gcom
   |pris/8b8d86313f591bcd7f8b3d |pris/4d26c711d1bde1abc71780
   |20ea53def6b630a58e  |c7d21c33666a2ec70f

--- Comment #2 from Jazeix Johnny  ---
Git commit 4d26c711d1bde1abc71780c7d21c33666a2ec70f by Johnny Jazeix.
Committed on 01/06/2016 at 20:24.
Pushed by jjazeix into branch 'KDE/0.60'.

M  +5-2src/activities/enumerate/Enumerate.qml

http://commits.kde.org/gcompris/4d26c711d1bde1abc71780c7d21c33666a2ec70f

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

[kdenlive] [Bug 363813] New: Problems with buttons on Ubuntu 16.04

[Robert Orzanna via KDE Bugzilla]

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

Bug ID: 363813
   Summary: Problems with buttons on Ubuntu 16.04
   Product: kdenlive
   Version: 16.04.0
  Platform: Ubuntu Packages
   URL: http://i.imgur.com/RoJ1bJ1.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: orsch...@gmail.com

Dear all, 

As shown in the below screenshot, some of the buttons such as `Play` are
improperly shown on Ubuntu 16.04:

http://i.imgur.com/RoJ1bJ1.png

I installed the version 16.04.0 from the ppa:kdenlive/kdenlive-testing.

Can anyone confirm this problem?

Thankfully,

~Robert

Reproducible: Always

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

[digikam] [Bug 363412] Tree structure is not getting read

[Frank Hommes via KDE Bugzilla]

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

--- Comment #8 from Frank Hommes  ---
Ok, so the problem is that the XMP-Keywords which contains the trees have not
been saved somehow?

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

[valgrind] [Bug 362329] Valgrind does not support the IBM POWER ISA 3.0 instructions, part 3

[Carl Love via KDE Bugzilla]

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

Carl Love  changed:

   What|Removed |Added

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

--- Comment #9 from Carl Love  ---
Updated patch committed.   

Vex commit 3220
Valgrind commit 15890

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

[digikam] [Bug 363412] Tree structure is not getting read

[Frank Hommes via KDE Bugzilla]

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

--- Comment #7 from Frank Hommes  ---
I only use digikam for tagging and Nikon Capture-D for developing the raws.

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

[kmail2] [Bug 338969] KMail2 sending fails w/o notice at more than 83 recipients

[Axel Braun via KDE Bugzilla]

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

--- Comment #4 from Axel Braun  ---
By the way, I cross-checked with a different mailer - it is not an issue of the
provider (blocking large number of recipients), it is really a KMail Problem...

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

[digikam] [Bug 363412] Tree structure is not getting read

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #6 from Maik Qualmann  ---
The last test image has no XMP tags. The keywords coming from
"Iptc.Application2.Keywords". Here we can actually have a point as separator. I
will look which applications uses points as separators. I would disable
"Iptc.Application2.Keywords" in the metadata settings and add new keywords to
the image.

Maik

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

[plasmashell] [Bug 363812] saved session broken: application unreachable

[arne anka via KDE Bugzilla]

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

--- Comment #1 from arne anka  ---
that's what i see when clicking the taskbar entry.
the issue persists even after reboot

QXcbConnection: XCB error: 8 (BadMatch), sequence: 52951, resource id:
50331653, major code: 42 (SetInputFocus), minor code: 0

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

[plasmashell] [Bug 363812] New: saved session broken: application unreachable

[arne anka via KDE Bugzilla]

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

Bug ID: 363812
   Summary: saved session broken: application unreachable
   Product: plasmashell
   Version: 5.6.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kde-b...@ginguppin.de
CC: bhus...@gmail.com, plasma-b...@kde.org

i have  a saved session, that starts konsole with several tabs.
aftrer today's update, the konsole appears in the task manager in panel, but is
unreachable:

- klicking the taskbar entry does nothing
- context menu of the taskbar entry -> maximize does nothing
- ALT+TAB and selecting the konsole in  does nothing

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

[Breeze] [Bug 363811] window titlebar too large

[arne anka via KDE Bugzilla]

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

--- Comment #1 from arne anka  ---
Created attachment 99312
  --> https://bugs.kde.org/attachment.cgi?id=99312=edit
screenshot illustration wasted space for huge titlebar

as you can see, both the close button and the icon are small -- there's no need
(let alone justification) for that waste of screen space

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

[Breeze] [Bug 363811] New: window titlebar too large

[arne anka via KDE Bugzilla]

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

Bug ID: 363811
   Summary: window titlebar too large
   Product: Breeze
   Version: 5.6.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: window decoration
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: kde-b...@ginguppin.de

starting with one of the latest updates, the title bar of windows is all of a
sudden at least one third higher than before.
although buttons, icon and title font all are small, there's  a huge empty
space around wich apparently cannot be removed by any configuration.

please, fix.

Reproducible: Always

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

[plasmashell] [Bug 363810] font size calculation broken

[arne anka via KDE Bugzilla]

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

--- Comment #1 from arne anka  ---
Created attachment 99310
  --> https://bugs.kde.org/attachment.cgi?id=99310=edit
original, previously working panel height with broken clock display

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

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||d...@ptmx.org

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

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

[digikam] [Bug 363510] Wrong filename shown in album view

[Torsten Crass via KDE Bugzilla]

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

--- Comment #16 from Torsten Crass  ---
OK,

I found out what's going on!

After installing tons of dependencies, I compiled and debugged the 
digikam 4.4.14 source (from 
http://download.kde.org/stable/digikam/digikam-4.14.0.tar.bz2) from 
within kdevelop. The problem resides in the function

QString DItemDelegate::squeezedTextCached(QPainter* const p, int width, 
const QString& text) const

at line 184 in .../core/libs/widgets/itemviewditemdelegate.cpp. It seems 
that my problematic filenames prove that unlikely events like cache 
collisions are prone to occur sooner or later, regardless how unlikely 
they may seem. (Think Fukushima... ;)

When commenting out lines 191-194, which return a cached version of the 
squeezed filename, if existant, the correct filename gets displayed in 
the album view, freshly generated by applying the squeezedText function 
to the filename.

I suppose very little can be done about this. On the other hand, if you 
digikam developer folks can't reproduce my problem in 5.0, something 
must have changed in the sourc, preventing that cache collision from 
happening any longer. So I guess I'll for now stick with my modified 
digikam version with the uncommented caching code and just wait for 5.0 
to eventually show up in Debian.

Anyway, thanks for your great work on this great application!

Cheers --

Torsten

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

[plasmashell] [Bug 363810] font size calculation broken

[arne anka via KDE Bugzilla]

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

--- Comment #2 from arne anka  ---
Created attachment 99311
  --> https://bugs.kde.org/attachment.cgi?id=99311=edit
panel height almost doubled only to fix broken clock display (just because one
is not allowed to decide the font size)

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

[kwin] [Bug 363809] occasionally, screen briefly freezes, followed by kwin 5.5.5 crashing

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
"kcmshell5 kwindedcoration", switch to breeze.

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

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

[plasmashell] [Bug 363810] New: font size calculation broken

[arne anka via KDE Bugzilla]

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

Bug ID: 363810
   Summary: font size calculation broken
   Product: plasmashell
   Version: 5.6.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: mklape...@kde.org
  Reporter: kde-b...@ginguppin.de
CC: plasma-b...@kde.org

after the latest update the size calculation is completely broken. whereas i
had the date _below_ the time before, i now have to almost double the height of
the panel to get the same layout again.

for incomprehensible reasons, clock insists on putting the date on the same
line (albeit sill in smaller font) insetad of doing the sensible thing, that is
using font sizes for time and date that allow two lines.

see attached screenshots. clock.png has the panel size that worked flwlessly
before. clock1.png has the panel size that again puts the date below the time.

the only _sensible_ thing is to get back the configurable font size instead of
the stupid automatic calculation -- this is especially stupid, since one cannot
even easily resize the panel, but has to do that clumsily with the mouse.

Reproducible: Always

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

[plasmashell] [Bug 363397] plasma crash after install nvidia proprietary driver

[Alan De Smet via KDE Bugzilla]

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

Alan De Smet  changed:

   What|Removed |Added

 CC||ch...@highprogrammer.com

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

[amarok] [Bug 363054] Building amarok-2.8.90 with GCC-6.1.0 fails with "error: 'Playlists::Playlist::ModelStack' has not been declared"

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/amar
   ||ok/9308403e1c8484052f277bf6
   ||de32ee07c93a4beb
 Resolution|--- |FIXED

--- Comment #9 from Rex Dieter  ---
Git commit 9308403e1c8484052f277bf6de32ee07c93a4beb by Rex Dieter.
Committed on 01/06/2016 at 18:58.
Pushed by rdieter into branch 'master'.

gcc6 buildfix

courtesy of opensuse, thx

M  +2-1src/core-impl/playlists/types/file/xspf/XSPFPlaylist.cpp

http://commits.kde.org/amarok/9308403e1c8484052f277bf6de32ee07c93a4beb

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

[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

[Onno Molenkamp via KDE Bugzilla]

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

Onno Molenkamp  changed:

   What|Removed |Added

 CC||o...@flox.org

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

[plasmashell] [Bug 357642] Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year

[Vadym Krevs via KDE Bugzilla]

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

--- Comment #8 from Vadym Krevs  ---
(In reply to Martin Klapetek from comment #6)
> > According to comment 1, this should have been fixed, but it is not. When 
> > can we expect this to land in any released version of Plasma?
> 
> As you can read in that very comment, it says Fixed in Plasma 5.7.
> 
> > You closed bug 363775 but please don't ignore remarks about ...
> 
> Couple things - multiple issues should always go into separate reports,
> there's no sensible way to handle them in a single report. That said, in 5.7
> holidays are marked, today is highlighted, ability to copy date and you can
> skip dates by month/year/decade. In other words, everything from your list.

Sorry, I missed the "fixed in plasma 5.7" part. Thank you.

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

[kwin] [Bug 363809] New: occasionally, screen briefly freezes, followed by kwin 5.5.5 crashing

[via KDE Bugzilla]

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

Bug ID: 363809
   Summary: occasionally, screen briefly freezes, followed by kwin
5.5.5 crashing
   Product: kwin
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: d...@ptmx.org

Application: kwin_x11 (5.5.5)

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

-- Information about the crash:
- Unusual behavior I noticed:

Sometimes I notice that the screen freezes for a brief moment (~500ms),
followed by a kwin crash. I noticed this on two machines with Kubuntu 16.04
installed, one with an nvidia card and the closed-source drive, another with an
intel graphics chipset (using the driver that was preconfigured by the Kubuntu
setup). I've also noticed that sometimes the glyphs on window titles appear
"smeared" and unrecognizable.  Backtrace also suggests a problem with the glyph
cache in Qt5.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9f5a046900 (LWP 1700))]

Thread 4 (Thread 0x7f9f3b345700 (LWP 1755)):
#0  0x7f9f59b3bd13 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9f5834010f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) (nfds=13, fdread=fdread@entry=0x7f9f2c000a78,
fdwrite=fdwrite@entry=0x7f9f2c000d08, fdexcept=fdexcept@entry=0x7f9f2c000f98,
orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75
#2  0x7f9f58341c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (timeout=0x0, exceptfds=0x7f9f2c000f98, writefds=0x7f9f2c000d08,
readfds=0x7f9f2c000a78, nfds=, this=0x7f9f2c0008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  0x7f9f58341c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7f9f2c0008e0, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196
#4  0x7f9f5834213e in
QEventDispatcherUNIX::processEvents(QFlags)
(this=0x7f9f2c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f9f582ebdea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f9f3b344ca0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f9f581088a4 in QThread::exec() (this=this@entry=0x1aba3f0) at
thread/qthread.cpp:503
#7  0x7f9f52c1e3c5 in QQmlThreadPrivate::run() (this=0x1aba3f0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f9f5810d84e in QThreadPrivate::start(void*) (arg=0x1aba3f0) at
thread/qthread_unix.cpp:331
#9  0x7f9f53ac16fa in start_thread (arg=0x7f9f3b345700) at
pthread_create.c:333
#10 0x7f9f59b45b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f9f33056700 (LWP 1780)):
#0  0x7f9f53ac73a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9f57295bd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f9f57295c19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f9f53ac16fa in start_thread (arg=0x7f9f33056700) at
pthread_create.c:333
#4  0x7f9f59b45b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f9ea5aeb700 (LWP 2113)):
#0  0x7f9f59b3bd13 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9f5834010f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) (nfds=26, fdread=fdread@entry=0x7f9ea00aeef8,
fdwrite=fdwrite@entry=0x7f9ea00af188, fdexcept=fdexcept@entry=0x7f9ea00af418,
orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75
#2  0x7f9f58341c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (timeout=0x0, exceptfds=0x7f9ea00af418, writefds=0x7f9ea00af188,
readfds=0x7f9ea00aeef8, nfds=, this=0x7f9ea0089890) at
kernel/qeventdispatcher_unix.cpp:320
#3  0x7f9f58341c0e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7f9ea00aed60, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196
#4  0x7f9f5834213e in
QEventDispatcherUNIX::processEvents(QFlags)
(this=0x7f9ea0089890, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f9f582ebdea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f9ea5aeaca0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f9f581088a4 in QThread::exec() (this=this@entry=0x202a970) at
thread/qthread.cpp:503
#7  0x7f9f52c1e3c5 in QQmlThreadPrivate::run() (this=0x202a970) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f9f5810d84e in QThreadPrivate::start(void*) (arg=0x202a970) at
thread/qthread_unix.cpp:331
#9  0x7f9f53ac16fa in start_thread 

[amarok] [Bug 363054] Building amarok-2.8.90 with GCC-6.1.0 fails with "error: 'Playlists::Playlist::ModelStack' has not been declared"

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||rdie...@math.unl.edu
 Status|UNCONFIRMED |CONFIRMED

--- Comment #8 from Rex Dieter  ---
marking confirmed

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

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Git commit f1f247f1cc71e948c377ec7d1daa1389728fe88c by Gilles Caulier.
Committed on 01/06/2016 at 18:32.
Pushed by cgilles into branch 'master'.

be more verboze about dependency with libusb1 required by libgphoto2 to prevent
crash when libopencv is linked with libdc1394.
See bug #268267 for details about this problem.
FIXED-IN: 5.0.0

M  +1-0CMakeLists.txt
M  +1-1README

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

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

[kate] [Bug 363765] Allow “Tab key inserts tab character” as tab key action

[fantasai via KDE Bugzilla]

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

fantasai  changed:

   What|Removed |Added

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

--- Comment #2 from fantasai  ---
That's an interesting workaround, but it is not very discoverable, and
therefore not solving the usability problem. This should just be one of the
options in the same panel that sets all the other options for what a Tab key
does.

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

[krita] [Bug 363808] New: Lines between the end and the start of a stroke using my yiynova 22u tablet monitor

[sebagm via KDE Bugzilla]

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

Bug ID: 363808
   Summary: Lines between the end and the start of a stroke using
my yiynova 22u tablet monitor
   Product: krita
   Version: 3.0
  Platform: Windows CE
   URL: http://puu.sh/pd0K8/534d98f3bc.jpg
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: sebastian.a@gmail.com

When i draw, there are lines between the end and the start of a stroke using my
yiynova 22u tablet monitor. This issue is not happening in the 2.9 version :

http://puu.sh/pd0WM/f5b83ba42d.jpg

.. Thanks

Reproducible: Always

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

[krita] [Bug 359255] OSX Japanese env: Krita3.0 prealpha assert on startup

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #16 from Boudewijn Rempt  ---
Could you try

http://www.valdyas.org/~boud/krita-f0cbffc-3.0.dmg

This has the stuff in the Resources folder and the share a link to that. If
that doesn't work, I'll make a version with more debug output.

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

[kdenlive] [Bug 363604] Project bin doesn't list folders in proper numerical order (screenshot included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #3 from Jesse  ---
Confirmed its implementation in the latest git build. Works great! Thanks so
much JB! Marking this bug as resolved/fixed.

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

[umbrello] [Bug 363807] Reversed sequence numbers on stack trace import

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||2.19.2 (KDE Applications
   ||16.04.2)
  Latest Commit||http://commits.kde.org/umbr
   ||ello/3dd3d99df813776598e50c
   ||2012ade8ce309a0620
 Resolution|--- |FIXED

--- Comment #2 from Ralf Habacker  ---
Git commit 3dd3d99df813776598e50c2012ade8ce309a0620 by Ralf Habacker.
Committed on 01/06/2016 at 17:59.
Pushed by habacker into branch 'Applications/16.04'.

Fix 'Reversed sequence numbers on stack trace import'.
 FIXED-IN:2.19.2 (KDE Applications 16.04.2)

M  +4-3umbrello/codeimport/import_utils.cpp

http://commits.kde.org/umbrello/3dd3d99df813776598e50c2012ade8ce309a0620

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

[umbrello] [Bug 363807] Reversed sequence numbers on stack trace import

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #1 from Ralf Habacker  ---
Created attachment 99309
  --> https://bugs.kde.org/attachment.cgi?id=99309=edit
stack trace file

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

[umbrello] [Bug 363807] New: Reversed sequence numbers on stack trace import

[Ralf Habacker via KDE Bugzilla]

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

Bug ID: 363807
   Summary: Reversed sequence numbers on stack trace import
   Product: umbrello
   Version: 2.19.2 (KDE Applications 16.04.1)
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de

With bug 358867 support for importing stack traces has been added. Using this
import the displayed sequence numbers are starting at a high value and are
decremented on each following message.

Reproducible: Always

Steps to Reproduce:
1. open umbrello
2. create sequence diagram
3. import appended stack trace file

Actual Results:  
Sequence numbers are starting with high values and are decremented on each
following message.

Expected Results:  
The sequence numbers should start be 1. and should be incremented on each
following message.

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

[plasmashell] [Bug 363800] Can't preview windows on the task manager that are minimized

[via KDE Bugzilla]

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

--- Comment #2 from thanosshad...@yahoo.com ---
Yes but in cinnamon this one works, for example, and is pretty useful because I
usually end up with many windows (most of them minimized) and I can't preview
them. Which would be very handy because you can easily see what's going on
without opening the window and being "distracted". But ok, let's wait for
wayland...

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

[Discover] [Bug 363611] ratings don't work from packagekit component

[Jonathan Riddell via KDE Bugzilla]

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

--- Comment #11 from Jonathan Riddell  ---
Ah hah, can we hide the Ratings box on the front page until that gets
implemented?

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

[muon] [Bug 363695] Segmentation fault after startup of muon updater

[Frank via KDE Bugzilla]

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

--- Comment #5 from Frank  ---
Comment on attachment 99273
  --> https://bugs.kde.org/attachment.cgi?id=99273
crash report for muon updated

My system started working again yesterday and works even better today.  Have
received new updates through muon-updater and everything seems to be fine.
Is there any relationship to the long Memorial Day weekend in the USA?  Maybe
servers weren't available to respond to muon?

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

[kate] [Bug 363767] KWrite crashes during the opening of a file txt

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
should be fixed in KF5 versions.

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

[kate] [Bug 356473] Crashes after trying to open c/c++ files

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Dominik Haumann  ---
is fixed meanwhile.

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

[kshisen] [Bug 363797] won't launch

[Carl Symons via KDE Bugzilla]

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

--- Comment #3 from Carl Symons  ---
(In reply to Carl Symons from comment #2)
> (In reply to Frederik Schwarzer from comment #1)
> > What version are you running?
> 
> I apologize for the oversight.
> Version 1.10.0
>  Using:
> KDE Frameworks 5.22.0
> Qt 5.6.0 (built against 5.6.0)
> The xcb windowing system
> 
> openSUSE Tumbleweed

probably broken since 
Tumbleweed=20160529
kshisen (15.12.3 -> 16.04.1)

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

[plasmashell] [Bug 358128] Application Launcher should allow forgetting of documents separate from applications

[apache via KDE Bugzilla]

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

--- Comment #3 from apache  ---
I will check that. I never used activities before, I didn't need it. But I'd
prefer this preference to be available in menu or at least option from KDE4 to
delete recent documents from menu.

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

[Discover] [Bug 363806] front banner contains increasing number of repeated slides

[Jonathan Riddell via KDE Bugzilla]

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

--- Comment #1 from Jonathan Riddell  ---
Created attachment 99308
  --> https://bugs.kde.org/attachment.cgi?id=99308=edit
screenshot of it after a few hours running]

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

[Discover] [Bug 363806] New: front banner contains increasing number of repeated slides

[Jonathan Riddell via KDE Bugzilla]

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

Bug ID: 363806
   Summary: front banner contains increasing number of repeated
slides
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: j...@jriddell.org

I had Discover running for a while and the front banner which started with 7
slides (repeating through 4 different displays) gained more slides over time
until it ended up with lots.


Reproducible: Always

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

[kate] [Bug 361632] Crashes on closing does not loose anything Version 15.12.3

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

   Version Fixed In|Applications 16.04  |Applications > 15.12.3 (not
   ||15.12.3)

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

[kshisen] [Bug 363797] won't launch

[Carl Symons via KDE Bugzilla]

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

--- Comment #2 from Carl Symons  ---
(In reply to Frederik Schwarzer from comment #1)
> What version are you running?

I apologize for the oversight.
Version 1.10.0
 Using:
KDE Frameworks 5.22.0
Qt 5.6.0 (built against 5.6.0)
The xcb windowing system

openSUSE Tumbleweed

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

[kate] [Bug 361632] Crashes on closing does not loose anything Version 15.12.3

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #5 from Dominik Haumann  ---
Now also fixed for 15.12, but KDE itself will not do another release of this
branch.

If you are lucky, your distribution will get these fixes from the 15.12 branch,
and then this is also fixed there.

No fixes for the KDE 4 version for now, though.

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

[kate] [Bug 354630] Inconsitency in Kate's color schemes resulting in very difficult to read buttons and tabs for some KDE color schemes.

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kate |http://commits.kde.org/kate
   |/4ff786ca8eeeb65ad95669c8ad |/5c522177a9cdb7356cc4498ba0
   |de74fe02f1dfff  |bfc02ffda4f61e

--- Comment #4 from Dominik Haumann  ---
Git commit 5c522177a9cdb7356cc4498ba0bfc02ffda4f61e by Dominik Haumann.
Committed on 01/06/2016 at 17:09.
Pushed by dhaumann into branch 'Applications/15.12'.

Tabbar: use QPalette::WindowText role instead of ButtonText role as foreground
color

M  +1-1kate/katetabbutton.cpp

http://commits.kde.org/kate/5c522177a9cdb7356cc4498ba0bfc02ffda4f61e

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

[korganizer] [Bug 363805] New: korganizer Segv when adding todo item

[Mike Hammond via KDE Bugzilla]

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

Bug ID: 363805
   Summary: korganizer Segv when adding todo item
   Product: korganizer
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: kor...@koranzen.net

Application: korganizer (5.1.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Adding a new todo to a Google calendar

- Custom settings of the application:
approximately 12 calendars, includeing Google, Exchange, local.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0d17a38940 (LWP 8962))]

Thread 28 (Thread 0x7f0d0f5ef700 (LWP 8964)):
#0  0x7f0d2f68aae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f0d2f6459b0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0d2f6462cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0d2f6464ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0d38006a9b in QEventDispatcherGlib::processEvents
(this=0x7f0d080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f0d37faddea in QEventLoop::exec (this=this@entry=0x7f0d0f5eec80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f0d37dca8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f0d37dcf84e in QThreadPrivate::start (arg=0x1c3fd20) at
thread/qthread_unix.cpp:331
#8  0x7f0d2fb676fa in start_thread (arg=0x7f0d0f5ef700) at
pthread_create.c:333
#9  0x7f0d374cfb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7f0d0edee700 (LWP 8966)):
#0  0x7f0d374c3e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0d2f64639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0d2f6464ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0d38006a9b in QEventDispatcherGlib::processEvents
(this=0x7f0d08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f0d37faddea in QEventLoop::exec (this=this@entry=0x7f0d0ededc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f0d37dca8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f0d37dcf84e in QThreadPrivate::start (arg=0x1c42fa0) at
thread/qthread_unix.cpp:331
#7  0x7f0d2fb676fa in start_thread (arg=0x7f0d0edee700) at
pthread_create.c:333
#8  0x7f0d374cfb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7f0d0e5ed700 (LWP 8968)):
#0  0x7f0d37da4b30 in clock_gettime@plt () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f0d37e7fc16 in qt_clock_gettime (ts=0x7f0d0e5ec9f0, clock=) at tools/qelapsedtimer_unix.cpp:105
#2  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#4  0x7f0d38004529 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f0d04002ed0) at kernel/qtimerinfo_unix.cpp:84
#5  0x7f0d38004a95 in QTimerInfoList::timerWait (this=0x7f0d04002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#6  0x7f0d38005e7e in timerSourcePrepareHelper (timeout=0x7f0d0e5ecac4,
src=) at kernel/qeventdispatcher_glib.cpp:127
#7  timerSourcePrepare (source=, timeout=0x7f0d0e5ecac4) at
kernel/qeventdispatcher_glib.cpp:160
#8  0x7f0d2f64592d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f0d2f6462cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f0d2f6464ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f0d38006a9b in QEventDispatcherGlib::processEvents
(this=0x7f0d040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#12 0x7f0d37faddea in QEventLoop::exec (this=this@entry=0x7f0d0e5ecc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#13 0x7f0d37dca8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#14 0x7f0d37dcf84e in QThreadPrivate::start (arg=0x1c88020) at
thread/qthread_unix.cpp:331
#15 0x7f0d2fb676fa in start_thread (arg=0x7f0d0e5ed700) at
pthread_create.c:333
#16 0x7f0d374cfb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7f0d0ddec700 (LWP 8970)):
#0  0x7f0d374bf9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0d2f689740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0d2f645e84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0d2f646340 in ?? () from 

[kwin] [Bug 363804] Struts are broken with multiple screens

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #1 from Thomas Lübking  ---
please run "xprop" on the supposingly strutting panel and "xrandr -q" and
attach both outputs.

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

[kwin] [Bug 363804] Struts are broken with multiple screens

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||se...@kde.org

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

[kwin] [Bug 363804] New: Struts are broken with multiple screens

[Aleix Pol via KDE Bugzilla]

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

Bug ID: 363804
   Summary: Struts are broken with multiple screens
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend-x11
  Assignee: kwin-bugs-n...@kde.org
  Reporter: aleix...@kde.org

I have 2 screens, one panel at the bottom of one of the screens. Maximizing
windows get under the panel.

This doesn't happen if I "openbox --replace"
This doesn't happen with just 1 screen.

Reproducible: Always

Steps to Reproduce:
1. Start plasma with one panel at the bottom of one of the screen
2.
3.

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

[plasmashell] [Bug 363571] Switch user keeps adding unused entries

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #3 from Kai Uwe Broulik  ---
That's probably KDisplayManager doing weird things, or logind telling us
rubbish. Or, well, you really have tons of unused sessions :)

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

[plasmashell] [Bug 358128] Application Launcher should allow forgetting of documents separate from applications

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #2 from Kai Uwe Broulik  ---
You can create a new activity and enable "Private mode", then it shouldn't
track opened documents there.

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

[plasmashell] [Bug 363800] Can't preview windows on the task manager that are minimized

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #1 from Kai Uwe Broulik  ---
I can confirm. Might be related to this
https://quickgit.kde.org/?p=plasma-framework.git=commit=1e196fdfb2a6eaf1664e1155c086616d55c6712b
We stop redirecting when the thumbnail closes for performance reasons. The
problem is that when on X a window is minimized the window is *gone* and you
cannot grab a thumbnail anymore. As a workaround you can enable "Keep
thumbnails (breaks minmization)" in Compositor settings. (Also, Wayland will
fix it)

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