[kde] [Bug 359523] New: Start Thunderbird

[Alexsandr via KDE Bugzilla]

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

Bug ID: 359523
   Summary: Start Thunderbird
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bag.linux@rambler.ru

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 i686
Distribution: Linux Mint 17.1 Rebecca

-- Information about the crash:
- What I was doing when the application crashed:
Im start Thunderbird and connect to internet 3G-modem (Nokia E5).

-- Backtrace:
Application: Оболочка Plasma (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb13ee980 (LWP 12607))]

Thread 5 (Thread 0xa3d86b40 (LWP 12608)):
#0  0xb779d424 in __kernel_vsyscall ()
#1  0xb222dd4b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb7651dcc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb3162c92 in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#4  0xb3162cdf in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#5  0xb2229f70 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb7644bee in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xa1c8bb40 (LWP 12609)):
#0  0xb222edf0 in pthread_getspecific () from
/lib/i386-linux-gnu/libpthread.so.0
#1  0xb2152622 in g_private_get () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb2133f1e in g_thread_self () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb210d516 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb60bb95f in QEventDispatcherGlib::processEvents (this=0xa1300468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0xb608a823 in QEventLoop::processEvents (this=this@entry=0xa1c8b258,
flags=...) at kernel/qeventloop.cpp:149
#6  0xb608ab49 in QEventLoop::exec (this=this@entry=0xa1c8b258, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb5f7723d in QThread::exec (this=this@entry=0x93abd48) at
thread/qthread.cpp:537
#8  0xb606ac44 in QInotifyFileSystemWatcherEngine::run (this=0x93abd48) at
io/qfilesystemwatcher_inotify.cpp:265
#9  0xb5f79b6f in QThreadPrivate::start (arg=0x93abd48) at
thread/qthread_unix.cpp:349
#10 0xb2229f70 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#11 0xb7644bee in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0x9d7ffb40 (LWP 12613)):
#0  0xb5f5a533 in __x86.get_pc_thunk.bx () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#1  0xb60bbb72 in socketNotifierSourceCheck (source=0x9ce02870) at
kernel/qeventdispatcher_glib.cpp:80
#2  0xb210cdff in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb210d37a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb210d528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb60bb95f in QEventDispatcherGlib::processEvents (this=0x9ce00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0xb608a823 in QEventLoop::processEvents (this=this@entry=0x9d7ff258,
flags=...) at kernel/qeventloop.cpp:149
#7  0xb608ab49 in QEventLoop::exec (this=this@entry=0x9d7ff258, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb5f7723d in QThread::exec (this=this@entry=0x9be3d68) at
thread/qthread.cpp:537
#9  0xb606ac44 in QInotifyFileSystemWatcherEngine::run (this=0x9be3d68) at
io/qfilesystemwatcher_inotify.cpp:265
#10 0xb5f79b6f in QThreadPrivate::start (arg=0x9be3d68) at
thread/qthread_unix.cpp:349
#11 0xb2229f70 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb7644bee in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0x9f63bb40 (LWP 31724)):
#0  0xb779d424 in __kernel_vsyscall ()
#1  0xb7652872 in clock_gettime () from /lib/i386-linux-gnu/libc.so.6
#2  0xb5fd48cc in do_gettime (frac=0x9f63b010, sec=0x9f63b008) at
tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0xb60bd2a2 in updateCurrentTime (this=0x9ed00d9c) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x9ed00d9c, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0xb60bb82b in timerSourcePrepareHelper (src=,
timeout=0x9f63b10c) at kernel/qeventdispatcher_glib.cpp:143
#7  0xb60bb8bd in timerSourcePrepare (source=0x9ed00d68, timeout=0x9f63b10c) at
kernel/qeventdispatcher_glib.cpp:176
#8  0xb210c9b3 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb210d2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb210d528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb60bb95f in QEventDispatcherGlib::processEvents (this=0x9ed08918,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#12 0xb608a823 in 

[kwin] [Bug 359467] KWin might cause recursive QXcbEventReader::lock()'s

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
(In reply to Thomas Lübking from comment #3)
> They might argue that our "correct usage" is a native event filter ;-)
> 
> Maybe we'll have to -steal- "borrow" QXcbConnection::getTimestamp()

No need to steal, I wrote the code (9c45260942c0ee32267e651d981bfa33a6acb64d)
;-) And the reason for that was that it's impossible to implement it in a
native event filter (at least back then).

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

[plasmashell] [Bug 359522] New: Certain icons have purple background

[via KDE Bugzilla]

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

Bug ID: 359522
   Summary: Certain icons have purple background
   Product: plasmashell
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: sosa.danie...@gmail.com

Created attachment 97278
  --> https://bugs.kde.org/attachment.cgi?id=97278=edit
Screenshot of the system tray. Icons with purple background.

Some icons have a purple background. Applications such as the official telegram
desktop client and the qt5 branch of kfilebox. I don't know if its relevant but
both were installed from Arch AUR.

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

[kwin] [Bug 346275] KWIN broken vsync and wrong fps.

[Gerardo Exequiel Pozzi via KDE Bugzilla]

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

Gerardo Exequiel Pozzi  changed:

   What|Removed |Added

 CC||vmlinuz...@gmail.com

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

[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage

[Gerardo Exequiel Pozzi via KDE Bugzilla]

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

Gerardo Exequiel Pozzi  changed:

   What|Removed |Added

 CC||vmlinuz...@gmail.com

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

[kwin] [Bug 357988] Black screen when reconnecting display

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #17 from Bernd Steinhauser  ---
FYI, a bug was reported upstream, the issue was found and got fixed:
https://bugs.freedesktop.org/show_bug.cgi?id=93746

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

[plasmashell] [Bug 336570] Task list not updated in multiscreen setup

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #18 from Bernd Steinhauser  ---
I didn't really try this, because multiple panels for me caused massive
performance issues (opened a bug for that), so I couldn't use them.

Now that you mentioned it, I tried again at it seems to work for me, so somehow
it got fixed, I guess. Didn't try for long, though.

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

[konsole] [Bug 358560] Konsole crashes when I unplug a second monitor

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #2 from Bernd Steinhauser  ---
I did notice, that for me, it's not actually crashing, but konsole just
disappears (as in not visible anymore).

The process is reparanted to init and childs run until I kill konsole.

That's also why drkonqi doesn't appear.

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

[kdenlive] [Bug 359279] 15.13.0 git master - "Open" and "Save As" windows are missing icons, and won't let me choose destination path or folders (video example included)

[Evert Vorster via KDE Bugzilla]

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

--- Comment #12 from Evert Vorster  ---
Hmm... 

I wonder if this issue also exists on Arch with a GNOME desktop. I'd have to
make a virtual machine for it to make sure that it's not contaminated with my
KDE libraries. 

Unfortunately my day job will keep me plenty entertained for the next week or
so, and I will not have time to dick around with this. 

Honestly I have not had any reports on the kdenlive-git package about
incompatibilities with GNOME on Arch.

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

[kmail2] [Bug 352897] Kmail segfaults on configuring appearance

[Dan Ramaley via KDE Bugzilla]

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

Dan Ramaley  changed:

   What|Removed |Added

 CC||daniel.rama...@drake.edu

--- Comment #2 from Dan Ramaley  ---
I have this exact same issue. Kmail 4.14.10 crashes every time I try to access
the Appearance settings.

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

[kdenlive] [Bug 359521] breeze icons missing from the ui

[farid via KDE Bugzilla]

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

--- Comment #4 from farid  ---
Created attachment 97277
  --> https://bugs.kde.org/attachment.cgi?id=97277=edit
bin folder icons

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

[kdenlive] [Bug 359521] breeze icons missing from the ui

[farid via KDE Bugzilla]

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

--- Comment #2 from farid  ---
Created attachment 97275
  --> https://bugs.kde.org/attachment.cgi?id=97275=edit
open dialog

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

[kdenlive] [Bug 359521] breeze icons missing from the ui

[farid via KDE Bugzilla]

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

--- Comment #3 from farid  ---
Created attachment 97276
  --> https://bugs.kde.org/attachment.cgi?id=97276=edit
save dialog

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

[kdenlive] [Bug 359521] breeze icons missing from the ui

[farid via KDE Bugzilla]

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

--- Comment #1 from farid  ---
Created attachment 97274
  --> https://bugs.kde.org/attachment.cgi?id=97274=edit
new dialog - project folder

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

[kdenlive] [Bug 359521] New: breeze icons missing from the ui

[farid via KDE Bugzilla]

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

Bug ID: 359521
   Summary: breeze icons missing from the ui
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: snd.no...@gmail.com

just realized that the breeze icons aren't used in all of the ui. see attached
images.

Reproducible: Always


Actual Results:  
using desktop theme icons.

Expected Results:  
to use kdenlive's breeze icons.

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

[dolphin] [Bug 359520] New: Dolphin crashes when trying to copy a file

[mzs . 112000]

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

Bug ID: 359520
   Summary: Dolphin crashes when trying to copy a file
   Product: dolphin
   Version: 15.12.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mzs.112...@gmail.com

Application: dolphin (15.12.1)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-040500rc3-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I tried to copy a file in dolphin when it crashed, I copied it to that same
folder as the original file.
Expected behavior: Dolphin should have asked if I wanted to type a new name, or
if I want to cancel.
What actually happened: Dolphin crashed.

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

Thread 3 (Thread 0x7f5426c9a700 (LWP 16090)):
#0  0x7f543da0d8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f54320acbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f54320ae74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f54296197e9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f54385cfa6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5434d786aa in start_thread (arg=0x7f5426c9a700) at
pthread_create.c:333
#6  0x7f543da18eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f541d806700 (LWP 16092)):
#0  0x7fffaac45c3f in clock_gettime ()
#1  0x7f543da2738d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f5438680006 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f5438804f99 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5438805505 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f54388068ee in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f54341ed77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f54341ee11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f54341ee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f543880750b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f54387ae50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f54385caac4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f54385cfa6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f5434d786aa in start_thread (arg=0x7f541d806700) at
pthread_create.c:333
#14 0x7f543da18eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f54299c0800 (LWP 16089)):
[KCrash Handler]
#6  0x7f543947f214 in QScrollArea::widget() const () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f543c2ec497 in KIO::RenameDialog::resizePanels() () from
/usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#8  0x7f54387e07b1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f54392f874b in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f54392b59dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f54392baea6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f54387b0d7b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f54387b3176 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f54388070e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f54341edff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7f54341ee250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f54341ee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f54388074ef in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f54387ae50a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f54394b0a6d in QDialog::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f543c2f7b97 in KIO::JobUiDelegate::askFileRename(KJob*, QString
const&, QUrl const&, QUrl const&, QFlags, QString&,
unsigned long long, 

[kshisen] [Bug 358773] kshisen shows as stuck when obvious moves remain

[chili555 via KDE Bugzilla]

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

chili555  changed:

   What|Removed |Added

 CC||wrwes...@gmail.com

--- Comment #5 from chili555  ---
Created attachment 97273
  --> https://bugs.kde.org/attachment.cgi?id=97273=edit
Second example of report 'stuck' when a move is apparent.

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

[kshisen] [Bug 358773] kshisen shows as stuck when obvious moves remain

[chili555 via KDE Bugzilla]

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

--- Comment #4 from chili555  ---
Here is another example. Please see the cursor.

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

[clazy] [Bug 359000] new check: warn about unused Qt objects

[Nyall Dawson via KDE Bugzilla]

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

--- Comment #3 from Nyall Dawson  ---
Here's a simple test case:

#include 
#include 

int main(int, char **)
{
QString string; //no warning
QList list; //no warning
QVariant var; //no warning
QIcon i; //no warning

int num; //warning
}

building this with clang 3.7 warns only about the unused int variable, not the
unused QString/QList/QVariant etc.

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

[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #8 from Martin Klapetek  ---
Created attachment 97272
  --> https://bugs.kde.org/attachment.cgi?id=97272=edit
Patch

Ok here's a patch. It should work against 5.17 too.

Let me know if this does anything useful.

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

[plasmashell] [Bug 359155] Large memory leak and crash

[via KDE Bugzilla]

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

--- Comment #3 from roemhil...@gmail.com ---
(In reply to Marco Martin from comment #2)
> also, needed the ~/.xsession-errors file

Here is the xsession-errors file. Thanks!

grep: /home/gregg/.gnupg/gpg-agent.conf: No such file or directory
Loading stage  "initial" 72
startkde: Starting up...
kdeinit5: preparing to launch 'libkdeinit5_klauncher'
kdeinit5: Launched KLauncher, pid = 4027, result = 0
Qt: Session management error: networkIdsList argument is NULL
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0
kdeinit5: preparing to launch 'libkdeinit5_kded5'
kdeinit5: Launched KDED, pid = 4029 result = 0
kdeinit5: preparing to launch 'libkdeinit5_kcminit_startup'
kdeinit5: Launched 'kcminit_startup', pid = 4030 result = 0
kdeinit5: Got SETENV 'KDE_MULTIHEAD=false' from launcher.
Initializing  "kcm_style" :  "kcminit_style"
kf5.kded: found kded module "powerdevil" by prepending 'kded_' to the library
path, please fix your metadata.
kf5.kded: found kded module "networkmanagement" by prepending 'kded_' to the
library path, please fix your metadata.
kf5.kded: found kded module "printmanager" by prepending 'kded_' to the library
path, please fix your metadata.
kf5.kded: found kded module "accounts" by prepending 'kded_' to the library
path, please fix your metadata.
kf5.kded: found kded module "statusnotifierwatcher" by prepending 'kded_' to
the library path, please fix your metadata.
kf5.kded: found kded module "ksysguard" by prepending 'kded_' to the library
path, please fix your metadata.
kf5.kded: found kded module "kscreen" by prepending 'kded_' to the library
path, please fix your metadata.
kdeinit5: Got EXEC_NEW '/usr/lib64/libexec/kf5/kconf_update' from launcher.
kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/kconf_update'
kdeinit5: PID 4035 terminated.
powerdevil: Loading UPower backend...
powerdevil: Success!
powerdevil: Backend loaded, loading core
powerdevil: Core loaded, initializing backend
powerdevil: No outputs have backlight property
powerdevil: Falling back to helper to get brightness
kdeinit5: Got SETENV
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/gregg/.gtkrc:/home/gregg/.config/gtkrc' from
launcher.
kdeinit5: Got SETENV
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/gregg/.gtkrc-2.0:/home/gregg/.config/gtkrc-2.0'
from launcher.
Setting the name:  "org.kde.ActivityManager.ActivityTemplates"
Setting the name:  "org.kde.ActivityManager.Resources.Scoring"
Creating directory:  "/home/gregg/.local/share/kactivitymanagerd/resources/"
KActivities: Database connection: 
"kactivities_db_resources_140216270669696_readwrite" 
query_only:  QVariant(qlonglong, 0) 
journal_mode:QVariant(QString, "wal") 
wal_autocheckpoint:  QVariant(qlonglong, 100) 
synchronous: QVariant(qlonglong, 1)
Service started, version: 6.2.0
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was
':1.8'
detected kglobalaccel restarting, re-registering all shortcut keys
bluedevil: Already in OfflineMode
Initializing  "kcm_input" :  "kcminit_mouse"
powerdevil: current screen brightness value:  100
powerdevil: Backend is ready, KDE Power Management system initialized
XSync seems available and ready
XSync Inited
Supported, init completed
Initializing  "kded_touchpad" :  "kcminit_touchpad"
powerdevil: Session path: "/org/freedesktop/login1/session/_34"
powerdevil: ACTIVE SESSION PATH: "/org/freedesktop/login1/session/_34"
powerdevil: Current session is now active
powerdevil: fd passing available: true
kdeinit5: Got SETENV 'XCURSOR_THEME=breeze_cursors' from launcher.
Initializing  "kcm_access" :  "kcminit_access"
kdeinit5: Got EXEC_NEW '/usr/bin/kaccess' from launcher.
kdeinit5: preparing to launch '/usr/bin/kaccess'
Initializing  "kcm_kgamma" :  "kcminit_kgamma"
kdeinit5: PID 4030 terminated.
kdeinit5: Got KWRAPPER 'ksmserver' from wrapper.
kdeinit5: preparing to launch 'libkdeinit5_ksmserver'
QCoreApplication::arguments: Please instantiate the QApplication object first
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
powerdevil: systemd powersave events handling inhibited, descriptor: 32
powerdevil: systemd support initialized
powerdevil: Got a valid offer for  "DPMSControl"
kdeinit5: PID 4059 terminated.
powerdevil: Core is ready, registering various services on the bus...
powerdevil: Can't contact ck
powerdevil: We are now into activity  "8ae5c401-2e28-437d-9706-5f9b237540c7"
powerdevil: () ()
powerdevil: () ()
powerdevil: No batteries found, loading AC
powerdevil: Activity is not forcing a profile
Created alarm 20971521
Created alarm 20971524
powerdevil: Handle button events action could not check for screen
configuration
powerdevil: 
powerdevil: Loading timeouts with  30
Created alarm 20971525
Created alarm 20971526
Created alarm 20971527
kscreen: launcherDataAvailable: 

[kwin] [Bug 359467] KWin might cause recursive QXcbEventReader::lock()'s

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #3 from Thomas Lübking  ---
They might argue that our "correct usage" is a native event filter ;-)

Maybe we'll have to -steal- "borrow" QXcbConnection::getTimestamp()

-- 
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

[jamese via KDE Bugzilla]

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

--- Comment #19 from jamese  ---
Created attachment 97271
  --> https://bugs.kde.org/attachment.cgi?id=97271=edit
Incorrect panel placement post resume

The panel at the bottom of DP1-2 was placed on Laptop Screen pre-suspend the
previous day. Post resume it appears on DP1-2, it should be on Laptop Screen.
The panel on DP1-2 at the top was placed on DP1-2. the previous day.

If I place the panel at the top of Laptop Screen then post-resume DP1-2 ends up
with two panels at the top, one overlapping the other.

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

[systemsettings] [Bug 359519] New: keyboard shortcut settings ignored on first keypress

[illumilore via KDE Bugzilla]

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

Bug ID: 359519
   Summary: keyboard shortcut settings ignored on first keypress
   Product: systemsettings
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: illumil...@gmail.com

When pressing the media mute key on my keyboard, which is configured to mute
the audio, kde will frequently ignore the first keypress, requiring a second
before the audio actually mutes. Subsequent keypresses seem to work until
reboot.

Reproducible: Sometimes

-- 
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

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #18 from jamese  ---
Can confirm this issue, when resuming the panel from the bottom of "Laptop
Screen" moves to the bottom of one of the two DP screens plugged in. See
attachment coming up.

Plasma 5.5 backports packages, latest as of date on Kubuntu 15.10, using DP1.2
screens in an MST chain.

xrandr -q after resume:

Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
eDP1 connected primary 1920x1080+948+1080 (normal left inverted right x axis y
axis) 309mm x 173mm
   1920x1080 60.05*+  59.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1440x900  59.89  
   1280x960  60.00  
   1368x768  60.00  
   1360x768  59.8059.96  
   1152x864  60.00  
   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  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
527mm x 296mm
   1920x1080 60.00*+  50.0059.94  
   1600x1200 60.00  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0860.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
DP1-2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm
x 296mm
   1920x1080 60.00*+
   1600x1200 60.00  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1024x768  75.0860.00  
   800x600   75.0060.32  
   640x480   75.0060.00  
   720x400   70.08  
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 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)




Can't agree more with Samuel in Comment 16, using KDE with multiple screens is
a complete PITA. I wonder how many people try out KDE, find it doesn't work
consistently with multiple screens, then silently switch to something else?
There are a quite a few bug reports about DisplayPort issues lodged, search for
DisplayPort in bugs.kde.org and you'll see

In my case, if the panel from the laptop display moves to another screen and
there is a separate bug where that screen doesn't back post resume then the
laptop display is nearly unusable without knowing the keystrokes to drop to
runlevel 1 and kill sddm.

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

[kwin] [Bug 338999] [unspecific] Desktop freezes time to time on plasma 5 (collection of various unrelated problems, WONTFIX)

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||rajind...@hotmail.com

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

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

[kde] [Bug 359489] kde desktop becomes unresponsive

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Please check the discussion and possible workarounds in bug 338999.

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

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

[kdenlive] [Bug 359518] New: No icons in the interface.

[Leny via KDE Bugzilla]

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

Bug ID: 359518
   Summary: No icons in the interface.
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: morfheu...@hotmail.com

The icons do not appear in Kadenlive interface.

Reproducible: Always



Expected Results:  
Already, I say it's an excellent program Kdenlive . What could improve the
effects of zoom, should have an easy tool to draw a rectangle in the area to be
apliada .

Ubuntu 15.10 Wilye Wolf

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

[systemsettings] [Bug 359517] New: Can't extend onto second screen in VMWare

[Nicholas via KDE Bugzilla]

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

Bug ID: 359517
   Summary: Can't extend onto second screen in VMWare
   Product: systemsettings
   Version: 5.4.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nicho...@nshiell.com

Can't extend desktop onto secondary screen on VMWare (Plasma 5)

Given I am running Kubuntu inside VMWare fusion
 When I connect a second physical screen
   And I see VMware fullscreen the guest OS onto the screen
  Then I should be able to extend my desktop onto the second screen in system
settings

(Sorry if this bug is filed into the wrong place)

Reproducible: Always

Steps to Reproduce:
1. Run Kubuntu 15.10 inside VMWare Fusion (I have OSX as a host)
2. Plug in a second screen
3. Goto system settings > Display Configuration

Actual Results:  
Observe you can't extend the screen, second screen doesn't appear to be
detected

Expected Results:  
I should be able to extend my screen

This works with Plasma 4, on the same host OS, with the same install of VMWare
fusion

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

[kdenlive] [Bug 359279] 15.13.0 git master - "Open" and "Save As" windows are missing icons, and won't let me choose destination path or folders (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #11 from Jesse  ---
Alright, I gave in. I might've chickened out on Antergos because an update
happened that had my whole software management apps down, and I got spooked. I
installed Antergos with KDE Plasma 5.5.4, and naturally it works flawlessly.
This issue doesn't exist.

I'd still like to see if there's a way to have this running smoothly from
source on non-KDE desktops (as much of the community still doesn't use KDE).
The reputation of Kdenlive would excel that much more if it worked the same
regardless of the desktop/distro, but I get it's not that simple.

Anyways, thanks Evert for the little nudge back towards Antergos/Arch. I solved
the biggest issue with screen tearing (which was the final straw that had me
pull away from it), so I'll give it another run. :)

Marking this bug as resolved > invalid.

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

[digikam] [Bug 359087] Preview image scroll position should be smarter when changing between images with different resolutions

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
This commit should solve the problem from Comment 1.

Maik

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

[digikam] [Bug 359087] Preview image scroll position should be smarter when changing between images with different resolutions

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #2 from Maik Qualmann  ---
Git commit 07f09f47cb876b4b964f4ca5fe9d8cf5f6fe97ea by Maik Qualmann.
Committed on 17/02/2016 at 21:58.
Pushed by mqualmann into branch 'master'.

fix wrong 100% visual view of a half size RAW preview

M  +3-3libs/widgets/graphicsview/imagezoomsettings.cpp

http://commits.kde.org/digikam/07f09f47cb876b4b964f4ca5fe9d8cf5f6fe97ea

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

[digikam] [Bug 359516] New: Trash not sortable by deletion time

[Michal Sylwester via KDE Bugzilla]

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

Bug ID: 359516
   Summary: Trash not sortable by deletion time
   Product: digikam
   Version: 5.0.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Albums View
  Assignee: digikam-de...@kde.org
  Reporter: msylwes...@gmail.com

Items in trash seem to be always sorted by name. Would be nice to have it
sortable by date as well. It would be easier to find recently removed items.

Reproducible: Always

Steps to Reproduce:
1. Go to trash, check how images are sorted

Actual Results:  
Sorted always by name

Expected Results:  
Possible to change between sort by name/sort by deletion time

It would be nice to have the sorting changeable by clicking the table headers.

Also, perhaps it would make sense to disable the View->Sort order while in
trash? It does not really work here, and changing order in the real albums
while they are not visible may be confusing.

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

[digikam] [Bug 359431] When importing images if they are available in pairs with same name/different format consider pairing them as 2 versions of same image

[Michal Sylwester via KDE Bugzilla]

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

--- Comment #2 from Michal Sylwester  ---
Nice. I've never used grouping before, I'll see how it works for me.

Michal

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

[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #4 from Thomas Lübking  ---
Those look fishy:
0x2600040 "UE4 Dummy GL window": ("UE4-Linux-Test" "UE4-Linux-Test")  1x1+0+0 
+0+0
0x260003d "UE4 Dummy GL window": ("UE4-Linux-Test" "UE4-Linux-Test")  1x1+0+0 
+0+0

But the relevant should be the game:
0x2600043 "UnrealTournament (64-bit, GLSL_150)": ("UE4-Linux-Test"
"UE4-Linux-Test")
and the dialog:
0x2e2 "READ ME FIRST": ()  505x146+0+0  +711+340

Basically all unreal related windows with names (the outer ones are technical
wrappers)

Please update the tree as well when obtaining the wininfo and props (so we can
see the window relation in case the windows are not directly transient to each
other - the id's change with restarting the game)

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

[dolphin] [Bug 359456] Dolphin Copy Crash

[Frank Reininghaus via KDE Bugzilla]

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

Frank Reininghaus  changed:

   What|Removed |Added

 CC||frank7...@googlemail.com

--- Comment #2 from Frank Reininghaus  ---
Thanks for the bug report. Since this seems to be related to the context menu
and threads according to the backtrace, I'm wondering if this could be a
duplicate of bug 351485 (which will be fixed in KDE Frameworks 5.20).

Could you check if the crash is gone if you disable the context menu plugin for
linking files to activities (Services section in the Settings dialog)? Thanks.

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

[clazy] [Bug 356372] new check: Find lambdas capturing local variables by ref, when inside connects

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/claz
   ||y/d984f82856e12a2948f8aa0ab
   ||86950d30dd6bbd8

--- Comment #3 from Sergio Martins  ---
Git commit d984f82856e12a2948f8aa0ab86950d30dd6bbd8 by Sergio Martins.
Committed on 17/02/2016 at 21:17.
Pushed by smartins into branch 'master'.

lambda-in-connect: Relax the warning if the sender is on the stack

The connection will disconnect when the sender goes out of scope
so it's safe. Unless the connect was made in a nested scope but that's rare,
patches accepted.

M  +8-0checks/lambda-in-connect.cpp
M  +4-0tests/lambda-in-connect/main.cpp

http://commits.kde.org/clazy/d984f82856e12a2948f8aa0ab86950d30dd6bbd8

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

[dolphin] [Bug 359456] Dolphin Copy Crash

[Frank Reininghaus via KDE Bugzilla]

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

Frank Reininghaus  changed:

   What|Removed |Added

 CC||b...@openaliasbox.org

--- Comment #1 from Frank Reininghaus  ---
*** Bug 359481 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 359481] Dolphin plante

[Frank Reininghaus via KDE Bugzilla]

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

Frank Reininghaus  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||frank7...@googlemail.com

--- Comment #1 from Frank Reininghaus  ---


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

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

[dolphin] [Bug 359455] Dolphin Preview Resize Crash

[Frank Reininghaus via KDE Bugzilla]

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

Frank Reininghaus  changed:

   What|Removed |Added

 CC||frank7...@googlemail.com
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Frank Reininghaus  ---
Thanks for the bug report. This looks pretty much like a crash in the
activities plugin for the context menu. It will be fixed in KDE Frameworks
5.20.

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

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

[frameworks-kactivities] [Bug 351485] Crash after opening Activities context-menu

[Frank Reininghaus via KDE Bugzilla]

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

Frank Reininghaus  changed:

   What|Removed |Added

 CC||b.we...@gmail.com

--- Comment #29 from Frank Reininghaus  ---
*** Bug 359455 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 359384] Logout/leave dialog design disaster

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||colo...@autistici.org

--- Comment #2 from Thomas Pfeiffer  ---
There is currently a redesign of all screens "around" Plasma (from GRUB to
shutdown) in progress, so the leave dialog will be tackled as well.

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

[dolphin] [Bug 359515] New: Search works in Kickoff, Krunner but not Dolphin and Places Panel

[via KDE Bugzilla]

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

Bug ID: 359515
   Summary: Search works in Kickoff, Krunner but not Dolphin and
Places Panel
   Product: dolphin
   Version: 15.12.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: perrantre...@googlemail.com

balooctl status shows that baloo is working normally. I can search for files
using Krunner (Alt+F2) or by typing in the Kickoff application launcher.

However, in Dolphin, search produce 0 results whether I use the Places panel
and click on 'Documents', 'Images' etc. or if I use the Ctrl + F search toolbar
and search by either filename or content.

I have tried using a new user with a brand new config but the same problem
happens.



Reproducible: Always

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

[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)

[Geert Janssens via KDE Bugzilla]

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

--- Comment #2 from Geert Janssens  ---
Some further evolution. It looks like this bug is fixed for kf5 based
applications. Current Dolphin (dolphin-15.12.1-1.fc23.x86_64) no longer has
this issue.

KDE 4 based applications still behave erratically. For example, current okular
still won't properly show the contents of an nfs share not owned by the logged
in user.

Note also that even though the folder contents is not shown (or only briefly),
I can still navigate deeper down the hierarchy by typing the the address bar.
This still correctly autocompletes as well. So it's really something in the
folder content view area that's messed up.

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

[valgrind] [Bug 359201] futex syscall "skips" argument 5 if op is FUTEX_WAIT_BITSET

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
Summary|futex syscall "skips"   |futex syscall "skips"
   |argument 5 if op is |argument 5 if op is
   |FUTEXT_WAIT_BITSET  |FUTEX_WAIT_BITSET

--- Comment #1 from Mark Wielaard  ---
valgrind svn r15793

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

[systemsettings] [Bug 359322] fontinst: improve family and style filter (serif, bold, italic, …)

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||colo...@autistici.org
 Ever confirmed|0   |1

--- Comment #5 from Thomas Pfeiffer  ---
I can confirm: When filtering by style, all fonts matching the style entered
should be found.
I don't really know what else that filter type should be used for.

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

[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.

[Stephan Lahl via KDE Bugzilla]

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

--- Comment #100 from Stephan Lahl  ---
Not resolved, not fixed.
KMail 4.14.3 on KDE 4.14.13 (Ubuntu 14.04 LTS) is completely broken.
Every 4 or 5 mails one has to yell some akondactl restart at a shell.
If you bugfix is to install other servers - this is unacceptable. 
The real bugfix in this case is to switch from KMail to Thunderbird.

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

[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.

[Stephan Lahl via KDE Bugzilla]

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

Stephan Lahl  changed:

   What|Removed |Added

 CC||s.l...@gmx.de

--- Comment #99 from Stephan Lahl  ---
Not resolved, not fixed.
KMail 4.14.3 on KDE 4.14.13 (Ubuntu 14.04 LTS) is completely broken.
Every 4 or 5 mails one has to yell some akondactl restart at a shell.
If you bugfix is to install other servers - this is unacceptable. 
The real bugfix in this case is to switch from KMail to Thunderbird.

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

[plasmashell] [Bug 359514] New: Plasmashell crash

[Morten Søltoft via KDE Bugzilla]

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

Bug ID: 359514
   Summary: Plasmashell crash
   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: mor...@soeltoft.dk
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

-- Information about the crash:
Just after login (any user on the system)

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f3c773c9700 (LWP 2736)):
#0  0x7f3c88c2524d in poll () from /lib64/libc.so.6
#1  0x7f3c8dafa432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f3c8dafc007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f3c79b49e29 in QXcbEventReader::run (this=0x24f5e60) at
qxcbconnection.cpp:1229
#4  0x7f3c8931594f in QThreadPrivate::start (arg=0x24f5e60) at
thread/qthread_unix.cpp:331
#5  0x7f3c8842c4a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f3c88c2dbdd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f3c6fbde700 (LWP 2751)):
#0  0x7ffeefba8c9f in clock_gettime ()
#1  0x7f3c88c3a7d6 in clock_gettime () from /lib64/libc.so.6
#2  0x7f3c893c11a6 in qt_clock_gettime (ts=0x7f3c6fbdda60, clock=) at tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#5  0x7f3c895380e9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f3c68002ed0) at kernel/qtimerinfo_unix.cpp:84
#6  0x7f3c895385f5 in QTimerInfoList::timerWait (this=0x7f3c68002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#7  0x7f3c8953998e in timerSourcePrepareHelper (timeout=0x7f3c6fbddb14,
src=) at kernel/qeventdispatcher_glib.cpp:127
#8  timerSourcePrepare (source=, timeout=0x7f3c6fbddb14) at
kernel/qeventdispatcher_glib.cpp:160
#9  0x7f3c853198bd in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f3c8531a1c3 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x7f3c8531a39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x7f3c8953a52b in QEventDispatcherGlib::processEvents
(this=0x7f3c680008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#13 0x7f3c894e463a in QEventLoop::exec (this=this@entry=0x7f3c6fbddcb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#14 0x7f3c89310b1c in QThread::exec (this=this@entry=0x25da5b0) at
thread/qthread.cpp:503
#15 0x7f3c8c5e09a5 in QQmlThreadPrivate::run (this=0x25da5b0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#16 0x7f3c8931594f in QThreadPrivate::start (arg=0x25da5b0) at
thread/qthread_unix.cpp:331
#17 0x7f3c8842c4a4 in start_thread () from /lib64/libpthread.so.0
#18 0x7f3c88c2dbdd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f3c64106700 (LWP 2753)):
#0  0x7f3c85319b48 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f3c8531a20f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f3c8531a39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c8953a52b in QEventDispatcherGlib::processEvents
(this=0x7f3c5c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f3c894e463a in QEventLoop::exec (this=this@entry=0x7f3c64105cb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f3c89310b1c in QThread::exec (this=this@entry=0x27aa5a0) at
thread/qthread.cpp:503
#6  0x7f3c8c5e09a5 in QQmlThreadPrivate::run (this=0x27aa5a0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7f3c8931594f in QThreadPrivate::start (arg=0x27aa5a0) at
thread/qthread_unix.cpp:331
#8  0x7f3c8842c4a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3c88c2dbdd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f3c6274c700 (LWP 2754)):
#0  0x7f3c88430110 in __pthread_mutex_unlock_usercnt () from
/lib64/libpthread.so.0
#1  0x7f3c8472ab69 in ?? () from /usr/lib64/libGL.so.1
#2  0x7f3c8472e81b in ?? () from /usr/lib64/libGL.so.1
#3  0x7f3c805c1fc0 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.96
#4  0x7f3c8535c290 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f3c85319dc4 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f3c8531a238 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7f3c8531a39c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#8  

[plasmashell] [Bug 359480] Plasma crashes when switching desktops

[Vince Radice via KDE Bugzilla]

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

--- Comment #3 from Vince Radice  ---
Created attachment 97270
  --> https://bugs.kde.org/attachment.cgi?id=97270=edit
Backtrace from Plasma crash

I get the backtrace but a message box popped up that said more packages needed
to be installed.  There was a button in the message box to get the packages but
the box dissappeared before I could click the button.

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

[telepathy] [Bug 347219] files overlap with gnome account

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #22 from Martin Klapetek  ---
Ok, turns out this actually breaks everything as the provider
id needs to match the filename.

So we've brainstormed this with Alberto again and we have
a better solution, which will involve a patch to libaccounts-glib
to look into /usr/share/accounts/{providers, services}/$XDG_CURRENT_DESKTOP/*
with /usr/share/accounts/{providers, services}/* as a fallback.

This way we can install our files into special directory without
needing any new env vars and/or changes in AppArmor and/or
needing to rename anything. All this will need is a new release
of libaccounts-glib.

I'll keep this bug updated.

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

[krita] [Bug 359288] Vector Text and Shape back-front arrangement resets

[kyril via KDE Bugzilla]

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

--- Comment #6 from kyril  ---
I think this was my first time reporting a bug and watching it die(get fixed)
with my own eyes. This was awesome :D /endOfUnrelatedComments

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

[plasmashell] [Bug 359480] Plasma crashes when switching desktops

[Vince Radice via KDE Bugzilla]

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

--- Comment #2 from Vince Radice  ---
Which debug packages need to be installed?  I have a lot already installed but
obviously I am missing some.  I think I have seen the option to create the
backtrace by clicking the Developer tab.  Is that the right one?

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

[valgrind] [Bug 359289] s390x: popcnt (B9E1) not implemented

[Florian Krohm via KDE Bugzilla]

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

Florian Krohm  changed:

   What|Removed |Added

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

--- Comment #6 from Florian Krohm  ---
(In reply to Andreas Arnez from comment #4)

> > In opcodes.h you define POPCNT. Good! Why not use it in popcnt.c?
> Just a matter of taste.  I prefer leaving the choice of operand registers to
> the compiler, like you would do in production code.

I've added opcodes.h mainly to deal with certain issues in old binutils
versions. I don't recall exactly what those problems were. 

> Can you add a check_popcnt call in popcnt.c where all input bits are 1?
> Sure.  Any particular reason for testing this specific value?

I like to test boundary values.

> > We also need configury to check whether the machine has the POPCNT insn. And
> > only if the machine supports that opcode we should build the test.
> Not sure about that one.  The patch always emulates the instruction,
> independent of the host capabilities. 

Right! Not sure what I was thinking. 

Thanks for the respin. I've added the patch as r15792 and VEX r3210

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

[plasmashell] [Bug 358849] Minimum plasmoid width and height not respected

[Luca Giambonini via KDE Bugzilla]

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

Luca Giambonini  changed:

   What|Removed |Added

 CC||luc...@bluewin.ch

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

[neon] [Bug 359513] New: Network app constantly requires manual input of wireless network passwords

[Jose Gomez-Dans via KDE Bugzilla]

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

Bug ID: 359513
   Summary: Network app constantly requires manual input of
wireless network passwords
   Product: neon
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: unstable packaging
  Assignee: n...@kde.org
  Reporter: jgomezd...@gmail.com

Since I installed the Neon repository on my Kubuntu 15.10 system, the Network
app will ask for the password for any configured wireless networks on the
system. The wireless networks get recognised, and NM tries to connect to them,
but I do get a pop up dialogue window asking me to provide the password. When I
do, connection quickly ensues without further problems. After I suspend my
laptop (for example), I need to re-enter the wireless password.

Reproducible: Always

Steps to Reproduce:
1. Start a KDE session
2. Make sure your wifi card is on
3. Be in range of an already configured wireless network.

Actual Results:  
You get a dialogue asking you to enter the wireless network password, although
it should have been remembered.

Expected Results:  
The dialogue shouldn't show up, and the system should connect automatically to
a known network to which the password has been saved.

Used to work fine with the Kubuntu 15.10 PPA packages, only the neon packages
broke this.

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

[digikam] [Bug 359512] xx.jpg2614 files

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
With metadata BQM tool digiKam do not create temp file. But Exiv2 in background
yes.

So i suspect a Exiv2 bug. Please check Exiv2 bugzilla history to be sure if
problem have already been reported.

Gilles Caulier

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

[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

[Fuchs via KDE Bugzilla]

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

--- Comment #10 from Fuchs  ---
In addition to that, the monochrome icons yet again get used in places where
they weren't supposed to be used, so I'd say it even actively goes against the
UX guidelines wrt icons. 

So yeah, I'd say this still needs to be fixed.

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

[calligrawords] [Bug 359511] New: Changing line spacing removes text formatting.

[bat cooper via KDE Bugzilla]

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

Bug ID: 359511
   Summary: Changing line spacing removes text formatting.
   Product: calligrawords
   Version: 2.9.11
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: b...@jbc.me.uk

In Words, if I format some text in a paragraph e.g. add bold, italics,
coloured, underlined, etc, and then if I try to change the line-spacing, the
text looses most of the formatting I have put in except for superscripts and
subscripts. 

Reproducible: Always

Steps to Reproduce:
1. Format some text with italics, underlined, bold, etc.
2. Select the paragraph with the mouse. 
3. Goto Paragraph Format -> Indent/Spacing tab and change line spacing.


Actual Results:  
Line spacing changes correctly but the other text formatting is lost. 

Expected Results:  
Line spacing changes correctly and text formatting should also be preserved.

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

[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

[Rex Dieter via KDE Bugzilla]

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

--- Comment #9 from Rex Dieter  ---
It is indeed a possible slippery slope when plasma themes include application
icons (like konversation), when/how to use them.

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

[kdeconnect] [Bug 355015] SFTP: Can't browse files on phone using kdeconnect-kde5

[via KDE Bugzilla]

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

--- Comment #18 from alfa...@gmx.de ---
Created attachment 97269
  --> https://bugs.kde.org/attachment.cgi?id=97269=edit
description how to access ext sd card content if predefined links are not
working

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

[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

[Fuchs via KDE Bugzilla]

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

--- Comment #8 from Fuchs  ---
If it really is by design, then I call that faulty behaviour from an UX
perspective. 

1) The icon used differs between icon tasks and everywhere else, including the
pager, krunner, the application menu, kwin and the application itself. That's a
massive breach of consistency. 

2) only a very limited amount of applications do provide these icons, so they
also look inconsistent within icon tasks. 

If this is by design: faulty behaviour. If it isn't: faulty behaviour. So still
a bug to be fixed.

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

[kdeconnect] [Bug 355015] SFTP: Can't browse files on phone using kdeconnect-kde5

[via KDE Bugzilla]

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

--- Comment #17 from alfa...@gmx.de ---
> could you say to how correctly edit paths for sdcard and camera?

Hello Alex

It's little "tricky", so I made a short presentation to show you how I get
access to my photos on sd card in my HTC one M8.
Please find it attached.

Kind regards
Florian

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

[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

[Rex Dieter via KDE Bugzilla]

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

--- Comment #7 from Rex Dieter  ---
I think this is by design, that the plasma-themed icons will get used in
preference to application-supplied ones, included as a fix for bug #353358

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

[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

[Fuchs via KDE Bugzilla]

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

--- Comment #6 from Fuchs  ---
I was hoping for this to be fixed with the other (systray) icon fix backported
via
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f640b7c3b14c747f026e5667beddbf7def4d0549,
 unfortunately this seems to be a completely unrelated issue and is still
present.

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

[kdenlive] [Bug 358161] kdenlive-git HEAD shows black clip when using GPU/movit and GLES2

[Anton Gubarkov via KDE Bugzilla]

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

Anton Gubarkov  changed:

   What|Removed |Added

Summary|kdenlive-git HEAD shows |kdenlive-git HEAD shows
   |black clip when using   |black clip when using
   |GPU/movit   |GPU/movit and GLES2

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

[plasmashell] [Bug 359510] New: Plasma crashes right after entering password on new user

[via KDE Bugzilla]

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

Bug ID: 359510
   Summary: Plasma crashes right after entering password on new
user
   Product: plasmashell
   Version: 5.5.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 31i73h4c...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.1-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
- Create new user via Account Settings
- Log out from main user
- Enter password on new user
- Plasma crash

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f546f312700 (LWP 9103)):
#0  0x7f547b72d57d in poll () from /lib64/libc.so.6
#1  0x7f547f6cfac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f547f6d1747 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f5471a986c9 in QXcbEventReader::run (this=0x1459380) at
qxcbconnection.cpp:1229
#4  0x7f547be0c292 in QThreadPrivate::start (arg=0x1459380) at
thread/qthread_unix.cpp:331
#5  0x7f547af40424 in start_thread () from /lib64/libpthread.so.0
#6  0x7f547b7365fd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f5467fff700 (LWP 9104)):
#0  0x7f54775e54b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f547759fee0 in g_main_context_acquire () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f54775a0e05 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f54775a105c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f547bffc71b in QEventDispatcherGlib::processEvents
(this=0x7f5468c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f547bfae6fa in QEventLoop::exec (this=this@entry=0x7f5467ffede0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f547be07c74 in QThread::exec (this=this@entry=0x151c7e0) at
thread/qthread.cpp:503
#7  0x7f547e5a0675 in QQmlThreadPrivate::run (this=0x151c7e0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f547be0c292 in QThreadPrivate::start (arg=0x151c7e0) at
thread/qthread_unix.cpp:331
#9  0x7f547af40424 in start_thread () from /lib64/libpthread.so.0
#10 0x7f547b7365fd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f545d55f700 (LWP 9105)):
#0  0x7f54775e54b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f54775a0ad6 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f54775a0fb0 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f54775a105c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f547bffc71b in QEventDispatcherGlib::processEvents
(this=0x7f54580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f547bfae6fa in QEventLoop::exec (this=this@entry=0x7f545d55ede0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f547be07c74 in QThread::exec (this=this@entry=0x170a860) at
thread/qthread.cpp:503
#7  0x7f547e5a0675 in QQmlThreadPrivate::run (this=0x170a860) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f547be0c292 in QThreadPrivate::start (arg=0x170a860) at
thread/qthread_unix.cpp:331
#9  0x7f547af40424 in start_thread () from /lib64/libpthread.so.0
#10 0x7f547b7365fd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f5457592700 (LWP 9106)):
#0  0x7f547b72d57d in poll () from /lib64/libc.so.6
#1  0x7f54775a0f4c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f54775a105c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f547bffc71b in QEventDispatcherGlib::processEvents
(this=0x7f5458c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f547bfae6fa in QEventLoop::exec (this=this@entry=0x7f5457591de0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f547be07c74 in QThread::exec (this=this@entry=0x1788050) at
thread/qthread.cpp:503
#6  0x7f547e5a0675 in QQmlThreadPrivate::run (this=0x1788050) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f547be0c292 in QThreadPrivate::start (arg=0x1788050) at
thread/qthread_unix.cpp:331
#8  0x7f547af40424 in start_thread () from /lib64/libpthread.so.0
#9  0x7f547b7365fd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f5455c8a700 (LWP 9107)):
#0  0x7f547af45faf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f548095a1a4 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f548095a1e9 in ?? () from /usr/lib64/libQt5Script.so.5
#3  

[kdenlive] [Bug 358161] kdenlive-git HEAD shows black clip when using GPU/movit

[Anton Gubarkov via KDE Bugzilla]

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

--- Comment #21 from Anton Gubarkov  ---
I've recompiled kdenlive with no gles2 support (together with the following qt
dependencies: qtwidgets qtdeclarative qtopengl qtprintsupport plasma qtgui). 
movit works now! 

OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Mobile "
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Mobile "
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false

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

[valgrind] [Bug 359289] s390x: popcnt (B9E1) not implemented

[Andreas Arnez via KDE Bugzilla]

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

Andreas Arnez  changed:

   What|Removed |Added

  Attachment #97264|0   |1
is obsolete||

--- Comment #5 from Andreas Arnez  ---
Created attachment 97268
  --> https://bugs.kde.org/attachment.cgi?id=97268=edit
Implement popcnt for s390x (v2)

Updated patch:
- add popcnt to Makefile.am;
- test all-one value;
- enable s390x_features to check for facility bit 45.

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

[telepathy] [Bug 347219] files overlap with gnome account

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #21 from Martin Klapetek  ---
Matt, the last commit should fix it for good.

Let me know if there are still troubles.

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

[valgrind] [Bug 359289] s390x: popcnt (B9E1) not implemented

[Andreas Arnez via KDE Bugzilla]

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

--- Comment #4 from Andreas Arnez  ---
(In reply to Florian Krohm from comment #3)
> Thanks for the patch.
> As Mark said: none/tests/s390x/Makefile.am needs adjustment. Otherwise the
> popcnt test does not get built during "make check".
Right, I missed to include that change.  Thanks to Mark for pointing out.

> In opcodes.h you define POPCNT. Good! Why not use it in popcnt.c?
Just a matter of taste.  I prefer leaving the choice of operand registers to
the compiler, like you would do in production code.

> Can you add a check_popcnt call in popcnt.c where all input bits are 1?
Sure.  Any particular reason for testing this specific value?

> We also need configury to check whether the machine has the POPCNT insn. And
> only if the machine supports that opcode we should build the test.
Not sure about that one.  The patch always emulates the instruction,
independent of the host capabilities.  Do you think that should change? 
Wouldn't that be inconsistent with setting facility bit 45?

> Other than that the patch looks good.
Thanks for reviewing!

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

[plasmashell] [Bug 359508] New: Plasma crash after opening Audio Volume Settings via Tray

[via KDE Bugzilla]

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

Bug ID: 359508
   Summary: Plasma crash after opening Audio Volume Settings via
Tray
   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: erikhub...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160212) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Rightclick on sound in system tray, clicked Audio Volume Settings

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 0x7f3451261900 (LWP 4979))]

Thread 14 (Thread 0x7f3432dbf700 (LWP 4989)):
#0  0x7f344b0e3591 in QTimerInfoList::repairTimersIfNeeded() () at
/usr/lib64/libQt5Core.so.5
#1  0x7f344b0e3603 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f344b0e498e in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f3446ec48bd in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f3446ec51c3 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3446ec539c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f344b0e552b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f344b08f63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f344aebbb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f344e18b9a5 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f344aec094f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f3449fd74a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f344a7d8bdd in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f342671a700 (LWP 4990)):
#0  0x7f344a7d024d in poll () at /lib64/libc.so.6
#1  0x7f3446ec5294 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3446ec539c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f344b0e552b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f344b08f63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f344aebbb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f344e18b9a5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f344aec094f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3449fd74a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f344a7d8bdd in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f3424e45700 (LWP 4991)):
#0  0x7f344b0e496b in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f3446ec48bd in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f3446ec51c3 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f3446ec539c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f344b0e552b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f344b08f63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f344aebbb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f344e18b9a5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f344aec094f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f3449fd74a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f344a7d8bdd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f341f3ef700 (LWP 4992)):
#0  0x7f3449fdd07f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3450933a84 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f3450933ac9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f3449fd74a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f344a7d8bdd in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f341c884700 (LWP 4993)):
#0  0x7f344a7d024d in poll () at /lib64/libc.so.6
#1  0x7f3446ec5294 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3446ec539c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f344b0e552b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f344b08f63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f344aebbb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f344ed10e42 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7f344aec094f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3449fd74a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f344a7d8bdd in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f33929f5700 (LWP 5001)):
#0  0x7f3449fdd07f in pthread_cond_wait@@GLIBC_2.3.2 () at

[kcalc] [Bug 359507] New: Conflicting accelerators

[Fabian Vogt via KDE Bugzilla]

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

Bug ID: 359507
   Summary: Conflicting accelerators
   Product: kcalc
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: fab...@ritter-vogt.de

In the german localization, the H accelerator is used both by the menu item
"Hilfe" and the base selection "Hex".

Reproducible: Always

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

[krusader] [Bug 329896] SMB URI does not handle hashes in filenames

[Martin Kostolný via KDE Bugzilla]

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

Martin Kostolný  changed:

   What|Removed |Added

 CC||clearmar...@zoho.com

--- Comment #1 from Martin Kostolný  ---
I think this ticket should be marked as a duplicate of this one: 270150

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

[digikam] [Bug 359505] Image deleted after applying tag

[antonio via KDE Bugzilla]

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

--- Comment #2 from antonio  ---
Thank you Gilles.
Waiting your help I disabled writing metadata into image and I enable writing
them to sidecar file just to avoid unwanted effect. That work well.
Now, in order to follow your suggestion, I have restore the initial setting:
label into images, caption and titles and template (copyright etc)
Now I can reproduce the bug because now all it working, I don't know wy, Well!!
If problem appears again I'll put in action your suggestion.
Many thanks for you help
Best regards
Antonio

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

[kdenlive] [Bug 358161] kdenlive-git HEAD shows black clip when using GPU/movit

[Anton Gubarkov via KDE Bugzilla]

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

--- Comment #20 from Anton Gubarkov  ---
(In reply to Jean-Baptiste Mardelle from comment #17)
> Can you please test with the commit I just made ? It should fix Movit if
> your GPU does not support the GL_ARB_sync extension, and also should prints
> some useful debug info in terminal if this does not solve your problem..

My MESA/Intel drivers also support ARB_sync:

anton@r9-008cln ~ $ glxinfo|grep -i ARB_sync
GL_ARB_shading_language_packing, GL_ARB_sync, GL_ARB_texture_barrier, 
GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync,

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

[kdenlive] [Bug 358161] kdenlive-git HEAD shows black clip when using GPU/movit

[Anton Gubarkov via KDE Bugzilla]

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

--- Comment #19 from Anton Gubarkov  ---
I tested with my optimus Nvidia Geforce 730M (nvidia closed-source drivers).
movit doesn't initialize either.
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GT 730M/PCIe/SSE2"
OpenGL ARG_SYNC:  false
OpenGL OpenGLES:  true

(In reply to Jean-Baptiste Mardelle from comment #17)
> Can you please test with the commit I just made ? It should fix Movit if
> your GPU does not support the GL_ARB_sync extension, and also should prints
> some useful debug info in terminal if this does not solve your problem..

nvidia drivers do support GL_ARB_sync:

anton@r9-008cln ~/Видео/2016-01-24 Венчание/Материал $ glxinfo|grep -i ARB_sync
GL_ARB_stencil_texturing, GL_ARB_sync, GL_ARB_tessellation_shader, 
GL_ARB_stencil_texturing, GL_ARB_sync, GL_ARB_tessellation_shader,

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

[valgrind] [Bug 359289] s390x: popcnt (B9E1) not implemented

[Florian Krohm via KDE Bugzilla]

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

Florian Krohm  changed:

   What|Removed |Added

 CC||flor...@eich-krohm.de

--- Comment #3 from Florian Krohm  ---
(In reply to Andreas Arnez from comment #1)
> Created attachment 97264 [details]
> Implement popcnt for s390x
> 
> Suggested fix for this Bug.

Thanks for the patch.
As Mark said: none/tests/s390x/Makefile.am needs adjustment. Otherwise the
popcnt test does not get built during "make check".
In opcodes.h you define POPCNT. Good! Why not use it in popcnt.c?

Can you add a check_popcnt call in popcnt.c where all input bits are 1?

We also need configury to check whether the machine has the POPCNT insn. And
only if the machine supports that opcode we should build the test.
Other than that the patch looks good.

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

[plasma4] [Bug 349962] Segmentation fault libthread_db

[via KDE Bugzilla]

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

--- Comment #5 from nk0...@yahoo.fr ---
Today a new crash (same as the others with auto recovery)  in another manner !.
This time using a program !!!

Program Used : Image Scan For Linux
Forecast for outpout file type : xxx.png
 Scanning in 96dpi method a A4 paper

Steps :
Opening Program : ok
Preview scan  : ok done
Press bouton scan : "Copie/valider"

Then appears a popup with "espace disque insuffisant" and plasma crashes.

This crash can be reproduced

Debug file containing :

Application: Outil de gestion de fenêtres Plasma (plasma-desktop), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7b65f7d780 (LWP 3370))]

Thread 3 (Thread 0x7f7b3a345700 (LWP 3371)):
#0  0x7f7b6480c67f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7b56d3f73a in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQtScript.so.4
#2  0x7f7b56d3f769 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQtScript.so.4
#3  0x7f7b648075bd in start_thread () from /lib64/libpthread.so.0
#4  0x7f7b635805cd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7ab2c98700 (LWP 3377)):
#0  0x7f7b6358dc2f in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7f7b63574d12 in poll () from /lib64/libc.so.6
#2  0x7f7b6065aeb4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f7b6065afbc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f7b64bc4e3e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQtCore.so.4
#5  0x7f7b64b96931 in
QEventLoop::processEvents(QFlags) () from
/lib64/libQtCore.so.4
#6  0x7f7b64b96c45 in
QEventLoop::exec(QFlags) () from
/lib64/libQtCore.so.4
#7  0x7f7b64a94899 in QThread::exec() () from /lib64/libQtCore.so.4
#8  0x7f7b64b783d3 in QInotifyFileSystemWatcherEngine::run() () from
/lib64/libQtCore.so.4
#9  0x7f7b64a96fff in QThreadPrivate::start(void*) () from
/lib64/libQtCore.so.4
#10 0x7f7b648075bd in start_thread () from /lib64/libpthread.so.0
#11 0x7f7b635805cd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7b65f7d780 (LWP 3370)):
[KCrash Handler]
#5  0x7f7aa2b31fb1 in mov_probe () from /lib64/libavformat.so.56
#6  0x7f7aa81dd6a5 in FFMPEGEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /usr/lib64/strigi/strigiea_ffmpeg.so
#7  0x7f7b5ade96a8 in
Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#8  0x7f7b5adc0bf5 in Strigi::AnalysisResult::indexChild(std::string
const&, long, Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#9  0x7f7b5ae04753 in OdfEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#10 0x7f7b5ade96a8 in
Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#11 0x7f7b5b451471 in KFileMetaInfoPrivate::init(QIODevice&, KUrl const&,
long, QFlags) () from /usr/lib64/libkio.so.5
#12 0x7f7b5b45195a in KFileMetaInfo::KFileMetaInfo(QString const&, QString
const&, QFlags) () from /usr/lib64/libkio.so.5
#13 0x7f7b5b43e95f in KFileItem::metaInfo(bool, int) const () from
/usr/lib64/libkio.so.5
#14 0x7f7b428bdf6c in ToolTipWidget::metaInfo() const () from
/usr/lib64/kde4/plasma_applet_folderview.so
#15 0x7f7b428c07fb in ToolTipWidget::setContent() () from
/usr/lib64/kde4/plasma_applet_folderview.so
#16 0x7f7b428c0aee in ToolTipWidget::toolTipAboutToShow() () from
/usr/lib64/kde4/plasma_applet_folderview.so
#17 0x7f7b64b9fa72 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () from
/lib64/libQtCore.so.4
#18 0x7f7b64ba1d2e in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from
/lib64/libQtCore.so.4
#19 0x7f7b5970869a in Plasma::ToolTipManagerPrivate::showToolTip() () from
/usr/lib64/libplasma.so.3
#20 0x7f7b59709069 in Plasma::ToolTipManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.25] () from
/usr/lib64/libplasma.so.3
#21 0x7f7b64bab88a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /lib64/libQtCore.so.4
#22 0x7f7b64bafc2b in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
#23 0x7f7b63d0f79c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQtGui.so.4
#24 0x7f7b63d15e40 in 

[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing

[antti via KDE Bugzilla]

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

--- Comment #3 from antti  ---
xwininfo -root -tree shows multiple entries (see attachment) related to UT4 -
which entries should be chosen to be checked by xprop and xwininfo?

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

[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing

[antti via KDE Bugzilla]

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

--- Comment #2 from antti  ---
Created attachment 97267
  --> https://bugs.kde.org/attachment.cgi?id=97267=edit
Output of xwininfo -root -tree

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

[valgrind] [Bug 359289] s390x: popcnt (B9E1) not implemented

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #2 from Mark Wielaard  ---
Thanks. Works for me on both the original program (libgccjit) and the simple
reproducer.

BTW. I believe the patch is missing an update to none/tests/s390x/Makefile.am
to make sure the new test is build and the vgtest file is added.

Index: none/tests/s390x/Makefile.am
===
--- none/tests/s390x/Makefile.am(revision 15402)
+++ none/tests/s390x/Makefile.am(working copy)
@@ -11,7 +11,7 @@
  ex_sig ex_clone cu14 cu14_1 cu41 fpconv ecag fpext fpext_warn \
  rounding-1 rounding-2 rounding-3 rounding-4 rounding-5 bfp-1 \
  bfp-2 bfp-3 bfp-4 srnm srnmb comp-1 comp-2 exrl tmll tm stmg \
- ex clst mvc test_fork test_sig rounding-6 rxsbg\
+ ex clst mvc test_fork test_sig rounding-6 rxsbg popcnt \
  spechelper-alr spechelper-algr \
  spechelper-slr spechelper-slgr \
  spechelper-cr  spechelper-clr  \

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

[kdeconnect] [Bug 355015] SFTP: Can't browse files on phone using kdeconnect-kde5

[Axel via KDE Bugzilla]

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

Axel  changed:

   What|Removed |Added

 CC||a738...@trbvn.com

--- Comment #16 from Axel  ---
(In reply to alfaflo from comment #15)
> (In reply to Albert Vaca from comment #14)
> > I made the fix that Johannes suggested, because it seems to work well in
> > every case. Thanks for your help!
> 
> Thanks Albert,
> 
> I've tested the latest git version and now I it works.
> Only "path short cuts" for camera and sdcard don't work (show only empty
> folders; I think paths are wrong), but I can manually access them by editing
> paths in Dolphin.
> 
> Kind regards
> Florian

could you say to how correctly edit paths for sdcard and camera?

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

[krunner] [Bug 358421] Krunner search window repeatedly crashes

[Twix]

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

--- Comment #2 from Eugene (Twix) Balagansky  ---
Created attachment 97266
  --> https://bugs.kde.org/attachment.cgi?id=97266=edit
New crash information added by DrKonqi

krunner (0.1) using Qt 5.4.2

- What I was doing when the application crashed:

Trying to start Konsole application. (typed Konsole and press ENTER)

-- Backtrace (Reduced):
#6  mdb_env_pick_meta (env=0x7f169c50b8e0, env=0x7f169c50b8e0) at mdb.c:3706
#7  mdb_txn_renew0 (txn=txn@entry=0x7f16900d1f30) at mdb.c:2512
#8  0x7f16addfbc10 in mdb_txn_begin (env=0x7f169c50b8e0, parent=, flags=, ret=0x7f16a9f9c9e8) at mdb.c:2740
#9  0x7f16ae4717ce in Baloo::SearchStore::exec
(this=this@entry=0x7f16a9f9cad0, term=..., offset=0, limit=10,
sortResults=) at ../../../src/lib/searchstore.cpp:74
#10 0x7f16ae460a32 in Baloo::Query::exec (this=this@entry=0x7f16a9f9cb80)
at ../../../src/lib/query.cpp:210

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

[dolphin] [Bug 359506] Dolphin doesn't show file's rating, tags, and comment.

[Naufal Fachrian via KDE Bugzilla]

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

Naufal Fachrian  changed:

   What|Removed |Added

 CC||naufal.fachr...@mail.ru

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

[dolphin] [Bug 359506] Dolphin doesn't show file's rating, tags, and comment.

[Naufal Fachrian via KDE Bugzilla]

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

--- Comment #1 from Naufal Fachrian  ---
Created attachment 97265
  --> https://bugs.kde.org/attachment.cgi?id=97265=edit
screenshot

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

[dolphin] [Bug 359506] New: Dolphin doesn't show file's rating, tags, and comment.

[Naufal Fachrian via KDE Bugzilla]

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

Bug ID: 359506
   Summary: Dolphin doesn't show file's rating, tags, and comment.
   Product: dolphin
   Version: 15.12.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: naufal.fachr...@mail.ru

I gave a file rating, tags, and comment. It shown on the panel but doesn't show
on file list. I've tried other view mode but it still doesn't show.

Reproducible: Always

Steps to Reproduce:
1. Give a file rating, tags, or comment (via panel).

Actual Results:  
The panel shows rating, tags, and comment of the file. But the file list
doesn't show them.

Expected Results:  
Both panel and file list should be able to show them.

There are no error or warning box.

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

[digikam] [Bug 359505] Image deleted after applying tag

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
turn on debug space with kdebugdialog and run digiKAm from a console. Look
trace printed while the destructive action.

See this page for details :

https://www.digikam.org/contrib

Gilles Caulier

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

[plasmashell] [Bug 347724] Digital Clock Plasmoid does not use fixed-width font

[Daniel Faust via KDE Bugzilla]

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

Daniel Faust  changed:

   What|Removed |Added

 CC||fabio.coa...@gmail.com

--- Comment #7 from Daniel Faust  ---
*** Bug 353716 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 353716] Plasma clock changes size (and moves other widget) when clock number changes

[Daniel Faust via KDE Bugzilla]

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

Daniel Faust  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||hessija...@mailbox.org

--- Comment #2 from Daniel Faust  ---


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

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

[digikam] [Bug 359505] New: Image deleted after applying tag

[antonio via KDE Bugzilla]

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

Bug ID: 359505
   Summary: Image deleted after applying tag
   Product: digikam
   Version: 4.14.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: antoniodipo...@gmail.com

I'm experiencing a problem when I try to add/modify exif/iptc and other
metadata tags 
This is a very strange and dangerous isn'it?
My environment is:
Ubuntu 14.04 xamd64
Linux 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64
GNU/Linux
digikam 4:4.14.0-trusty~ppa1
Since digiKam use external libraries to manage metadata (Exiv2) I would like to
involve exiv2 people clicking on Exiv2 library bugs and wishes on your support
page  
but I can't do it because the link dev.robotbattle.com/bugs/my_view_page.php
dosen't work.

Could you help me to find this destructive problem?
If you need more info or more test tell me that.
Waiting your help I send you my best regards
Antonio

Reproducible: Always

Steps to Reproduce:
1.Open digikam and select an image
2.try to change anything metadata 
3.click on apply button

Actual Results:  
the selected file will be deleted

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

[plasmashell] [Bug 336570] Task list not updated in multiscreen setup

[Christof Kaufmann via KDE Bugzilla]

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

Christof Kaufmann  changed:

   What|Removed |Added

 CC||christofkaufmann.dev@gmail.
   ||com

--- Comment #17 from Christof Kaufmann  ---
I can confirm this bug in Kubuntu 15.10 with Kubuntu Backports PPA (but
libtaskmanager5 is Version 4:5.4.2-0ubuntu1). It happens occasionally, when I
switch to two screen mode. However, I can also confirm that the workaround
described in bug 268259, comment 43 and restarting plasmashell helped. So they
seem to be related (and so bug 346878). I wonder if the OP can still confirm
the bug, as it should have been resolved in bug 268259, comment 50 as far as I
can see and that was for version 5.3.

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

[kleopatra] [Bug 358666] Short dates are used everywhere in the UI

[via KDE Bugzilla]

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

--- Comment #4 from kokotokos...@yopmail.fr ---
(In reply to Andre Heinecke from comment #3)

> As far as I understood you the original report was about: "(e.g., Thu 28
> Jan)"  So not including the Year and this is what you meant by ambiguous.

Correct.

> Which I took down as "Bad configuration"

Ok, this is what happened: before the last update to my system (I am running
Tumbleweed, currently on 20160126), the default short date format for my locale
(en_GB) was as mentioned above (Thu 28 Jan). It has since changed to
28/01/2016, which is what you are seeing, and so am I now on this machine
(though not on my OpenSUSE 13.1 box, though at least I can actually change the
defaults in System Configuration, as opposed to KDE5 (bug #340982 refers).

So all in all, you're correct that this bug should be closed insofar as the
default short date format now does display the year (thus resolving the
ambiguity) and the long date format would be too unwieldy.

> You can always respond (as you did) even to closed or resolved tickets. If
> one does not change the status directly tickets tend to "rot" in my
> experience.

Yeah, I know. I leave mine open for a few days after last comment unless I'm in
direct contact with the reporter. It does increase workload a bit though.

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

[kdenlive] [Bug 358161] kdenlive-git HEAD shows black clip when using GPU/movit

[Anton Gubarkov via KDE Bugzilla]

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

--- Comment #18 from Anton Gubarkov  ---
Hi, Jean-Baptiste.

I tested your latest commit. I still get a message to disable movit in the
monitors. 
Here is what I see in the term (besides the usual output):
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Mobile "
OpenGL ARG_SYNC:  false
OpenGL OpenGLES:  true
OpenGL vendor:  "Intel Open Source Technology Center"
OpenGL renderer:  "Mesa DRI Intel(R) Haswell Mobile "
OpenGL ARG_SYNC:  false
OpenGL OpenGLES:  true

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

[valgrind] [Bug 359289] s390x: popcnt (B9E1) not implemented

[Andreas Arnez via KDE Bugzilla]

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

Andreas Arnez  changed:

   What|Removed |Added

 CC||ar...@linux.vnet.ibm.com

--- Comment #1 from Andreas Arnez  ---
Created attachment 97264
  --> https://bugs.kde.org/attachment.cgi?id=97264=edit
Implement popcnt for s390x

Suggested fix for this Bug.

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

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

[Tom Hughes via KDE Bugzilla]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #3 from Tom Hughes  ---
How many of these have you actually tested though?

The point of leaving them commented out rather than just enabling them all is
to wait until people find something that is actually using them so that we can
get some sort of view of whether they work when we enable them.

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

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

[Marcin Juszkiewicz via KDE Bugzilla]

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

Marcin Juszkiewicz  changed:

   What|Removed |Added

  Attachment #97262|0   |1
is obsolete||

--- Comment #2 from Marcin Juszkiewicz  ---
Created attachment 97263
  --> https://bugs.kde.org/attachment.cgi?id=97263=edit
add all missing syscalls for aarch64 - rebased to svn HEAD

Ops, previous version was done against older valgrind tree...

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

[kdevelop] [Bug 359504] New: Show values of constants when hovering them

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 359504
   Summary: Show values of constants when hovering them
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aspotas...@gmail.com

Please display values of constants when hovering them with mouse pointer.

Examples of constants in C++:
  static const size_t size = 16;
  static const std::string blablabla("BlaBlaBla");

When you hover "size" or "blablabla" anywhere in the code where these
identifiers reference the above defined constants, a popup widget tells where
they are defined but doesn't show their values.

Reproducible: Always

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

[kate] [Bug 190214] copy to clipboard does not work quite right with kate

[via KDE Bugzilla]

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

chris27wjoy...@gmail.com changed:

   What|Removed |Added

 CC||chris27wjoy...@gmail.com

--- Comment #2 from chris27wjoy...@gmail.com ---
I am having the same problem, all I know is that after using copy in kate, then
closing kate, my clipboard is cleared. 

I never had this problem with kate before, it only started this today. Can
someone help out with what setting in Linux Mint or Ubuntu 14.04 LTS might need
to be changed to allow the clipboard to remain after kate is closed?

A temporary solution to this problem is to keep kate open until after the paste
has been made.

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

[valgrind] [Bug 356676] Unhandled arm64-linux syscalls: 125 and 126 (sched_get_priority_max/min)

[Marcin Juszkiewicz via KDE Bugzilla]

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

Marcin Juszkiewicz  changed:

   What|Removed |Added

 CC||mar...@juszkiewicz.com.pl

--- Comment #1 from Marcin Juszkiewicz  ---
patch from https://bugs.kde.org/show_bug.cgi?id=359503 handles it

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