[kactivitymanagerd] [Bug 364525] New: kactivitymanagerd spams .xsession-errors with QSqlError messages

[James Ring via KDE Bugzilla]

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

Bug ID: 364525
   Summary: kactivitymanagerd spams .xsession-errors with
QSqlError messages
   Product: kactivitymanagerd
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: s...@jdns.org
CC: plasma-b...@kde.org

Hi there,

I noticed that all my disk space would be slowly eaten up. After digging, I
found the culprit was kactivitymanagerd writing gigabytes of logs in a tight
loop to $HOME/.xsession-errors. The error message was:

QSqlError("5", "Unable to fetch row", "database is locked")
"DELETE FROM ResourceScoreCache WHERE  usedActivity =
'9181d38a-b709-4bbb-b13b-765a9a036ba2'  AND  1  AND targettedResource LIKE
:targettedResource ESCAPE '\\'"

To work around, I blew away the $HOME/.local/share/kactivitymanagerd/resources/
directory and restarted KDE, after which all was OK. I don't know specific
steps to reproduce, but possibly kactivitymanagerd should behave better in
these circumstances.

Reproducible: Always

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

[klipper] [Bug 356687] Clipboard applet should allow timeouting the selection

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin  ---
I don't think that it's possible to accidentally paste ancient stuff. One needs
to manually select elements from the history. The only automatic entry in the
clipboard is the current one. On that one klipper doesn't have the control to
really erase it as applications can set it.

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

[klipper] [Bug 364516] klipper chain mode

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
>From klipper's side this is not implementable. Klipper doesn't know when Ctrl+V
is performed in another application and thus cannot know when to update the
clipboard.

It's possible to set a global shortcut to move to next clipboard item. With
that you can define your manual chain. Given that I set this feature request to
worksforme.

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

[plasmashell] [Bug 360173] Plasma freeze sometime with notification & high load CPU and RAM

[miku84 via KDE Bugzilla]

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

--- Comment #13 from miku84  ---
Yes i have. I use it with Clementine. I removed it from the panel but the issue
remained.

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

[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

[Fuchs via KDE Bugzilla]

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

--- Comment #5 from Fuchs  ---
No worries, thanks for having a look and fixing :)

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

[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

[andreas via KDE Bugzilla]

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

--- Comment #4 from andreas  ---
ah sorry don't saw it.

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

[systemsettings] [Bug 364524] New: kcmshell5 kcm_sddm dumps core everytime it is executed

[Bob Wya via KDE Bugzilla]

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

Bug ID: 364524
   Summary: kcmshell5 kcm_sddm dumps core everytime it is executed
   Product: systemsettings
   Version: 5.6.95
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bob.mt@gmail.com

Application: systemsettings5 (5.6.95)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.23.0
Operating System: Linux 4.6.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
I'm unable to access the KCM module for SDDM (either via the SystemSettings5
menu or via a direct launch from a console).

I'm getting the following message when I attempt:
kcmshell 5 kcm_sddm

QDBusArgument: read from a write-only object
Aborted (core dumped)

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff41bcdb7c0 (LWP 19310))]

Thread 6 (Thread 0x7ff3ea693700 (LWP 19317)):
#0  0x7ff41836537d in poll () from /lib64/libc.so.6
#1  0x7ff4139dd0ac in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7ff4139dd432 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x7ff3eb17da26 in gdbus_shared_thread_func () from
/usr/lib64/libgio-2.0.so.0
#4  0x7ff413a037b5 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0
#5  0x7ff415732424 in start_thread () from /lib64/libpthread.so.0
#6  0x7ff41836e3fd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7ff3eae94700 (LWP 19316)):
#0  0x7ff41836537d in poll () from /lib64/libc.so.6
#1  0x7ff4139dd0ac in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7ff4139dd1bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff4139dd1f9 in glib_worker_main () from /usr/lib64/libglib-2.0.so.0
#4  0x7ff413a037b5 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0
#5  0x7ff415732424 in start_thread () from /lib64/libpthread.so.0
#6  0x7ff41836e3fd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7ff3f4801700 (LWP 19315)):
#0  0x7ff41836537d in poll () from /lib64/libc.so.6
#1  0x7ff4139dd0ac in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7ff4139dd1bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff418cdbebb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7ff418c831ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7ff418ac088b in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7ff41736f2e5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#7  0x7ff418ac62ad in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7ff415732424 in start_thread () from /lib64/libpthread.so.0
#9  0x7ff41836e3fd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7ff4027aa700 (LWP 19313)):
#0  0x7ff41836537d in poll () from /lib64/libc.so.6
#1  0x7ff4139dd0ac in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7ff4139dd1bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff418cdbebb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7ff418c831ba in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7ff418ac088b in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7ff41bddfc08 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7ff418ac62ad in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7ff415732424 in start_thread () from /lib64/libpthread.so.0
#9  0x7ff41836e3fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ff40b321700 (LWP 19312)):
#0  0x7ff41836537d in poll () from /lib64/libc.so.6
#1  0x7ff415faa8f2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7ff415fac707 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7ff40deb9bf9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff418ac62ad in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7ff415732424 in start_thread () from /lib64/libpthread.so.0
#6  0x7ff41836e3fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff41bcdb7c0 (LWP 19310)):
[KCrash Handler]
#6  0x7ff4182b82f8 in raise () from /lib64/libc.so.6
#7  0x7ff4182b974a in abort () from /lib64/libc.so.6
#8  0x7ff418aae9e9 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib64/libQt5Core.so.5
#9  0x7ff41bddef88 in
QDBusArgumentPrivate::checkRead(QDBusArgumentPrivate*) [clone .part.27] () from

[plasmashell] [Bug 364523] Task Manager and Launcher (Application Menu) inoperative after update to Plasma 5.6.95 openSUSE Leap 42.1

[Eike Hein via KDE Bugzilla]

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

--- Comment #3 from Eike Hein  ---
No problem, hope it gets worked out!

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

[plasmashell] [Bug 364523] Task Manager and Launcher (Application Menu) inoperative after update to Plasma 5.6.95 openSUSE Leap 42.1

[RobinK via KDE Bugzilla]

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

--- Comment #2 from RobinK  ---
Thank you.  Will do.  Sorry to bother you.

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

[plasmashell] [Bug 364523] Task Manager and Launcher (Application Menu) inoperative after update to Plasma 5.6.95 openSUSE Leap 42.1

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Eike Hein  ---
Hi,

this is a packaging/installation issue on your distro: It looks like your Task
Manager and Application Menu packages were built against a different version of
the ActivitiesStats library from KDE Frameworks than you have installed. Please
get in touch with the support folks of openSUSE to resolve this.

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

[plasmashell] [Bug 364523] New: Task Manager and Launcher (Application Menu) inoperative after update to Plasma 5.6.95 openSUSE Leap 42.1

[RobinK via KDE Bugzilla]

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

Bug ID: 364523
   Summary: Task Manager and Launcher (Application Menu)
inoperative after update to Plasma 5.6.95 openSUSE
Leap 42.1
   Product: plasmashell
   Version: 5.6.95
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: ro...@xtra.co.nz
CC: plasma-b...@kde.org

Recent update to plasma 5.6.95 openSUSE Leap 42.1 with openSUSE repositories
.KDE:/Frameworks5/openSUSE_Leap_42.1/ and
..KDE:/Qt5/openSUSE_Leap_42.1/ active.  After the update, in the desktop
both the Task Manager section of the Panel and the KDE Application Launcher are
permanently inoperative, though the individual application icons on the panel
continue to work.  I can also invoke GUI apps successfully from the command
line, (though this is a pain).  

Trying to invoke the launcher from the panel gives this error message:

"Error loading QML file:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1:
plugin cannot be loaded for module "org.kde.plasma.private.kicker": Cannot load
library /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so:
(libKF5ActivitiesStats.so.1: cannot open shared object file: No such file or
directory)"

I don't know if it's relevant, but I also note that although Yast2 tells me
that plasma components are at level 5.6.95, the KInfoCentre tells me they are
at level 5.5.5 (with QT at 5.6.1)   

Reproducible: Always

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

[ksvg2] [Bug 364504] ksvg is not able to display inkscape svg filter effects

[Christoph Feck via KDE Bugzilla]

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

--- Comment #1 from Christoph Feck  ---
Neither icons, nor the wallpapers use KSVG2. It is probably only used in KHTML.

If you want better SVG support in icons or wallpapers, they would need to
switch to QWebEngine, because that's the only Qt SVG renderer, that supports
SVG filters.

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

[dolphin] [Bug 364522] New: Dolphin crash when moving files between tabs : local drive (home directory) to a NAS (SMB)

[via KDE Bugzilla]

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

Bug ID: 364522
   Summary: Dolphin crash when moving files between tabs : local
drive (home directory) to a NAS (SMB)
   Product: dolphin
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cogre...@yahoo.com

Application: dolphin (16.04.1)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.6-300.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

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

Moving 8 files (2.6GiB) from my home directory to an SMB share on my NAS, using
2 tabs on one Dolphin window. The number & size of files being moved / copied
appears to be irrelevant to whether or not Dolphin crashes.

Tracking through the various bugs that were marked as duplicates/superseds of
the one that is most similar to the crash that I experienced ( 'Bug 364117 -
Crash when drag/drop a file to network location Status RESOLVED DUPLICATE of
bug 356558', which says 'Bug 356558 - Dolphin crashes when selecting multiple
files Status RESOLVED DUPLICATE of bug 356298', which says ' Bug 356298 - Baloo
crash - Baloo::File::load - mdb_dbi_open Status UNCONFIRMED' )

the installed Baloo version: baloo 5.22.0 (and the corresponding Frameworks
version is also 5.22.0)

The crash is reproducible sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f88c2cd2940 (LWP 5470))]

Thread 5 (Thread 0x7f88958c6700 (LWP 5491)):
#0  0x7f88b91a4b64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f88b915ff70 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f88b916096b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f88b9160b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f88be96065b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f88be90fa6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f88be76fa03 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f88be77403a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f88bb6ae5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f88bdb59ead in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f889ccb6700 (LWP 5485)):
#0  0x7f88bb6b3bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f889e029773 in radeon_drm_cs_emit_ioctl () at
/usr/lib64/dri/r600_dri.so
#2  0x7f889e028eb7 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so
#3  0x7f88bb6ae5ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f88bdb59ead in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f889f8de700 (LWP 5472)):
#0  0x7f88b91a4b64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f88b9160a3a in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f88b9160b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f88be96065b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f88be90fa6a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f88be76fa03 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f88beb6c3b9 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f88be77403a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f88bb6ae5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f88bdb59ead in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f88a4e8e700 (LWP 5471)):
#0  0x7f88bdb4e32d in poll () at /lib64/libc.so.6
#1  0x7f88b9ce8f80 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f88a4e8db80) at /usr/include/bits/poll2.h:46
#2  0x7f88b9ce8f80 in _xcb_conn_wait (c=c@entry=0x5609039fa470,
cond=cond@entry=0x5609039fa4b0, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:459
#3  0x7f88b9ceab79 in xcb_wait_for_event (c=0x5609039fa470) at xcb_in.c:693
#4  0x7f88a73310f9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#5  0x7f88be77403a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#6  0x7f88bb6ae5ca in start_thread () at /lib64/libpthread.so.0
#7  0x7f88bdb59ead in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f88c2cd2940 (LWP 5470)):
[KCrash Handler]
#5  0x7f88be910929 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/lib64/libQt5Core.so.5
#6  0x7f88bf483325 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#7  0x7f88bf48852f in QApplication::notify(QObject*, QEvent*) () at

[kmymoney4] [Bug 364487] I wish I could hide accounts / categories in reports AND roll up there amount in parent

[Hugo via KDE Bugzilla]

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

--- Comment #2 from Hugo  ---
Yes, I do actually mean not including them by unchecking them on the
configuration page.

I do realize that for now it is not only hiding them, but not including them at
all : this is my concern since I believe I'm not supposed to suppress an
account in a balanced double entry book.

Choosing betwin "include" and "display" checks for each account/category/...
would be perfect.

I will definitely consider exporting my reports to open office : I believe this
will be the best workaround for me now.

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

[kio-extras] [Bug 362709] kio_sftp.cpp:1239]: (style) Suspicious condition

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Replaced with bug 364381.

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

[systemsettings] [Bug 356237] Unable to change icon associated with mimetype if ~/.local/share/mime/packages does not already exist.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #6 from Christoph Feck  ---
Hm, I was incorrectly assuming that this commit went to "kio". Am I right that
this does not fix dolphin? How about other applications that uses the property
dialog?

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

[systemsettings] [Bug 356237] Unable to change icon associated with mimetype if ~/.local/share/mime/packages does not already exist.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||kevinlekil...@gmail.com

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

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

[dolphin] [Bug 364511] Changing an icon for a file or folder does not function.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
If you are using Plasma 5.6.5, and this is not fixed, please add a comment to
bug 356237.

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

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

[plasmashell] [Bug 364439] trying to switch to virtualdesktop by leftclick minimizes previewed apps unser Mousepointer instead of switching to desktop

[Eike Hein via KDE Bugzilla]

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

--- Comment #5 from Eike Hein  ---
The Task Manager applet is part of plasma-desktop upstream. I don't know how
various distros split this up.

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

[plasmashell] [Bug 364467] Task Tooltips disappears after closing one of many windows

[Eike Hein via KDE Bugzilla]

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

--- Comment #6 from Eike Hein  ---
There's no code differences between the regular and icons-only Task Managers as
far as the tooltip is concerned. Both currently close the tooltip. It's
possible to change this and I'm not opposed.

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

[plasmashell] [Bug 364508] no way of sorting "by desktop" and "from left to right" or "manually"

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |FIXED

--- Comment #1 from Eike Hein  ---
I don't really understand this report. FWIW, here's how it works in the current
version of the Task Manager (5.7) with "By Desktop" sorting: Tasks are sorted
by desktop number, and then alphabetical sorting. Alphabetical sorting sorts
first by application name, and then by window title. What exactly do you want
differently?

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

[plasmashell] [Bug 364505] grouping by application without ticked "only when taskbar is full" disables the "by desktop" sorting

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---
Plasma 5.7 ships a fully rewritten Task Manager backend, eliminating problems
like this:
https://blogs.kde.org/2016/05/31/new-plasma-task-manager-backend-faster-better-wayland

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

[plasmashell] [Bug 364445] Right-click on taskbar -> "Unlock Widgets". Expect "Lock" at same location.

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Component|Task Manager|Panel
   Assignee|h...@kde.org|plasma-b...@kde.org

--- Comment #4 from Eike Hein  ---
This is a VDG issue and Thomas is a VDG rep, so I think it's resolved. The best
I can do for you otherwise is reassign it to the Panel component.

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

[plasmashell] [Bug 364492] Upgrade from 5.6: if existing launchers are there, moving around icons deletes them

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---
Do you still have a copy of your old config by any chance? Did the launchers
initially get added correctly?

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

[kcharselect] [Bug 364490] Incorrect decoding of "Tang" field from Unihan data

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kwid
   ||getsaddons/6212418479aaf92a
   ||ef6a880137e942fff944a5f7
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christoph Feck  ---
Fixed in KF5 5.24, see
http://commits.kde.org/kwidgetsaddons/6212418479aaf92aef6a880137e942fff944a5f7

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

[digikam] [Bug 357617] Batch rename fails when using custom file extensions

[Larx via KDE Bugzilla]

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

--- Comment #11 from Larx  ---
I use openSUSE Tumbleweed (rolling release) and the problem has been present
for as long as I can remember, probably over quite a few digikam- and
exiv-versions. I just had time to file a bug a few months ago. 
That's very unspecific, I admit, I will try to create some kind of test case.

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

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

[Bob Wya via KDE Bugzilla]

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

--- Comment #40 from Bob Wya  ---
Martin,

I saw you'd made some commits to plasma/kwin to resolve the "ongoing" STRUT
issues in Plasma 5 - that got merged into Plasma 5.6.95. Updating my Gentoo
install from Plasma 5.6.5 to 5.6.95 resolved the panel issues for me. The panel
STRUT values are back to being positive integers again!

Great stuff. Thanks for your hardwork!!

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

[kcharselect] [Bug 364488] KCharSelect has (virtually) no Unicode support

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #5 from Christoph Feck  ---
Yes.

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

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

[kcharselect] [Bug 142625] Support 'astral' Unicode planes (those beyond codepoint FFFF)

[Christoph Feck via KDE Bugzilla]

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

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

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

[plasmashell] [Bug 360173] Plasma freeze sometime with notification & high load CPU and RAM

[Kott via KDE Bugzilla]

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

--- Comment #12 from Kott  ---
>>I also get every second the following error message in the journald log: 
plasma.engine.mpris2: Enabling stop action

Do you have plasmoid PlayBar2 installed?

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

[kopete] [Bug 140775] History plugin logs for each session (not month)

[Bonne Eggleston via KDE Bugzilla]

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

Bonne Eggleston  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from Bonne Eggleston  ---
I'm closing this since I don't use Kopete any more and the last comment from
anyone else was nearly 10 years ago.

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

[konqueror] [Bug 129015] remove whitespace from dom tree option

[Bonne Eggleston via KDE Bugzilla]

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

Bonne Eggleston  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Bonne Eggleston  ---
Closing this bug since I don't use Konqueror any more and noone else cares
about this anyway.

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

[kaffeine] [Bug 364517] Kaffeine can't tune in RTL (dvb-c / german television)

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #4 from Mauro Carvalho Chehab  ---
(In reply to boris64 from comment #3)
> Hi Mauro,
> 
> thank you for your help (and for moving forward on kaffeine (finally!)). 

Anytime.

> Do  you have a link for that patch / fix you are talking about? I'll report my
> issue tomorrow upstream ,)

I didn't identify the specific patchset that fixed it. I noticed one patchset
that says something about making MPEG-TS (or mpeg4?) more reliable and tried to
backport to 2.2.4. Didn't solve. 

So, either I picked up the wrong patch or it is a series of fixes that made the
difference. As I was busy with other things,  I opted to install vlc 3.0 from
the Fedora 24 UnitedRpm repository, and moved on.

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

[kaffeine] [Bug 364298] Regression Channels scan: channels are missing

[via KDE Bugzilla]

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

--- Comment #23 from lev.co...@gmail.com ---
Created attachment 99615
  --> https://bugs.kde.org/attachment.cgi?id=99615=edit
dvb-apps scan dvbv3_channels.conf

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

[kaffeine] [Bug 364298] Regression Channels scan: channels are missing

[via KDE Bugzilla]

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

--- Comment #22 from lev.co...@gmail.com ---
(In reply to Mauro Carvalho Chehab from comment #19)
> The MPEG-TS has two NIT tables and two SDT tables. By using dvbv5-scan with
> the "-p" option, it was able to get 52 transponders instead of 12. However,
> the second SDT tables contain programs that aren't actually there. Not sure
> if the channels at the other NIT tables are valid or not.
> 
> Could you please test scanning it with:
>$ dvbv5-scan -a0 -f1  ~/dtv-scan-tables/dvb-c/ch-Zuerich-upc-cablecom -p
> 
> PS.: there's a rationale for "-p" to not be the default: it takes a lot more
> time to scan. Also, there's a bug with dvb-utils causing it to not work. I
> just fixed it upstream:
> https://git.linuxtv.org/v4l-utils.git/log/

I did build v4l-utils from the commits 11c6e2c earlier and 9b8e58f now and with
neither version I manage to make a complete scan with "dvbv5-scan -p", it
always segfaults or stalls. Using the verbose command line parameter it crashes
even faster. There are also a lot of error messages of "channels not found on
PMT" shown and the channels are not stored with their "names" but in the
pattern "FREQUENCY#SERVICE_ID", which is somewhat cumbersome.

In comparison to "dvbv5-scan -p" the old "scan -n"  from
  https://linuxtv.org/hg/dvb-apps
manages to do this flawlessly, even the different "Network Names" 
(probably the different Network-IDs) are identified. I attached the 
resulting file "dvbv3_channels.conf" with the 533 services found.

By the way, with my TV set I have to enter the Network-ID (here 43016) for the
channels scan. Could this enhance or speed up the scanning process if the user
could define that and it would be incorporated in the scanning process?

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

[kaffeine] [Bug 364517] Kaffeine can't tune in RTL (dvb-c / german television)

[boris64 via KDE Bugzilla]

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

--- Comment #3 from boris64  ---
Hi Mauro,

thank you for your help (and for moving forward on kaffeine (finally!)). Do you
have a link for that patch / fix you are talking about? I'll report my issue
tomorrow upstream ,)

thank you in advance!

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

[Akonadi] [Bug 338571] Performance Regression: Folder synchronisation in Akonadi 15.12 (actually in any release, starting with 4.14) very slow, compared to kMail from KDE 4.13.x

[Martin Steigerwald via KDE Bugzilla]

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

--- Comment #17 from Martin Steigerwald  ---
I am running with 16.04 already, but it was already way faster with 15.12.

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

[Akonadi] [Bug 338571] Performance Regression: Folder synchronisation in Akonadi 15.12 (actually in any release, starting with 4.14) very slow, compared to kMail from KDE 4.13.x

[Martin Steigerwald via KDE Bugzilla]

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

--- Comment #16 from Martin Steigerwald  ---
Tore, two things:

1) AFAIK KMail 15.12 neeeds Akonadi 15.12 or at least any *other* Qt 5 based
Akonadi. Akonadi 1.13 to my knowledge is Qt 4 based. So I wonder why it works
at all on your system. It might be that in Fedora the Qt5 based Akonadi still
has a 1.13 version number, but I wouldn´t know why.

2) With Akonadi 15.12 there should be noticable performance improvements. Yet I
recommend testing with KMail + Akonadi 16.04.

I have a larger setup:

~/.local/share/akonadi> LANG=C du -sch * | sort -rh | head -4
6.9Gtotal
5.1Gdb_data
1.7Gsearch_db
117Mfile_db_data

yet, with Akonadi 15.12 I think a file leak with Akonadi´s file_db_data has
been fixed. You still seem to have it.

On any account: Akonadi 1.13 is too old. Please test more recent versions. They
old ones will not be fixed.

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

[Baloo] [Bug 364521] New: Baloo File Indexing Daemon crashes every time i log in to my user account

[Taskin via KDE Bugzilla]

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

Bug ID: 364521
   Summary: Baloo File Indexing Daemon crashes every time i log in
to my user account
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: taskin@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

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

-- Information about the crash:
-The Application crashes after startup evrytime though auto-sign in is enabled
-It also crashes when i log into the only user account after returning from
sleep mode

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7fafb1142bb4 in mdb_txn_begin () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x004212a3 in Baloo::FileContentIndexerProvider::size() ()
#8  0x0041aa49 in Baloo::FileIndexScheduler::scheduleIndexing() ()
#9  0x7fafb361be4f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fafb361be4f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x0043205c in KInotify::Private::_k_addWatches() ()
#12 0x004269b4 in Baloo::FileWatch::watchFolder(QString const&) ()
#13 0x00426a58 in Baloo::FileWatch::watchIndexedFolders() ()
#14 0x7fafb36285b8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fafb361ce53 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fafb35ed60c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fafb364289d in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fafb3642da1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7fafafbde127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7fafafbde380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fafafbde42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fafb3643a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fafb35eadea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fafb35f2e8c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x0041698c in main ()

Possible duplicates by query: bug 357106.

Reported using DrKonqi

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

[Baloo] [Bug 364520] New: Baloo daemon crashes after login

[Jan Binder via KDE Bugzilla]

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

Bug ID: 364520
   Summary: Baloo daemon crashes after login
   Product: Baloo
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: wh...@herr-der-mails.de
CC: pinak.ah...@gmail.com

Application: baloo_file (5.22.0)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
Debian unstable/experimental.

File indexing is activated and no special configration or exclusions were
configured.

The crash can be reproduced sometimes.

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

Thread 2 (Thread 0x7f8bf0375700 (LWP 2518)):
#0  0x7f8bf9b3862d in poll () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f8bf6cd839c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f8be8003220, timeout=, context=0x7f8be8000990) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f8bf6cd839c in g_main_context_iterate
(context=context@entry=0x7f8be8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f8bf6cd84ac in g_main_context_iteration (context=0x7f8be8000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f8bfa7571cb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8bfa6ffe4a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f8bfa5289e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f8bfbb0c515 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f8bfa52d808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f8bf91c0454 in start_thread () at
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f8bf9b4178d in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f8bf068e8c0 (LWP 2515)):
[KCrash Handler]
#6  0x7f8bf9a8d218 in raise () at /lib/x86_64-linux-gnu/libc.so.6
#7  0x7f8bf9a8e69a in abort () at /lib/x86_64-linux-gnu/libc.so.6
#8  0x7f8bf8246e72 in  () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x7f8bf823c4c5 in  () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x7f8bf823d683 in  () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#11 0x7f8bf823d8e9 in  () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#12 0x7f8bf823f544 in  () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#13 0x7f8bf8243697 in mdb_cursor_del () at
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#14 0x7f8bf8244c00 in  () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#15 0x7f8bfabf938e in Baloo::IdFilenameDB::del(unsigned long long) () at
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#16 0x7f8bfac0e421 in
Baloo::WriteTransaction::replaceDocument(Baloo::Document const&,
QFlags) () at
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#17 0x0041da75 in  ()
#18 0x0041e073 in  ()
#19 0x7f8bfa72ea74 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00420cf2 in  ()
#21 0x7f8bfa72ea74 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f8bfa7a9b1e in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f8bfa73ab4b in QSocketNotifier::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f8bfa7020eb in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f8bfa75766d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f8bf6cd81a7 in g_main_context_dispatch (context=0xe62e90) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3154
#27 0x7f8bf6cd81a7 in g_main_context_dispatch
(context=context@entry=0xe62e90) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3769
#28 0x7f8bf6cd8400 in g_main_context_iterate
(context=context@entry=0xe62e90, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3840
#29 0x7f8bf6cd84ac in g_main_context_iteration (context=0xe62e90,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#30 0x7f8bfa7571af in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f8bfa6ffe4a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7f8bfa70850c in 

[frameworks-kdoctools] [Bug 355393] l10n: make understandable the doc

[Luigi Toscano via KDE Bugzilla]

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

Luigi Toscano  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.24
 Resolution|--- |FIXED

--- Comment #9 from Luigi Toscano  ---
Sorry for the long delay. 
The two man pages have been updated to the real options available for Qt 5 and
(most of) Frameworks 5 applications, so the patch does not apply anymore.
Nevertheless, the issues highlighted (lack of missing dots at the end of
sentences and search for better titles for the man pages) have been addressed
in the last changes in the current master and which will be released as part of
the upcoming Frameworks 5.24.

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

[plasmashell] [Bug 364467] Task Tooltips disappears after closing one of many windows

[Thomas Pfeiffer via KDE Bugzilla]

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

--- Comment #5 from Thomas Pfeiffer  ---
Strange. I've just re-tried and the task manager still keeps it open.
Maybe you both are using 5.7 beta or master and it was changed with the new
task manager?

I don't know, but keeping it open definitely makes more sense.

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

[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

[via KDE Bugzilla]

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

--- Comment #18 from aux...@gmail.com ---
I used both pure 16.04.2 and the patch; neither fix this.

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

[kdenlive] [Bug 364105] git master - Freezing then crashing when adding video clip to Project Bin

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #8 from Jean-Baptiste Mardelle  ---
Git commit 6d517d66be2acac9db952e0bc673edc97d582322 by Jean-Baptiste Mardelle.
Committed on 19/06/2016 at 20:33.
Pushed by mardelle into branch 'master'.

Make sure to abort audio thumb jobs before changing profile

M  +2-1src/doc/kdenlivedoc.cpp

http://commits.kde.org/kdenlive/6d517d66be2acac9db952e0bc673edc97d582322

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

[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

[Fuchs via KDE Bugzilla]

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

--- Comment #3 from Fuchs  ---
(In reply to andreas from comment #2)
> Hi Fuchs,

Hi Andreas.

> In this bug I think it's not a bug, cause when you select an item (blue
> selection) the icon color change to the color of the text (white). This is
> new (and awesome).

Please re-read the bug report and attachment description. 
It is a bug, the icon that is lacking is on the _right_ side, in the list of
e-mails.

Thanks, kind regards, 

Christian

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

[Breeze] [Bug 364452] Regression: after updating frameworks and plasma kmail is missing the "task" icon

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

[andreas via KDE Bugzilla]

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

--- Comment #2 from andreas  ---
Hi Fuchs,

thanks for the bug report, cause I don't use kmail it's always good to get
feedback. 

In this bug I think it's not a bug, cause when you select an item (blue
selection) the icon color change to the color of the text (white). This is new
(and awesome).

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

[kaffeine] [Bug 364401] module "Digital TV" not working for DVB-S/S2

[via KDE Bugzilla]

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

--- Comment #8 from gonzo...@gmx.de ---
I can reconfirm that after compiling the latest git-version everything is
working well again.

Thanks for the fast response!

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

[plasmashell] [Bug 364467] Task Tooltips disappears after closing one of many windows

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #4 from Kai Uwe Broulik  ---
I just checked the code and both applets should behave the same, ie. close the
popup when one window is closed

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

[plasmashell] [Bug 364439] trying to switch to virtualdesktop by leftclick minimizes previewed apps unser Mousepointer instead of switching to desktop

[Christoph via KDE Bugzilla]

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

--- Comment #4 from Christoph  ---
(In reply to Eike Hein from comment #3)

Hello Elke,

thanks for taking care ;-) .. I  try to get this temporally working again by a
downgrade .. which package of your distro would be affected by this bug in your
opinion ? (may lead me to a trace regarding my distro)

thanks

-christoph-

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

[frameworks-networkmanager-qt] [Bug 362736] Compile vs. runtime symbols discrepancy

[Lamarque V . Souza via KDE Bugzilla]

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

Lamarque V. Souza  changed:

   What|Removed |Added

   Version Fixed In||5.24
  Latest Commit||http://commits.kde.org/netw
   ||orkmanager-qt/751f79ea7b054
   ||c2fa7d5c1e7d996b70198e2dcc9
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Lamarque V. Souza  ---
Git commit 751f79ea7b054c2fa7d5c1e7d996b70198e2dcc9 by Lamarque V. Souza, on
behalf of Palo Kisa.
Committed on 19/06/2016 at 20:03.
Pushed by lvsouza into branch 'master'.

Make network manager version checks in runtime (to avoid compile vs. run-time
discrepancies).
FIXED-IN: 5.24
REVIEW: 128093

M  +1-1CMakeLists.txt
M  +18   -35   src/CMakeLists.txt
M  +3-9src/accesspoint.cpp
M  +2-4src/accesspoint.h
M  +0-2src/accesspoint_p.h
M  +0-19   src/activeconnection.cpp
M  +0-4src/activeconnection.h
M  +0-2src/activeconnection_p.h
M  +5-10   src/connection.cpp
M  +1-8src/connection.h
M  +0-2src/connection_p.h
M  +12   -37   src/device.cpp
M  +13   -28   src/device.h
M  +0-6src/device_p.h
M  +116  -134  src/ipconfig.cpp
M  +2-6src/ipconfig.h
M  +40   -72   src/manager.cpp
M  +39   -30   src/manager.h
M  +6-10   src/manager_p.h
M  +4-32   src/settings.cpp
M  +0-4src/settings.h
M  +5-16   src/settings/bondsetting.cpp
M  +1-1src/settings/bondsetting.h
M  +2-16   src/settings/bridgesetting.cpp
M  +24   -73   src/settings/connectionsettings.cpp
M  +0-10   src/settings/connectionsettings.h
M  +0-6src/settings/connectionsettings_p.h
M  +6-29   src/settings/gsmsetting.cpp
M  +2-2src/settings/gsmsetting.h
M  +0-12   src/settings/infinibandsetting.cpp
M  +0-2src/settings/infinibandsetting.h
M  +0-2src/settings/infinibandsetting_p.h
M  +0-6src/settings/setting.cpp
M  +6-16   src/settings/teamsetting.cpp
M  +1-1src/settings/teamsetting.h
M  +9-2src/settings/tunsetting.cpp
M  +5-16   src/settings/vlansetting.cpp
M  +1-1src/settings/vlansetting.h
M  +5-16   src/settings/wirelesssetting.cpp
M  +1-0src/settings/wirelesssetting.h
M  +0-7src/settings_p.h
M  +9-9src/vlandevice.cpp
M  +2-4src/vlandevice.h
M  +0-2src/vlandevice_p.h
M  +0-14   src/wimaxdevice.cpp
M  +0-15   src/wirelessdevice.cpp
M  +1-2src/wirelessdevice.h

http://commits.kde.org/networkmanager-qt/751f79ea7b054c2fa7d5c1e7d996b70198e2dcc9

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

[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so

[Christian David via KDE Bugzilla]

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

--- Comment #8 from Christian David  ---
Hi,

in the log you linked I can see that kmm_payeeidentifier is compiled correctly:
"[ 16%] Built target kmm_payeeidentifier"

However, you build failed at a different point. So linking will not work.

CMakeFiles/mymoneyseqaccessmgrtest.dir/mymoneyseqaccessmgrtest.cpp.o: In
function `MyMoneySeqAccessMgrTest::testEmptyConstructor()':
/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/kmymoney/mymoney/storage/mymoneyseqaccessmgrtest.cpp:61:
undefined reference to `bool QTest::qCompare(unsigned int const&, unsigned long const&, char const*, char const*, char
const*, int)'
/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/kmymoney/mymoney/storage/mymoneyseqaccessmgrtest.cpp:62:
undefined reference to `bool QTest::qCompare(unsigned int const&, unsigned long const&, char const*, char const*, char
const*, int)'
/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/kmymoney/mymoney/storage/mymoneyseqaccessmgrtest.cpp:63:
undefined reference to `bool QTest::qCompare(unsigned int const&, unsigned long const&, char const*, char const*, char
const*, int)'
/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/kmymoney/mymoney/storage/mymoneyseqaccessmgrtest.cpp:64:
undefined reference to `bool QTest::qCompare(unsigned int const&, unsigned long const&, char const*, char const*, char
const*, int)'
/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/kmymoney/mymoney/storage/mymoneyseqaccessmgrtest.cpp:65:
undefined reference to `bool QTest::qCompare(unsigned int const&, unsigned long const&, char const*, char const*, char
const*, int)'
CMakeFiles/mymoneyseqaccessmgrtest.dir/mymoneyseqaccessmgrtest.cpp.o:/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/kmymoney/mymoney/storage/mymoneyseqaccessmgrtest.cpp:66:
more undefined references to `bool QTest::qCompare(unsigned int const&, unsigned long const&, char const*, char const*, char
const*, int)' follow
collect2: error: ld returned 1 exit status
kmymoney/mymoney/storage/CMakeFiles/mymoneyseqaccessmgrtest.dir/build.make:194:
recipe for target 'kmymoney/mymoney/storage/mymoneyseqaccessmgrtest' failed
make[2]: *** [kmymoney/mymoney/storage/mymoneyseqaccessmgrtest] Error 1
make[2]: Leaving directory '/home/iurt/rpmbuild/BUILD/kmymoney-4.8.0/build'
CMakeFiles/Makefile2:2838: recipe for target
'kmymoney/mymoney/storage/CMakeFiles/mymoneyseqaccessmgrtest.dir/all' failed
make[1]: ***
[kmymoney/mymoney/storage/CMakeFiles/mymoneyseqaccessmgrtest.dir/all] Error 2

Maybe this and the parallel build cause the linking error you have. I do not
think that your parallel build is the problem, btw.

I think the compiler errors you have were fixed in the 4.8 branch already. Also
you can disable the test, which you may want to do anyway. Setting the cmake
variable "BUILD_TESTING" to off should do this.

libkmm_payeeidentifier.so should be build and installed by KMyMoney. It works
on my system and KDE's CI (there are several tests which depend on
kmm_payeeidentifier).

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

[digikam] [Bug 364333] Random resets of several configuration values

[via KDE Bugzilla]

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

--- Comment #6 from caulier.gil...@gmail.com ---
because it work as expected. We cannot reproduce the problem.

Gilles Caulier

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

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost

[via KDE Bugzilla]

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

--- Comment #5 from caulier.gil...@gmail.com ---
>Digikam 5 (beta6), when started first, did not recognize my existing albums 
>and >collections from Digikam 4.14 (on Ubuntu Linux) and just showed me a 
>welcome and >setup screen. So I logically assumed there must be a migration 
>procedure.

No. The reason why the old collection is not recognized (and first run
assistant launched) is the location of  digikamrc file including all DK
configuration which have been moved from ~/.kde4/share/config to ~/.config
which is the standardized place under Linux. If you copy this file at this
place all will start as expected.

In all cases, the migration option is not the right way to process.

It's right than no rule to copy old digikamrc file from old place to new one is
not implemented.

But, starting with a new fresh DK setup and configure the collections and the
place where the database is stored will normally not touch the DB content and
all will be available as with 4.x release. 

Gilles Caulier

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

[neon] [Bug 364519] New: KDE neon gpg verification links to key via HTTP

[Peter Gerber via KDE Bugzilla]

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

Bug ID: 364519
   Summary: KDE neon gpg verification links to key via HTTP
   Product: neon
   Version: unspecified
  Platform: Neon Packages
   URL: https://neon.kde.org/download
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: pe...@arbitrary.ch
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

Verifying the GPG signature for the KDE neon live images, I noticed that the
link to Ubuntu's keyserver uses HTTP. I'd recommend using HTTPS instead.

Reproducible: Always

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

[kate] [Bug 338819] Kate does not auto-select the only modified file on disk

[Martin via KDE Bugzilla]

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

Martin  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Martin  ---
I think this is a very good solution: Kate is not intrusive and writing to
another file does not get interrupted. Otherwise, e.g. log files would be
really annoying. Can you add the version that contains the new behaviour?

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

[kdenlive] [Bug 360882] git master - dialog boxes are missing button icons and features on non-KDE desktops. (video example included)

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[digikam] [Bug 364333] Random resets of several configuration values

[Victor Engmark via KDE Bugzilla]

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

--- Comment #5 from Victor Engmark  ---
@gilles: Why was this marked "works for me"? Were you not able to reproduce it?

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

[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

[Craig via KDE Bugzilla]

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

--- Comment #17 from Craig  ---
Also can confirm 16.04.2 did not resolve/still an issue :( Thanks for the
commit Laurent, did that resolve the issue/just need to wait for it to hit in
.3 ? auxsvr did you mean you patched using the commit above and still not
working? 

Thanks Laurent for all your work over the years :) And thanks Eric for
helping/trying to figure it out, hopefully can get it figured soon

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

[plasmashell] [Bug 364518] New: Plasmashell takes up to 50% CPU

[Tom Kijas via KDE Bugzilla]

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

Bug ID: 364518
   Summary: Plasmashell takes up to 50% CPU
   Product: plasmashell
   Version: 5.6.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: t.ki...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Plasmashell takes up to 50% CPU
OS is slow

Reproducible: Didn't try


Actual Results:  
Plasmashell takes up to 50% CPU

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

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

[Bob Wya via KDE Bugzilla]

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

--- Comment #39 from Bob Wya  ---
Created attachment 99614
  --> https://bugs.kde.org/attachment.cgi?id=99614=edit
xprop (external HDMI monitor bottom panel)


LHS screen: HDMI external monitor
Correct panel functionality observed
Arch Linux with Qt 5.6.1

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

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

[Bob Wya via KDE Bugzilla]

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

--- Comment #38 from Bob Wya  ---
Created attachment 99613
  --> https://bugs.kde.org/attachment.cgi?id=99613=edit
xprop (laptop bottom panel)


RHS screen: Laptop bottom panel
Correct panel functionality observed
Arch Linux with Qt 5.6.1

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

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

[Bob Wya via KDE Bugzilla]

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

--- Comment #37 from Bob Wya  ---
So I'm booted into my Arch install - same machine - same 2 panels - same
monitor setup.
My Arch install is on Qt 5.6.1 / plasma 5.6.5.

The strut's for the panels are clearly being miscalculated when 2+ mismatched
screen size multi-monitor setups are used. Compare the following with the
Gentoo Qt 5.7.0 results (see above).

Screen 0: minimum 8 x 8, current 4480 x 1588, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 1920x1080+2560+508 (normal left inverted right x axis y
axis) 382mm x 215mm
   1920x1080 60.02*+
HDMI-0 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm
x 336mm
   2560x1440 59.95*+
   1920x1200 59.9559.88  
   1920x1080 60.0059.9450.0029.9760.0560.0050.04  
   1680x1050 59.95  
   1600x1200 60.00  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0059.9459.93

With Qt 5.6.1 (LHS):
_NET_WM_STRUT(CARDINAL) = 0, 0, 0, 190
_NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 190, 0, 0, 0, 0, 0, 0, 0, 2559

With Qt 5.6.1 (RHS):
_NET_WM_STRUT(CARDINAL) = 0, 0, 0, 44
_NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 44, 0, 0, 0, 0, 0, 0, 2560, 4479

So the RHS base is -148 of the LHS screen (1440-508-1080).
Top strut is 190 on LHS panel (higher) = 42 pixel panel height = correct!!
Top strut is 44 on RHS panel (lower) = 44 pixel panel height = correct!!

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

[kaffeine] [Bug 364517] Kaffeine can't tune in RTL (dvb-c / german television)

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Mauro Carvalho Chehab  ---
Maybe you could open a bug also for VLC, asking them to fix it on the stable
branch, and providing them more info and maybe a sample record. 

https://trac.videolan.org/vlc/query?group=status=2.2.x+maintenance+branch

FYI, even if Kaffeine/libVLC is unable to play, you can still record the show
by scheduling a record.

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

[kaffeine] [Bug 364517] Kaffeine can't tune in RTL (dvb-c / german television)

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #1 from Mauro Carvalho Chehab  ---
Hmm...

[7fc468145878] core decoder error: Could not convert timestamp 0

I noticed the same issue while watching to ISDB-T channels, with are also
encoded with MPEG-4. This is an issue with VLC 2.2.x. This was fixed on VLC 3.0
(development versions), but, at least until 2.2.4, the fix was not backported
yet.

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

[print-manager] [Bug 362143] Show notification if a document is sent to offline printer

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost

[Jens B . Benecke via KDE Bugzilla]

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

--- Comment #4 from Jens B. Benecke  ---
Let me explain.

Digikam 5 (beta6), when started first, did not recognize my existing albums and
collections from Digikam 4.14 (on Ubuntu Linux) and just showed me a welcome
and setup screen. So I logically assumed there must be a migration procedure.
(This I would consider a bug - if there are previous existing collections, a
new version of Digikam should just open them or offer to import them.)

I found the migration option and selected my digikam4.db (the target was
already preselected) and started the migration. This destroyed the digikam4.db
tables as described below so subsequent starts of Digikam 4.14 wouldn't show
tags etc. any more.
Starting the migration might have been my mistake but a user friendly
application should prevent users from doing something stupid (like starting a
migration when it isn't required or possible) so I consider this a bug too.

The solution is simple: upon start, just load the digikam4 config (if
available) and - if required - copy it to a digikam5 config. And when a user
starts the Migration task from the maintenance menu and selects database files
or formats which cannot be migrated, show an appropriate error message and
refuse the migration.

Do you agree?

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

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

--- Comment #54 from Michael Butash  ---
Interestingly enough I installed kde-backports and dist-upgraded to pull down
plasma 5.6.5, but that kept qt at 5.5.1.  I gave it a stress test flipping my
3x displays on and off in various orders, and it's behaving a far sight better
than it had, and hasn't crashed.  

The only anomalies now so far currently is it still doesn't put the displays
back in the right places and offsets, which results in me having to move them
about to realign after the third on/off and it doesn't always move the kde
panel to the primary display, sometimes even flickering back and forth.

I'm going to see if I can find where to get libqt5 in 5.6.1 or higher too, but
this seems to indicate it isn't entirely a Qt problem.

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

[kaffeine] [Bug 364401] module "Digital TV" not working for DVB-S/S2

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #7 from Mauro Carvalho Chehab  ---
(In reply to m.felix from comment #6)
> It works!

Great!

> Thanks for the quick fix.

Anytime.

> P.S. To record something with dvbv5-zap, I have to add the output and 
> satelite number.
> dvbv5-zap -r -P -t 30 --lnbf=universal -c /tmp/dvb-s/Astra-19.2E 12551500 -S 
> 1 -v -o dvbs_record.ts

Ah, yeah, that's needed in order to setup the DiSEqC switch.

As the bug is fixed, I'm closing it. If you notice some other problem, please
open a new bug.

Fixed on:  
http://commits.kde.org/kaffeine/4e857581ad963117fe8e55f1f6426f6f7fd31a3d

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

[kaffeine] [Bug 364517] New: Kaffeine can't tune in RTL (dvb-c / german television)

[boris64 via KDE Bugzilla]

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

Bug ID: 364517
   Summary: Kaffeine can't tune in RTL (dvb-c / german television)
   Product: kaffeine
   Version: 2.0.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: bugs@boris64.net

Since kaffeine 1.3 (directly _after_ the switch from xine-lib to libvlc) the
german dvb-c channel "RTL" isn't tuneable anymore. i  sometimes can see the
first frame of the stream, but normally the image stays black. There ist no
sound, but EPG/OSD seems to work.
I did run a channel search several times and re-added RTL, but without any
progress.
Btw., watching this channel via smplayer works fine.

Additional used software:
-Arch Linx (including packages from *-testing)
-mesa-11.2.2-1
-mesa-vdpau-11.2.2-1
-xf86-video-ati-7.7.0-1
-vlc-2.2.4-1
-kaffeine-2.x (daily recompiled git-version)

Please tell me what you need from me to have a look into this issue. Thank you!

Reproducible: Always

Steps to Reproduce:
1. start kaffeine
2. start watching dvb-c
3. tune to RTL in sender list

Actual Results:  
RTL can't be watched.

Expected Results:  
Well, RTL sucks, but sometimes you need to watch to awkward/stupid tc shows
like "Bauer sucht Frau".
So... expected result: watch RTL in Kaffeine

[Console Output while tuning in RTL]
...
kmix(1736) Mixer_PULSE::updateRecommendedMaster: Selecting master 
"restore:sink-input-by-media-role:event"  for type  2
kmix(1736) Mixer::getGlobalMasterMD: Mixer::masterCardDevice() returns 0 (no
globalMaster), returning the first device
kmix(1736) Mixer::getGlobalMasterMD: Mixer::masterCardDevice() returns 0 (no
globalMaster), returning the first device
kmix(1736) Mixer::getGlobalMasterMD: Mixer::masterCardDevice() returns 0 (no
globalMaster), returning the first device
kmix(1736) Mixer_PULSE::pulseControlsReconfigured: Reconfigure 
"PulseAudio::Playback_Streams:1"
[7fc468145878] avcodec decoder: Using G3DVL VDPAU Driver Shared Library
version 1.0 for hardware decoding.
[7fc468145878] core decoder error: Could not convert timestamp 0
[7fc438025438] vdpau_display vout display error: presentation queue display
failure: An invalid handle value was provided. Either the handle does not exist
at all, or refers to an object of an incorrect type.
[7fc438025438] vdpau_display vout display error: presentation queue display
failure: An invalid handle value was provided. Either the handle does not exist
at all, or refers to an object of an incorrect type.
...
[/Console Output while tuning in RTL]

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

[kdenlive] [Bug 364510] 16.04 - git - Position and Zoom "Original Size" icon not working

[Evert Vorster via KDE Bugzilla]

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

--- Comment #4 from Evert Vorster  ---
Thanks, JBM. 

I'm currently using the Applications 16.04 branch in git, will test once I have
finished the project I am playing with.

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

[kdenlive] [Bug 364510] 16.04 - git - Position and Zoom "Original Size" icon not working

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
Git commit 8a050baaabc0522701304d34c93b948fccaeb70d by Jean-Baptiste Mardelle.
Committed on 19/06/2016 at 18:13.
Pushed by mardelle into branch 'master'.

Add "Fit to original" and "Adjust and center in frame " in resize options

M  +1-0src/effectstack/parametercontainer.cpp
M  +45   -5src/effectstack/widgets/geometrywidget.cpp
M  +3-0src/effectstack/widgets/geometrywidget.h

http://commits.kde.org/kdenlive/8a050baaabc0522701304d34c93b948fccaeb70d

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

[digikam] [Bug 357617] Batch rename fails when using custom file extensions

[via KDE Bugzilla]

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

--- Comment #10 from caulier.gil...@gmail.com ---
Not reproducible here too.

Did you use Mysql database ?

Which Exiv2 library did you use exactly ?

Look in Help/Components Info dialog for details

Gilles Caulier

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

[klipper] [Bug 364516] New: klipper chain mode

[Alexander Zaitsev via KDE Bugzilla]

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

Bug ID: 364516
   Summary: klipper chain mode
   Product: klipper
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: shu...@yandex.ru

there will be good enough to have chain mode in klipper.
Say we have to copy 10 entries from one place to other. We copy source lines
one by one, selecting and copying its.
Item1 - select, copy
item2 - select, copy,
...
item X - select, copy.

Then, we just paste the content by pressing Ctrl+V, and Klipper paste item1 on
first press Ctrl+V, then Item2, Item3, ItemX.
Every Ctrl+C starts new chain, so if you need to copy only element, you will
not see the changes it will copy and paste the element.

It will allow to simplify operations in Excel or similar programs.

Reproducible: Always

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

[digikam] [Bug 363998] DigiKam sees Nikon D700 but cannot import files

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Nikon and PTP want mean Gphoto2 driver is user to communicate with the camera.

Gilles Caulier

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

[plasmashell] [Bug 364515] New: Network Monitor panel on desktop missing update interval in menu

[via KDE Bugzilla]

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

Bug ID: 364515
   Summary: Network Monitor panel on desktop missing update
interval in menu
   Product: plasmashell
   Version: 5.6.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: slartibar...@gmail.com

When placing the network monitor on the desktop, you are free to setup the
update interval using the panels controls or by using the 'network monitor
settings' popup menu.
But, when it is placed there for a longer time (didn't check if just a logout
is sufficient), the 'update interval' input field is gone. Just a radio button
for selecting/deselecting the interface is left over.

Reproducible: Always

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

[digikam] [Bug 364206] Crash when moving images outside Digikam

[via KDE Bugzilla]

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

--- Comment #3 from caulier.gil...@gmail.com ---
Here i tried to reproduce the problem, and i cannot.

How many items are stored in albums moved with Dolphin.

Gilles Caulier

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

[digikam] [Bug 364206] Crash when moving images outside Digikam

[via KDE Bugzilla]

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

--- Comment #2 from caulier.gil...@gmail.com ---
DK has of course a mechanism to follow changes in disk processed by another
application.

Class is AlbumWatch based on QFileSystemWatcher API.

Gilles Caulier

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

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost

[via KDE Bugzilla]

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

--- Comment #3 from caulier.gil...@gmail.com ---
Why do you talk about "migration" to import DK sqlite database from version 4
to 5 ?

As i said before, it'z the same file !

There is nothing to migrate. Just configure DK 5 as DK 4. that all...

Migration tool is to switch from one DB type to another and different one. Not
to the same DB type from original to target.

Gilles Caulier

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

[parley] [Bug 364373] parley crashed when I changed from practice to the editor

[Jörg Lorenz via KDE Bugzilla]

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

--- Comment #6 from Jörg Lorenz  ---
Am 18.06.2016 um 18:24 schrieb Alexander Potashev via KDE Bugzilla:
> https://bugs.kde.org/show_bug.cgi?id=364373
>
> Alexander Potashev  changed:
>
> What|Removed |Added
> 
>   Status|CONFIRMED   |RESOLVED
>Latest Commit||http://commits.kde.org/parl
> ||ey/45c5fb4fd3c6635fe9ae8b37
> ||b367eb8bb22125ac
>   Resolution|--- |FIXED
>
> --- Comment #5 from Alexander Potashev  ---
> Git commit 45c5fb4fd3c6635fe9ae8b37b367eb8bb22125ac by Alexander Potashev.
> Committed on 18/06/2016 at 16:26.
> Pushed by aspotashev into branch 'Applications/16.04'.
>
> Remove the google_images.py script: Google image search API is not available
> anymore
> REVIEW: 128229
>
> M  +0-7plugins/CMakeLists.txt
> D  +0-94   plugins/google_images.desktop
> D  +0-257  plugins/google_images.py
> D  +0-141  plugins/google_images.ui
>
> http://commits.kde.org/parley/45c5fb4fd3c6635fe9ae8b37b367eb8bb22125ac
>
Hi Alexander Potashev,
I removed following files from usr/share/parley/plugins:

plugins/google_images.desktop
plugins/google_images.py
plugins/google_images.ui

Now I don't have a crash when I change from practice to editor. Now 
parley is running. But no scripts are available. Neither 
google-dictionary nor leo-dictionary nor parley-example nor 
wiktionary-sounds. But now I can work with it at least. Cheers Jörg

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

[digikam] [Bug 364333] Random resets of several configuration values

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
 Resolution|INVALID |WORKSFORME

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

[dolphin] [Bug 364514] New: Dolphin always uses small icons

[via KDE Bugzilla]

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

Bug ID: 364514
   Summary: Dolphin always uses small icons
   Product: dolphin
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: icons mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: valentin.pet...@aon.at

The new dolphin does (independent of the actual size) in icon mode only use the
16x16 or 22x22 icons, don’t know which one it is, while it should be 32x32 or
64x64. This is especially weird in case of directories, for the generic icon
for inode/directory is completely different to the special folder icons.

Reproducible: Always




Using dolphin 16.04.1

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

[digikam] [Bug 364333] Random resets of several configuration values

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 364513] New: Secondary monitor is black and right mouse button does not work

[Fabio Coatti via KDE Bugzilla]

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

Bug ID: 364513
   Summary: Secondary monitor is black and right mouse button does
not work
   Product: plasmashell
   Version: 5.6.5
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: fabio.coa...@gmail.com
CC: plasma-b...@kde.org

I'm using a laptop alternating two-monitors setup to single monitor arrangement
when moving. 
Description of issue:
starting from a working one-screen setup, I turn off the laptop
then I connect the external monitor and turn on the laptop
The result is that the applets are on the laptop screen and the same screen is
ok and it shows the wallpaper. External monitor is another story: no wallpaper
(black background), no panels and right mouse button does not shows any context
menu.
I can , however, drag windows on external monitor with no problems.
If I disconnect the external monitor and then plug-in it again, the change is
noticed by plasma, wallpaper appears on the external monitor and right mouse
button works again. I can also drag panels to the external monitor.
If I then turn off the laptop, without disconnecting the external monitor, I'm
back to square one: turning laptop on I get again no wallpaper and other
functionalities on external monitor, as described at first step above.


Reproducible: Always




plasma 5.6.5 (plasma-workspace-5.6.5.1)
kde-frameworks 5.23.0
kde-apps 16.04.2
Gentoo packages

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

[kdenlive] [Bug 364510] 16.04 - git - Position and Zoom "Original Size" icon not working

[Evert Vorster via KDE Bugzilla]

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

--- Comment #2 from Evert Vorster  ---
We actually need both fit to profile and zoom to original resolution buttons,
then all confusion will go away. :)

I remember using that button that is there to zoom in to original resolution
when working with footage that is larger than the project.

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

[kdenlive] [Bug 364462] git master: off by frame when adding clip zones ending on final clip frame to the project bin

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 93a7dc89241026a9788a7ed0838c80cff5fcad91 by Jean-Baptiste Mardelle.
Committed on 19/06/2016 at 16:48.
Pushed by mardelle into branch 'master'.

Fix one frame offset in clip monitor selection

M  +3-11   src/monitor/monitor.cpp
M  +1-2src/renderer.cpp
M  +2-2src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/93a7dc89241026a9788a7ed0838c80cff5fcad91

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

[kaffeine] [Bug 364401] module "Digital TV" not working for DVB-S/S2

[via KDE Bugzilla]

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

--- Comment #6 from m.fe...@gmx.de ---
It works!
I recompiled kaffeine again, with your latest patch. The error message is gone.
And after I exchanded the LNB satelites and restored my old channel list
(sqlite.db), it works again.
Zapping the channels works well.

Thanks for the quick fix.

P.S. To record something with dvbv5-zap, I have to add the output and satelite
number.
dvbv5-zap -r -P -t 30 --lnbf=universal -c /tmp/dvb-s/Astra-19.2E 12551500 -S 1
-v -o dvbs_record.ts

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

[kdenlive] [Bug 364082] Crash on start when no binary nvidia driver is available

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from Wegwerf  ---
Yueqi, after installing: is the problem still present? Or does Kdenlive start
correctly? If yes, then this is a distro packager problem. It may be that your
distro packagers didn't package the required OpenGL drivers when you don't
install the binary drivers. This looks much like a problem the Kdenlive project
can't help you with.

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

[kdenlive] [Bug 363199] Pan and Zoom / Position and Zoom problem (possibly other effects too) on rescaling clip in timeline, even in newest version 16.04.1

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from Wegwerf  ---
Noticed that too, and it seems to affect static clips, such as titles and
images. However, if I remember correctly, the bug doesn't manifest for video
clips.

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

[kdenlive] [Bug 364510] 16.04 - git - Position and Zoom "Original Size" icon not working

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Evert, I think you are correctly assuming that the "original size" button
should set 200% for UHD on FullHD. However, I'm not exactly sure now whether
the button shows the zoom-to-fit icon? If yes, then the hint doesn't match the
button and function. If not, then button function doesn't match the hint. Oh
well...

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

[plasmashell] [Bug 360173] Plasma freeze sometime with notification & high load CPU and RAM

[miku84 via KDE Bugzilla]

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

miku84  changed:

   What|Removed |Added

 CC||mik...@gmail.com

--- Comment #11 from miku84  ---
I also get every second the following error message in the journald log:
plasma.engine.mpris2: Enabling stop action

I think something is broken here.

Plasma 5.6.5 KF5.23 Manjaro

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

[plasmashell] [Bug 364512] New: Switching from 3 monitors to 2 monitors causes main panel to disappear

[via KDE Bugzilla]

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

Bug ID: 364512
   Summary: Switching from 3 monitors to 2 monitors causes main
panel to disappear
   Product: plasmashell
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: mishuga...@gmail.com

I have a 3 monitor setup (LTR: HDMI, DVI, DVI) most of the time. My main panel
is located on the rightmost monitor on the right side of the screen.

When I use my HDMI switcher, my HDMI monitor (the leftmost) is removed as far
as my main computer is concerned, so it enters a 2 monitor state. In this 2
monitor state, the main panel is completely missing. When I switch back to the
3 monitor state, the main panel is now on my middle monitor, and my right
monitor is completely black (no desktop image, can't right click the desktop).
The only way I've found to get the right monitor back to the way it should be
is by killing plasmashell and restarting.

Reproducible: Always

Steps to Reproduce:
1. Have 3 monitor setup.
2. Unplug left monitor
3. Unexpected monitor layout
4. Replug left monitor

Actual Results:  
The activity bar is missing during step 3 completely.

Expected Results:  
The activity bar should remain on my rightmost monitor throughout all the steps

After the switch, my leftmost desktop (wallpaper and icons) is now on my
rightmost monitor, although the windows in the previously center desktop are on
my rightmost monitor. And all the windows from the leftmost monitor move to the
now leftmost (previously center) monitor. But, the center monitor retains the
same background.

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

[plasmashell] [Bug 364467] Task Tooltips disappears after closing one of many windows

[kthiele via KDE Bugzilla]

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

--- Comment #3 from kthiele  ---
For me it doesn't work in either the regular nor icon- only task manager

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

[kaffeine] [Bug 364401] module "Digital TV" not working for DVB-S/S2

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #5 from Mauro Carvalho Chehab  ---
(In reply to Mauro Carvalho Chehab from comment #4)
> (In reply to m.felix from comment #3)

> > 19-06-16 10:26:37.175 [Critical] FE_SET_PROPERTY: Das Argument ist ungültig
> > 19-06-16 10:26:37.175 [Warning ] ioctl FE_SET_PROPERTY failed for frontend
> > /dev/dvb/adapter0/frontend0

I guess I found the culprit for this issue. Basically, libdvbv5 supports an
special antenna arrangement for SCR/Unicable. I didn't add the needed bits to
Kaffeine yet, but it was already passing an extra parameter to the library. It
happens that such parameter were not initialized properly, causing the library
to try to tune into an out of range frequency:

19-06-16 13:04:26.812 [Debug   ] src/dvb/dvbdevice_linux.cpp#84: void
dvbv5_log(int, const char*, ...): BPF: 101 KHz
19-06-16 13:04:26.951 [Debug   ] src/dvb/dvbdevice_linux.cpp#84: void
dvbv5_log(int, const char*, ...): L-Band frequency: 10700,50 MHz (offset =
23252,00 MHz)

(those logs are with a newer libdvbv5 patch I merged today)

Anyway, I was able to produce a Kaffeine fix, and to test it with a DVB-S board
and my RF generator, using a setup that would be the one with an universal
LNBf. As I said, I can't simulate the LNBf here, so I'd appreciate if you could
test. Also, I ended by using a DVB-C  MPEG-TS, as I'm currently lacking a DVB-S
(and DVB-S2) mpeg TS samples.

The patch is at:
http://commits.kde.org/kaffeine/4e857581ad963117fe8e55f1f6426f6f7fd31a3d

Please test and provide feedback. Thanks!

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

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

[Yi Yang via KDE Bugzilla]

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

--- Comment #13 from Yi Yang  ---
Hi all,

I upgraded to Plasma 5.6 today. It seems to be handling hi-res screens in a new
way (by handling font DPI better it seems), so that the "scale display" option
is no longer needed in most common cases. Therefore, even if the Okular bug
still exists, its severity becomes even lower.

I'm not sure if this means this bug should be closed. I leave that to your
decision. But I think it's my duty to report on the progress. Thank you for all
your hard work, people ;)

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

[kmymoney4] [Bug 364487] I wish I could hide accounts / categories in reports AND roll up there amount in parent

[Jack via KDE Bugzilla]

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

--- Comment #1 from Jack  ---
By "hiding" do you actually mean not including them by unchecking them on the
configuration page?  As you realize, that is not hiding them, it is not
including them at all.  I think one way to describe what you want is to have
separate "include" and "display" checks for each account/category/...

Have you tried exporting the report to excel?  It would still be work, but not
require manually redoing the sums.

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

[kmail2] [Bug 362896] Account freezes for several weeks when processing lots of emails

[krystalcode via KDE Bugzilla]

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

--- Comment #1 from krystalcode  ---
Additional information:

After setting a few thousand of emails to expire by date, the whole folder
(Inbox) stopped displaying emails and it was empty and unusable for a month or
so. It was also blocking other operations - I added another account and emails
were not downloaded. Other existing accounts were working.

I'm on a quite slow internet connection. At some point I monitored network
traffic and I noticed "akonadi_imap_resource" was downloading a huge amount of
data from the IMAP server. I left it all night long, it downloaded about 1.5GB
and still going.

Another day I happened to be in a hotel with a decent internet connection. I
monitored the network traffic again, it downloaded about 2GB of data within an
hour or so, and it finished - all my email was displayed again.

Points of interest:

- Why did Kmail (or akonadi) needed to download so much data? All the email
were locally available via the offline use setting, it shouldn't have to
download anything, only move them to another folder and delete them from the
server.

- Even if it has to download the emails again, the amount of data (2GB+)
indicates it was downloading all emails again, not just the ones requested to
be moved. That requested emails would be much less.

- It seems like it had to do all operations at one go, otherwise it would start
from scratch next time. This was going on for a month, maybe more, there was
certainly plenty of time to download everything even with a slow connection.
There were probably dozens of GBs of data downloaded over this time with this
behaviour. Still, it only worked when it was able to download 2GB+ in one go,
otherwise the Inbox was empty and unusable.

When expiring smaller amounts of emails e.g. 100 days, everything works ok.

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

[dolphin] [Bug 364511] New: Changing an icon for a file or folder does not function.

[kevin via KDE Bugzilla]

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

Bug ID: 364511
   Summary: Changing an icon for a file or folder does not
function.
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kevinlekil...@gmail.com

First, I'm sorry if this is a duplicate, I've searched and could not find this
exact issue.


Issue:

When trying to change an icon for a file or folder through the properties menu
in Dolphin, the icon does not change.


Solution:

The problem is because one or all of these files/folders are not created
automatically by Dolphin (Dolphin will append errors to ~/.xsessions-errors if
these files/folders do not exist):

~/.local/share/applications/
~/.local/share/applications/mimeapps.list
~/.config/mimeapps.list
~/.local/share/mime/
~/.local/share/mime/packages/

Manually creating all these files/folders fixes the issue.

Reproducible: Always

Steps to Reproduce:
1. Open Dolphin.
2. Right click on a folder.
3. Click Properties.
4. Click the icon under General.
5. Select an icon.
6. Click OK.

Actual Results:  
The original icon is still in use.

Expected Results:  
The new icon should be used.

This issue affects every distributions I've tested: Arch Linux, OpenSuse
Tumbleweed, Manjaro, KDE Neon.

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

[konsole] [Bug 360010] Crash after running a script that runs konsole -e

[via KDE Bugzilla]

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

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

konsole (15.12.3) using Qt 5.5.1

- What I was doing when the application crashed:
Another crash, same situation for me. Again, wasn't running a separate script
or anything, just had a few tabs idling with active SSH sessions. Just crashed
while I was doing something else on my desktop (not in the terminal).

-- Backtrace (Reduced):
#6  poll_for_reply (c=c@entry=0x176c430, request=request@entry=97016,
reply=reply@entry=0x7ffe8d7ca678, error=error@entry=0x7ffe8d7ca768) at
xcb_in.c:428
#7  0x7f3b0f30dd74 in wait_for_reply (c=c@entry=0x176c430,
request=request@entry=97016, e=e@entry=0x7ffe8d7ca768) at xcb_in.c:515
#8  0x7f3b0f30ded2 in xcb_wait_for_reply64 (c=c@entry=0x176c430,
request=97016, e=e@entry=0x7ffe8d7ca768) at xcb_in.c:560
#9  0x7f3b10ce91f0 in _XReply (dpy=dpy@entry=0x176b1e0,
rep=rep@entry=0x7ffe8d7ca7e0, extra=extra@entry=0, discard=discard@entry=0) at
xcb_io.c:596
#10 0x7f3b03e4b0e2 in XIQueryDevice (dpy=0x176b1e0, deviceid=11,
ndevices_return=0x7ffe8d7ca85c) at XIQueryDevice.c:60

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

[frameworks-baloo] [Bug 364475] baloo_file_extractor crashes whenever the index exceeds 5G in size

[Hao Zhang via KDE Bugzilla]

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

--- Comment #4 from Hao Zhang  ---
The relevant code is in line 97 of the file src/engine/database.cpp

mdb_env_set_mapsize(m_env, static_cast(1024) * 1024 * 1024 * 5); // 5
gb

The size of the database is HARDCODED to be 5gb!! Is there any specific reason
this size cannot be larger? 5gb is far from enough if there are lots of files
to index.

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