[kleopatra] [Bug 372654] New: Cannot get ADELE to respond correctly to my first email with public key attached.

[Ramon Tan]

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

Bug ID: 372654
   Summary: Cannot get ADELE to respond correctly to my first
email with public key attached.
   Product: kleopatra
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: tanra...@gmail.com
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

Created attachment 102314
  --> https://bugs.kde.org/attachment.cgi?id=102314=edit
Entire contents of ADELE email response with error messages

I installed GPG4WIN 2.3.3, created and exported a new key pair successfully.
All self-tests ran perfectly. I sent an email to ad...@gnupp.de  with my public
key as attachment.  I made sure that Outlook 2007 (which I am using) was
configured to send mail in plain text format only, and not HTML.  I got an
error message response back from Adele, saying:

"The following email is rejected because the correctness of the address given
has not been confirmed yet."

The complete email from ADELE is attached.

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

[kile] [Bug 336118] [project website] images kile_big.png and kile.png are broken

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

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

--- Comment #4 from Michel Ludwig  ---
Images have been recreated and they seem to be displayed fine in gwenview and
Konqueror now,

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

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Marax Faraii]

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

--- Comment #10 from Marax Faraii  ---
I rebuild kde-plasma/plasma-workspace after upgrading kde-frameworks/kpackage
and I can confirm it works.

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

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Nikos Chantziaras]

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

--- Comment #11 from Nikos Chantziaras  ---
Thanks.

I think it might be a good idea to revbump plasma-workspace though.

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

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Bhushan Shah]

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

Bhushan Shah  changed:

   What|Removed |Added

 CC||bhus...@gmail.com

--- Comment #9 from Bhushan Shah  ---
(In reply to Nikos Chantziaras from comment #8)
> I've hit a slow mirror. I updated again, and there was an update to
> kpackage, which applies the patch.
> 
> It doesn't fix anything. The same issues are still there.

With that commit in, you also need to rebuild plasma-workspace to fix the
issue. Alternatively you can update plasma-workspace to latest 5.8 branch too

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

[korgac] [Bug 372653] New: korgac crash on startup (korgac version 5.3.3 )

[blambin]

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

Bug ID: 372653
   Summary: korgac crash on startup  (korgac version 5.3.3 )
   Product: korgac
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: blambinn...@gmail.com
  Target Milestone: ---

bug log : 

---

Application: kwin_x11 (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f428587e840 (LWP 797))]

Thread 5 (Thread 0x7f424dc76700 (LWP 877)):
#0  0x7f427e55e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f42818b4ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f42818b4b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f427e558454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f42852c67df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f4261444700 (LWP 874)):
#0  0x7f42852bd551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f428296dac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f428296f3b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f428291c23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f428273f0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f4282743d78 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f427e558454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f42852c67df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f4262445700 (LWP 864)):
#0  0x7f42852bd551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f428296dac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f428296f3b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f428291c23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f428273f0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f427d2b62d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f4282743d78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f427e558454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f42852c67df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f4269567700 (LWP 834)):
[KCrash Handler]
#6  0x7f428294d9cf in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () at /usr/lib/libQt5Core.so.5
#7  0x7f427c494530 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7f427c480f62 in  () at /usr/lib/libQt5DBus.so.5
#9  0x7f4282743d78 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f427e558454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f42852c67df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f428587e840 (LWP 797)):
#0  0x7f427e55e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4282744c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f428274391e in QThread::wait(unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f427c480cc6 in  () at /usr/lib/libQt5DBus.so.5
#4  0x7f427c480d59 in  () at /usr/lib/libQt5DBus.so.5
#5  0x7f4285213990 in __run_exit_handlers () at /usr/lib/libc.so.6
#6  0x7f42852139ea in  () at /usr/lib/libc.so.6
#7  0x7f426bcc4ba3 in  () at /usr/lib/libQt5XcbQpa.so.5
#8  0x7f428294a4b9 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#9  0x7f42835fde0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#10 0x7f4283605581 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#11 0x7f428291dde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#12 0x7f428292056d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#13 0x7f4285583a26 in  () at /usr/lib/libkdeinit5_kwin_x11.so
#14 0x7f4282949659 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#15 0x7f4283f3160b in KSelectionOwner::filterEvent(void*) () at
/usr/lib/libKF5WindowSystem.so.5
#16 0x7f428291b37f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
at /usr/lib/libQt5Core.so.5
#17 0x7f426bcc3c14 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() at /usr/lib/libQt5XcbQpa.so.5
#18 0x7f426bcc48a5 in QXcbConnection::processXcbEvents() () at
/usr/lib/libQt5XcbQpa.so.5
#19 0x7f428294a4b9 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#20 0x7f42835fde0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7f4283605581 in QApplication::notify(QObject*, QEvent*) 

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Nikos Chantziaras]

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

--- Comment #8 from Nikos Chantziaras  ---
I've hit a slow mirror. I updated again, and there was an update to kpackage,
which applies the patch.

It doesn't fix anything. The same issues are still there.

Please reopen this bug.

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

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Nikos Chantziaras]

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

--- Comment #7 from Nikos Chantziaras  ---
This bug was closed as "FIXED". So what do I do? There's no update in portage
or anything.

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

[krita] [Bug 362881] Crash when applying transform

[Richard Raimund]

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

Richard Raimund  changed:

   What|Removed |Added

 CC||spamgoesh...@tutanota.com

--- Comment #13 from Richard Raimund  ---
Same for me, crashes each time transform mask applied, no crashes with
transform tool though.

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Alexey Putz]

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

--- Comment #6 from Alexey Putz  ---
I 've managed to drag from Gwenview 16.04.3 , I just needed to open thumbnail
bar to drag from it.

Digikam 5 is still unable to drag from albums. But can drag to Dolphin from
Digikam 5. 

digiKam
Version 5.3.0

Kubuntu 16.10
KDE Plasma Version : 5.7.5
KDE Frameworks Version : 5.26.0
Qt Version : 5.6.1
Kernel Version : 4.8.0-22-generic
OS Type: 64-bit

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Rafael]

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

Rafael  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #5 from Rafael  ---
> About Gwenview, I wasn't able to drag from it as far as primary tool in this
> program is "navigating" hand, and it doesn't drag anything.
Well, Gwenview is the "smaller brother" of Digikam, that's to say, you can
explore image thumbnails and manipulate them, or view them. If you hit "ESC"
key in Gwenview, you will see images thumbnails.
> 
> GIMP 2.8.18
> 
> Dolphin 16.04.3
> 
> Kubuntu 16.10
> KDE Plasma Version : 5.7.5
> KDE Frameworks Version : 5.26.0
> Qt Version : 5.6.1
> Kernel Version : 4.8.0-22-generic
> OS Type: 64-bit

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

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

[Michael Butash]

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

--- Comment #245 from Michael Butash  ---
So far, I've not been able to make 5.8.3 behave in the least in terms of
keeping the task bar entirely sticky to the actual intended monitor using
either nvidia-settings or kde settings/display.  They definitely do not get
along, today I got sick of having it crash every day to force a hard reboot and
had some time to fiddle with it.

I did try as well the script mentioned here for giggles, which didn't do
anything for me at all.

I set up nvidia-settings as the defacto, and let it create an xorg.conf file
just to let it setup as standard old school style.  My intention is always to
use my middle display, dp-2 as the "primary" for the taskbar to be sticky to,
but not since my old desktop on 5.7.2 can I get it to stay.  I shutdown sddm
from alt vty, and removed .config/plasma*, .config/kwin*, and
.local/share/kscreen/* to reset things, and has so far helped some, but the
taskbar doesn't stay still when I shut off all displays, and most annoyingly,
it resets my center wallpaper every time.  Same as it was in 5.5.x ubuntu 16.04
shipped with.

I have not used kde display properties since clearing these out.  I tried
rearranging the dp-2 as the primary display as per the nvidia xorg.conf
setting, which only seemed to confuse kde more to move things around again.  I
had to reset the xorg.conf file again with nvidia-settings to get the taskbar
back there, and reset my wallpaper.

I shut down all 3 displays again, again the center wallpaper resets, and the
taskbar jumps over to dp-0 on the left.  Cairo-dock, which I seat atop in the
center stays there, it is set to use what it sees as "Screen 0 (middle)", which
seems to reflect what I had set xorg to, making the "middle" dp-2 as primary.

Almost every time, once I've shut the displays off and on at least 2 times,
almost certainly, the next time, it simply doesn't wake up fully, and crashes.

Here's my xrandr -q and xorg.conf currently.  I see nothing obviously wrong
from .local/share/kscreen/kscreen.log, but I can post that as well with some
notation of events if helpful

user@host:~$ xrandr -q
Screen 0: minimum 8 x 8, current 11520 x 2160, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 1872mm
x 1053mm
   3840x2160 60.00*+  59.9450.0029.9725.0023.98  
   4096x2160 59.9450.0029.9725.0024.0023.98  
   1920x1080 60.0059.9450.0029.9725.0023.9760.00   
50.04  
   1680x1050 59.95  
   1600x900  60.00  
   1440x900  59.89  
   1366x768  59.79  
   1280x1024 75.0260.02  
   1280x800  59.81  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.32  
   720x576   50.0050.08  
   720x480   59.9460.05  
   640x480   75.0072.8159.94  
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 3840x2160+3840+0 (normal left inverted right x axis y
axis) 1872mm x 1053mm
   3840x2160 60.00*+  59.9450.0029.9725.0023.98  
   4096x2160 59.9450.0029.9725.0024.0023.98  
   1920x1080 60.0059.9450.0029.9725.0023.9760.00   
50.04  
   1680x1050 59.95  
   1600x900  60.00  
   1440x900  59.89  
   1366x768  59.79  
   1280x1024 75.0260.02  
   1280x800  59.81  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.32  
   720x576   50.0050.08  
   720x480   59.9460.05  
   640x480   75.0072.8159.94  
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 connected 3840x2160+7680+0 (normal left inverted right x axis y axis)
1872mm x 1053mm
   3840x2160 60.00*+  59.9450.0029.9725.0023.98  
   4096x2160 59.9450.0029.9725.0024.0023.98  
   1920x1080 60.0059.9450.0029.9725.0023.9760.00   
50.04  
   1680x1050 59.95  
   1600x900  60.00  
   1440x900  59.89  
   1366x768  59.79  
   1280x1024 75.0260.02  
   1280x800  59.81  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.32  
   720x576   50.0050.08  
   720x480   59.9460.05  
   640x480   75.0072.8159.94  
DP-5 disconnected (normal left inverted right x axis y axis)
user@host:~$ cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 361.42  (buildd@lgw01-18)  Tue Apr  5 14:33:28 UTC
2016

Section 

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Alexey Putz]

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

--- Comment #4 from Alexey Putz  ---
I suppose that GIMP do support XDND.
Found a quote about XDND:
XDND defines a standard for drag and drop on X11. It is implemented by GTK+.

Dragging from Dolphin to GIMP do work.
About Gwenview, I wasn't able to drag from it as far as primary tool in this
program is "navigating" hand, and it doesn't drag anything.

GIMP 2.8.18

Dolphin 16.04.3

Kubuntu 16.10
KDE Plasma Version : 5.7.5
KDE Frameworks Version : 5.26.0
Qt Version : 5.6.1
Kernel Version : 4.8.0-22-generic
OS Type: 64-bit

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

[krita] [Bug 372605] alt-draging frames outside loaded time line length crashes Krita

[bugzilla_noreply]

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

--- Comment #2 from apelsinchok...@gmail.com ---
https://www.dropbox.com/s/ryhna616mdqfce0/krita%20timeline%20crash.m4v?dl=0

(lldb) bt
* thread #1: tid = 0x2be56, 0x000100502b74
libkritaui.15.dylib`KisNodeDummy::node() const + 4, queue =
'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x20)
  * frame #0: 0x000100502b74 libkritaui.15.dylib`KisNodeDummy::node() const
+ 4
frame #1: 0x00011ca281a4
kritaanimationdocker.so`TimelineFramesModel::nodeAt(QModelIndex) const + 36
frame #2: 0x00011ca25c87
kritaanimationdocker.so`KisTimeBasedItemModel::offsetFrames(QList,
QPoint const&, bool, KUndo2Command*) + 359
frame #3: 0x00011ca2a19e
kritaanimationdocker.so`TimelineFramesModel::dropMimeData(QMimeData const*,
Qt::DropAction, int, int, QModelIndex const&) + 446
frame #4: 0x000101f3864f
QtWidgets`QAbstractItemView::dropEvent(QDropEvent*) + 191
frame #5: 0x00011ca3108e
kritaanimationdocker.so`TimelineFramesView::dropEvent(QDropEvent*) + 46
frame #6: 0x000101d033a3 QtWidgets`QWidget::event(QEvent*) + 2611
frame #7: 0x000101dfe28d QtWidgets`QFrame::event(QEvent*) + 45
frame #8: 0x000101e8e317
QtWidgets`QAbstractScrollArea::viewportEvent(QEvent*) + 135
frame #9: 0x000101f35cc5
QtWidgets`QAbstractItemView::viewportEvent(QEvent*) + 1397
frame #10: 0x000101e8efb4
QtWidgets`___lldb_unnamed_function2750$$QtWidgets + 36
frame #11: 0x000102a6ddab
QtCore`QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
QEvent*) + 203
frame #12: 0x000101cc2a65
QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 293
frame #13: 0x000101cc47c4 QtWidgets`QApplication::notify(QObject*,
QEvent*) + 2836
frame #14: 0x0001007dc058
libkritaui.15.dylib`KisApplication::notify(QObject*, QEvent*) + 24
frame #15: 0x000102a6db14
QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164
frame #16: 0x000101d25a87
QtWidgets`___lldb_unnamed_function533$$QtWidgets + 631
frame #17: 0x000101d2341e
QtWidgets`___lldb_unnamed_function520$$QtWidgets + 1022
frame #18: 0x000101cc2a7a
QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 314
frame #19: 0x000101cc3eae QtWidgets`QApplication::notify(QObject*,
QEvent*) + 510
frame #20: 0x0001007dc058
libkritaui.15.dylib`KisApplication::notify(QObject*, QEvent*) + 24
frame #21: 0x000102a6db14
QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164
frame #22: 0x00010233fbe0
QtGui`QGuiApplicationPrivate::processDrop(QWindow*, QMimeData const*, QPoint
const&, QFlags) + 96
frame #23: 0x000102323a45
QtGui`QWindowSystemInterface::handleDrop(QWindow*, QMimeData const*, QPoint
const&, QFlags) + 213
frame #24: 0x000107e95e5a
libqcocoa.dylib`___lldb_unnamed_function385$$libqcocoa.dylib + 346
frame #25: 0x7fff86e6b975 AppKit`NSCoreDragReceiveMessageProc + 289
frame #26: 0x7fff88d51e94 HIServices`DoMultipartDropMessage + 325
frame #27: 0x7fff88d51ba5 HIServices`DoDropMessage + 41
frame #28: 0x7fff88d51b4f HIServices`SendDropMessage + 41
frame #29: 0x7fff88d4e11e HIServices`DragInApplication + 512
frame #30: 0x7fff88d4d177 HIServices`CoreDragStartDragging + 519
frame #31: 0x7fff86e67a54 AppKit`-[NSCoreDragManager
_dragUntilMouseUp:accepted:] + 862
frame #32: 0x7fff8701f3a4 AppKit`-[NSCoreDragManager
dragImage:fromWindow:at:offset:event:pasteboard:source:slideBack:] + 1355
frame #33: 0x7fff8730585b AppKit`-[NSWindow(NSDrag)
dragImage:at:offset:event:pasteboard:source:slideBack:] + 133
frame #34: 0x000107eb9266
libqcocoa.dylib`___lldb_unnamed_function948$$libqcocoa.dylib + 726
frame #35: 0x00010235032d QtGui`QDragManager::drag(QDrag*) + 189
frame #36: 0x00010234f868 QtGui`QDrag::exec(QFlags,
Qt::DropAction) + 88
frame #37: 0x00011ca30b40
kritaanimationdocker.so`TimelineFramesView::startDrag(QFlags) +
3328
frame #38: 0x000101f365d1
QtWidgets`QAbstractItemView::mouseMoveEvent(QMouseEvent*) + 433
frame #39: 0x00011ca32115
kritaanimationdocker.so`TimelineFramesView::mouseMoveEvent(QMouseEvent*) + 229
frame #40: 0x000101d02fc9 QtWidgets`QWidget::event(QEvent*) + 1625
frame #41: 0x000101dfe28d QtWidgets`QFrame::event(QEvent*) + 45
frame #42: 0x000101e8e317
QtWidgets`QAbstractScrollArea::viewportEvent(QEvent*) + 135
frame #43: 0x000101f35cc5
QtWidgets`QAbstractItemView::viewportEvent(QEvent*) + 1397
frame #44: 0x000101e8efb4
QtWidgets`___lldb_unnamed_function2750$$QtWidgets + 36
frame #45: 0x000102a6ddab
QtCore`QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*,
QEvent*) + 203
frame #46: 0x000101cc2a65
QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 293
frame #47: 0x000101cc5c93 

[krita] [Bug 372612] 歪みツールでレイヤーが消える。

[栗田]

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

--- Comment #4 from 栗田  ---
tokiedianさん日本語でご案内を頂き大変助かります。
誠にありがとうございます。
私の環境を・・・Krita3.0.92β（Zipアーカイブポータブル版）です。
GPU環境は、オンボードのintel HD Graphics4000　ドライバー 4.0.0 - Build
9.17.10.2963です。OpenGL3.0/4.0対応になっているので、OpenGL的な問題ではないと思うのですが...？
とりあえず、V=3.0.0.1.1（安定版）までは問題ありませんでした。

【--問題状況詳細です。--】
変形ツール ＞ 歪み　で、画面を拡大するとレイヤーが消えるか、歪み状況が表示されませんでした。
画面を縮小するとレイヤー表示も歪み状況も反映されていました。

【--今回とった対応です。--】
教えて下さったGPUの問題を解決すべく、Krita環境設定のパフォーマンスタブにある【進行報告を有効にする】というチェックボックスのチェックを外して問題が解決しました。この行為が他の操作にどのような影響を与えるかについてはまだ分かりません。

以上の状態です。ご案内頂き大変助かりました。Kritaは、GIMPより高機能な感じなので大変興味深く使わせて貰っています。また分からない事があったら日本語質問上げさせて頂きます。その時はどうぞ宜しくお願いします。

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

[dolphin] [Bug 372652] New: The process for the mtp protocol died unexpectedly.

[Peter]

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

Bug ID: 372652
   Summary: The process for the mtp protocol died unexpectedly.
   Product: dolphin
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: plowe...@tampabay.rr.com
  Target Milestone: ---

trying too access my android phone with my computer I received the following
message: The process for the mtp protocol died unexpectedly.

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

[plasmashell] [Bug 372651] New: Plasma crash after update

[bugzilla_noreply]

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

Bug ID: 372651
   Summary: Plasma crash after update
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: olipro...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.8-2-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I updated some packages (with pacman) and while upgrading an unrelated package
(not sure between networkmanager-qt and oxygen-icons), plasma crashed. 
I noticed that plasmaframework updated a bit before so it could be the source
of the crash. I haven't come across another crash yet.

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

Thread 10 (Thread 0x7f32ad4b0700 (LWP 6071)):
#0  0x7f336ff37dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f336fef2171 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f336fef2724 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f336fef289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f337554c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f33754f623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f33753190f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f32af9dc0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#8  0x7f337531dd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f337442d454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f3374c337df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f32c21c8700 (LWP 5880)):
#0  0x7f33753152e9 in QMutex::unlock() () at /usr/lib/libQt5Core.so.5
#1  0x7f337554c015 in  () at /usr/lib/libQt5Core.so.5
#2  0x7f336fef2179 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f336fef2724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f336fef289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f337554c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f33754f623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f33753190f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f337921b856 in  () at /usr/lib/libQt5Quick.so.5
#9  0x7f337531dd78 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f337442d454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f3374c337df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f32c7b35700 (LWP 5869)):
#0  0x7f337443310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32cb961ec3 in  () at /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f32cb961d27 in  () at /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f337442d454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3374c337df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f32c8336700 (LWP 5868)):
#0  0x7f337443310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32cb961ec3 in  () at /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f32cb961d27 in  () at /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f337442d454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3374c337df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f3355900700 (LWP 5866)):
#0  0x7f337443310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f337acabac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f337acabb09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f337442d454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3374c337df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f335759a700 (LWP 5850)):
#0  0x7f3374c2a48d in poll () at /usr/lib/libc.so.6
#1  0x7f336fef2786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f336fef289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f337554c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f33754f623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f33753190f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f337867c2d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f337531dd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f337442d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f3374c337df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f335d391700 

[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Chris]

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

--- Comment #124 from Chris  ---
New drivers with new kernel were recently released, Linux 4.8.8 and Nvidia
375.20. The problem isn't solved yet. There is a recently active thread on
Nvidia's forums about an issue with resume-from-suspend that may be related, so
I posted there.
https://devtalk.nvidia.com/default/topic/919984/linux/resume-from-suspend-not-working-with-980-ti-drivers-352-370-kernels-3-16-4-4/

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

[kstars] [Bug 372649] EKOS focus module claims it is focusing when it is not

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/ksta
   ||rs/198cf16d7fb164dd2ad37f74
   ||8877c40b10805411
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Jasem Mutlaq  ---
Git commit 198cf16d7fb164dd2ad37f748877c40b10805411 by Jasem Mutlaq.
Committed on 19/11/2016 at 00:51.
Pushed by mutlaqja into branch 'master'.

Consider wait stage prior to progress so that other modules are not blocked
while in the waiting period which should expire after a particular timeout.

M  +1-1kstars/ekos/align/align.cpp
M  +2-2kstars/ekos/ekos.h
M  +16   -4kstars/ekos/focus/focus.cpp
M  +3-0kstars/ekos/focus/focus.h

http://commits.kde.org/kstars/198cf16d7fb164dd2ad37f748877c40b10805411

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

[digikam] [Bug 372650] New: When tagging multiple images a few sidecars get truncated, on OS X.

[Philip Tuckey]

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

Bug ID: 372650
   Summary: When tagging multiple images a few sidecars get
truncated, on OS X.
   Product: digikam
   Version: 5.3.0
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: philip.tuc...@free.fr
  Target Milestone: ---

Digikam is configured to write to sidecars only.
Select multiple images, e.g. about 100.
Apply the same tag to all of them, using the Captions pane.
For most images the sidecars are updated correctly, but for a few of them the
sidecars are truncated to just their first line. This affects a different
subset of files each time a tag is applied, apparently at random.
The console output shows most sidecars being written without error messages,
while for the few files concerned it shows:

digikam.metaengine: Exiv2 ( 3 ) :  XMP Toolkit error 101: Unregistered schema
namespace URI
digikam.metaengine: Exiv2 ( 3 ) :  Failed to encode XMP metadata.

This behaviour happens on OS X.
Running under linux (ubuntu) in a virtual machine I do NOT see the same
problem.

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

[kio] [Bug 347715] Konsole (KF5) freezes trying to open http url with rpm package

[Anatoly Roschenya]

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

Anatoly Roschenya  changed:

   What|Removed |Added

 CC||anatol.ro...@gmail.com

--- Comment #17 from Anatoly Roschenya  ---
(In reply to Martin Sandsmark from comment #1)
> KDE uses kio, which by default opens URLs in the appropriate application
> based on mimetype (text files are opened in your text editor, images are
> opened in your image viewer, packages are opened in your package manager,
> etc.).
> 
> If you want to change this behaviour go to System Settings, Applications,
> Default Applications, Web Browser and change the setting there to whatever
> you want.

I arrived at this report while researching a different problem. My mistake was
the same, so i'll just explain it for fellow idiots. 

In my case the URL being fed to kio was a https link with a bad certificate;
instead of launching the web browser, konsole first fired up a "Server
Authentication" window listing the reasons why the server failed the
authenticity check. After agreeing to continue anyway, i got my browser which
offered a similar certificate error. There's really no point in kio's warning
before going to the browser, but it can't be helped because kio wants to
retrieve the mimetype and needs to establish a https connection before knowing
to launch the browser.

What's worse is that on certain URLs this warning never appeared - the
notification window freezes and i get myself a handful of unaccessible konsole
tabs. Killing the frozen warning window killed the parent along with all its
tabs. I never cared to debug what was causing the freeze, likely local to my
build, but the resolution is to set the default web browser. Thanks Martin!

Another case for this: with kio, dead URLs get no launch feedback from konsole,
only a very tiny plasma notification, and a timeout pop-up after the timeout,
which leaves you lost until it appears. Expected behaviour would be for kio to
trigger launch feedback while attempting to connect, should this be filed
somewhere?

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

[kstars] [Bug 372649] New: EKOS focus module claims it is focusing when it is not

[Hans Lambermont]

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

Bug ID: 372649
   Summary: EKOS focus module claims it is focusing when it is not
   Product: kstars
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: h...@lambermont.dyndns.org
  Target Milestone: ---

The EKOS focus module can be controlled manually by pressing 'capture' and then
'focus in' and 'focus out'. In this use case it prevents the main CCD imaging
camera to work as that one then reports 'cannot capture while focus module is
busy'. The focus module is not active. Its 'Stop' button is greyed out which is
good of course, just confirming it's not active.

As a workaround I instructed the focus module to complete an additional 'Auto
focus' round. When that completed the main CCD imaging camera can work.

kstars-bleeding PPA under Ubuntu 16.04.1 , 4.4.0-47-generic kernel.
kstars-bleeding 5:16.10+201611151019~ubuntu16.04.1

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

[kstars] [Bug 372648] New: Save from preview crashes EKOS

[Hans Lambermont]

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

Bug ID: 372648
   Summary: Save from preview crashes EKOS
   Product: kstars
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: h...@lambermont.dyndns.org
  Target Milestone: ---

EKOS Camera tab, add an exposure to the sequence queue, click preview button,
the preview window pops up with the image in it. So far so good.

Now click 'save' in the preview window. Immedate crash. This has been happening
for at least a month using various kstars/EKOS versions from kstars-bleeding
PPA under Ubuntu 16.04.1 . Todays' crash was on 4.4.0-47-generic kernel.
kstars-bleeding 5:16.10+201611151019~ubuntu16.04.1

Here's the backtrace :

#0  0x73c46efc in QUrl::~QUrl() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x00664107 in FITSTab::saveFile (this=0x4887d60) at
/build/kstars-bleeding-NXAMd5/kstars-bleeding-16.10+201611151019~ubuntu16.04.1/kstars/fitsviewer/fitstab.cpp:261
#2  0x0065fbbe in FITSViewer::saveFile (this=) at
/build/kstars-bleeding-NXAMd5/kstars-bleeding-16.10+201611151019~ubuntu16.04.1/kstars/fitsviewer/fitsviewer.cpp:601
#3  0x005a6f05 in FITSViewer::qt_static_metacall (_o=,
_c=, _id=, _a=) at
/build/kstars-bleeding-NXAMd5/kstars-bleeding-16.10+201611151019~ubuntu16.04.1/obj-x86_64-linux-gnu/kstars/moc_fitsviewer.cpp:205
#4  0x73d21d2a in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x74ac5412 in QAction::triggered(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x74ac7898 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x74bcd560 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x74bcd694 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x74c9214a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x74b11f88 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x74c92229 in QToolButton::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x74acf05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x74ad4c19 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x73cf338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x74ad3b32 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x74b2c57b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x74b2eb3b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x74acf05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x74ad4516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x73cf338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7451e4e1 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#22 0x745201a5 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#23 0x74503f08 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#24 0x7fffe4ef0060 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#25 0x7fffef0fc1a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7fffef0fc400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fffef0fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x73d497cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x73cf0b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x73cf8bec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00483cf3 in main (argc=1, argv=) at
/build/kstars-bleeding-NXAMd5/kstars-bleeding-16.10+201611151019~ubuntu16.04.1/kstars/main.cpp:277

This seems hard to reproduce on other systems (save from preview works for
lupinix and knro) but it always reproduces on my system.

-- 
You are 

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[Ralf Habacker]

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

--- Comment #17 from Ralf Habacker  ---
Comment on attachment 102312
  --> https://bugs.kde.org/attachment.cgi?id=102312
Turn PinPortBase into real child widget.

A quick look shows that the following code 

+foreach(QGraphicsItem* item, widget->childItems()) {
+UMLWidget* child = dynamic_cast(item);
+QDomDocument doc;
+m_children.append(doc.createElement(QLatin1String("child")));
+child->saveToXMI(doc, m_children.back());
+}
+

needs to goto into ComponentWidget::saveToXMI()

and this
+foreach(QDomElement childElement, m_children) {
+widgetElement = childElement.firstChild().toElement();
+widget = umlScene->loadWidgetFromXMI(widgetElement);
+if (0 != widget) {
+addWidgetToScene(widget);
+}
+}

into ComponentWidget::loadToXMI() to support also saving to and loading from
file. 

If this is fixed I'm going to test this implementation. Thanks for
contribution.

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

[kdenlive] [Bug 371707] Allow disabling audio scrub

[bugzilla_noreply]

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

--- Comment #7 from qubo...@gmail.com ---
Created attachment 102313
  --> https://bugs.kde.org/attachment.cgi?id=102313=edit
volume icon in the bottom (timeline) bar

Audio scrub would be well placed next to show audio or video thumbnails, as
it's another representation of the  timeline. It can be just a volume/speaker
icon.

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

[gwenview] [Bug 372647] Gwenview crashes on zooming/magnifying

[bugzilla_noreply]

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

--- Comment #2 from benjamin.s...@gmail.com ---
Furthermore it only seems to happen with grayscale (png) images. With rgb png I
cannot reproduce the crash, regardless of mousewheel or slider.

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

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[bugzilla_noreply]

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

--- Comment #16 from clush...@gmx.net ---
I could reproduce the crash. It's due to remove undo not restoring the child
widgets. Subsequent undo commands assume the child widget exists and access a
deleted widget.
I've splitted and updated the patch to fix this issue as well.

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

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[bugzilla_noreply]

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

clush...@gmx.net changed:

   What|Removed |Added

 Attachment #102196|0   |1
is obsolete||

--- Comment #15 from clush...@gmx.net ---
Created attachment 102312
  --> https://bugs.kde.org/attachment.cgi?id=102312=edit
Turn PinPortBase into real child widget.

(2/2) PinPortBase as child widget: Turn PinPortBase into real child widget.

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

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[bugzilla_noreply]

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

--- Comment #14 from clush...@gmx.net ---
Created attachment 102311
  --> https://bugs.kde.org/attachment.cgi?id=102311=edit
Restrict write access to UMLScene::widgetList to track NULL-pointer list
entries.

(1/2) PinPortBase as child widget: Restrict write access to
UMLScene::widgetList to track NULL-pointer list entries.

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

[gwenview] [Bug 372647] Gwenview crashes on zooming/magnifying

[bugzilla_noreply]

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

--- Comment #1 from benjamin.s...@gmail.com ---
It seems to only happen if I use the slider widget in the bottom left. Control
+ mouse wheel does not crash.

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

[gwenview] [Bug 372647] New: Gwenview crashes on zooming/magnifying

[bugzilla_noreply]

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

Bug ID: 372647
   Summary: Gwenview crashes on zooming/magnifying
   Product: gwenview
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: benjamin.s...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

Application: gwenview (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.27-2-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
When I magnify an image in gwenview it often, but not always crashes.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc24bb679c0 (LWP 22384))]

Thread 3 (Thread 0x7fc231420700 (LWP 22386)):
#0  0x7fc2402167b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc2401d4969 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc2401d5230 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc2401d542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc246dfb32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc246da8fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc246be3f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc2461981d5 in  () at /usr/lib64/libQt5DBus.so.5
#8  0x7fc246be89e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc2406f9734 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc2464f2d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc233420700 (LWP 22385)):
#0  0x7fc2464ea49d in poll () at /lib64/libc.so.6
#1  0x7fc23e2543e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc23e255fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc23578a839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc246be89e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc2406f9734 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc2464f2d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc24bb679c0 (LWP 22384)):
[KCrash Handler]
#6  0x7fc245337cf0 in  () at /usr/lib64/liblcms2.so.2
#7  0x7fc24533e77b in  () at /usr/lib64/liblcms2.so.2
#8  0x7fc24b26aab1 in Gwenview::RasterImageView::updateFromScaler(int, int,
QImage const&) () at /usr/lib64/libgwenviewlib.so.5
#9  0x7fc246dd51c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fc24b2d3611 in Gwenview::ImageScaler::scaledRect(int, int, QImage
const&) () at /usr/lib64/libgwenviewlib.so.5
#11 0x7fc24b28ed74 in Gwenview::ImageScaler::scaleRect(QRect const&) () at
/usr/lib64/libgwenviewlib.so.5
#12 0x7fc24b28efaf in Gwenview::ImageScaler::doScale() () at
/usr/lib64/libgwenviewlib.so.5
#13 0x7fc24b26972c in Gwenview::RasterImageView::updateBuffer(QRegion
const&) () at /usr/lib64/libgwenviewlib.so.5
#14 0x7fc24b269863 in Gwenview::RasterImageView::onZoomChanged() () at
/usr/lib64/libgwenviewlib.so.5
#15 0x7fc24b25c15f in  () at /usr/lib64/libgwenviewlib.so.5
#16 0x7fc24b2641c3 in Gwenview::DocumentView::setZoom(double) () at
/usr/lib64/libgwenviewlib.so.5
#17 0x7fc246dd51c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7fc24b2d3d60 in Gwenview::ZoomWidget::zoomChanged(double) () at
/usr/lib64/libgwenviewlib.so.5
#19 0x7fc24b2c3cf3 in Gwenview::ZoomWidget::slotZoomSliderActionTriggered()
() at /usr/lib64/libgwenviewlib.so.5
#20 0x7fc246dd4bb1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#21 0x7fc24858f381 in QAbstractSlider::actionTriggered(int) () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7fc24858f9b9 in
QAbstractSlider::triggerAction(QAbstractSlider::SliderAction) () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7fc248623418 in QSlider::mouseMoveEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#24 0x7fc2484d784e in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#25 0x7fc248623a66 in QSlider::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#26 0x7fc248495e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#27 0x7fc24849ad14 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#28 0x7fc246daafc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#29 0x7fc248499a10 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQt5Widgets.so.5
#30 

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[Herr Schmidt]

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

Herr Schmidt  changed:

   What|Removed |Added

 CC|wettererscheinung@bb-goetti |
   |ngen.de |

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

[umbrello] [Bug 352858] Crash on setting multiplicity on a self referencing association

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

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

--- Comment #1 from Ralf Habacker  ---
I could not reproduce this issue with a compiled version 2.15.3. Because there
is no backtrace added to this ticket it is not possible to find the root cause
by looking at the code. If this problem persists with recent versions feel free
to reopen this bug with a related backtrace.

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[Luke-Jr]

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

Luke-Jr  changed:

   What|Removed |Added

 CC||luke-jr+kdeb...@utopios.org

--- Comment #250 from Luke-Jr  ---
Got the same crash as awilfox here with 5.7.5

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

[kmymoney4] [Bug 372547] Unable to load some investments on KF5

[allan]

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

--- Comment #2 from allan  ---
@ lukasz.wojnilow...@gmail.com

Hi Łukasz/Anyone, Do you have any interest in resolving this issue?
I've had a first go at restoring the widgets that were removed and have had to
reorganise some of the others, trying to keep together those logically related.

If you are still interested, I can add attachments here.  I've not had
time/opportunity to look into revising the coding.
Allan

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

[bomber] [Bug 363573] The game could be auto paused when you click on any menu item

[Sebastian Dicke]

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

Sebastian Dicke  changed:

   What|Removed |Added

 CC||sdi...@live.de

--- Comment #1 from Sebastian Dicke  ---
It would be helpful to play the game.

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

[krita] [Bug 372646] Unable to pan after picking color from reference image until canvas is clicked once first

[Andy Statia]

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

--- Comment #1 from Andy Statia  ---
This issue also appears to affect the colour picker (and probably any tool
change prompted by a keyboard shortcut).

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

[Breeze] [Bug 358224] breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable

[bugzilla_noreply]

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

--- Comment #5 from k...@part4.tech ---
(In reply to David Kahles from comment #4)
> (In reply to kde from comment #2)
> > Can this be switched from resolved? I'm having the same issue with Anki
> > which is still using QT4. The problem also effects input fields.
> 
> Do you have this problem only with Anki, or with some KDE applications too?
> Because I remember that Anki hardcodes some colors, and uses some other
> colors from the theme, so it's hard to read with some themes. (On your
> screenshot it looks like Anki hardcodes the font color to black, but uses
> the background color of the theme)
> If that's the case, you should report this bug to Anki.

Thanks. I'll report it upstream.

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

[krita] [Bug 372646] New: Unable to pan after picking color from reference image until canvas is clicked once first

[Andy Statia]

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

Bug ID: 372646
   Summary: Unable to pan after picking color from reference image
until canvas is clicked once first
   Product: krita
   Version: 3.1 Beta
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: asta...@neverdot.com
  Target Milestone: ---

When using the reference image docker to pick a colour, it is not possible to
immediately pan using the pan shortcut (typically spacebar).  The tool icon
still shows the last active tool, such as fill or brush, despite the pan
shortcut being pressed.  One must first click somewhere outside the reference
image before the tool will switch to the pan tool.

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

[LabPlot2] [Bug 372591] Doesn't work with dark theme

[Alexander Semke]

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

Alexander Semke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[dolphin] [Bug 369523] DolphinPart: Cannot paste without refreshing the destination tab/window

[sebaro]

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

--- Comment #5 from sebaro  ---
The patch works for me, dolphin & konqueror from git.

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

[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw

[María]

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

--- Comment #46 from María  ---
One thing I've noticed is that cleaning all krita remnants on the computer and
starting with a new workspace any version works better, not specific problems
but crash and hung with no apparent commun reason are very scarce after that
thorough cleaning. But afterwards, with more use of the program,  they are more
frecuently. So I thinking if it is possible that some things are accumulating
in the registry that causes those crashes and hungs with apparent nonsense. 
In the same way I have noticed that it is not the same to try a new version
downloading it on the previous one than starting from scratch with a new
workspace.

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

[kde-windows] [Bug 363613] emerge --package does not remove hard links to build path from executables

[Hannah von Reth]

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

Hannah von Reth  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED
 Resolution|WORKSFORME  |REMIND
 CC||vonr...@kde.org

--- Comment #1 from Hannah von Reth  ---
Looks like all dbus services are affected.
I think they should not use an absolute path on windows at all.
Maybe we could add something in ecm for that?

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

[minuet] [Bug 372645] New: [Feature Request] Pubish app to F-Droid

[Kolya Ay]

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

Bug ID: 372645
   Summary: [Feature Request] Pubish app to F-Droid
   Product: minuet
   Version: unspecified
  Platform: Other
OS: Android 5.x
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sandroandr...@kde.org
  Reporter: kolya...@gmail.com
  Target Milestone: ---

I don't know if it's the right place for such kind of requests. Sorry if I make
noise in bug tracker;)

However it would be cool to promote the free software repo
https://f-droid.org/contribute/

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

[kde-windows] [Bug 363613] emerge --package does not remove hard links to build path from executables

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 350279] System monitor incorrect width when in panel

[Rafael]

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

--- Comment #5 from Rafael  ---
(In reply to David Edmundson from comment #3)
> Each applet specifies it's own size, if other applets do things wrong they
> need separate bug reports please.

The applets that do this bad work come with Plasma. How to contact with their
developers? I can't find something like "applet" in bug reports.

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[bugzilla_noreply]

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

--- Comment #16 from alvinhoc...@gmail.com ---
Git commit 927781453f601cef80cdd75ea510b1e3fb89b4a4 by Alvin Wong.
Committed on 18/11/2016 at 19:51.
Pushed by alvinwong into branch 'krita/3.1'.

Fix bent stabilizer finishing line segment
Maniphest Tasks: T4182

M  +5-1libs/ui/tool/kis_stabilized_events_sampler.cpp
M  +3-3libs/ui/tool/kis_tool_freehand_helper.cpp

http://commits.kde.org/krita/927781453f601cef80cdd75ea510b1e3fb89b4a4

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[bugzilla_noreply]

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

--- Comment #15 from alvinhoc...@gmail.com ---
Git commit 768c1e6529b84b20a3446d29b765a0d8912144a4 by Alvin Wong.
Committed on 18/11/2016 at 19:48.
Pushed by alvinwong into branch 'rempt/impex-refactoring'.

Fix bent stabilizer finishing line segment
Maniphest Tasks: T4182

M  +5-1libs/ui/tool/kis_stabilized_events_sampler.cpp
M  +3-3libs/ui/tool/kis_tool_freehand_helper.cpp

http://commits.kde.org/krita/768c1e6529b84b20a3446d29b765a0d8912144a4

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

[kwin] [Bug 370920] Meta key sometimes stops working after suspend phase

[Basti]

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

--- Comment #10 from Basti  ---
Sorry for late reply, but at the moment the meta key seems to work always. I
switched libinput. I can suspend/resume and switch to virtual terminals, the
meta key continues to work. Maybe the last KDE applications update fixed it?

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

[digikam] [Bug 372568] Krita (.kra) thumbnails are not showed

[Rafael]

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

Rafael  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael  ---
You have reason. Is Digikam 5.3 version. Anyway, I can see that Digikam is
showing some KRA files thumbnails, but not others, so I can't understand what's
the problem.

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

[dolphin] [Bug 372642] Could not find the program 'konqueror'

[Alexey Putz]

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

Alexey Putz  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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

[kstart] [Bug 372644] Firefox link became a Konqueror link.

[Alexey Putz]

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

Alexey Putz  changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Kubuntu Packages

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

[kwin] [Bug 228210] KWin crashed when dragging Maximized Window to top of second Screen (to maximize it there with smaller screen-size)

[Luiz Angelo De Luca]

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

Luiz Angelo De Luca  changed:

   What|Removed |Added

 CC||luizl...@gmail.com

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

[kstart] [Bug 372644] New: Firefox link became a Konqueror link.

[alexeyputz]

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

Bug ID: 372644
   Summary: Firefox link became a Konqueror link.
   Product: kstart
   Version: 5.7.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: putz.ale...@gmail.com
  Target Milestone: ---

Created attachment 102310
  --> https://bugs.kde.org/attachment.cgi?id=102310=edit
kstart screenshot

1. Install digikam through apt-get install.
2. Install gimp through apt-get install.

Firefox link became a Konqueror link.

If I activate this Konqueror link, a bar named Konqueror appears at the panel
for a second and then launches Firefox with text/html query for google opened.

Kubuntu 16.10
KDE Plasma Version : 5.7.5
KDE Frameworks Version : 5.26.0
Qt Version : 5.6.1
Kernel Version : 4.8.0-22-generic
OS Type: 64-bit

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[Randy Barlow]

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

Randy Barlow  changed:

   What|Removed |Added

 CC||ra...@electronsweatshop.com

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

[plasmashell] [Bug 372509] Second monitor settings are reset on every boot

[Randy Barlow]

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

Randy Barlow  changed:

   What|Removed |Added

 CC||ra...@electronsweatshop.com

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

[plasmashell] [Bug 372543] when you restart the computer broken desktop settings, widgets disappear and the room is not displayed as the folder view

[Randy Barlow]

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

Randy Barlow  changed:

   What|Removed |Added

 CC||ra...@electronsweatshop.com

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

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||maraxfar...@gmail.com

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

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

[kcachegrind] [Bug 372643] New: kcachegrind in kf5 has untranslated gui messages from catalog kcachegrind_qt.po

[Burkhard Lueck]

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

Bug ID: 372643
   Summary: kcachegrind in kf5 has untranslated gui messages from
catalog kcachegrind_qt.po
   Product: kcachegrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: josef.weidendor...@gmx.de
  Reporter: lu...@hube-lueck.de
  Target Milestone: ---

The messages from subdirs libcore + libviews are extracted using Qt translation
system ( tr() calls ) into the catalog kcachegrind_qt, but this catalog is not
loaded into kcachgrind nor into qcachegrind.
In KF5 a translation catalog named *_qt.po by default is installed as qm
translation catalog and can not be used by a kf5 app any more, such a catalog
has to be loaded using the Qt Translator.

Solutions for this issue:

1) use a function loadTranslation(..) as in
https://cgit.kde.org/marble.git/tree/src/apps/marble-kde/kdemain.cpp to load
the Qt catalog translations into kcachgrind

2) use xgettext for the subdirs libcore + libviews to extract all messages into
one single catalog kcachegrind and merge the existinhg translations in the
catalog kcachegrind_qt into the catalog kcachegrind

>From my pov no 1) is completely useless because there is no application loading
the translation from the catalog kcachegrind_qt not even qcachegrind.

@Josef: what is the preferred solution for the maintainer?

I can file a review request for solution 2) but not for 1) until I see code in
qcachegrind that loads translations from a qm catalog.

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

[frameworks-plasma] [Bug 372610] Change wallpaper

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
DK and Krita are based on Qt5.

Gimp is GTK stuff.

Qt manage the D through the XDND standard.

Look "Interoperating with Other Applications" section for details.

http://doc.qt.io/qt-5/dnd.html

So the question is : Gimp support XDND ?

Gilles Caulier

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|Kipiinterface   |Usability

--- Comment #2 from caulier.gil...@gmail.com ---
Can you drag and drop from Dolphin file manager or Gwenview to Gimp ?

Note : testing with DK 4 is not valid, as it's based on Qt4 and is not
maintained. DK 5 is the main implementation now and is based on Qt5 which can
have serious difference about D this last one is managed by Qt in fact in
background.

Gilles Caulier

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[alexeyputz]

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

alexeyputz  changed:

   What|Removed |Added

 CC||putz.ale...@gmail.com

--- Comment #1 from alexeyputz  ---
I tried, and I can confirm the issue.

GIMP 2.8.18

digiKam
Version 4.14.0
Using KDE Development Platform 4.14.22


Kubuntu 16.10
KDE Plasma Version : 5.7.5
KDE Frameworks Version : 5.26.0
Qt Version : 5.6.1
Kernel Version : 4.8.0-22-generic
OS Type: 64-bit

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Philippe Waroquiers]

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

--- Comment #8 from Philippe Waroquiers  ---
Note also that we should avoid modifying vgversion.h
each time we call make, as otherwise this will imply to recompile
the including file(s).

So, what we need is a command like:
   create_or_update_vgversion_h_if_needed
which compares the current version with the version in the file
and creates or updates the file if needed.

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

[valkyrie] [Bug 372478] utils/vk_utils.cpp:145]: (error) Memory leak: tmpname

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

Product|valgrind|valkyrie
  Component|general |general
   Assignee|jsew...@acm.org |cer...@valgrind.org
Version|3.12 SVN|unspecified

--- Comment #3 from Philippe Waroquiers  ---
Changing the product to Valkyrie

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

[dolphin] [Bug 372642] New: Could not find the program 'konqueror'

[alexeyputz]

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

Bug ID: 372642
   Summary: Could not find the program 'konqueror'
   Product: dolphin
   Version: 16.08.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: putz.ale...@gmail.com
  Target Milestone: ---

Created attachment 102309
  --> https://bugs.kde.org/attachment.cgi?id=102309=edit
screenshot

1. Open dolphin.
2. Input any url to "places" line edit component.
3. Dolphin throws error window with text "Could not find the program
'konqueror'"


As I thought the Konqueror isnt used at the moment...
Screenshot included.

Kubuntu 16.10
KDE Plasma Version : 5.7.5
KDE Frameworks Version : 5.26.0
Qt Version : 5.6.1
Kernel Version : 4.8.0-22-generic
OS Type: 64-bit

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

[gwenview] [Bug 372641] New: Процесс: gwenview PID: 3079 Сигнал завершения: Segmentation fault

[Alex-boss]

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

Bug ID: 372641
   Summary: Процесс: gwenview PID: 3079 Сигнал завершения:
Segmentation fault
   Product: gwenview
   Version: 5.0.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: a...@donnetwork.ru
CC: myr...@kde.org
  Target Milestone: ---

Процесс: gwenview PID: 3079 Сигнал завершения: Segmentation fault

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

[digikam] [Bug 372640] New: Can't drag any image file from digikam to GIMP

[Rafael]

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

Bug ID: 372640
   Summary: Can't drag any image file from digikam to GIMP
   Product: digikam
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Kipiinterface
  Assignee: digikam-de...@kde.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

When I try to drag any image file from Digikam to GIMP, a "Prohibited" mouse
pointer appears, so I CAN'T drop any image from Digikam to GIMP. However, drag
and drop works fine from Gwenview or Dolphin to GIMP. I saw this issue is
pretend to be solved (bug 22286 from 2001) but it's not.

However, I can drag from Digikam to Krita, so is like there were compatibility
issues still in 2016

I'm using KDE 5.8 on OpenSUSE.

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

[dolphin] [Bug 369523] DolphinPart: Cannot paste without refreshing the destination tab/window

[Jonathan Marten]

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

--- Comment #4 from Jonathan Marten  ---
Found an easier solution.  If anyone can compile from source, please test.
The fix is to Dolphin, even though the problem only affects Konqueror...

--- a/src/dolphinpart.cpp
+++ b/src/dolphinpart.cpp
@@ -78,6 +78,7 @@ DolphinPart::DolphinPart(QWidget* parentWidget, QObject*
parent, const QVariantL
 this, ::slotErrorMessage);

 connect(m_view, ::directoryLoadingCompleted, this,
static_cast(::completed));
+connect(m_view, ::directoryLoadingCompleted, this,
::updatePasteAction);
 connect(m_view, ::directoryLoadingProgress, this,
::updateProgress);
 connect(m_view, ::errorMessage, this,
::slotErrorMessage);

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #9 from RJVB  ---
FWIW, this seems to work acceptably for me:

```C++
void KateRenderer::updateFontHeight()
{
// use height of font + round down, ensure we have at least one pixel
// we round down to avoid artifacts: line height too large vs. qt
background rendering of text attributes
const qreal height = config()->fontMetrics().height();
#ifdef Q_OS_OSX
m_fontHeight = qMax(1, qFloor(1.005f * height));
#else
m_fontHeight = qMax(1, qFloor(height));
#endif
}

```

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

[kinfocenter] [Bug 372639] New: KInfocenter crashes in file indexing page

[Sebastian Dicke]

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

Bug ID: 372639
   Summary: KInfocenter crashes in file indexing page
   Product: kinfocenter
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: sdi...@live.de
  Target Milestone: ---

Application: kinfocenter (5.8.2)

Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

Opened the file indexing page, which do not show any exept of a gray background
and click with the left or right mouse key bottom on the gray area. Then the
application crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Info Center (kinfocenter), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9ad65358c0 (LWP 2536))]

Thread 5 (Thread 0x7f9ab2108700 (LWP 2541)):
#0  0x7f9ad36ff56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9ad03939f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9ad0393b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9ad401a51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9ad3fc219a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9ad3de7e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9ad2ef7a55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9ad0dd2464 in start_thread (arg=0x7f9ab2108700) at
pthread_create.c:333
#9  0x7f9ad37089df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f9ab3df9700 (LWP 2540)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x7f9ad36ff562 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f9ad03939f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9ad0393b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9ad401a51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9ad3fc219a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9ad3de7e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9ad2ef7a55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f9ad0dd2464 in start_thread (arg=0x7f9ab3df9700) at
pthread_create.c:333
#10 0x7f9ad37089df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f9abc49a700 (LWP 2538)):
#0  0x7f9ad36ff56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9ad03939f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9ad0393b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9ad401a51b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9ad3fc219a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9ad3de7e53 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9ad667a525 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9ad0dd2464 in start_thread (arg=0x7f9abc49a700) at
pthread_create.c:333
#9  0x7f9ad37089df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f9ac4cfc700 (LWP 2537)):
#0  0x7f9ad36ff56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9acd6ea150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9acd6ebee9 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f9ac725aa79 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f9ad3decd78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9ad0dd2464 in start_thread (arg=0x7f9ac4cfc700) at
pthread_create.c:333
#6  0x7f9ad37089df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f9ad65358c0 (LWP 2536)):
[KCrash Handler]
#6  0x7f9ad49409de in QWidget::setFocus(Qt::FocusReason) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f9ad4946daf in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f9ad4900bec in 

[kdevelop] [Bug 372637] Build sometimes preventing quick open from working correctly

[Ian Haber]

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

--- Comment #2 from Ian Haber  ---
no debug output in the terminal when it happens.

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

[kdevelop] [Bug 372637] Build sometimes preventing quick open from working correctly

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #1 from Kevin Funk  ---
Can't reproduce. Works fine here (using latest 5.0).

Can you check the debug output of KDevelop? There's usually debug output
whenever the popup is hidden via some event.

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

[plasmashell] [Bug 372361] Choose color and transparency for each panel individually

[alxgvr]

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

--- Comment #2 from alxgvr  ---
I thought KDE philosophy is to make maximum tweakable DE. Thats what differ it
from others. Almost all stuff in System Settings could be called "niche". You
can set color for every graphical element (feature that majority of users don`t
realy use), finetune visual effects, windows behavior, set wallpapers for each
desktop individually (that is what realy complicate user experience - not to
find wallpapers in System Settings). 

When global menu will be added to Plasma, many users will want to emulate Unity
look by placing one panel to the top, other to left side as Dock for apps. And
those people would want to tweak colors for each, to make them look different
(now it just look horrible, when two panels merging in top left corner, so
whole construction looks like monolith "Г" shaped frame).

I believe wish to tweak panels colors much more natural for user when wish to
tweak color for different text modes, or windows decorations. 

I was impressed how clean Plasma panels look as Dock. I thought I will use it 
instead of Plank. Seems like I have to use Plank again, so Plasma not differs
much from many other DE`s in that sense... :(

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #8 from RJVB  ---
(In reply to RJVB from comment #4)

> This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3

Clearly not only that commit. Reverting just that makes line spacing too
generous (total text height increases by approx. 16%).

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

[Discover] [Bug 370349] No way to go back from full Application description

[bugzilla_noreply]

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

k...@douglasmcmillan.com changed:

   What|Removed |Added

 CC||k...@douglasmcmillan.com

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

[Discover] [Bug 372616] discover not showing available upgrades

[bugzilla_noreply]

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

k...@douglasmcmillan.com changed:

   What|Removed |Added

 CC||k...@douglasmcmillan.com

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

[KScreen] [Bug 372632] The window does not fit on the screen

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|frameworks-kwindowsystem|KScreen
   Assignee|mgraess...@kde.org  |se...@kde.org
  Component|general |kcm

--- Comment #2 from Martin Gräßlin  ---
video shows it's kscreen's config ui, thus reassigning.

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #7 from RJVB  ---
(In reply to RJVB from comment #4)

> This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3

Clearly not only that commit. Reverting just that makes line spacing too
generous (total text height increases by approx. 16%).

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

[Breeze] [Bug 370213] Breeze Dark is listed as Breeze in System Settings

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

--- Comment #5 from Rex Dieter  ---
Per comment #4, kf5-5.27 (final) release was affected by this too (presumably
the fix was inluded in recent 5.28.0 release, but I didn't have time to verify)

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

[frameworks-ktexteditor] [Bug 372638] New: "the file was created by another program"

[RJVB]

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

Bug ID: 372638
   Summary: "the file was created by another program"
   Product: frameworks-ktexteditor
   Version: 5.27.0
  Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
  Target Milestone: ---

Maybe it's because of the new kind of external modification alerts, but I find
the message that "the file X has been created by another program" quite weird
when I know that I've been having this file open possibly even for days in the
same editor that posts the alert.

While the message may be technically correct when some other application
replaced the file with an edited version it isn't how we think of it
semantically. What counts for the user is whether the document contents have
changed on disk compared to what is in the editor buffer. 

OTOH, the message may in fact be correct if the document was indeed created by
another application (tar, for instance), but that's hardly relevant to the
situation to which the alert draws attention.

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

[kdevelop] [Bug 372637] New: Build sometimes preventing quick open from working correctly

[Ian Haber]

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

Bug ID: 372637
   Summary: Build sometimes preventing quick open from working
correctly
   Product: kdevelop
   Version: 5.0.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: master.ha...@gmail.com
  Target Milestone: ---

using the hotkey to open quick open file often doesnt work while building.

Steps to reproduce:
1. start long build
2. use hotkey combination to open quick open dialog

What happens:
popup will show but then immediately disappear about 90% of the time.

Expected results:
popup should display and stay visible as normal when not compiling

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

[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw

[María]

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

--- Comment #45 from María  ---
Most of the problems on saving in 3.0.93 are "saving as" from auto-save files,
not exclusively, but in these cases is almost always, at least in large
documents. But in 3.0.93 there is not problem saving when there is text on the
document as in 3.0.92

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

[krita] [Bug 372636] New: Quick Brush engine brushes dont generate mirror strokes when used with mirror tools

[Raghavendra kamath]

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

Bug ID: 372636
   Summary: Quick Brush engine brushes dont generate mirror
strokes when used with mirror tools
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com
  Target Milestone: ---

When the user click on the horizontal or vertical mirror tools in the tool bar
, the brush strokes get mirrored, how ever this is not the case with the quick
brush engine brushes.

dmitry said on IRC that this may not have been implemented yet. Hence I request
for this feature. i know quick brush is limited with parameters but having
ability to mirror strokes would be a plus.

How to reproduce 

- open krita and a new document
- Select a quick brush preset
- choose horizontal and vertical mirror tool from the tool bar
- start to draw

Actual result

- strokes are not mirrored

Expected result

- strokes should be mirrored when mirror tool are enabled

Thank you

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

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

[Jim Jones]

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

--- Comment #244 from Jim Jones  ---
(In reply to Christoph Feck from comment #243)
> If kill of plasmashell helps to resolve a multiscreen issue, then
> this might be fixed in Plasma 5.8.4.

Please read https://bugs.kde.org/show_bug.cgi?id=356225#c236, this doesn't
solve the issue for me. As soon as 2 screens are used and the primary screen
(let's call it A) takes longer to wake up from sleep/powersave mode than screen
B, screen B will be the main screen with the panel moved to it after both
screens resume from sleep mode

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

[krunner] [Bug 372635] do not follow mousepointer when accessing krunner via keyboard

[Martin Steigerwald]

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

Martin Steigerwald  changed:

   What|Removed |Added

 CC||mar...@lichtvoll.de

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

[krunner] [Bug 372635] New: do not follow mousepointer when accessing krunner via keyboard

[Martin Steigerwald]

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

Bug ID: 372635
   Summary: do not follow mousepointer when accessing krunner via
keyboard
   Product: krunner
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: martin.steigerw...@teamix.de
  Target Milestone: ---

I usually use krunner via keyboard, like this:

- Alt-F2
- "fi"
- Enter

to start Firefox.

# Actual results
Yet if I happen to have the mouse pointer within the area to which krunner
expands to while listing search results krunner shows the entry over the mouse
pointer as selected. When I then hit return, I do not get Firefox started but
an PDF opened or an image or whatnot.

# Expected result
Start the best fit that matches what I type and ignore the mouse pointer
location.

I think an easy workaround would to only select an item from krunner by mouse
if the user actually presses the left mouse button. I see no point in the on
hover selection. Sure I could use the mouse and then still hit the enter key,
but what for? Either I use the keyboard or I use the mouse.

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

[frameworks-ktexteditor] [Bug 335079] Text rendering broken for unicode characters

[RJVB]

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

RJVB  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=372629

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

[kde] [Bug 372634] New: KDE4 crashed while system was updating.

[Lloyd]

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

Bug ID: 372634
   Summary: KDE4 crashed while system was updating.
   Product: kde
   Version: 4.14.1
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: hayesll...@gmail.com
  Target Milestone: ---

Crash Handler report:

Application: kded4 (4.14.16)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: Linux Mint 18 Sarah

-- Information about the crash:


-- Backtrace:
Application: KDE Daemon (kded4), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35
#7  0x7f70724a25d2 in QBuffer::readData(char*, long long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f70724bc596 in QIODevice::read(char*, long long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f70724a35b5 in QDataStream::operator>>(int&) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f7072aadad3 in KSycocaDict::Private::offsetForKey(QString const&)
const () from /usr/lib/libkdecore.so.5
#11 0x7f7072aadc58 in KSycocaDict::find_string(QString const&) const ()
from /usr/lib/libkdecore.so.5
#12 0x7f7072a2b443 in KServiceTypeFactory::findServiceTypeByName(QString
const&) () from /usr/lib/libkdecore.so.5
#13 0x7f7072a30179 in KServiceTypeTrader::defaultOffers(QString const&,
QString const&) const () from /usr/lib/libkdecore.so.5
#14 0x7f7072a30621 in KServiceTypeTrader::query(QString const&, QString
const&) const () from /usr/lib/libkdecore.so.5
#15 0x7f7068c24ba4 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#16 0x7f7068c25208 in ?? () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#17 0x7f707254fdb1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7f7071877fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x7f707187ef16 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x7f70733016aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#21 0x7f707253590d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x7f70725393c6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x7f707256613e in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7f706e0f51a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f706e0f5400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f706e0f54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f70725662ae in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x7f7071925616 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#29 0x7f707253418f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x7f70725344f5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x7f707253a4b9 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#32 0x7f7068c265bd in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#33 0x004089cc in ?? ()
#34 0x00405e41 in ?? ()
#35 0x7f7070f7b830 in __libc_start_main (main=0x404980, argc=2,
argv=0x7fff324313f8, init=, fini=,
rtld_fini=, stack_end=0x7fff324313e8) at ../csu/libc-start.c:291
#36 0x004063f9 in _start ()

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

RJVB  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=335079

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

[dolphin] [Bug 372633] New: Unable to copy directory recursively from smb to mtp

[Julien HENRY]

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

Bug ID: 372633
   Summary: Unable to copy directory recursively from smb to mtp
   Product: dolphin
   Version: 16.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: henr...@yahoo.fr
  Target Milestone: ---

Hi,

I'm trying to copy a folder from my NAS (using SMB) to my phone (using MTP).
Directories are created in the target, when for files it fails with "Unable to
create file XXX". If I first copy from smb to the local disk, then move from
local disk to mtp, it works fine.

URL in Dolphin look like:
smb://julien@192.168.0.200/music/Albums/L/Les /

MTP URL:
mtp:/Samsung Galaxy S7/Phone/Music/

journalctl -b is full of:
kdeinit5[3282]: QIODevice::write (QTemporaryFile, ""): device not open

Tell me if you need more details.

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #6 from RJVB  ---
Created attachment 102308
  --> https://bugs.kde.org/attachment.cgi?id=102308=edit
better line spacing with 5.24.0

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #5 from RJVB  ---
Created attachment 102307
  --> https://bugs.kde.org/attachment.cgi?id=102307=edit
touching lines with 5.27.0

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #4 from RJVB  ---
Hah, well, that misfired then, at least on OS X. I didn't check if 5.24.0 does
worse with the FreeType font engine.

This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3

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

[telepathy] [Bug 372631] OTR messages in chat history are not decrypted (history not readable)

[bugzilla_noreply]

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

--- Comment #1 from pi...@gmx.de ---
My version is 16.04.3

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

[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[frameworks-kwindowsystem] [Bug 372632] The window does not fit on the screen

[Walddys Emmanuel Dorrejo Céspedes]

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

--- Comment #1 from Walddys Emmanuel Dorrejo Céspedes  
---
Created attachment 102306
  --> https://bugs.kde.org/attachment.cgi?id=102306=edit
System info

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

[frameworks-kwindowsystem] [Bug 372632] New: The window does not fit on the screen

[Walddys Emmanuel Dorrejo Céspedes]

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

Bug ID: 372632
   Summary: The window does not fit on the screen
   Product: frameworks-kwindowsystem
   Version: 5.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: dev.dorr...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

hello i use, KDE v5.8 Opensuse leap 42.2 and in the next video, i show some
config windows bugged.https://youtu.be/xNe9XVtcWd8

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

[telepathy] [Bug 372631] New: OTR messages in chat history are not decrypted (history not readable)

[bugzilla_noreply]

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

Bug ID: 372631
   Summary: OTR messages in chat history are not decrypted
(history not readable)
   Product: telepathy
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OTR
  Assignee: kde-telepathy-b...@kde.org
  Reporter: pi...@gmx.de
CC: ziem...@gmail.com
  Target Milestone: Future

I use OTR, which works erfect. But when I close the chat window of a friend and
open it up again, I see all the previous messages but all are labeled
"Encrypted message".

Is it possible to store them either unencrypted in the hostory or decrypt them
again? The first would be better if the key changes over time.

Thanks
Andreas

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

[krita] [Bug 372630] New: Filling canvas uses blending mode of the tool in use

[bugzilla_noreply]

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

Bug ID: 372630
   Summary: Filling canvas uses blending mode of the tool in use
   Product: krita
   Version: 3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: rebuilders...@gmail.com
  Target Milestone: ---

In a document set to 16 bit float colorspace, filling the canvas with white via
backspace or similar produces unexpected results

Steps to reproduce:
1. Paint several strokes on canvas with "Addition" color mode, until you have
color values over "1".
2. Fill canvas with white.
3. Use color picker to sample an area that previously had superwhite values.
You'd expect the values to be "1", but it seems the fill operation has worked
in "Addition" mode, so you have superwhite values.

This seems rather unexpected.

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