[kontact] [Bug 377855] KMail crashes when selecting new email recipients

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Hi,
no crash here.
Could you test with new version ? Last version is 5.4.3
your version is very old.

Regards

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

[plasmashell] [Bug 369658] Different windows from same app show icon defined in .desktop file instead of app-specified icon

[Andreas Kilgus]

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

--- Comment #35 from Andreas Kilgus  ---
(In reply to Anguo from comment #31)
> What you refer to as bugs are slight visual ugliness in some places. I much
> prefer those to the complete unusability of the current default behaviour.
Thanks for your fix. I spent hours looking for where and when I might have
messed things up that much so that the favicons of all my konqueror instances
in the taskbar have gone. I simply couldn't imagine, that this is not caused by
misconfiguration or missing or incompatible packages. Finding this bug report
eventually I learned that it's because of me switching from KDE4 to plasma5. A
pleasure to read that it is "by design" to render my taskbar partly useless -
see attachment https://bugs.kde.org/attachment.cgi?id=104664.

Well, upstream says "WONTFIX" - but thanks to you now there's a way to regain
this part of my workflow. Perhaps I can offer packages with your patch applied
in openSUSEs build service.

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

[plasmashell] [Bug 369658] Different windows from same app show icon defined in .desktop file instead of app-specified icon

[Andreas Kilgus]

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

Andreas Kilgus  changed:

   What|Removed |Added

 CC||k...@fuenfsieben.de

--- Comment #34 from Andreas Kilgus  ---
Created attachment 104664
  --> https://bugs.kde.org/attachment.cgi?id=104664=edit
Happy guessing which konqueror entry might be the right one to click on.

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

[plasma-nm] [Bug 377867] New: avahi creates new connection that doesn't exist

[Paul]

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

Bug ID: 377867
   Summary: avahi creates new connection that doesn't exist
   Product: plasma-nm
   Version: 5.7.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: jgrul...@redhat.com
  Reporter: paul.hancock.17041...@live.com
  Target Milestone: ---

avahi appears to have a tendancy to create a new network connection for an
existing ethernet adapter while the adapter is inactive/asleep/disconnected.
This resulting adapter shows up in the network manager and can conflict with
other connections, including the wifi card (removing or editing the ethernet
connections can cause the wifi to fail for unknown reasons).


ifconfig
enp1s0: flags=4099  mtu 1500
ether 70:5a:0f:85:fb:b2  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0:avahi: flags=4099  mtu 1500
inet 169.254.10.110  netmask 255.255.0.0  broadcast 169.254.255.255
ether 70:5a:0f:85:fb:b2  txqueuelen 1000  (Ethernet)

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Local Loopback)
RX packets 36833  bytes 3321005 (3.3 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 36833  bytes 3321005 (3.3 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vpn_vectrobevpn: flags=4163  mtu 1500
inet6 fe80::2ac::fefc:4d2d  prefixlen 64  scopeid 0x20
ether 00:ac:ff:fc:4d:2d  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 2660 overruns 0  carrier 0  collisions 0

wlo1: flags=4163  mtu 1500
inet 10.15.238.196  netmask 255.0.0.0  broadcast 10.255.255.255
inet6 fe80::94fd:274a:5138:7532  prefixlen 64  scopeid 0x20
ether 08:d4:0c:ef:9b:4c  txqueuelen 1000  (Ethernet)
RX packets 560696  bytes 599284948 (599.2 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 620583  bytes 107201838 (107.2 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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

[systemsettings] [Bug 375708] Turn on numlock at startup does not work under Wayland

[Andriy Rysin]

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

Andriy Rysin  changed:

   What|Removed |Added

   Assignee|ary...@gmail.com|unassigned-b...@kde.org

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

[frameworks-kiconthemes] [Bug 365363] Changing icons from System Settings is broken

[Pulfer]

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

--- Comment #20 from Pulfer  ---
(In reply to Michael Pyne from comment #19)
> If this is the problem, then running your KDE desktop with the env var
> "KDE_IS_PRELINKED" set to 1 should cause Dolphin to work with icon theme
> changes even when run from KRunner. (This env var disables the kdeinit trick)

Thanx for the hint, it fixes the issue indeed. :-) Should I add
KDE_IS_PRELINKED export to startkde script in my distro's package? Or maybe you
can fix kdeinit to handle icon theme changes even if KDE_IS_PRELINKED is not
set to 1?

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

[frameworks-kiconthemes] [Bug 365363] Changing icons from System Settings is broken

[Michael Pyne]

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

--- Comment #19 from Michael Pyne  ---
I suspect the behavior you're seeing when running another Dolphin instance from
KRunner (not kicker ;)) is related to an optimization enabled by default in KDE
4 that is supposed to speed up startup of KDE apps (by routing startup through
an always-running kdeinit that clones another copy of itself and morphs into
the right application).

If this is the problem, then running your KDE desktop with the env var
"KDE_IS_PRELINKED" set to 1 should cause Dolphin to work with icon theme
changes even when run from KRunner. (This env var disables the kdeinit trick)

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

[juk] [Bug 377320] Request to update Juk to KF5 because it is great software!

[Michael Pyne]

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

--- Comment #3 from Michael Pyne  ---
I still love JuK but I'm the last active developer on it and I've not had the
time needed to port it over, let alone improve it.

I keep toying with the idea of doing a re-write from scratch of a very simple
facsimile of the JuK we love (playlists, songs in each playlist, probably not
much else).  Maybe that would make it possible, but otherwise I don't know what
to say. :(

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

[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work

[bugzilla_noreply]

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

--- Comment #5 from ci3...@gmail.com ---
Created attachment 104663
  --> https://bugs.kde.org/attachment.cgi?id=104663=edit
Screenshot 3

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

[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work

[bugzilla_noreply]

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

--- Comment #4 from ci3...@gmail.com ---
Created attachment 104662
  --> https://bugs.kde.org/attachment.cgi?id=104662=edit
Screenshot 2

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

[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work

[bugzilla_noreply]

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

--- Comment #3 from ci3...@gmail.com ---
Created attachment 104661
  --> https://bugs.kde.org/attachment.cgi?id=104661=edit
Screenshot 1

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

[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work

[bugzilla_noreply]

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

--- Comment #2 from ci3...@gmail.com ---
Created attachment 104660
  --> https://bugs.kde.org/attachment.cgi?id=104660=edit
Picture 3

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

[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work

[bugzilla_noreply]

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

--- Comment #1 from ci3...@gmail.com ---
Created attachment 104659
  --> https://bugs.kde.org/attachment.cgi?id=104659=edit
Picture 2

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

[dragonplayer] [Bug 377866] New: crash playing dvd iso after installing libdvdcss2

[Aram]

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

Bug ID: 377866
   Summary: crash playing dvd iso after installing libdvdcss2
   Product: dragonplayer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: aramgrigor...@protonmail.ch
CC: myr...@kde.org
  Target Milestone: ---

Application: dragon (16.12.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
before installing libdvdcss2 dragonplayer didnt crash but where stopping at
particular moment of video, after installing libdvdcss2 it just crashed at the
same postition of time

-- Backtrace:
Application: Dragon Player (dragon), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1064ff74c0 (LWP 23018))]

Thread 5 (Thread 0x7f0fc37fe700 (LWP 23072)):
#0  0x7f10603427bd in poll () at /lib64/libc.so.6
#1  0x7f105b2b9896 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f105b2b99ac in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f105b2b99f1 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f105b2e1275 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f105da8f537 in start_thread () at /lib64/libpthread.so.0
#6  0x7f106034c04f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f0fc3fff700 (LWP 23064)):
#0  0x7f1060347389 in syscall () at /lib64/libc.so.6
#1  0x7f105b2ff0af in g_cond_wait () at /usr/lib64/libglib-2.0.so.0
#2  0x7f104390268e in  () at /usr/lib64/libgstreamer-1.0.so.0
#3  0x7f105b2e1275 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f105da8f537 in start_thread () at /lib64/libpthread.so.0
#5  0x7f106034c04f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f10495d1700 (LWP 23020)):
#0  0x7f10603427bd in poll () at /lib64/libc.so.6
#1  0x7f105b2b9896 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f105b2b99ac in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1060f7818b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f10440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1060f21aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f10495d0cc0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f1060d4f813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f106138a385 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f1060d544c8 in QThreadPrivate::start(void*) (arg=0x7f10615fbd20) at
thread/qthread_unix.cpp:368
#8  0x7f105da8f537 in start_thread () at /lib64/libpthread.so.0
#9  0x7f106034c04f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f10508a6700 (LWP 23019)):
#0  0x7f10603427bd in poll () at /lib64/libc.so.6
#1  0x7f105d6543e0 in  () at /usr/lib64/libxcb.so.1
#2  0x7f105d656179 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f1052e11889 in QXcbEventReader::run() (this=0xd64330) at
qxcbconnection.cpp:1343
#4  0x7f1060d544c8 in QThreadPrivate::start(void*) (arg=0xd64330) at
thread/qthread_unix.cpp:368
#5  0x7f105da8f537 in start_thread () at /lib64/libpthread.so.0
#6  0x7f106034c04f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f1064ff74c0 (LWP 23018)):
[KCrash Handler]
#6  0x7f1060293ff0 in raise () at /lib64/libc.so.6
#7  0x7f10602956ea in abort () at /lib64/libc.so.6
#8  0x7f1058f77389 in  () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so
#9  0x7f1058f77d7f in pa_fdsem_after_poll () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#10 0x7f1058f8f92d in  () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so
#11 0x7f105cfeeff6 in  () at /usr/lib64/libpulse-mainloop-glib.so.0
#12 0x7f105b2b9697 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#13 0x7f105b2b9900 in  () at /usr/lib64/libglib-2.0.so.0
#14 0x7f105b2b99ac in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#15 0x7f1060f7816f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0xd9c050, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#16 0x7f1060f21aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff2eacf100, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#17 0x7f1060f2a25c in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1261
#18 0x7f10616f541c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1633
#19 0x7f1061e9ee05 in QApplication::exec() () at
kernel/qapplication.cpp:2975
#20 0x0041bfa4 in main(int, char**) (argc=,
argv=) at /usr/src/debug/dragon-16.12.3/src/app/main.cpp:91

Reported using DrKonqi

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

[dolphin] [Bug 377864] iPhone 5 doesn't mount correctly; shows up as empty, instead of displaying the pictures inside

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[KScreen] [Bug 377865] New: (De)Activating monitors on wayland does not work

[bugzilla_noreply]

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

Bug ID: 377865
   Summary: (De)Activating monitors on wayland does not work
   Product: KScreen
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: ci3...@gmail.com
  Target Milestone: ---

See the attached screenshots and pictures for actual results. My steps are:
1. Go to systemsettings -> kscreen settings
2. Switch DVI-I monitor off and press "Apply".
   - Result: Screenshot 1, nothing had happened
3. Switch DVI-I and HDMI monitor off and press "Apply".
   - Result: Screenshot 2, Picture 2, strange duplicating of the toolbar.
4. Switch DVI-I and HDMI on and off again and press "Apply".
   - Result: Screenshot 3, Picture 3

It has to be noted, that only the picture is moved. The actually mouse
interaction remains at the same positions as before. (i.e. you click with the
mouse on the upper left of the screen and the k-menu pops up in the middle of
the screen).

I'm using Gentoo with Plasma 5.9.3, Qt 5.7.1, Wayland session started with SDDM
and use of OpenRC and elogind.

This bug is reproducible. If you need other information, please say so.

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

[dolphin] [Bug 377864] New: iPhone 5 doesn't mount correctly; shows up as empty, instead of displaying the pictures inside

[Nate Graham]

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

Bug ID: 377864
   Summary: iPhone 5 doesn't mount correctly; shows up as empty,
instead of displaying the pictures inside
   Product: dolphin
   Version: 16.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Dolphin 16.12.3 and KDE Plasma 5.9.2 on openSUSE Tumbleweed.

My iPhone 5 doesn't mount in Dolphin correctly. Every time I plug in the phone,
it displays the "trust this device?" dialog, and I tell it to trust the
computer. The phone shows up in Dolphin as a camera removable device
(camera:/), which is correct. If I open it up in Dolphin, the only thing
displayed inside that is a folder named "Apple iPhone 5 (PTP Mode) with two
empty text files and an empty directory. None of the photos on the device show
up.

I had a similar problem in GNOME, but managed to work around it by mounting the
phone in a slightly different way (remove the trailing ":3" from the gphoto
URL), so I know it's not a problem with the device--just how it's handled. I
can confirm that the device is trusting the computer, so there's some problem
with how its contents are being mounted.

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

[krusader] [Bug 377828] Input focus on copy/move dialogue needs work

[KF]

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

--- Comment #2 from KF  ---
(In reply to Alex Bikadorov from comment #1)
> KDE 5 does not have a progress bar dialogue and the "File already exists"
> dialog is instantly focused. Btw. both dialogs are not part of Krusader but
> KF5/KDELibs.
> 
> And you should always be able to focus another dialog/window with ALT+Tab.

Thanks Alex. So it looks like a KDE in Unity/gnome issue which I'll just have
to live with.

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

[KScreen] [Bug 377863] Strange scrolling behaviour on Wayland

[bugzilla_noreply]

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

--- Comment #1 from ci3...@gmail.com ---
As you see the text on the buttons is not aligned very well. Is this a
localisation failure and should I report this bug somewhere else?

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

[KScreen] [Bug 377863] New: Strange scrolling behaviour on Wayland

[bugzilla_noreply]

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

Bug ID: 377863
   Summary: Strange scrolling behaviour on Wayland
   Product: KScreen
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: ci3...@gmail.com
  Target Milestone: ---

Created attachment 104658
  --> https://bugs.kde.org/attachment.cgi?id=104658=edit
Screenshot of error

Scrolling in a Wayland session leads to unwanted results. See attached
screenshots. I'm not sure if this is a KScreen bug at all, but this is the
component I saw it.

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

[plasmashell] [Bug 377862] New: Plasma crashed, when moving control bar on wayland

[bugzilla_noreply]

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

Bug ID: 377862
   Summary: Plasma crashed, when moving control bar on wayland
   Product: plasmashell
   Version: 5.9.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ci3...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.3)
 (Compiled from sources)
Qt Version: 5.7.1
Frameworks Version: 5.32.0
Operating System: Linux 4.9.16-gentoo x86_64
Distribution: "NAME=Gentoo"

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

I have three monitors. I right clicked into the most left monitor, and select
new control bar. The bar spawns on the most right monitor, so I go to the edit
options of the control and move it to the left monitor. Plasma then crashes.

I'm currently experimenting with Plasma on Wayland (started from SDDM) on
Gentoo with openrc and elogind. Plasma is 5.9.3. Qt is 5.7.1.

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

Thread 33 (Thread 0x7f5285e61700 (LWP 3888)):
#0  0x7ffd96b66a5a in clock_gettime ()
#1  0x7f5293342016 in clock_gettime () from /lib64/libc.so.6
#2  0x7f5293a7f361 in qt_gettime() () from /usr/lib64/libQt5Core.so.5
#3  0x7f5293bc83d9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7f5293bc87d5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f5293bc9b1c in timerSourcePrepareHelper(GTimerSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f5293bc9bf5 in timerSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f528ef5a4ed in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#8  0x7f528ef5aed8 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#9  0x7f528ef5b0bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f5293bc9e7c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#11 0x7f5293b7deaa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#12 0x7f52939e2d84 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#13 0x7f5298a64445 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#14 0x7f52939e728c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#15 0x7f52928f0454 in start_thread () from /lib64/libpthread.so.0
#16 0x7f529333528d in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f527700 (LWP 3932)):
#0  0x7f529332c202 in poll () from /lib64/libc.so.6
#1  0x7f528ef5afac in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f528ef5b0bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5293bc9e7c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f5293b7deaa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f52939e2d84 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f5295f862a5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#7  0x7f52939e728c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f52928f0454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f529333528d in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f527e9a9700 (LWP 3935)):
#0  0x7f528ef9ebd9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f528ef5a4f9 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f528ef5aed8 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f528ef5b0bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f5293bc9e7c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f5293b7deaa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f52939e2d84 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f5295f862a5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#8  0x7f52939e728c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f52928f0454 in start_thread () from /lib64/libpthread.so.0
#10 0x7f529333528d in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f5277fff700 (LWP 4138)):
#0  0x7f52928f602f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f529839c9b4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQt5Script.so.5
#2  0x7f529839c9f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from 

[kmail2] [Bug 371509] reading every new message resynchronizes folder

[Jure Repinc]

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

--- Comment #1 from Jure Repinc  ---
I can confirm this and am using KMail 5.4.3

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

[kmail2] [Bug 371509] reading every new message resynchronizes folder

[Jure Repinc]

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

Jure Repinc  changed:

   What|Removed |Added

 CC||j...@holodeck1.com

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

[digikam] [Bug 370093] Opening a picture (double-click) in Showfoto (default viewer) does not show the other pictures in the folder (similar to Bug 221245)

[FabRic]

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

FabRic  changed:

   What|Removed |Added

Version|5.2.0   |5.5.0

--- Comment #2 from FabRic  ---
Still the same problem with digikam 5.5.0

(the menus - Color, Enhance, Decorate, Effects - are OK, though)

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

[kmenuedit] [Bug 377861] New: Aborted while pasting submenu, after cutting

[bugzilla_noreply]

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

Bug ID: 377861
   Summary: Aborted while pasting submenu, after cutting
   Product: kmenuedit
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: rlagg...@mail.com
  Target Milestone: ---

Application: kmenuedit (5.8.2)

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

-- Information about the crash:
Extensive (dozens) of menu restructioning moves. Saved every dozen moves. Last
save about 3 moves back. Submenu contained about 8-12 items. No other system
activity. Kontact open; Kdirstat open; firefox open; kdiskfree open.  Lotsa
memory, lotsa disk space. Suse LEAP 42.2.

-- Backtrace:
Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb97e774940 (LWP 7879))]

Thread 4 (Thread 0x7fb95a176700 (LWP 7882)):
#0  0x7fb975b770af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb9614d8533 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7fb9614d7d57 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7fb975b72734 in start_thread () at /lib64/libpthread.so.0
#4  0x7fb97e0c8d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fb9679cc700 (LWP 7881)):
#0  0x7fb97e0c049d in poll () at /lib64/libc.so.6
#1  0x7fb9751f7314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fb9751f742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fb97a06032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fb97a00dfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fb979e48f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fb97b6cf1d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fb979e4d9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fb975b72734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fb97e0c8d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fb969557700 (LWP 7880)):
#0  0x7fb97e0c049d in poll () at /lib64/libc.so.6
#1  0x7fb972f4c3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fb972f4dfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fb96b487839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fb979e4d9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fb975b72734 in start_thread () at /lib64/libpthread.so.0
#6  0x7fb97e0c8d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb97e774940 (LWP 7879)):
[KCrash Handler]
#6  0x7fb979aae2a0 in __dynamic_cast () at /usr/lib64/libstdc++.so.6
#7  0x7fb97e3a5e27 in  () at /usr/lib64/libkdeinit5_kmenuedit.so
#8  0x7fb97e3a5ca8 in  () at /usr/lib64/libkdeinit5_kmenuedit.so
#9  0x7fb97e3a5e5d in  () at /usr/lib64/libkdeinit5_kmenuedit.so
#10 0x7fb97e3a5ca8 in  () at /usr/lib64/libkdeinit5_kmenuedit.so
#11 0x7fb97e3a7e18 in  () at /usr/lib64/libkdeinit5_kmenuedit.so
#12 0x7fb97a03a1c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x7fb97ad0d892 in QAction::triggered(bool) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7fb97ad1042d in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7fb97ae8b582 in  () at /usr/lib64/libQt5Widgets.so.5
#16 0x7fb97ae90730 in  () at /usr/lib64/libQt5Widgets.so.5
#17 0x7fb97ae9427b in QMenu::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#18 0x7fb97ad58c9a in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#19 0x7fb97ae94bbb in QMenu::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7fb97ad16e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#21 0x7fb97ad1bd14 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7fb97a00ffc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#23 0x7fb97ad1aa10 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/libQt5Widgets.so.5
#24 0x7fb97ad71eb4 in  () at /usr/lib64/libQt5Widgets.so.5
#25 0x7fb97ad73eb3 in  () at /usr/lib64/libQt5Widgets.so.5
#26 0x7fb97ad16e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#27 0x7fb97ad1b49a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#28 0x7fb97a00ffc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#29 0x7fb97a56368b in

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

[Eugene]

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

Eugene  changed:

   What|Removed |Added

 CC||o1o2o3o...@gmail.com

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

[kdenlive] [Bug 377853] git master - Project Settings window won't fit in 1366x768 screen size [screenshots included]

[Jean-Baptiste Mardelle]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 425efe4527dd50abeda4003334c6231bab0a by Jean-Baptiste Mardelle.
Committed on 20/03/2017 at 23:07.
Pushed by mardelle into branch 'Applications/17.04'.

Profile widget: make UI more compact, remember filter status if default profile
matches, ensure selected profile is visible

M  +1-0src/dialogs/kdenlivesettingsdialog.cpp
M  +11   -0src/kdenlivesettings.kcfg
M  +0-1src/profiles/tree/profilefilter.cpp
M  +2-1src/profiles/tree/profiletreemodel.cpp
M  +39   -38   src/project/dialogs/profilewidget.cpp
M  +1-0src/project/dialogs/projectsettings.cpp
M  +85   -92   src/ui/configmisc_ui.ui
M  +21   -38   src/ui/configproject_ui.ui
M  +25   -36   src/ui/projectsettings_ui.ui

https://commits.kde.org/kdenlive/425efe4527dd50abeda4003334c6231bab0a

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

[Akonadi] [Bug 358559] akonadi_imap_resource incorrectly handles RFC 5464

[Daniel Vrátil]

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

--- Comment #7 from Daniel Vrátil  ---
Thanks. From the logs, it's visible that we *do* adhere to the RFC (DEPTH
infinity), so it's likely a bug on the server side.

You mentioned Cyrus 2.5, but the only place where I could find the error
message you are getting is in an old metadata plugin for Dovecot [0]. Now I
suspect that quoting the infinity keyword might make it work, but I'm hesitant
to implement it as it might break other IMAP servers.




[0] http://hg.dovecot.org/dovecot-metadata-plugin

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

[plasmashell] [Bug 377860] New: Screen went black when starting Chromium App Readium

[Stefano Carlesso]

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

Bug ID: 377860
   Summary: Screen went black when starting Chromium App Readium
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: stefano.carle...@yahoo.it
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

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

-- Information about the crash:
- What I was doing when the application crashed:
I was starting a "Chromium App" from KDE Application menu. The name of the
application is Readium (an Epub reader).

- Unusual behavior I noticed:
The whole screen became black; for a moment I could not see the Panel or any of
the opened windows.

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

Thread 11 (Thread 0x7fbb611cd700 (LWP 4897)):
#0  0x7fbc384d251d in read () at /lib64/libc.so.6
#1  0x7fbc2dac2931 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7fbc2e14b3be in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7fbc2e14bdd2 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7fbc2e14be90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7fbc2e15a006 in  () at /usr/lib64/libpulse.so.0
#6  0x7fbc2daf1408 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7fbc37cdf734 in start_thread () at /lib64/libpthread.so.0
#8  0x7fbc384ded3d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fbb621ce700 (LWP 4896)):
#0  0x7fbc384d649d in poll () at /lib64/libc.so.6
#1  0x7fbc34b9e314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbc34b9e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbc38ddd32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbc38d8afdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbc38bc5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbc3bed29c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbc38bca9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbc37cdf734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbc384ded3d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fbb6ef22700 (LWP 2803)):
#0  0x7fbc384d649d in poll () at /lib64/libc.so.6
#1  0x7fbc34b9e314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbc34b9e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbc38ddd32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbc38d8afdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbc38bc5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbb7034a8f7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7fbc38bca9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbc37cdf734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbc384ded3d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fbb802a3700 (LWP 2576)):
#0  0x7fbc384d649d in poll () at /lib64/libc.so.6
#1  0x7fbc34b9e314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbc34b9e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbc38ddd32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbc38d8afdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbc38bc5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbc3ca55632 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7fbc38bca9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbc37cdf734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbc384ded3d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fbb8916d700 (LWP 2556)):
#0  0x7fbc37ce40af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbb8f98e533 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7fbb8f98dd57 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7fbc37cdf734 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbc384ded3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fbc157f0700 (LWP 2538)):
#0  0x7fbc37ce40af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbc3e69c93b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fbc3e69c969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fbc37cdf734 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbc384ded3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fbc17452700 

[plasmashell] [Bug 370464] On reboot desktop wallpaper settings are forgotten

[davidblunkett]

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

--- Comment #14 from davidblunkett  ---
In the interim time is there anyway to hard code the background - swap a file
or edit a config file directly to fix this?

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

[kmail2] [Bug 377344] Some emails are duplicated

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #3 from Daniel Vrátil  ---
Do you have any local filters? If yes, could you see if maybe disabling them
temporarily prevents the duplicates from appearing?

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

[kdenlive] [Bug 377859] New: High CPU usage while idle.

[bugzilla_noreply]

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

Bug ID: 377859
   Summary: High CPU usage while idle.
   Product: kdenlive
   Version: Appimage | Snap
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: skoupad-bugzi...@yahoo.com
  Target Milestone: ---

I just started learning Kdenlive and I noticed something strange. I am using
Debian 8.7 and an Appimage of Kdelive Version 16.12.2.  When I run Kdenlive
from the Appimage I see unexpected CPU usage in idle. I've found out that if I
do the following steps it stops:

 -If I press play and then pause (with or without any videos inside the
project) with the Clip Monitor Tab selected, the CPU usage returns back to
normal.

 -If I do anything in Kdenlive (like selecting the Project Monitor Tab) the CPU
usage rises again. In order to stop it I have to select the Clip Monitor Tab
and press play and pause again (the CPU usage stops only after pressing pause).

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

[Discover] [Bug 377819] Can't review software

[Unreal Name]

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

Unreal Name <2112...@jeffcoschools.us> changed:

   What|Removed |Added

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

--- Comment #3 from Unreal Name <2112...@jeffcoschools.us> ---
If it is fixed in master, neon Developer should have recieved an update by now,
but I still have this issue.
Again this may just be because flatpak is not installed/support is not
included.

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

[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar

[wildcowboy]

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

--- Comment #3 from wildcowboy  ---
(In reply to Jens from comment #2)
> Just out of curiosity: what is missing for 90%? 99%? 100%? :)

Tag tree is one on the features I really enjoying in digiKam so I might switch
to the tab with the full tag tree from time to time.  Maybe not... I have used
programs where you have to start typing the tag too.

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

[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar

[Jens]

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

--- Comment #2 from Jens  ---
Just out of curiosity: what is missing for 90%? 99%? 100%? :)

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

[krazy] [Bug 377858] New: False warnings about missing explicit with move constructors

[Friedrich W . H . Kossebau]

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

Bug ID: 377858
   Summary: False warnings about missing explicit with move
constructors
   Product: krazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: win...@kde.org
  Reporter: kosse...@kde.org
  Target Milestone: ---

The [explicit] check currently wants move constructors to be declared
"explicit". Which might run against recommended practices?

I am only still learning since recently about move constructors, but if I
understood correctly move constructors should have the same handling as the
copy constructors they overload with together, as some template algorithms
expect this now and then, so the only decision is by lvalue vs. rvalue and not
due to different explicit declarations.

Example for false negative on move constructor:

Krazy result listed at
http://ebn.kde.org/krazy/reports/extragear/kdevelop/kdevplatform/
has for item "10. Check for C++ ctors that should be declared 'explicit'
[explicit]...OOPS! 14 issues found!"
as first hit
plugins/outlineview/outlinenode.h: line# 43 (1) 
which is
OutlineNode(OutlineNode&& other) Q_DECL_NOEXCEPT;
https://lxr.kde.org/source/extragear/kdevelop/kdevplatform/plugins/outlineview/outlinenode.h#0043

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

[krusader] [Bug 371765] Documents suddenly open as archives

[Alex Bikadorov]

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

--- Comment #14 from Alex Bikadorov  ---
The fix is not in the last release, 2.5.0.

You actually have to change only one line. In the file
"/usr/share/kservices5/krarc.protocol" the (long) argument for
"archiveMimetype" must be set to
>archiveMimetype=application/x-7z,application/x-7z-compressed,application/x-ace,application/x-ace-compressed,application/x-arj,application/x-arj-compressed,application/x-cpio,application/x-lha,application/x-lha-compressed,application/x-rar,application/x-rar-compressed,application/zip,application/x-zip,application/x-zip-compressed

But this is inconvenient of course. I think we can manage a new release within
the next three weeks.

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

[krusader] [Bug 377000] openning odt files with krarc:/

[Alex Bikadorov]

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

--- Comment #11 from Alex Bikadorov  ---
Please use the discussion for bug 371765

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

[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar

[wildcowboy]

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

wildcowboy  changed:

   What|Removed |Added

 CC||aegor...@gmail.com

--- Comment #1 from wildcowboy  ---
I like the idea. It could be a good additional "Quick Access" tab. I would use
it 80% of the time.

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

[krusader] [Bug 377000] openning odt files with krarc:/

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||andr...@stikonas.eu

--- Comment #10 from Andrius Štikonas  ---
(In reply to livier from comment #9)
> I said it is fine now, it was a mistake.
> krarc was used again to open odt file instead of libreoffice
> trying to update : 
> krusader est déjà installé avec la version demandée
> (1:2.5.0-0neon+16.04+build1)
> 
> Is not it the last release ?

It is the last release but the fix is not in the release, you need to run git
master.

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

[krusader] [Bug 371765] Documents suddenly open as archives

[bugzilla_noreply]

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

--- Comment #13 from liv...@penserpouragir.org ---
from https://bugs.kde.org/show_bug.cgi?id=377000

I said it is fine now, it was a mistake.
krarc was used again to open odt file instead of libreoffice
trying to update : 
krusader est déjà installé avec la version demandée
(1:2.5.0-0neon+16.04+build1)

Is not it the last release ?

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

[okular] [Bug 377688] No output to print for PDF since update to 1.0.3

[Ian Newton]

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

--- Comment #5 from Ian Newton  ---
DM200_UM_EN.pdf is the original and DM200_UM_EN_3.pdf is the re-saved version
from Libre Office

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Michal Donat]

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

Michal Donat  changed:

   What|Removed |Added

 CC||mic...@donat.cz

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

[telepathy] [Bug 360976] Chat window is empty after second open of XMPP conference channel

[Tamás Gere]

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

--- Comment #3 from Tamás Gere  ---
UPDATE: I can rarely pop up chat window with textarea too by clicking on
contact. The success rate is same (~1/10).

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

[digikam] [Bug 377857] New: Ideas to improve usability of metadata sidebar

[Jens]

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

Bug ID: 377857
   Summary: Ideas to improve usability of metadata sidebar
   Product: digikam
   Version: 5.5.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: digikam-de...@kde.org
  Reporter: jens-bugs.kde@spamfreemail.de
  Target Milestone: ---

Created attachment 104657
  --> https://bugs.kde.org/attachment.cgi?id=104657=edit
improved metadata sidebar - mockup & screenshot

See also my post in digikam-users (and users's replies) starting 13.02.2017.

I originally come from iPhoto and similar commercial apps. My workflow
when importing images (and videos) into Digikam might reflect this a
little - I find myself constantly switching between tabs in Digikam to
perform simple image management / organizational tasks.

I think this can be improved a lot by modifying the layout and usability
of Digikam's "Properties" sidebar (the top one on the right) and
converting it into a summary-/ dashboard kind of sidebar which covers
80-90% of all requirements in one single place. Currently the "Properties"
sidebar is just a list of image and file properties and not used for editing at
all - which makes it kind of superfluous (IMHO).

I have created a mockup of how this sidebar can be improved by
incorporating simple metadata editing tasks. The idea is that for simple asset
management tasks (adding titles, ratings and tags, editing dates and
viewing basic image metadata) you *only* need this single sidebar. The
idea is *NOT* to squeeze all possible metadata into one dialog.

This is a little inspired by  iPhoto's organization of metadata which I
found quite usable.

Please have a look and tell me what you think.

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

[telepathy] [Bug 360976] Chat window is empty after second open of XMPP conference channel

[Tamás Gere]

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

--- Comment #2 from Tamás Gere  ---
I have same problem with a fresh install of KDE neon stable (KDE 5.9.3, KF
5.32, Qt 5.7.1).
Used gtalk (google) connection. In my case the textarea rarely (approx every
10th  times) getting visible on new chat window, but only when someone else
pops it up (writes to me when no chat window is open).

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

[krusader] [Bug 377000] openning odt files with krarc:/

[bugzilla_noreply]

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

--- Comment #9 from liv...@penserpouragir.org ---
I said it is fine now, it was a mistake.
krarc was used again to open odt file instead of libreoffice
trying to update : 
krusader est déjà installé avec la version demandée
(1:2.5.0-0neon+16.04+build1)

Is not it the last release ?

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

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

[Julian Seward]

https://bugs.kde.org/show_bug.cgi?id=303877
Bug 303877 depends on bug 377717, which changed state.

Bug 377717 Summary: Fix massive space leak when reading compressed debuginfo 
sections
https://bugs.kde.org/show_bug.cgi?id=377717

   What|Removed |Added

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

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

[valgrind] [Bug 377717] Fix massive space leak when reading compressed debuginfo sections

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

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

--- Comment #2 from Julian Seward  ---
Fixed, r16279.

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

[kaffeine] [Bug 351774] --no-xlib" to libvlc_new() error when watching tv

[Michal Donat]

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

Michal Donat  changed:

   What|Removed |Added

 CC||mic...@donat.cz

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

[kate] [Bug 377856] Kate Project plugin does not add 'search in project' on startup

[Christian Saemann]

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

Christian Saemann  changed:

   What|Removed |Added

 CC||christian.saem...@gmx.de

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

[kate] [Bug 377856] New: Kate Project plugin does not add 'search in project' on startup

[Christian Saemann]

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

Bug ID: 377856
   Summary: Kate Project plugin does not add 'search in project'
on startup
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: christian.saem...@gmx.de
  Target Milestone: ---

When I open a file of a project, kate adds the project tab to the bar with
"Documents" and "File Browser" on the left. It doesn't add the "in project"
option to the global search tab accessible via the button on the bottom
of the window. Instead, I have to deactivate the project plugin and reactivate
it in settings in order to get this option.

I'm running Kate 16.12.3-1.1 from openSUSE Tumbleweed.

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

[telepathy] [Bug 360976] Chat window is empty after second open of XMPP conference channel

[Tamás Gere]

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

Tamás Gere  changed:

   What|Removed |Added

 CC||g...@kani.hu

--- Comment #1 from Tamás Gere  ---
Created attachment 104656
  --> https://bugs.kde.org/attachment.cgi?id=104656=edit
Screenshot of issue

Here is my screenshot from KDE neon (stable) distribution: 
KDE 5.9.3, KF 5.32, Qt 5.7.1

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

[kontact] [Bug 377855] New: KMail crashes when selecting new email recipients

[Michele Roofe]

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

Bug ID: 377855
   Summary: KMail crashes when selecting new email recipients
   Product: kontact
   Version: 5.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: michele.ro...@gmail.com
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.8.0-42-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Opened new email in KMail
Click SELECT to select recipient email address. 
KMail crashed.
Repeated procedure and same result.

- Unusual behavior I noticed:
Nil.

- Custom settings of the application:

The crash can be reproduced every time.

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

Thread 32 (Thread 0x7f0bff1e1700 (LWP 17104)):
#0  0x7f0cf5fa0a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f0cf5f5bd4a in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0cf5f5c330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0cf5f5c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0cfd32737b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0cfd2cfffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0cfd0f89e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0cfd0fd808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0cf67866ba in start_thread (arg=0x7f0bff1e1700) at
pthread_create.c:333
#9  0x7f0cfc7f582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 31 (Thread 0x7f0c0e1e7700 (LWP 17102)):
#0  0x7f0cfc7e9b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0cf5f5c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0cf5f5c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0cfd32737b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0cfd2cfffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0cfd0f89e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0cfd0fd808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0cf67866ba in start_thread (arg=0x7f0c0e1e7700) at
pthread_create.c:333
#8  0x7f0cfc7f582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 30 (Thread 0x7f0bd700 (LWP 17091)):
#0  0x7ffca5504b0b in clock_gettime ()
#1  0x7f0cfc803c86 in __GI___clock_gettime (clock_id=1, tp=0x7f0bc9e0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f0cfd1a96c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0cfd324f09 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0cfd325475 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0cfd32685e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0cf5f5b91d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f0cf5f5c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f0cf5f5c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f0cfd32737b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f0cfd2cfffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f0cfd0f89e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f0cfd0fd808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f0cf67866ba in start_thread (arg=0x7f0bd700) at
pthread_create.c:333
#14 0x7f0cfc7f582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 29 (Thread 0x7f0c24bc3700 (LWP 16982)):
#0  0x7ffca5504b0b in clock_gettime ()
#1  0x7f0cfc803c86 in __GI___clock_gettime (clock_id=1, tp=0x7f0c24bc29e0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f0cfd1a96c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0cfd324f09 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0cfd325475 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0cfd32685e in ?? () from 

[amarok] [Bug 377854] New: Amarok crashes while querying MusicBrainz to update album tags

[Edward]

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

Bug ID: 377854
   Summary: Amarok crashes while querying MusicBrainz to update
album tags
   Product: amarok
   Version: 2.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: edwardb_...@shaw.ca
  Target Milestone: 2.9

Application: amarok (2.8.0)
KDE Platform Version: 4.14.30
Qt Version: 4.8.6
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
Querying MusicBrainz in order to update tags on Amy Winehouse's album "Lioness:
Hidden Treasures".
Crash happens consistently for this album in particular, with the progress bar
at about fifty percent. Does not happen with other albums.
My offhand guess: MusicBrainz is returning malformed data, and amarok is not
catching the resulting error and handling it gracefully.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f12fbda8940 (LWP 12823))]

Thread 23 (Thread 0x7f1246106700 (LWP 12857)):
#0  0x7f12f767d0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f12f912c066 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f12f4a6d69c in  () at /usr/lib64/libthreadweaver.so.4
#3  0x7f12f4a70133 in  () at /usr/lib64/libthreadweaver.so.4
#4  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#5  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#6  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#7  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#8  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#9  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#10 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#11 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#12 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#13 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#14 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#15 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#16 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#17 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#18 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#19 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#20 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#21 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#22 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#23 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#24 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#25 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#26 0x7f12f4a6ee4f in ThreadWeaver::Thread::run() () at
/usr/lib64/libthreadweaver.so.4
#27 0x7f12f912bb7f in  () at /usr/lib64/libQtCore.so.4
#28 0x7f12f7678734 in start_thread () at /lib64/libpthread.so.0
#29 0x7f12f8a6dd3d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f129685e700 (LWP 12854)):
#0  0x7f12f767d0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f12f912c066 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f12f4a6d69c in  () at /usr/lib64/libthreadweaver.so.4
#3  0x7f12f4a70133 in  () at /usr/lib64/libthreadweaver.so.4
#4  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#5  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#6  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#7  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#8  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#9  0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#10 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#11 0x7f12f4a7014c in  () at /usr/lib64/libthreadweaver.so.4
#12 0x7f12f4a6ee4f in ThreadWeaver::Thread::run() () at
/usr/lib64/libthreadweaver.so.4
#13 0x7f12f912bb7f in  () at /usr/lib64/libQtCore.so.4
#14 0x7f12f7678734 in start_thread () at /lib64/libpthread.so.0
#15 0x7f12f8a6dd3d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f129705f700 (LWP 12852)):
#0  0x7f12f767d0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f12f912c066 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f12f4a6d69c in  () at /usr/lib64/libthreadweaver.so.4
#3  0x7f12f4a70133 in  () at /usr/lib64/libthreadweaver.so.4
#4  0x7f12f4a7014c in  () at 

[digikam] [Bug 376615] Missing icon in GNOME shell dock

[Craig Drummond]

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

Craig Drummond  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #5 from Craig Drummond  ---
This is does not appwar to be fixed in 5.5.0

I've attached a screenshot that shows 2 digikam icons. The top one is the
launcher icon added to favourites, the second comes from the running digikam
instance.

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

[digikam] [Bug 376615] Missing icon in GNOME shell dock

[Craig Drummond]

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

--- Comment #4 from Craig Drummond  ---
Created attachment 104655
  --> https://bugs.kde.org/attachment.cgi?id=104655=edit
GNOME dock

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

[kdevelop] [Bug 371565] KDevelop can't find header files if the project path contains spaces

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||kf...@kde.org

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

[kdevelop] [Bug 371565] KDevelop can't find header files if the project path contains spaces

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #5 from Kevin Funk  ---
Thanks. I'll check again.

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

[krusader] [Bug 377828] Input focus on copy/move dialogue needs work

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Alex Bikadorov  ---
KDE 5 does not have a progress bar dialogue and the "File already exists"
dialog is instantly focused. Btw. both dialogs are not part of Krusader but
KF5/KDELibs.

And you should always be able to focus another dialog/window with ALT+Tab.

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

[digikam] [Bug 377849] albums disappear when the network is interrupted.

[weini]

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

--- Comment #3 from weini  ---
i used mysql (MariaDB)
the database is local.

First I used sqlite as a database.
Not even the captions and keywords were saved.

Then I found on digikam.org this article -> https://www.digikam.org/node/219
" filesystems (check this FAQ entry). But, network "
http://www.sqlite.org/faq.html#q5
And i have read the sqlite can not deal with network paths.
Then I switched to mysql.

Now the entire assignments (labels and keywords) are saved and are not lost any
more, but the problem remains with the loading of the picture folders.

The problem occurs only to whom digiKam is opened and then the network
connection breaks. If the connection to the network from the beginning is
missing and then opens digiKam is all still there and the images are correctly
marked as unavailable.

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

[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]

[Maik Qualmann]

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

--- Comment #78 from Maik Qualmann  ---
Git commit 2a54e446e2a9cf04d9b79360d1d12405a188a2c3 by Maik Qualmann.
Committed on 20/03/2017 at 19:49.
Pushed by mqualmann into branch 'master'.

apply visual patch for grouped images without background color function

M  +3-1app/items/imagedelegate.cpp
M  +22   -6libs/widgets/itemview/ditemdelegate.cpp
M  +1-1libs/widgets/itemview/ditemdelegate.h
M  +31   -6libs/widgets/itemview/itemviewimagedelegate.cpp
M  +20   -20   libs/widgets/itemview/itemviewimagedelegate.h
M  +34   -2libs/widgets/mainview/thumbbardock.cpp
M  +2-1libs/widgets/mainview/thumbbardock.h

https://commits.kde.org/digikam/2a54e446e2a9cf04d9b79360d1d12405a188a2c3

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

[kdenlive] [Bug 377853] git master - Project Settings window won't fit in 1366x768 screen size [screenshots included]

[Jesse]

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

--- Comment #1 from Jesse  ---
Created attachment 104654
  --> https://bugs.kde.org/attachment.cgi?id=104654=edit
screenshot example

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

[kdenlive] [Bug 377853] git master - Project Settings window won't fit in 1366x768 screen size [screenshots included]

[Jesse]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 377853] New: git master - Project Settings window won't fit in 1366x768 screen size [screenshots included]

[Jesse]

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

Bug ID: 377853
   Summary: git master - Project Settings window won't fit in
1366x768 screen size [screenshots included]
   Product: kdenlive
   Version: git-master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

Created attachment 104653
  --> https://bugs.kde.org/attachment.cgi?id=104653=edit
screenshot example - workspace spread view in Unity 7.5.0.

Opening the Project Settings dialog window won't fit in a screen size that's
1366x768. See attached screenshots for examples. Should somehow be resizable or
scroll-able so it can fit in smaller screen sizes.

Bug discovered on Kdenlive 17.03.70 via kdenlive-master ppa.
Ubuntu 16.10 x64, Unity 7.5.0 desktop environment, 1366x768 display resolution.
MLT 6.5.0, KDE Frameworks 5.26.0, Qt 5.6.1.

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

[kwin] [Bug 377826] On irregular shutdowns in Wayland session KWin needs to be started manually in X

[Roman Gilg]

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

--- Comment #2 from Roman Gilg  ---
Maybe it's unrelated to my DRM work and instead it has something to do with
this line in ~/.xsession-errors (logged when X session starts with KWin
crashing):

kwin_x11: symbol lookup error:
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so:
undefined symbol: _ZN4KWin21ModifierOnlyShortcutsC1Ev

I compile the KWin tree and install it directly with kdesrc-build.

In order to solve this problem I tried to:
* delete KWin build directory
* delete the file ../KWinX11Platform.so

But KWin still crashes in X11 and it shows the aforementioned error in
~/.xsession-errors.

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

[digikam] [Bug 377849] albums disappear when the network is interrupted.

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
Which kind of database do you use ? mysql or sqlite ? Remote of local ?

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

[digikam] [Bug 377849] albums disappear when the network is interrupted.

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Database-Setup

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

[digikam] [Bug 377849] albums disappear when the network is interrupted.

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Alben verschwinden wenn |albums disappear when the
   |Netzwerk unterbrochen ist.  |network is interrupted.

--- Comment #1 from caulier.gil...@gmail.com ---
The albums that disappear are on network drives to digiKam open when the
network connection is lost, or when an error. (Eg when the computer wakes up
from standby, the network connection, and thus the network drive is not
immediately available).
Once the network drive is accessible again, digiKam will import the whole
collection again again.
Depending on the scope of the collections of images this may take several
hours.

Why Digikam does not recognize the image collection has already been read on
the network drive.

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

[kdevelop] [Bug 377852] New: KDevelop crashing when repeating ('.') last 'o'/'O' command in Vi Mode.

[bugzilla_noreply]

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

Bug ID: 377852
   Summary: KDevelop crashing when repeating ('.') last 'o'/'O'
command in Vi Mode.
   Product: kdevelop
   Version: 5.0.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: tuxtor...@openmailbox.org
  Target Milestone: ---

Application: kdevelop (5.0.4)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.1-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

Editing code. Sometimes, when I hit period, to repeat my last action (I use Vi
mode), KDevelop crashes.
It crashes only when the edit command that is being repeated begins with 'o' or
'O'(so «new line & edit above / below» respectively). With 'i','a','I' or 'A',
there is no problem, even if in the edit there is a new line added.

- Custom settings of the application:

Vi mode enabled.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7fbdbb249700 (LWP 14930)):
#0  0x7fbdfee90756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbdf6bff234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fbdf6bff279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fbdfee8a2e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fbe0547754f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fbda50b1700 (LWP 14846)):
#0  0x7fbdfee90756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbe05b6558b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbdfa2661d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fbdfa26a9d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#18 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#19 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#20 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#21 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#22 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#23 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#24 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#25 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#26 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#27 0x7fbdfa26aa32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#28 0x7fbdfa265263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#29 0x7fbdfa268249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#30 0x7fbe05b646d8 in  () at /usr/lib/libQt5Core.so.5
#31 0x7fbdfee8a2e7 in start_thread () at /usr/lib/libpthread.so.0
#32 0x7fbe0547754f in clone () 

[systemsettings] [Bug 377851] New: i save my Settings and than crash

[Schmidberger Daniel]

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

Bug ID: 377851
   Summary: i save my Settings and than crash
   Product: systemsettings
   Version: 5.8.4
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dani_schm...@web.de
  Target Milestone: ---

Application: systemsettings5 (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-2-amd64 x86_64
Distribution: Debian GNU/Linux 9.0 (stretch)

-- Information about the crash:
i configure Systemeinstellung\Work-Space-effects and than i save the settings. 
After that i become the chrash-report

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbfb0ad5d40 (LWP 4428))]

Thread 7 (Thread 0x7fbf4700 (LWP 4613)):
#0  0x7fbfad1f354d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbfa82c99f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbfa82c9b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbfadb0706b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbfadab09ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fbfad8de0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fbfac25f6a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fbfad8e2da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fbfaa3fe424 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7fbfad1fc9bf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7fbf71516700 (LWP 4612)):
#0  0x7fbfad1f354d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbfa82c99f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbfa82c9b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbfadb0706b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbfadab09ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fbfad8de0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fbfac25f6a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fbfad8e2da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fbfaa3fe424 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7fbfad1fc9bf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7fbf7d734700 (LWP 4585)):
#0  0x7fbfad1f354d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbfa82c99f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbfa82c9d82 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbf85a94636 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fbfa82f13d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbfaa3fe424 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7fbfad1fc9bf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7fbf8c96c700 (LWP 4584)):
#0  0x7fbfad1f354d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbfa82c99f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbfa82c9b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbfa82c9b51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbfa82f13d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbfaa3fe424 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7fbfad1fc9bf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7fbf9692d700 (LWP 4431)):
#0  0x7fbfad1ef5bd in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbfa830dd20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbfa82c94be in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbfa82c9994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbfa82c9b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbfadb0706b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fbfadab09ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fbfad8de0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fbfb0c2b6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fbfad8e2da8 in ?? () from 

[kdeconnect] [Bug 377850] New: Add intents for command plugin

[bugzilla_noreply]

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

Bug ID: 377850
   Summary: Add intents for command plugin
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: k...@ashka.me
  Target Milestone: ---

Hi,

It would be useful to be able to call the command plugin (or any plugin, the
media player would benefit from that as well) from an external source (e.g.
Tasker) with intents, to execute commands on events from Tasker. Example
application: run defined command "systemctl suspend" when the phone disconnects
from wifi.

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

[Akonadi] [Bug 377656] akonadiserver is aborting

[Steve]

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

--- Comment #2 from Steve  ---
I think this is different because its dying via an abort() call. They are
usually placed in code to stop a program when its doing something that violates
some expectation. The idea is to force a coredump to collect a backtrace to get
an idea of what's wrong.

At line 8 the code throws a protocol exception and this probably comes near the
code mentioned in line 9. So, something unexpected in the imap protocol is
probably causing the issue.

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

[digikam] [Bug 377849] New: Alben verschwinden wenn Netzwerk unterbrochen ist.

[weini]

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

Bug ID: 377849
   Summary: Alben verschwinden wenn Netzwerk unterbrochen ist.
   Product: digikam
   Version: 5.5.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: chw...@googlemail.com
  Target Milestone: ---

Die Alben die auf Netzlaufwerken liegen verschwinden bei geöffnetem digiKam
wenn die Netzwerkverbindung unterbrochen wird, oder eine Störung hat. (z.B.
wenn der Computer aus dem Standby erwacht, ist die Netzwerkverbindung und somit
das Netzlaufwerk nicht sofort wieder erreichbar). 
Sobald das Netzlaufwerk wieder erreichbar ist, wird digiKam die komplette
Bildersammlung wieder erneut einlesen.
Je nach Umfang der Bildersammlungen kann dies mehrere Stunden dauern.

Warum erkennt Digikam nicht das die Bildersammlung auf dem Netzlaufwerk bereits
eingelesen wurde.

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

[kmail2] [Bug 365138] Regression: new taskbar icon hard to read on both default themes

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

Version|5.2.2   |5.4.3

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

[kwordquiz] [Bug 377848] New: Kwordquiz editor only show 20 rows

[Pedro Olaya]

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

Bug ID: 377848
   Summary: Kwordquiz editor only show 20 rows
   Product: kwordquiz
   Version: 0.9.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pe...@peterandlinda.com
  Reporter: pedro.ol...@openmailbox.org
  Target Milestone: ---

Files created always show 20 rows. I cannot read the 21 row or follows. Also
only print 20 rows although the file have 200. I use Debian testing. Thks &
Rgds

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

[kmail2] [Bug 371664] Changes to (at least) the trash folder associated with imap account don't take effect until after restarting kmail

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

Version|5.4.0   |5.4.2

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
Version|5.4.0   |5.4.3

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

[digikam] [Bug 271751] Allow to export Advanced Slideshow rendering as a video file

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||mllaum...@yahoo.com

--- Comment #8 from caulier.gil...@gmail.com ---
*** Bug 377842 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 377842] Export slideshow as movie

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---


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

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[Albert Vaca]

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

Albert Vaca  changed:

   What|Removed |Added

 CC||ci3...@gmail.com

--- Comment #16 from Albert Vaca  ---
*** Bug 367877 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 367877] Use the PC keyboard to type directly into the phone

[Albert Vaca]

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

Albert Vaca  changed:

   What|Removed |Added

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

--- Comment #2 from Albert Vaca  ---


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

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[Albert Vaca]

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

Albert Vaca  changed:

   What|Removed |Added

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

--- Comment #15 from Albert Vaca  ---
It has been implemented, will be part of the next release.

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

[kwin] [Bug 377847] New: Blender menus flicker when you navigate them

[bugzilla_noreply]

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

Bug ID: 377847
   Summary: Blender menus flicker when you navigate them
   Product: kwin
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sun...@hotmail.ru
  Target Milestone: ---

It happens only on Wayland session and only in KDE. I've tested with Gnome +
wayland and it works there just as good as in KDE X session.

Start Blender and open up, lets say, File menu and move your mouse up and down
within this menu. You'll see menu flickering.

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

[kwin] [Bug 377846] New: ClusterSSH causes windows to become immovable and non-resizable

[Alan Gano]

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

Bug ID: 377846
   Summary: ClusterSSH causes windows to become immovable and
non-resizable
   Product: kwin
   Version: 5.9.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alang...@gmail.com
  Target Milestone: ---

Gentoo x86_64; Kernel 4.9.6; 2 screens; multiple active desktops; nvidia
TwinView

ClusterSSH (cssh from commandline) is a utility to multiplex the keyboard to
multiple xterm windows.

Upon first keypress into the cssh input window, all windows can no longer be
resized or moved.  Normal operation otherwise.

Moving and resizing can be reinstated with a 'kwin_x11 --replace', until next
keypress into the cssh input window.

Happens in all versions over plasma 5 I've encountered -- it was worse (crash
crash crash) in earlier version.

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

[Discover] [Bug 377819] Can't review software

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #2 from Aleix Pol  ---
This is fixed in master, will be in 5.10.

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

[kwin] [Bug 377845] New: kwin craches at resume from standby

[bugzilla_noreply]

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

Bug ID: 377845
   Summary: kwin craches at resume from standby
   Product: kwin
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: guit...@hotmail.de
  Target Milestone: ---

Application: kwin_x11 (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-34-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
- What I was doing when the application crashed:
I pressed a key on my keyboard to get my system resumed from standby.
I am also wondering, why bugs.kde.org tells me 5.8.4 is the oldest supported
version, while my up to date kubuntu 16.10 has kwin 5.7.5 installed - this
sound wrong for me.

- Unusual behavior I noticed:
The screen was off for tty7 (off - not black color displayed), a switch to tty1
and switch back to tty7 appears to restart kwin. And I was able to logon again.
No session state seems to be lost (all programms were stil opened).

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7f8837988700 (LWP 11362)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f890023cb2b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x55cd1380f0c0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x55cd1381b0f0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f88fb1b54f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f88fb1b5dea in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f890023bc68 in QThreadPrivate::start (arg=0x55cd1381b070) at
thread/qthread_unix.cpp:341
#6  0x7f88fbb896ca in start_thread (arg=0x7f8837988700) at
pthread_create.c:333
#7  0x7f89025ed0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f88dce5f700 (LWP 11361)):
#0  0x7f89025e2ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8900464caf in qt_safe_select (nfds=29,
fdread=fdread@entry=0x7f88cc000a78, fdwrite=fdwrite@entry=0x7f88cc000d08,
fdexcept=fdexcept@entry=0x7f88cc000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f8900466754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f88cc000f98, writefds=0x7f88cc000d08, readfds=0x7f88cc000a78,
nfds=, this=0x7f88cc0008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f88cc0008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f8900466c6a in QEventDispatcherUNIX::processEvents
(this=0x7f88cc0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f89004110fa in QEventLoop::exec (this=this@entry=0x7f88dce5eca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f8900236d43 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f88face7c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f890023bc68 in QThreadPrivate::start (arg=0x55cd136af050) at
thread/qthread_unix.cpp:341
#9  0x7f88fbb896ca in start_thread (arg=0x7f88dce5f700) at
pthread_create.c:333
#10 0x7f89025ed0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f88df5ef700 (LWP 8370)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f890023cb2b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x55cd135b8b00) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x55cd133e14d0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f88fb1b54f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f88fb1b5dea in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f890023bc68 in QThreadPrivate::start (arg=0x55cd133e1450) at
thread/qthread_unix.cpp:341
#6  0x7f88fbb896ca in start_thread (arg=0x7f88df5ef700) at
pthread_create.c:333
#7  0x7f89025ed0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f88d4fe0700 (LWP 2392)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f88ff5d0574 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f88ff5d05b9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f88fbb896ca in start_thread (arg=0x7f88d4fe0700) at
pthread_create.c:333
#4  0x7f89025ed0af in clone () at

[kdeconnect] [Bug 374417] not working (segfault)

[kailed]

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

kailed  changed:

   What|Removed |Added

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

--- Comment #6 from kailed  ---
Weird, the android App was too old (0.7.*). Dunno why... I manually removed the
old version and installed the new one from Play store.

Now kdeconnect works fine..
Closing bug !

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

[krita] [Bug 344533] Vector layer duplication is broken (produces distorted paths)

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|LATER   |FIXED

--- Comment #14 from Dmitry Kazakov  ---
Ouch, I commented in a wrong bug. This bug is actually fixed in my branch :)

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

[krita] [Bug 347660] Freehand Path Tool on a Vector Layer with Fill option set to Pattern doesn't fill shape area with pattern

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com
 Resolution|--- |LATER
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Dmitry Kazakov  ---
In the current version of patterns in my branch patterns are not implemented.
So I'll mark the bug as 'later' so we could check the bug when the real
functionality is implemented.

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

[krita] [Bug 344533] Vector layer duplication is broken (produces distorted paths)

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |LATER

--- Comment #13 from Dmitry Kazakov  ---
In the current version of my Vector branch, filling of the shapes in not
supported. So i'll mark this bug as "later" so we could check when the patterns
thing will be implemented properly.

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

[krazy] [Bug 377753] Line number urls point to last line, not the correct displayed text one

[Friedrich W . H . Kossebau]

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

--- Comment #3 from Friedrich W. H. Kossebau  ---
Thanks Allen, can confirm that it is fixed for what I tested :)

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

[plasmashell] [Bug 377844] New: Plasma (plasmashell), signal: Segmentation fault - KOrganizer Calendar in Local Directory

[Don Curtis]

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

Bug ID: 377844
   Summary: Plasma (plasmashell), signal: Segmentation fault -
KOrganizer Calendar in Local Directory
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugrprt21...@online.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

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

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

Deleted several Calendars in Local Directory resources with a view to moving to
Akonadi calendar folders.

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

Thread 11 (Thread 0x7fe352292700 (LWP 8968)):
#0  0x7fe437aa649d in poll () at /lib64/libc.so.6
#1  0x7fe434121314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe43412142c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe4383bf32b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe3280f9150, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fe43836cfdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe352291cb0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7fe4381a7f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7fe43b4d99c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fe4381ac9e9 in QThreadPrivate::start(void*) (arg=0x3ac7230) at
thread/qthread_unix.cpp:341
#8  0x7fe4372a5734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe437aaed3d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fe3544a4700 (LWP 8875)):
#0  0x7fe437aa649d in poll () at /lib64/libc.so.6
#1  0x7fe434121314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe43412142c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe4383bf32b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe33c01fee0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fe43836cfdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe3544a3cd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7fe4381a7f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7fe4381ac9e9 in QThreadPrivate::start(void*) (arg=0xfce130) at
thread/qthread_unix.cpp:341
#7  0x7fe4372a5734 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe437aaed3d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fe37335c700 (LWP 5422)):
#0  0x7fe4341627d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fe434120d4b in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fe4341212a8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fe43412142c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fe4383bf32b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe36c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fe43836cfdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe37335bc90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fe4381a7f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7fe3747ae8f7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#8  0x7fe4381ac9e9 in QThreadPrivate::start(void*) (arg=0x29947b0) at
thread/qthread_unix.cpp:341
#9  0x7fe4372a5734 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe437aaed3d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fe37ea34700 (LWP 5268)):
#0  0x7fe4341627b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fe434120ef6 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fe434121388 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fe43412142c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fe4383bf32b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fe3780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fe43836cfdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fe37ea33c70, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fe4381a7f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7fe43c060632 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7fe4381ac9e9 in QThreadPrivate::start(void*) (arg=0x1731a90) at
thread/qthread_unix.cpp:341
#9  0x7fe4372a5734 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe437aaed3d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fe387e6c700 (LWP 5167)):
#0  0x7fe4372aa0af in 

[plasmashell] [Bug 377526] Plasma Task Manager Widget Use Too Much Space when Screen Edging to Left or Right.

[tonny sofijan]

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

--- Comment #2 from tonny sofijan  ---
Thanks Eike, Look forward for 5.10!
PS: I think the problem is in the padding, not the icon.

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

[kwin] [Bug 375868] Window decorations not rendering properly on HiDPI

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/bfbcd0197181657d5dfac953a
   ||d77dd3de2ee7e92
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Marco Martin  ---
Git commit bfbcd0197181657d5dfac953ad77dd3de2ee7e92 by Marco Martin.
Committed on 20/03/2017 at 16:06.
Pushed by mart into branch 'master'.

support for high dpi in aurorae

Summary:
aurorae themes have hardoded sizes in pixels in their config files,
but the framesvgs scale by themselves based on font dpi leading
to corrupt results

scale all sizes using the same logic(that's also used in c++ based
kdecorations), gives correct looking scaled decorations

Test Plan: see screenshot

Reviewers: #plasma, graesslin

Reviewed By: #plasma, graesslin

Subscribers: plasma-devel, kwin, #kwin

Tags: #kwin

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

M  +46   -35   plugins/kdecorations/aurorae/src/lib/themeconfig.cpp

https://commits.kde.org/kwin/bfbcd0197181657d5dfac953ad77dd3de2ee7e92

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

[kexi] [Bug 377579] Criteria cannot be saved in Query Designer

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

Summary|Criterias cannot be saved   |Criteria cannot be saved in
   |in Query Designer   |Query Designer

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

[plasmashell] [Bug 377843] New: [Wayland] next tooltip is shown on the first element you hovered around

[bugzilla_noreply]

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

Bug ID: 377843
   Summary: [Wayland] next tooltip is shown on the first element
you hovered around
   Product: plasmashell
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: sun...@hotmail.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

1. Open two windows
2. However a mouse pointer near the first one. You can see a tooltip
3. Move mice pointer to another window on panel. You can see that tooltip
changes but is shown at the same place it first appeared.

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

[digikam] [Bug 377842] New: Export slideshow as movie

[Marius]

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

Bug ID: 377842
   Summary: Export slideshow as movie
   Product: digikam
   Version: 5.5.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Export
  Assignee: digikam-de...@kde.org
  Reporter: mllaum...@yahoo.com
  Target Milestone: ---

There used to be an export tool in Digikam in order to create a slideshow
presentation as a movie file but that is not present any more. It would be
great to have this back. I use ffDiaporama as a workaround. The current
slideshow functionality in Digikam is great; it would be even better if we
could save the resulting slideshow as a movie file.

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

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI

[Diane M]

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

Diane M  changed:

   What|Removed |Added

Summary|Missing memory check for|Missing memory check for
   |futex() uaddr arg for   |futex() uaddr arg for
   |FUTEX_WAKE and  |FUTEX_WAKE and
   |FUTEX_WAKE_BITSET   |FUTEX_WAKE_BITSET, check
   ||only 4 args for
   ||FUTEX_WAKE_BITSET, and 2
   ||args for FUTEX_TRYLOCK_PI

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

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET

[Diane M]

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

--- Comment #1 from Diane M  ---
In addition to the previously-described problems:

- FUTEX_WAKE_BITSET should not do scalar read check on all 6 arguments;
  it should check uaddr, op, val, and val3 only.

- FUTEX_TRYLOCK_PI should check only uaddr and op

Here is a modified patch:

diff -r 231368959406 coregrind/m_syswrap/syswrap-linux.c
--- a/coregrind/m_syswrap/syswrap-linux.c   Tue Mar 14 09:47:29 2017 -0700
+++ b/coregrind/m_syswrap/syswrap-linux.c   Mon Mar 20 08:26:03 2017 -0700
@@ -1633,9 +1633,11 @@
   }
   break;
case VKI_FUTEX_WAKE_BITSET:
-  PRE_REG_READ6(long, "futex",
-vki_u32 *, futex, int, op, int, val,
-int, dummy, int, dummy2, int, val3);
+  PRE_REG_READ3(long, "futex",
+vki_u32 *, futex, int, op, int, val);
+  if (VG_(tdict).track_pre_reg_read) {
+ PRA6("futex",int,val3);
+  }
   break;
case VKI_FUTEX_WAIT:
case VKI_FUTEX_LOCK_PI:
@@ -1645,11 +1647,11 @@
   break;
case VKI_FUTEX_WAKE:
case VKI_FUTEX_FD:
-   case VKI_FUTEX_TRYLOCK_PI:
   PRE_REG_READ3(long, "futex",
 vki_u32 *, futex, int, op, int, val);
   break;
case VKI_FUTEX_UNLOCK_PI:
+   case VKI_FUTEX_TRYLOCK_PI:
default:
   PRE_REG_READ2(long, "futex", vki_u32 *, futex, int, op);
   break;
@@ -1678,14 +1680,11 @@
case VKI_FUTEX_FD:
case VKI_FUTEX_TRYLOCK_PI:
case VKI_FUTEX_UNLOCK_PI:
+   case VKI_FUTEX_WAKE:
+   case VKI_FUTEX_WAKE_BITSET:
   PRE_MEM_READ( "futex(futex)", ARG1, sizeof(Int) );
  break;

-   case VKI_FUTEX_WAKE:
-   case VKI_FUTEX_WAKE_BITSET:
-  /* no additional pointers */
-  break;
-
default:
   SET_STATUS_Failure( VKI_ENOSYS );   // some futex function we don't
understand
   break;

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