[kwin] [Bug 366393] Crashes

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
As a workaround use the breeze window decoration

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

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||alexandre.nu...@gmail.com

--- Comment #28 from Martin Gräßlin  ---
*** Bug 366393 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 366385] reproducible crash of kwin/plasma in Kubuntu 16.04.1

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
If you are able to reproduce please provide the backtrace from drkonqi.

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

[digikam] [Bug 329091] MySQL : Maintenance leads to crash digiKam

[via KDE Bugzilla]

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

--- Comment #20 from uwe.hai...@gmx.net ---
I have finished  testing the maintenance modules:

- searching duplicates ok
- rebuild fingerprints ok
- searching new items ok
- thumbnails ok
- quality sort ok (but very slow - 2 days?)
- synchronizing metadata (both directions) leads to segementation vault & crash

Sorry, I can't see any error message for the segementation vault in the shell
(zsh). How can I get the informations you need?

uhai

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

[QtCurve] [Bug 363703] Popup Menu shadows not configurable

[Kott via KDE Bugzilla]

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

Kott  changed:

   What|Removed |Added

 CC||k...@kott.no-ip.biz

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

[akregator] [Bug 359191] aKregator does not honor LC_TIME / date and time in wrong format

[Geoff M via KDE Bugzilla]

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

Geoff M  changed:

   What|Removed |Added

 CC||geo...@gmx.com

--- Comment #5 from Geoff M  ---
Akregator displays dates as DD/MM/YY hh:mm AM/PM
it's supposed to display time in EN_CA format - -MM-DD hh:mm AM/PM as
configured in my time format.
Don't know why this is still unconfirmed?

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

[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel

[Pulfer via KDE Bugzilla]

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

--- Comment #4 from Pulfer  ---
(In reply to David Edmundson from comment #3)
> Do you have any custom plasmoids in the default Rosa panel?

There's only one custom plasmoid there:
https://git.reviewboard.kde.org/r/127651/

Here's our layout.js:
https://abf.rosalinux.ru/import/plasma5-config-fresh/blob/rosa2014.1/default-panel-layout.js

> This is caused by some plasmoid having some looping code. 

Looks like it's caused by system tray plasmoid. Without it adding second panel
works fine.

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

[katomic] [Bug 366396] New: KAtomic crashes upon Shift-Tab key combo

[via KDE Bugzilla]

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

Bug ID: 366396
   Summary: KAtomic crashes upon Shift-Tab key combo
   Product: katomic
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dim...@gmail.com
  Reporter: rnd...@gmail.com
CC: kde-games-b...@kde.org

Application: katomic (4.0)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.7.0-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

Pressing Shift-Tab while playing the game causes it to crash immediately. The
expected behavior is for it to cycle through the moveable atoms in reverse
order to how Tab cycles through them.

The crash can be reproduced every time.

-- Backtrace:
Application: KAtomic (katomic), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f58c3cd1800 (LWP 29165))]

Thread 3 (Thread 0x7f58b97b4700 (LWP 29167)):
#0  0x7ffd38f689ed in clock_gettime ()
#1  0x7f58d0f605cb in __GI___clock_gettime (clock_id=1, tp=0x7f58b97b3ac0)
at ../sysdeps/unix/clock_gettime.c:99
#2  0x7f58d173c793 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x7f58d188c079 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7f58d188c475 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f58d188d60c in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x7f58d188d6dd in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f58cbb126eb in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#8  0x7f58cbb1303b in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7f58cbb13234 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f58d188dadb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#11 0x7f58d183d542 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#12 0x7f58d169ab8e in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#13 0x7f58d3ee65d5 in ?? () from /usr/lib64/libQt5DBus.so.5
#14 0x7f58d169f21f in ?? () from /usr/lib64/libQt5Core.so.5
#15 0x7f58cd5b23b6 in start_thread (arg=0x7f58b97b4700) at
pthread_create.c:333
#16 0x7f58d0f538ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f58c14ca700 (LWP 29166)):
#0  0x7f58d0f4a79d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f58ca4808fa in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f58ca482897 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f58c3a2d109 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f58d169f21f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f58cd5b23b6 in start_thread (arg=0x7f58c14ca700) at
pthread_create.c:333
#6  0x7f58d0f538ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f58c3cd1800 (LWP 29165)):
[KCrash Handler]
#6  0x004198c8 in PlayField::previousAtom (this=0x18d2690) at
/var/tmp/portage/kde-apps/katomic-16.04.3/work/katomic-16.04.3/playfield.cpp:262
#7  0x7f58d18664d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#8  0x7f58d233dae2 in QAction::triggered(bool) () from
/usr/lib64/libQt5Widgets.so.5
#9  0x7f58d23407e8 in QAction::activate(QAction::ActionEvent) () from
/usr/lib64/libQt5Widgets.so.5
#10 0x7f58d234119f in QAction::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#11 0x7f58d2347344 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#12 0x7f58d234c8e7 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#13 0x7f58d183e701 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#14 0x7f58d1e28829 in QShortcutMap::dispatchEvent(QKeyEvent*) () from
/usr/lib64/libQt5Gui.so.5
#15 0x7f58d1e288e7 in QShortcutMap::tryShortcut(QKeyEvent*) () from
/usr/lib64/libQt5Gui.so.5
#16 0x7f58d1de391c in QWindowSystemInterface::handleShortcutEvent(QWindow*,
unsigned long, int, QFlags, unsigned int, unsigned int,
unsigned int, QString const&, bool, unsigned short) () from
/usr/lib64/libQt5Gui.so.5
#17 0x7f58d1dfa2af in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() from /usr/lib64/libQt5Gui.so.5
#18 0x7f58d1dff685 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib64/libQt5Gui.so.5
#19 0x7f58d1ddfd12 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib64/libQt5Gui.so.5
#20 0x7f58c3a63ad0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5

[plasmashell] [Bug 366395] panel size doesn't adjust to screen changes correctly

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Keywords||multiscreen
   Assignee|aleix...@kde.org|notm...@gmail.com

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

[plasmashell] [Bug 366395] New: panel size doesn't adjust to screen changes correctly

[Sebastian Kügler via KDE Bugzilla]

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

Bug ID: 366395
   Summary: panel size doesn't adjust to screen changes correctly
   Product: plasmashell
   Version: master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: se...@kde.org
CC: plasma-b...@kde.org

Situation: I have my panel on the larger laptop panel, there's a lower res
external monitor.

When I switch the primary to be the external monitor, the panel moves over to
it, but it remains at the size of its original location, so it gets cut off.

I'd expect the panel to adjust its width based on the screen it's on: if it's
maximized, it should probably stay that way (so resize horizontally), if not,
perhaps resize it based on it's relative size (for example 3/2 of screen
width)?

Reproducible: Always

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

[plasmashell] [Bug 362531] Plasma panels are not transparent after login

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #41 from Leslie Zhai  ---
git pull, but sitll... do I need to also git pull kwin master?

commit 3000e76396bd1ab248db2b80e61bd8fd5594cc06
Author: Martin Gräßlin 
Date:   Wed Aug 3 13:05:00 2016 +0200

[autotests] Try to make compositingenabled_test pass on build.kde.org

The test failed on build.kde.org. This change introduces a slight
variation with a wait on a signalspy instead of waiting with TRY_VERIFY

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

[plasmashell] [Bug 366394] single panel doesn't adjust to primary screen correctly

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Assignee|aleix...@kde.org|notm...@gmail.com

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

[plasmashell] [Bug 366394] single panel doesn't adjust to primary screen correctly

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

   Keywords||multiscreen

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

[plasmashell] [Bug 366394] New: single panel doesn't adjust to primary screen correctly

[Sebastian Kügler via KDE Bugzilla]

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

Bug ID: 366394
   Summary: single panel doesn't adjust to primary screen
correctly
   Product: plasmashell
   Version: master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: se...@kde.org
CC: plasma-b...@kde.org

Situation: I connect an external monitor to my laptop, and wish to use it as
primary screen, laptop panel stays on.

Expected: the content (panel, desktop containment) moves to the external
screen. When unplugging, it moves back to the laptop display.

What happens is that the desktop containment moves, but the panel gets lost. 



Reproducible: Always

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

[kwin] [Bug 366393] New: Crashes

[Alexandre Nunes via KDE Bugzilla]

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

Bug ID: 366393
   Summary: Crashes
   Product: kwin
   Version: 5.7.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alexandre.nu...@gmail.com

Application: kwin_x11 (5.7.0)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.6.4+ x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

Every window loses decoration. It seems to happen every time this crashes

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7fc35a156700 (LWP 10700)):
#0  0x0034c32dff73 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x0034d70d2a1f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x0034d70d445e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x0034d70d4972 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x0034d707fe4a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x0034d6ea89e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x0034e38c1405 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x0034d6ead808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x0034c3a07464 in start_thread (arg=0x7fc35a156700) at
pthread_create.c:333
#9  0x0034c32e730d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fc345878700 (LWP 3213)):
#0  0x0034c3a0d09f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0034d5b7c574 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x0034d5b7c5b9 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x0034c3a07464 in start_thread (arg=0x7fc345878700) at
pthread_create.c:333
#4  0x0034c32e730d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fc34cc89700 (LWP 3209)):
#0  0x7fffa0f08a4f in clock_gettime ()
#1  0x0034c32f3f66 in __GI___clock_gettime (clock_id=1, tp=0x7fc34cc88a10)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x0034d6f596c6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x0034d70d4d59 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x0034d70d415b in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x0034d70d4972 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x0034d707fe4a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x0034d6ea89e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x0034e38c1405 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x0034d6ead808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x0034c3a07464 in start_thread (arg=0x7fc34cc89700) at
pthread_create.c:333
#11 0x0034c32e730d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fc360aa7700 (LWP 3200)):
#0  0x0034c32dff73 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x0034d70d2a1f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x0034d70d445e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x0034d70d4972 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x0034d707fe4a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x0034d6ea89e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x0034d2615515 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x0034d6ead808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x0034c3a07464 in start_thread (arg=0x7fc360aa7700) at
pthread_create.c:333
#9  0x0034c32e730d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fc3625bc700 (LWP 3199)):
#0  0x0034c32de19d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x0034c5a0a382 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x0034c5a0bff7 in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fc363062a89 in  () at 

[KScreen] [Bug 349573] Multiple Monitors with Plasma 5.2

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

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

--- Comment #2 from Sebastian Kügler  ---
Good news. We have fixed a number of issues which lead to this bug. Would it be
possible for you to test 5.7, or better yet git master (perhaps from KDE Neon
or openSUSE tumbleweed)?

I'm closing this bugreport, since we already have the same root-cause reported
in others. If need be, it can be re-opened or a new one filed, and we take it
up from there.

Thanks for the patience!

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

[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 CC||se...@kde.org

--- Comment #31 from Sebastian Kügler  ---
I've found a problem in the code enabling outputs. Information about crtcs was
outdated, which meant outputs failed to enable in certain cases, and were
subsequently disabled. We're now querying the crtcs right before enabling an
output, which seems to be much more reliable.
I think this may well be the root cause for this bug, the symptoms would be
consistent.

I've tested suspending with dock attached quite extensively with a lenovo
onelink+ dock, and it would fail in similar ways: screen stays black. Switching
between these profiles (external and laptop panel) works reliably now.

These patches are in libkscreen master, I hope to get them into Plasma 5.7.4
(which is the next bugfix update).

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

[plasmashell] [Bug 366392] Brightness reset from lowest level after system restart

[anewuser via KDE Bugzilla]

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

anewuser  changed:

   What|Removed |Added

Version|5.7.1   |5.7.3

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #8 from Sebastian Kügler  ---
I've found a bug when enabling outputs. Information about crtcs was outdated,
which meant outputs failed to enable in certain cases, and were subsequently
disabled. We're now querying the crtcs before enabling an output, which seems
to be much more reliable.
I think this may well be the root cause for your problem, the symptoms would be
consistent.

I've tested suspending with dock attached quite extensively with a lenovo
onelink+ dock, and it would fail in similar ways as you describe, but with my
patches, it works pretty much flawlessly now. These patches are in master
(libkscreen), one fix also went into the 5.7 branch. I'll have to do some more
testing in the 5.7 branch, but I hope I can get these fixes into 5.7.4.

Is this something you could test and confirm?

Aside from that, master now also contains more useful logging, it will produce
a detailed log file in ~/.local/share/kscreen/kscreen.log .

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

[digikam] [Bug 366109] Slideshow freezes on first image (Windows)

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #4 from Alexander Schlarb  ---
Yes, I compiled digiKam for the `win32` target based on the instructions in
`project/mxe/README`.

My main wish for improvements would probably be to be able to use the
precompiled MXE dependencies from their repos instead of having to compile
QtWebkit (and everything else) myself. I needed 4 tries to compile it, since
the compilation kept causing OOMs.
Other than that it was surprisingly smooth sailing. 

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

[plasmashell] [Bug 353975] Black screen on second display.

[via KDE Bugzilla]

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

romulu...@gmail.com changed:

   What|Removed |Added

 CC||romulu...@gmail.com

--- Comment #44 from romulu...@gmail.com ---
Here too, using neon and up to date

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

[plasmashell] [Bug 366392] New: Brightness reset from lowest level after system restart

[anewuser via KDE Bugzilla]

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

Bug ID: 366392
   Summary: Brightness reset from lowest level after system
restart
   Product: plasmashell
   Version: 5.7.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Battery Monitor
  Assignee: k...@privat.broulik.de
  Reporter: caip...@fastmail.fm
CC: plasma-b...@kde.org

I set the brightness level of my monitor to the lowest possible level. After a
system restart, it's not longer at the lowest level.

Reproducible: Sometimes

Steps to Reproduce:
1. Use the system tray battery monitor/display settings icon to set your
brightness to the lowest level possible
2. Restart or turn your system off

Actual Results:  
The brightness level is no longer at the lowest level, but at the second lowest
level.

Expected Results:  
The brightness level should stay at the lowest level no matter how many times I
restart/shutdown the computer or log off from my account.

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

[kwin] [Bug 366081] kwin's windows stay translucent after moving, become invisible

[Michael Butash via KDE Bugzilla]

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

--- Comment #13 from Michael Butash  ---
Side note too, Martin's example to reproduce does not work for me, not after a
fresh reboot last night and minimal activity until today.  I switch a lot of
windows back and forth, even between desktops, and doing so does not
immediately manifest itself after reboots.  It's only after some time (~1-2
days) that this starts occurring normally, and sometimes moving just on the
same screen triggers it.

I just had Okular get peculiar, where I'd minimize and leave an impression of
the translucent window stuck in the compositing I couldn't remove, where
un-minimizing it, behaved perfectly normal until minimizing again, resulting in
"ghost". 

Such as:
1. Open url to download PDF, default to Okular reader.
2. Navigate document paging through.
3. Minimize document, leaves resulting translucent ghost image on screen,
cannot remove/manipulate.
4. Un-Minimize Okular, window reappears in focus, can move window normally.
5. Leave Okular on desktop, work with other applications, come back to read pdf
10 minutes later on screen, minimize works normally again.

More odd "coming and going" of these issues with compositing and general
destabilization over time.

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

[kmix] [Bug 364141] Kmix crashes when trying to change the volume for individual streams with scrollwheel from systray

[coffnix via KDE Bugzilla]

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

--- Comment #14 from coffnix  ---
Fixed with patches kmix-15.08.2-autostart_disable.patch and
kmix-kdebug364141.patch here on Funtoo Linux. Thanks :D

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

[kwin] [Bug 366081] kwin's windows stay translucent after moving, become invisible

[Michael Butash via KDE Bugzilla]

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

--- Comment #12 from Michael Butash  ---
Not sure how related, but I had a weird echo in the dimming module as well as
translucency, as I use both to make non-focus apps somewhat
ghosted/backgrounded.  I've observed when I get the ghosting, clicking between
two ghosted windows repeatedly causes them to continually dim further with the
translucency and never returning to full focus, thus the "echo" comment.  It
just keeps dimming until it's unviewable, or I restart compositing.

This seems to be present in more modules than just translucency potentially?

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

[plasmashell] [Bug 366188] Bad exception handling when the kholidays QML module isn't installed

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #3 from Martin Klapetek  ---
> The actual error from the screenshot comes from KHoliday I believe, which has 
> declarative imports that the plugin in Plasma-workspace uses.

What I forgot to add in this sentence is that the installed KHolidays version
is too old, that's the actual problem. I think.

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

[plasmashell] [Bug 366188] Bad exception handling when the kholidays QML module isn't installed

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Martin Klapetek  ---
No; the system is a bit more complicated.

Plasma-framework, which has the calendar backend and the events backend,
depends on KF5::CalendarEvents, which is part of KDeclarative.

Plasma-workspace then has a plugin based on KHolidays that is being loaded by
that Plasma-framework code.

The actual error from the screenshot comes from KHoliday I believe, which has
declarative imports that the plugin in Plasma-workspace uses.

I would advise to file a bug against Kubuntu packaging and at the same time add
a required version of KHolidays in -workspace, which seems to be missing. On a
side note, KHolidays is now in this strange limbo where it is a framework that
is being released with applications, so the versioning might be a bit weird.

Finally, Simon, for future reference, please always attach screenshots directly
to bugzilla or at least include the text of the error here, so that we know
what this is about in case the image is taken down from a 3rd party site.

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

[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #11 from Martin Klapetek  ---
> Shouldn't the notification disappear automatically after a few seconds

The timeout is computed from the notification text length iirc.

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

[plasmashell] [Bug 365139] Inconsistent localization of month names in calendar plasmoid

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #5 from Martin Klapetek  ---
They should actually all use LANG. If my LANG is Czech and I use US datetime
format, I still want all titles to be in Czech, not US.

-- 
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 #70 from Michael Butash  ---
It is really confusing where to begin to troubleshoot it, as I can't tell how
much is related to kwin, plasmashell, or libqt underneath.  Especially the
first time having to dig into KDE behind the scenes, but I've really loved the
5.x generation enough to want to try to fix this.

The only thing I will still add, that seems loosely related is that when I do
get kwin to crash, which is now happening more, it still seems to lose its
sense of identity among applications bound to which display.  When triggered,
things like the wall papers shuffle every time monitors come and go, or when
kwin crashes in particular.  

Also my taskbar can never figure out what display to end up on despite what I
set the primary display to.  It does at first, but then, doesn't after time,
really almost randomly lands, but never where it's supposed to - very odd. 
Almost like a non-obvious display index is getting broken, but at qt, plasma,
or kwin, not sure as they all seem to use/contribute in some way.  Plasmoids as
well acted oddly, crashing, ghosting between displays, etc.  

All seem related to core multi-monitor function, as unplugging just one,
reshuffles things, fixing some, breaking/shuffling others.  Finding the root of
that "shuffling" or random landing of apps on display among identities seems
key.

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

[digikam] [Bug 366391] New: rotating an image seems to forget to reset the orientation flag

[Nico Kruber via KDE Bugzilla]

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

Bug ID: 366391
   Summary: rotating an image seems to forget to reset the
orientation flag
   Product: digikam
   Version: 5.0.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import-PostProcessing
  Assignee: digikam-de...@kde.org
  Reporter: nico.kru...@gmail.com

Whenever I (auto-)rotate images, e.g. by the menu action or during import where
it seems to be done automatically, it looks like the image contents are rotated
but the metadata is not updated (or maybe only in the sidecar file but not in
the image itself). Manually setting the exif Orientation tag to "normal" via
the menu seems to fix the view inside digikam but not for external programs,
e.g. gimp.

Reproducible: Always

Steps to Reproduce:
1. find a jpeg which is rotated by its exif flag
2. rotate in digikam (with the settings above)
3. open the image in e.g. gimp to see the messed-up result

Actual Results:  
rotated image (contents) with the original exif orientation flag inside the jpg
file

Expected Results:  
rotated image (contents) including the exif orientation flag set to "normal"
inside the jpg file

related application settings:
* Metadata -> Rotation -> Rotate by changing the content if possible
* Metadata -> Rotation -> Write flag to metadata if possible
* Metadata -> Behaviour -> Read from sidecar files
* Metadata -> Behaviour -> Write to sidecar files + Write to XMP sidecar only
(* Metadata -> Behaviour -> Use lazy synchronisation OFF)

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

[plasmashell] [Bug 366390] New: Wallpaper config page not reading current/default settings when switching wallpaper type

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Bug ID: 366390
   Summary: Wallpaper config page not reading current/default
settings when switching wallpaper type
   Product: plasmashell
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kosse...@kde.org
CC: bhus...@gmail.com, plasma-b...@kde.org

When opening the Workspace Settings with the Wallpaper tab, on selecting
another wallpaper type the appearing config UI elements do not reflect the last
applied values (or the default, if never used), but instead seem all reset to
the default values of the UI elements (empty string, zero values).

When only opening the Workspace Settings with the Wallpaper tab, the initially
displayed config UI elements have the correct values as currently applied. But
only then. Once selecting another wallpaper type in the combobox and then
selecting the current again (without using "Ok" or "Apply" on the dialog), the
displayed values no longer reflect the current settings and are also
empty/zero.

>From what I see in the UI, it seems when loading the new config.qml into the
view for the new wallpaper type, that one does not get its settings injected
properly or at all.

Next to that, it seems that on storing the settings to the config file writing
of the key/value entries is also duplicated at a more general level, which
seems wrong not only because keys could be conflicting. Perhaps that is
related. Excerpt of my plasma-org.kde.plasma.desktop-appletsrc:
--- 8< ---
[Containments][9][Wallpaper][General]
Color=255,170,0
Speed=51
[Containments][9][Wallpaper][org.kde.color][General]
Color=255,170,0
[Containments][9][Wallpaper][org.kde.autumn][General]
Speed=51
--- 8< ---

Plasma frameworks is KF5 5.24.

Reproducible: Always

Steps to Reproduce:
Precondition: a wallpaper type != "Color" is currently active
1. Open Workspace Settings, choose Wallpaper tab
2. Select wallpaper type "Color"
3. Click the color button and choose e.g. some green color.
4. Click "Apply"
5. Select another wallpaper type, e.g. "Image"
6. Select again the "Color" wallpaper type


Actual Results:  
The config button for the color is set to "Black"


Expected Results:  
The config button for the color is set to the color selected and applied
previously.

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

[kdevelop] [Bug 366389] New: segfault on start

[Vladislav Tsendrovskii via KDE Bugzilla]

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

Bug ID: 366389
   Summary: segfault on start
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: v...@vltc.net.eu.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.1 x86_64
Distribution: "NAME=Gentoo"

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

I've tried to start kdevelop5 with any my project, created by kdevelop4.
kdevelop segfaults after start

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2a4a25b780 (LWP 6561))]

Thread 8 (Thread 0x7f2a30d1d700 (LWP 6562)):
#0  0x7f2a49f9bc7d in poll () from /lib64/libc.so.6
#1  0x7f2a3e2f0a72 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f2a3e2f2627 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f2a32a75ef9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f2a4a65e17b in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f2a4400d42c in start_thread () from /lib64/libpthread.so.0
#6  0x7f2a49fa4b8d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f2a2ae8d700 (LWP 6563)):
#0  0x7f2a4a656d41 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#1  0x7f2a4a845d73 in postEventSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f2a41fee76c in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2a41fef128 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f2a41fef30c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f2a4a845fac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f2a4a7fa162 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f2a4a659aa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f2a4c8831dd in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#9  0x7f2a4a65e17b in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f2a4400d42c in start_thread () from /lib64/libpthread.so.0
#11 0x7f2a49fa4b8d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f2a213ad700 (LWP 6565)):
#0  0x7f2a44012f4f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f2a23a4da43 in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f2a23a4d1b7 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f2a4400d42c in start_thread () from /lib64/libpthread.so.0
#4  0x7f2a49fa4b8d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f2a205a7700 (LWP 6566)):
#0  0x7f2a440132f8 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f2a4a65e7a8 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f2a480a17a0 in KDevelop::DUChainPrivate::CleanupThread::run() ()
from /usr/lib64/libKDevPlatformLanguage.so.10
#3  0x7f2a4a65e17b in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f2a4400d42c in start_thread () from /lib64/libpthread.so.0
#5  0x7f2a49fa4b8d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f2a17de5700 (LWP 6567)):
#0  0x7ffc4c350ad2 in clock_gettime ()
#1  0x7f2a49fb1596 in clock_gettime () from /lib64/libc.so.6
#2  0x7f2a4a6fa61b in qt_gettime() () from /usr/lib64/libQt5Core.so.5
#3  0x7f2a4a844459 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7f2a4a84485d in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f2a4a845b6c in timerSourcePrepareHelper(GTimerSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f2a4a845c2d in timerSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f2a41fee76c in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#8  0x7f2a41fef128 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7f2a41fef30c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f2a4a845fac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#11 0x7f2a4a7fa162 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#12 0x7f2a4a659aa4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#13 0x7f2a408ef3d5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#14 0x7f2a4a65e17b in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#15 0x7f2a4400d42c in start_thread () from /lib64/libpthread.so.0
#16 0x7f2a49fa4b8d in clone () from 

[kdeconnect] [Bug 366363] Does not load qml files to show in the plasmoid due to new PluginCheck feature

[Eldhrimer via KDE Bugzilla]

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

--- Comment #4 from Eldhrimer  ---
Here it is:
--
Error al cargar archivo QML:
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:24:1:
module "org.kde.kdeconnect" is not installed
--

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

[KBibTeX] [Bug 366191] kbibtex segfaults before any windows are displayed

[Thomas Fischer via KDE Bugzilla]

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

--- Comment #5 from Thomas Fischer  ---
(In reply to Jonathan Bisson from comment #4)
> Seems to start, fails opening .bib files (error about missing part)
Error about missing part is almost always about incomplete installations. There
is a Wiki page for details:
https://userbase.kde.org/KBibTeX/Development#Installation

> 10-15s to be usable after the main window appears
I cannot think of a good reason why such a delay exists, except for some
network issues that have a delay/timeout of several seconds. Does this happen
every time?
In case of doubt, (1) remove all traces of your KBibTeX installation from /usr
and /usr/local, (2) remove all copies of KBibTeX's configuration files in your
home (check in ~/.kde*, ~/.local, ~/.config at least), and (3) only then
re-install again.

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

[kdenlive] [Bug 348029] timeline corruption

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #16 from Jean-Baptiste Mardelle  ---
Git commit 353fff4e431da297d7dce0ffdceeb5947f064f71 by Jean-Baptiste Mardelle.
Committed on 03/08/2016 at 21:48.
Pushed by mardelle into branch 'Applications/16.08'.

Detect and remove invalid (overlapping) transitions on project opening

M  +0-1src/timeline/customtrackview.cpp
M  +38   -20   src/timeline/timeline.cpp

http://commits.kde.org/kdenlive/353fff4e431da297d7dce0ffdceeb5947f064f71

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

[plasma-nm] [Bug 365605] Network widget does not show speed statistics/usage

[Michael D via KDE Bugzilla]

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

--- Comment #3 from Michael D  ---
Created attachment 100441
  --> https://bugs.kde.org/attachment.cgi?id=100441=edit
No statistics

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

[frameworks-knotifications] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled

[via KDE Bugzilla]

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

--- Comment #6 from kakadu.hafan...@gmail.com ---
Folks, can we somehow raise priority of this bug?

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

[plasma-nm] [Bug 365605] Network widget does not show speed statistics/usage

[Michael D via KDE Bugzilla]

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

--- Comment #2 from Michael D  ---
Created attachment 100440
  --> https://bugs.kde.org/attachment.cgi?id=100440=edit
Showing statistics

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

[kontact] [Bug 366388] New: Could not create collection trash resourceId: 24

[Ewald Müller via KDE Bugzilla]

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

Bug ID: 366388
   Summary: Could not create collection trash resourceId: 24
   Product: kontact
   Version: 4.13
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: emu...@netscape.net

Just started Kontact, it was receiving mails, then the error occurs: Crash
trying to create a trash-folder for an imap-account (that was former under the
local folders)
Asus Eee PC, Kubuntu Trusty Tahr, 

Application: kontact (4.13.3)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.2.0-54-generic x86_64
Distribution: Ubuntu 14.04.4 LTS


Reproducible: Always

Steps to Reproduce:
1. start kontact
2. switch to kmail
3. crash occurs receiving mails



Application: kontact (4.13.3)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.2.0-54-generic x86_64
Distribution: Ubuntu 14.04.4 LTS

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

Just startet Firefox before (on that slow machine); then Kontact was starting,
receiving Mails

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7375f8c800 (LWP 4478))]

Thread 5 (Thread 0x7f7355568700 (LWP 4479)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7370d3081d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7370d30859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f736d452184 in start_thread (arg=0x7f7355568700) at
pthread_create.c:312
#4  0x7f737350237d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f7314c5d700 (LWP 4480)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7370a7120d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7370d5ffd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f736d452184 in start_thread (arg=0x7f7314c5d700) at
pthread_create.c:312
#4  0x7f737350237d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f7303eba700 (LWP 4497)):
#0  0x7f73734f4fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f736cf72fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f736cf730ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7373c7b7be in QEventDispatcherGlib::processEvents
(this=0x7f72fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f7373c4d0af in QEventLoop::processEvents
(this=this@entry=0x7f7303eb9da0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f7373c4d3a5 in QEventLoop::exec (this=this@entry=0x7f7303eb9da0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f7373b49c5f in QThread::exec (this=this@entry=0x1efe5c0) at
thread/qthread.cpp:537
#7  0x7f7373c2e823 in QInotifyFileSystemWatcherEngine::run (this=0x1efe5c0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f7373b4c32f in QThreadPrivate::start (arg=0x1efe5c0) at
thread/qthread_unix.cpp:349
#9  0x7f736d452184 in start_thread (arg=0x7f7303eba700) at
pthread_create.c:312
#10 0x7f737350237d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f73036b9700 (LWP 4500)):
#0  0x7f73734f4fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f736cf72fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f736cf730ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7373c7b7be in QEventDispatcherGlib::processEvents
(this=0x7f72f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f7373c4d0af in QEventLoop::processEvents
(this=this@entry=0x7f73036b8de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f7373c4d3a5 in QEventLoop::exec (this=this@entry=0x7f73036b8de0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f7373b49c5f in QThread::exec (this=) at
thread/qthread.cpp:537
#7  0x7f7373b4c32f in QThreadPrivate::start (arg=0x1e79540) at
thread/qthread_unix.cpp:349
#8  0x7f736d452184 in start_thread (arg=0x7f73036b9700) at
pthread_create.c:312
#9  0x7f737350237d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f7375f8c800 (LWP 4478)):
[KCrash Handler]
#6  0x7f737343ec37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7f7373442028 in __GI_abort () at abort.c:89
#8  0x7f7373b41c92 in qt_message_output (msgType=msgType@entry=QtFatalMsg,
buf=0x298ac48 "Fatal Error: Accessed global static 'KernelPrivate *sInstance()'
after 

[konqueror] [Bug 192372] images in table have no distance to each other

[Peter Möller via KDE Bugzilla]

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

Peter Möller  changed:

   What|Removed |Added

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

--- Comment #3 from Peter Möller  ---
old stuff, not worth considering anymore, website has changed also

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

[kdelibs] [Bug 233644] Missing the print option "media type"

[Peter Möller via KDE Bugzilla]

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

Peter Möller  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #2 from Peter Möller  ---
lots of changes meanwhile. I think it is time to close this guy ;-)

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

[digikam] [Bug 366387] New: video (mts and mov) not played (neither from camera nor local file)

[via KDE Bugzilla]

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

Bug ID: 366387
   Summary: video (mts  and mov) not played (neither from camera
nor local file)
   Product: digikam
   Version: 5.0.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: georg.li...@t-online.de

Version 5.0 is great - nice progress !

However I am no longer able to see the videos in digikam. The preview is still
correct, but the video is not playing. Instead it shows:

"Mit dem Medienspieler ist ein Fehler aufgetreten ..."

>From shell I find the following:

digikam.database: Complete scan took: 2645 msecs.
digikam.general: Event is dispatched to desktop notifier through DBUS
digikam.general: Stacked View Mode :  6
digikam.general: Error:  "Das QMediaPlayer-Objekt hat keinen gültigen Dienst"
digikam.general: Stacked View Mode :  6
digikam.general: Error:  "Das QMediaPlayer-Objekt hat keinen gültigen Dienst"

I am not able to play neither mov (Canon) nor mts (Sony).

I am unavailable the next four week - hope these details suffice to track the
problem.

Thanks,

Georg


Reproducible: Always

Steps to Reproduce:
1. Start digikam 
2. select video to play
3.

Actual Results:  
Not being played.

Expected Results:  
Video shall be played.

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

[plasmashell] [Bug 355353] Device Notifier fails to popup/notify of an added USB-stick

[Peter Möller via KDE Bugzilla]

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

Peter Möller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Peter Möller  ---
looking at my reported bugs, i can confirm now, that actual leap does not show
this problem anymore 
=> it is fixed :-)

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

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

[Simon via KDE Bugzilla]

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

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com

--- Comment #18 from Simon  ---
Created attachment 100439
  --> https://bugs.kde.org/attachment.cgi?id=100439=edit
Add information about configuration transition to welcome screen.

I agree that this is a very important point for the user. Of course ideally the
transition problems would be removed, but as always: This is open-source, if
you want it done, do it.
I attached a patch that adds information about the (non-)migration of the
configuration to the welcome screen.

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

[frameworks-kdeclarative] [Bug 343576] Crash when removing network-monitor applet

[Dainius Masiliūnas via KDE Bugzilla]

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

Dainius Masiliūnas  changed:

   What|Removed |Added

 CC||past...@gmail.com

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

[plasmashell] [Bug 366386] New: Plasma (black screen) crashed after kernel update 4.1.27-24-default

[Colin via KDE Bugzilla]

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

Bug ID: 366386
   Summary: Plasma (black screen) crashed after kernel update
4.1.27-24-default
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hckilb...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Just trying to login. Leap 42.1 after a kernel update to 4.1.27-24-default from
4.1.26-21-default.

 In a terminal I changed the greeter to xdm (/etc/sysconfig/displayManager
file) and rebooted. I was able to log in but Plasma chashed and I was presented
with this Crash Report Assistant.

Previously, on boot, I was able to choose to the previous kernel with the boot
menu and that worked fine. I since updated the kernel again to 4.1.27.27-
default ... now I cannot, as both kernels offered in the menu fail ... 

Not to confuse matters but I am using Parallels 11 VM tool on an iMac.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7fbe22357700 (LWP 2060)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe35f34422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fbe35f3600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fbe24ada3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fbe1b3ea700 (LWP 2075)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe318b4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe316d661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe349eae18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fbe0f046700 (LWP 2076)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe318b4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe316d661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe349eae18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fbe0d7ee700 (LWP 2077)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe318b4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe316d661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe349eae18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fbe07df7700 (LWP 2078)):
#0  0x7fbe307ee03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbe371b986b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fbe371b9899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbd7700 (LWP 2079)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in

[plasma-nm] [Bug 365605] Network widget does not show speed statistics/usage

[via KDE Bugzilla]

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

white...@gmail.com changed:

   What|Removed |Added

 CC||white...@gmail.com

--- Comment #1 from white...@gmail.com ---
Could you please provide a screenshot of the applet working and another of the
applet not working? Just to let us understand a little more the problem you are
facing.

thanks

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

[kwin] [Bug 366385] New: reproducible crash of kwin/plasma in Kubuntu 16.04.1

[proton via KDE Bugzilla]

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

Bug ID: 366385
   Summary: reproducible crash of kwin/plasma in Kubuntu 16.04.1
   Product: kwin
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: xpr1...@mail.ru

I have found a way to crash kwin/plasma in Kubuntu 16.04.1 on my system
(pentium g860, 8Gb, integrated video) and in Virtual Box. The method works in
freshly installed VM, live CD VM, live USB my system, and in my installed
system (which is based on ppa:kubuntu-ppa/backports).
In a fteshly installed VM system the result is a report about plasma crash that
instantly closes.
In live CD vm system and live USB VM systems kwin obviously crashes but there
is no report appear.
In my real system a report about a kwin crash appears.

Reproducible: Always

Steps to Reproduce:
1. boot the system (live usb/cd Kubuntu 16.04.1, freshly insalled Kubuntu
16.04.1, VM or may be your real system)
2. Press: Application Launcher - Applications - Settings -System Settings -
Applications Style - Window Decorations - Select Plastic - Apply
3. Press: All Settings (the back button) - Input Devices - Touchpad - Joystic
(or other tab, or back) - Discard
4. Close the System Settings window by clicking on the "X" close button
5. Do again: Application Launcher - Applications - Settings -System Settings -
Input Devices - Touchpad - Joystic (or other tab, or back) => KWin  crash
If you open any other windows before or inbetween, the method may not work.

Actual Results:  
In my real system (kubuntu backport) a report about kwin crash appears
In a freshly installed VM system after right clicking on the task button and
trying to close the System Settings window for a couple of times a plasma crash
report appears and instantly closes. The System Settings window doesn't close.
In live cd/usb systems nothing appears but I couldn't close the System Settings
window in a usual way because it had no caption and nothing happend when I
tried to close it by the method above..

Expected Results:  
the window about applying changes appears as usual and the System Settings
window can be closed in a usual way

Processor: 2x Intel(R) Pentium(R) CPU G860 @ 3.00GHz
Memory: 7852MB
Integrated Video
Operating System: Kubuntu 16.04.1 LTS ppa:kubuntu-ppa/backports

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

[kmix] [Bug 364141] Kmix crashes when trying to change the volume for individual streams with scrollwheel from systray

[via KDE Bugzilla]

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

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kmix
   ||/7aa904ecacfd2eeaa91068e17c
   ||c9bd79ba058206
 Resolution|--- |FIXED

--- Comment #13 from andreas.sturmlech...@gmail.com ---
Git commit 7aa904ecacfd2eeaa91068e17cc9bd79ba058206 by Andreas Sturmlechner.
Committed on 28/07/2016 at 21:27.
Pushed by asturmlechner into branch 'Applications/16.08'.

Fix infinite recursion by scroll wheel volume change
REVIEW: 128546

M  +3-1gui/viewdockareapopup.cpp

http://commits.kde.org/kmix/7aa904ecacfd2eeaa91068e17cc9bd79ba058206

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

[plasmashell] [Bug 366153] All Window Icons Are Intermittently Become "Active" on Task Manager Falsely

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||fufu...@outlook.com

--- Comment #16 from Eike Hein  ---
*** Bug 366384 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 366384] Minimize animation is drawn to the center of the desktop, instead of the task manager.

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---
Same as bug 366153 because requestPublishGeometry doesn't run for the same
reason.

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

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

[plasmashell] [Bug 366384] New: Minimize animation is drawn to the center of the desktop, instead of the task manager.

[via KDE Bugzilla]

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

Bug ID: 366384
   Summary: Minimize animation is drawn to the center of the
desktop, instead of the task manager.
   Product: plasmashell
   Version: 5.7.3
  Platform: Other
   URL: https://mega.nz/#!CZMiHJAI!gDTfa3JOVz9NEoGiv95wcJUd_GE
V-D5P3tqNTDLhCbw
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: fufu...@outlook.com
CC: plasma-b...@kde.org

The minimize animation/magic lamp is drawn to the center of the screen instead
of the task manager, this happens to about half of the windows. A given window
always exhibits the same behaviour.
e.g. The kwrite window always minimizes correctly to the task manager while the
firefox window is minimized to the center.

Reproducible: Sometimes

Steps to Reproduce:
Minimize a window

Actual Results:  
Minimize animation is drawn to the center of the desktop

Expected Results:  
Minimize animation is drawn to the task manager

Problem has been present since plasma 5.7.0, 5.6.x worked just fine.
Using NVIDIA 367.35 GTX 860M
Scale method: Smooth
Rendering backend: OpenGL 3.1

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Luis Silva via KDE Bugzilla]

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

Luis Silva  changed:

   What|Removed |Added

 CC||aman...@kde.org

--- Comment #58 from Luis Silva  ---
*** Bug 335776 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 335776] IMAP agent crashes frequently

[Luis Silva via KDE Bugzilla]

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

Luis Silva  changed:

   What|Removed |Added

 CC||lacsi...@gmail.com
 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Luis Silva  ---


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

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Luis Silva via KDE Bugzilla]

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

Luis Silva  changed:

   What|Removed |Added

   Priority|NOR |HI
 CC||lacsi...@gmail.com

--- Comment #57 from Luis Silva  ---
This bug is affecting all my imap accounts both at home and at work to the
point of making kmail useless. 

New duplicates often appear after after I move mails between folders.

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

[kmail2] [Bug 355498] Kmail 4.14.9 Error notification "Multiple merge candidates. aborting" after clicking "check mail" for an imap source

[Luis Silva via KDE Bugzilla]

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

Luis Silva  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||lacsi...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Luis Silva  ---


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

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Luis Silva via KDE Bugzilla]

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

Luis Silva  changed:

   What|Removed |Added

 CC||sl...@holisticmath.com

--- Comment #56 from Luis Silva  ---
*** Bug 355498 has been marked as a duplicate of this bug. ***

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

[frameworks-networkmanager-qt] [Bug 366334] VPN connection indication in the system tray

[altosch via KDE Bugzilla]

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

--- Comment #3 from altosch  ---
(In reply to Jan Grulich from comment #1)

dpkg -s plasma-nm: Version: 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1

Please see the screenshot.

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

[frameworks-networkmanager-qt] [Bug 366334] VPN connection indication in the system tray

[altosch via KDE Bugzilla]

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

altosch  changed:

   What|Removed |Added

 CC||a...@tosovsky.eu

--- Comment #2 from altosch  ---
Created attachment 100438
  --> https://bugs.kde.org/attachment.cgi?id=100438=edit
screenshot

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

[konversation] [Bug 366374] Crash on editing configured server details

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/konv
   ||ersation/4fa92f7e55dea6354a
   ||7dbeae1ddf62c4357912e2
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Eike Hein  ---
Git commit 4fa92f7e55dea6354a7dbeae1ddf62c4357912e2 by Eike Hein.
Committed on 03/08/2016 at 18:46.
Pushed by hein into branch '1.6'.

Fix copy constructor not setting m_bypassProxy.

This caused crashes all over the place because now operator== fails.

This will need a 1.6.2 hotfix release.
CCMAIL:anselmo...@gmail.com

M  +1-0src/irc/serversettings.cpp

http://commits.kde.org/konversation/4fa92f7e55dea6354a7dbeae1ddf62c4357912e2

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

[konversation] [Bug 366370] Konverstatio crash when using TOR

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Eike Hein  ---


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

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

[konversation] [Bug 366374] Crash on editing configured server details

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||shur...@gmail.com

--- Comment #5 from Eike Hein  ---
*** Bug 366370 has been marked as a duplicate of this bug. ***

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

[kdeplasma-addons] [Bug 361928] Comic-widget of Plasma5-addons 5.6.2-89.1 shows big yellow smiley instead of selected comic after restarting plasma5.

[Babalu via KDE Bugzilla]

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

Babalu  changed:

   What|Removed |Added

 CC||hethoch...@gmx.de

--- Comment #3 from Babalu  ---
Same here on openSUSE Leap 42.1 Plasma 5.7.3

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

[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems

[Liam Murphy via KDE Bugzilla]

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

Liam Murphy  changed:

   What|Removed |Added

 CC||l...@lpmdesigns.com

--- Comment #3 from Liam Murphy  ---
I am also having this issue. 

I have a dual boot with Windows, but separate SSD's for Windows and Linux. I've
attempted manual partition editing, and the default "erase disk" and let Neon
do the work. 

Getting same GRUB Minimal screen after rebooting when the install is complete. 

I get no errors during the install.

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

[neon] [Bug 366375] libkf5dgantt2-5 can't be upgraded kde neon user edition

[Denis Moon via KDE Bugzilla]

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

--- Comment #1 from Denis Moon  ---
Here is what I found additionally to the previous info:

sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) libkf5incidenceeditorsng5 [ amd64 ] < 4:15.12.3-0ubuntu1 > (
universe/libs )
Broken libkf5incidenceeditorsng5:amd64 Depends on libkf5kdgantt2-5 [ amd64 ] <
4:15.12.3-0ubuntu1 -> 4:16.04.3-0neon+16.04+build1 > ( libs ) (=
4:15.12.3-0ubuntu1)
  Considering libkf5kdgantt2-5:amd64 3 as a solution to
libkf5incidenceeditorsng5:amd64 6
  Added libkf5kdgantt2-5:amd64 to the remove list
  Fixing libkf5incidenceeditorsng5:amd64 via keep of libkf5kdgantt2-5:amd64
 Try to Re-Instate (0) libkf5kdgantt2-5:amd64
Done
Calculating upgrade... Done
The following packages have been kept back:
  libkf5kdgantt2-5
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

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

[plasma-nm] [Bug 366383] Applet keeps spinner as if still connecting even when connected

[Martin Bednar via KDE Bugzilla]

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

--- Comment #1 from Martin Bednar  ---
After plasmashell restart, ip is in applet, and spinner is gone.

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

[plasma-nm] [Bug 366383] New: Applet keeps spinner as if still connecting even when connected

[Martin Bednar via KDE Bugzilla]

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

Bug ID: 366383
   Summary: Applet keeps spinner as if still connecting even when
connected
   Product: plasma-nm
   Version: 5.7.2
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: martin+...@serafean.cz
CC: lu...@kde.org

Sometimes when connecting to a network (wired or wireless), the spinner that
notifies that connecting is in progress keeps spinning even when connection
gets state "connected" (visible in the applet).
The only unusual thing is the absence of ip address in the applet popup.

Combined with the fact that spinners in the tray are cpu power hogs, this makes
it a pretty serious issue.

Reproducible: Sometimes

Steps to Reproduce:
1. Initiate connection to network
2. wait for connected state
3. See internet working, state as connected and spinner still spinning.

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

[klipper] [Bug 366277] klipper systray applet autostarts on non-plasma DE's

[Michael Palimaka via KDE Bugzilla]

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

--- Comment #5 from Michael Palimaka  ---
Does it make sense to backport this to 5.7?

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

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

[Robin Kuzmin via KDE Bugzilla]

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

Robin Kuzmin  changed:

   What|Removed |Added

 CC||kuzmin.ro...@gmail.com

--- Comment #1 from Robin Kuzmin  ---
I have the same issue.
I have a suppression:
{
   google::protobuf::Message::PrintDebugString() const (text_format.cc:110)
   Memcheck:Leak
   match-leak-kinds: reachable
   fun:_Znwm
   ...
   fun:_ZNK6google8protobuf7Message11DebugStringEv
   fun:_ZNK6google8protobuf7Message16PrintDebugStringEv
   ...
}
This suppression is ignored for "--num-callers=20", but works fine (suppresses)
for "--num-callers=40". 
I didn't expect the suppressions to depend on "--num-callers".

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

[valgrind] [Bug 360574] Wrong parameter type for an ashmem ioctl() call on Android and ARM64

[Anton Kirilov via KDE Bugzilla]

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

--- Comment #2 from Anton Kirilov  ---
Yes, I can.

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

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

[Anton Kirilov via KDE Bugzilla]

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

--- Comment #2 from Anton Kirilov  ---
Yes, that is correct. ART also sets up a signal handler for SIGSEGV.

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

[kirigami] [Bug 363798] Make the Action Buttons smaller

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

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

--- Comment #5 from Thomas Pfeiffer  ---
Just built from Master, and on desktop, the drawer handles are 32px hight
whereas the secondary ABs are 40px. Something is wrong here...

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

[plasmashell] [Bug 366351] From a command line start I get black screen and movable pointer but nothing else

[cliff via KDE Bugzilla]

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

--- Comment #5 from cliff  ---
Do you think this is a Frameworks problem or Plasma, before we leave this?

thanks

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

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[via KDE Bugzilla]

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

dajrip...@gmail.com changed:

   What|Removed |Added

 CC|dajrip...@gmail.com |

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

[plasmashell] [Bug 366173] plasma task manager "show only tasks from the current screen" shows the wrong list

[Jan Pavlicek via KDE Bugzilla]

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

Jan Pavlicek  changed:

   What|Removed |Added

 CC||jan.pavli...@centrum.cz

--- Comment #2 from Jan Pavlicek  ---
I can confirm this too, with only 2 screens. Task manager entries are swaped,
windows on the right monitor are showed in taskbar on the left one and vice
versa. Removing and readding the taskbar seems to correct the issue, but it
returns after reboot. It is extremely annoying, making me think about switching
back to 5.6. I'm on ArchLinux, updated daily.

Interesting thing is, that on my desktop PC, if I go to display settings,
disable, apply and then reenable and apply the second monitor, it does not
help. But on my laptop, this fixes the issue and taskbars work as normal
(panels don't remember their positions and get repositioned both on one screen
and I need to manually correct this, but this is another issue).

Second interesting thing is, that on my desktop PC i have a 16:10 a 4:3
screens. I have respective resolution wallpapers and they get swapped too, the
wider one gets black corners and the thinner one is fitted to the screen.

Really hope this gets fixed soon, thanks!

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

[krita] [Bug 364034] Assistant tool icon is not correctly aligned

[z-uo via KDE Bugzilla]

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

--- Comment #4 from z-uo  ---
Comment on attachment 100437
  --> https://bugs.kde.org/attachment.cgi?id=100437
schema

Here the button is not clicable when it is on the same row as the color picker

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

[krita] [Bug 364034] Assistant tool icon is not correctly aligned

[z-uo via KDE Bugzilla]

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

z-uo  changed:

   What|Removed |Added

 CC||nicolas.boug...@z-uo.com

--- Comment #3 from z-uo  ---
Created attachment 100437
  --> https://bugs.kde.org/attachment.cgi?id=100437=edit
schema

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

[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch

[Markus Rechberger via KDE Bugzilla]

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

Markus Rechberger  changed:

   What|Removed |Added

 CC||kont...@sundtek.de

--- Comment #2 from Markus Rechberger  ---
We have a lot customers out there and also several new devices upcoming, if the
plan is to make things incompatible this is not the right way to go.

Mauro is breaking things on purpose, just because he can't do better.

However in order to support DVB a quick way our streamingserver can be used
instead of kaffeine:
http://support.sundtek.com/index.php/topic,2099.0.html

We're still working on it and it's an early version. The streamingserver also
works on ARM, MIPS, PPC, SH4, etc. and is easy to install.
VLC is usually available everywhere so there should not be any problem with it.

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

[plasmashell] [Bug 365139] Inconsistent localization of month names in calendar plasmoid

[Allan via KDE Bugzilla]

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

--- Comment #4 from Allan  ---
Since both the tooltip and calendar plasmoid are using the language for LC_TIME
except for the month on top, shouldn't the month also use the same language as
LC_TIME, without any trickery with LANG?

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

[kmix] [Bug 364141] Kmix crashes when trying to change the volume for individual streams with scrollwheel from systray

[Azamat H . Hackimov via KDE Bugzilla]

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

Azamat H. Hackimov  changed:

   What|Removed |Added

 CC||azamat.hacki...@gmail.com

--- Comment #12 from Azamat H. Hackimov  ---
Created attachment 100436
  --> https://bugs.kde.org/attachment.cgi?id=100436=edit
Fix-for-crashing-on-mousewheel-event-bug-364141.patch

Proposed patch from Fedora packaging
(http://pkgs.fedoraproject.org/cgit/rpms/kmix.git/commit/?id=3c680dd8ef185d2bd4aca22f69a517a988a01d0c)

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

[digikam] [Bug 287081] F2 renames image, not Album in Thumbnails mode

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #6 from Maik Qualmann  ---
Git commit d7f536a4030b664e99210ab696b4d3f4752ee220 by Maik Qualmann.
Committed on 03/08/2016 at 17:18.
Pushed by mqualmann into branch 'master'.

add shortcuts to context menu

M  +1-0app/utils/contextmenuhelper.cpp

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

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

[konversation] [Bug 366370] Konverstatio crash when using TOR

[shured via KDE Bugzilla]

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

--- Comment #2 from shured  ---
I've removed the konversationrc files from the .config. and session directory.
Started konversation, got the default host, clicked the + to open the hosts,
clicked hosts and edit... crash...

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

[digikam] [Bug 366361] createReadWriteLock and createMetadataProcessor should not be pure virtual

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/libk
   ||ipi/860f11a91c9398397246bf5
   ||54e24ff9b8b3adc6d
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Maik Qualmann  ---
Git commit 860f11a91c9398397246bf554e24ff9b8b3adc6d by Maik Qualmann.
Committed on 03/08/2016 at 16:35.
Pushed by mqualmann into branch 'master'.

apply patch #100422 to make implemented methods not pure virtual
FIXED-IN: 5.1.0

M  +2-2src/interface.h

http://commits.kde.org/libkipi/860f11a91c9398397246bf554e24ff9b8b3adc6d

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

[konversation] [Bug 366374] Crash on editing configured server details

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 366333] Plasma-5 crash using sddm as login manager using "users switch".

[Sandro via KDE Bugzilla]

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

--- Comment #7 from Sandro  ---
Excuse me I'm not an expert user.

1) I see on screen:
___
* Il blocco dello schermo non è più possibile.
* Per sbloccare, passa a un terminale virtuale (e.g. Ctrl + Alt + F2)
* Accedi ed esegui il comando:
*** loginctl unblock-session (but it is not present in my system)
* Successivamente, torna alla sessione in esecuzione (Ctrl + Alt+ F7).
__


2) /var/log/messages:

Aug  3 18:07:10 localhost syslog-ng[9245]: syslog-ng starting up;
version='3.7.3'
Aug  3 18:07:17 localhost su[9210]: pam_unix(su:session): session closed for
user root
Aug  3 18:07:27 localhost root[9273]: ACPI event unhandled: jack/lineout
LINEOUT unplug
Aug  3 18:07:27 localhost root[9276]: ACPI event unhandled: jack/videoout
VIDEOOUT unplug
Aug  3 18:07:27 localhost acpid[3539]: client 8830[0:0] has disconnected
Aug  3 18:07:27 localhost acpid[3539]: client connected from 9268[0:0]
Aug  3 18:07:27 localhost acpid[3539]: 1 client rule loaded
Aug  3 18:07:27 localhost kernel: snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid
ELD data byte 6
Aug  3 18:07:28 localhost sddm-helper[9282]: PAM unable to
dlopen(/lib64/security/pam_systemd.so): /lib64/security/pam_systemd.so: cannot
open shared object file: No such file or directory
Aug  3 18:07:28 localhost sddm-helper[9282]: PAM adding faulty module:
/lib64/security/pam_systemd.so
Aug  3 18:07:28 localhost sddm-helper[9282]: pam_unix(sddm-greeter:session):
session opened for user sddm by (uid=0)
Aug  3 18:07:28 localhost root[9319]: ACPI event unhandled: jack/lineout
LINEOUT plug
Aug  3 18:07:28 localhost root[9321]: ACPI event unhandled: jack/videoout
VIDEOOUT plug
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet(sddm:auth): (null):
pam_sm_authenticate
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet5(sddm:auth): (null):
pam_sm_authenticate
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet(sddm:setcred):
pam_kwallet: pam_sm_setcred
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_unix(sddm:session): session
opened for user vincio by (uid=0)
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_ck_connector(sddm:session):
nox11 mode, ignoring PAM_TTY :1
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet(sddm:session):
pam_kwallet: pam_sm_open_session
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet(sddm:session):
pam_kwallet: final socket path: /tmp/kwallet_vincio.socket
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
Aug  3 18:07:35 localhost sddm-helper[9344]: pam_kwallet5(sddm:session):
pam_kwallet5: final socket path: /tmp/kwallet5_vincio.socket
Aug  3 18:07:35 localhost dbus[3569]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Aug  3 18:07:35 localhost dbus[3569]: [system] Successfully activated service
'org.kde.powerdevil.backlighthelper'
Aug  3 18:07:36 localhost polkitd[3647]: Registered Authentication Agent for
unix-session:/org/freedesktop/ConsoleKit/Session20 (system bus name :1.226
[/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path
/org/kde/PolicyKit1/AuthenticationAgent, locale it_IT.UTF-8)
Aug  3 18:07:36 localhost pulseaudio[9593]: [pulseaudio] main.c: Compiled with
DEPRECATED libsamplerate support!
Aug  3 18:07:36 localhost pulseaudio[9593]: [pulseaudio] pid.c: Stale PID file,
overwriting.
Aug  3 18:07:37 localhost obexd[9636]: OBEX daemon 5.39
Aug  3 18:07:37 localhost pulseaudio[9661]: [pulseaudio] main.c: Compiled with
DEPRECATED libsamplerate support!
Aug  3 18:07:37 localhost pulseaudio[9661]: [pulseaudio] pid.c: Daemon already
running.
Aug  3 18:07:37 localhost pulseaudio[9667]: [pulseaudio] main.c: Compiled with
DEPRECATED libsamplerate support!
Aug  3 18:07:37 localhost pulseaudio[9667]: [pulseaudio] pid.c: Daemon already
running.
Aug  3 18:08:03 localhost polkitd[3647]: Unregistered Authentication Agent for
unix-session:/org/freedesktop/ConsoleKit/Session20 (system bus name :1.226,
object path /org/kde/PolicyKit1/AuthenticationAgent, locale it_IT.UTF-8)
Aug  3 18:08:05 localhost kernel: kactivitymanage[9452]: segfault at
7f9ac9942c50 ip 7f9aa2d82e31 sp 7f4241a8 error 4 in
libQt5Sql.so.5.6.1[7f9aa2d6e000+41000]
Aug  3 18:08:06 localhost root[9726]: ACPI event unhandled: jack/lineout
LINEOUT unplug
Aug  3 18:08:06 localhost root[9729]: ACPI event unhandled: jack/videoout
VIDEOOUT unplug
Aug  3 18:08:06 localhost acpid[3539]: client 9268[0:0] has disconnected
Aug  3 18:08:06 localhost acpid[3539]: client connected from 8830[0:0]
Aug  3 18:08:06 localhost acpid[3539]: 1 client rule loaded
Aug  3 18:08:06 localhost root[9746]: ACPI event unhandled: jack/lineout
LINEOUT 

[digikam] [Bug 287081] F2 renames image, not Album in Thumbnails mode

[Frederic Grelot via KDE Bugzilla]

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

--- Comment #5 from Frederic Grelot  ---
I would like to reopen this bug, for two reasons :

-Marcel (in comment #1) said that there is no such possibility in KDE framework
to affect a shortcut without any ambiguity. However, I can't believe that
point, since in every file manager I know, if the "tree" view has the focus and
I hit F2, the folder get renamed, while if the "file" view has it, the
currently selected file is renamed. Am I missing something?
-In the current situation, is it possible to add an hint in the right-click
popup to tell that "Shift+F2" renames the folder?

Actually, I came back to this bug for the second point, because it seems like I
hit it again... I hit "F2" as usual, and was asked to rename a picture. So I
remembered "my" bug, searched for it, and saw in comment #4 that "Shift+F2"
would do the trick : not really straightforward :-)

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

[kate] [Bug 112888] folding without end tags

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[frameworks-kio] [Bug 355441] DAV Resource 16.04.1: Broken state, The item was not deleted on the server.

[Till Schäfer via KDE Bugzilla]

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

--- Comment #13 from Till Schäfer  ---
-> also the mod_rewrite trick did not help me: I do not get a broken state
anymore, but whenever i delete an item, the deletion will silently fail on the
server side and after this fail there is no more synchronization going on at
all.

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

[konversation] [Bug 366374] Crash on editing configured server details

[Eike Hein via KDE Bugzilla]

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

--- Comment #4 from Eike Hein  ---
Tried both, no crash ...

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

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

[Christoph Cullmann via KDE Bugzilla]

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

Christoph Cullmann  changed:

   What|Removed |Added

 CC|cullm...@kde.org|

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

[konversation] [Bug 366374] Crash on editing configured server details

[Luigi Toscano via KDE Bugzilla]

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

--- Comment #3 from Luigi Toscano  ---
Consistently reproduced on a fresh profile, but I was not precise: it is:
Go to "File" menu, "Server List", select a server and expand it (for example,
expand "Freenode"), then select one of the servers ("chat.freenode.net:8001",
not sure it's the upstream default or Fedora's one), and then  press "Edit".

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

[kaddressbook] [Bug 366154] GPG Settings cannot be configured any more

[Laurent Montel via KDE Bugzilla]

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

--- Comment #5 from Laurent Montel  ---
it was a fedora rpm bug.
I discussed with fedora maintainer and he fixed it.

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

[kxkb] [Bug 355261] Low quality input sources flags

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[frameworks-kio] [Bug 355441] DAV Resource 16.04.1: Broken state, The item was not deleted on the server.

[via KDE Bugzilla]

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

tasb...@googlemail.com changed:

   What|Removed |Added

 CC||tasb...@googlemail.com

--- Comment #12 from tasb...@googlemail.com ---
I have the same problem deleting a task  using a davical resource. Creating and
changing tasks seems to get properly synchronized. (This is also using KF5 5.21
on openSuSE 42.1)

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

[kwin] [Bug 366081] kwin's windows stay translucent after moving, become invisible

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kwin
   ||/671740dc70c4d2fb091320c0da
   ||564cf2ea6029b2
 Resolution|--- |FIXED

--- Comment #11 from Martin Gräßlin  ---
Git commit 671740dc70c4d2fb091320c0da564cf2ea6029b2 by Martin Gräßlin.
Committed on 03/08/2016 at 14:16.
Pushed by graesslin into branch 'master'.

Ensure that EffectsHandlerImpl::slotClientShown is only invoked once per Window

Summary:
This fixes a regression introduced with
a1afeded6ae63e47d39fc08480e929c0451c51e8.
The connections were setup every the windowShown signal got emitted.
This caused effects to get multiple singals and start multiple animations
which then do not get cancelled correctly.

The incorrect behavior was most visible in the translucency effect which
did not cancel the move animation and the window stayed translucent.

Test Plan:
New test case which simulates the behavior of the translucency
effect.

Reviewers: #kwin, #plasma, sebas

Subscribers: kwin

Tags: #kwin

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

M  +1-0autotests/integration/CMakeLists.txt
A  +3-0autotests/integration/effects/CMakeLists.txt
A  +185  -0autotests/integration/effects/translucency_test.cpp
[License: GPL (v2)]
M  +1-1effectloader.h
M  +1-0effects.cpp

http://commits.kde.org/kwin/671740dc70c4d2fb091320c0da564cf2ea6029b2

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

[Discover] [Bug 366382] New: Discover crashes with 'better rated' apps

[Alejandro via KDE Bugzilla]

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

Bug ID: 366382
   Summary: Discover crashes with 'better rated' apps
   Product: Discover
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: alejandr...@openmailbox.org

The second column corresponding to better rated apps is not working right. All
apps have a smiley icon and when you try to click on them, discover crashes.

Reproducible: Always

Steps to Reproduce:
1. Open Discover
2. Select a better rated app
3. discover crashes

Actual Results:  
discover crashes

Expected Results:  
show app info

I observed when you open discover, better rated apps show them right, but after
three seconds better rated apps show smileys and crash discover.

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

[kdeconnect] [Bug 366363] Does not load qml files to show in the plasmoid due to new PluginCheck feature

[Aleix Pol via KDE Bugzilla]

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

--- Comment #3 from Aleix Pol  ---
Can you paste us the output of executing: plasmawindowed org.kde.kdeconnect

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

[konversation] [Bug 366374] Crash on editing configured server details

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org

--- Comment #2 from Eike Hein  ---
I can't reproduce either of these crashes.

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

[kdeconnect] [Bug 366363] Does not load qml files to show in the plasmoid due to new PluginCheck feature

[Eldhrimer via KDE Bugzilla]

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

--- Comment #2 from Eldhrimer  ---
I just 'make install'd in /usr/ and the same error appeared:
-
Error al cargar archivo QML:
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:48:34:
Type FullRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/FullRepresentation.qml:55:23:
Type DeviceDelegate unavailable
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/DeviceDelegate.qml:94:13:
Type Battery unavailable
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/Battery.qml:26:1:
PluginChecker is not a type
--
 Also if I uninstall the distro given package, a new error pops up:
---
Error al cargar archivo QML:
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:24:1:
module "org.kde.kdeconnect" is not installed
---
So... It's failing to import the module that it is? I'm a bit confused.

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