[krusader] [Bug 377092] Krusader crashed on opening jpeg image in built-in viewer (using F3)

[bugzilla_noreply]

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

--- Comment #1 from s-tr...@list.ru ---
Tried to open same picture again after restarting Krusader - it opened fine at
second time.

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

[krusader] [Bug 377092] New: Krusader crashed on opening jpeg image in built-in viewer (using F3)

[bugzilla_noreply]

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

Bug ID: 377092
   Summary: Krusader crashed on opening jpeg image in built-in
viewer (using F3)
   Product: krusader
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: s-tr...@list.ru
  Target Milestone: ---

Application: krusader (2.5.0 "Clear Skies")

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-8-generic x86_64
Distribution: Ubuntu Zesty Zapus (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Selected picture and pressed F3 on it, Krusader crashed...

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f7921578f80 (LWP 7204))]

Thread 5 (Thread 0x7f78dd682700 (LWP 22872)):
[KCrash Handler]
#6  0x7f791afb2f01 in __memcmp_sse4_1 () at
../sysdeps/x86_64/multiarch/memcmp-sse4.S:1452
#7  0x7f78f403db60 in std::_Rb_tree,
std::pair const, std::__cxx11::basic_string >,
std::_Select1st const,
std::__cxx11::basic_string
> >, std::less >,
std::allocator const,
std::__cxx11::basic_string
> >
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator const,
std::__cxx11::basic_string
> >, std::__cxx11::basic_string const&) () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#8  0x7f78f4118199 in  () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#9  0x7f78f4118a35 in  () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#10 0x7f78f4118dd7 in  () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#11 0x7f78f41435f0 in  () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#12 0x7f78f410b2d4 in  () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#13 0x7f78f4107c81 in Exiv2::XmpParser::initialize(void (*)(void*, bool),
void*) () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#14 0x7f78f410978c in Exiv2::XmpParser::decode(Exiv2::XmpData&,
std::__cxx11::basic_string
const&) () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#15 0x7f78f408fe72 in Exiv2::JpegBase::readMetadata() () at
/usr/lib/x86_64-linux-gnu/libexiv2.so.14
#16 0x7f78f56c92d0 in Gwenview::Exiv2ImageLoader::load(QByteArray const&)
() at /usr/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#17 0x7f78f56a9388 in  () at /usr/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#18 0x7f78f56a74b1 in  () at /usr/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#19 0x7f791b94803f in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f791b94bc98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f7919f516ca in start_thread (arg=0x7f78dd682700) at
pthread_create.c:333
#22 0x7f791af4f0ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f78c77fe700 (LWP 22871)):
[KCrash Handler]
#6  0x7f791afb2f01 in __memcmp_sse4_1 () at
../sysdeps/x86_64/multiarch/memcmp-sse4.S:1452
#7  0x7f78f403db60 in std::_Rb_tree,
std::pair const, std::__cxx11::basic_string >,
std::_Select1st const,
std::__cxx11::basic_string
> >, std::less >,
std::allocator const,
std::__cxx11::basic_string
> >
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator const,
std::__cxx11::basic_string
> >, std::__cxx11::basic_string const&) () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#8  0x7f78f4118199 in  () at 

[kmail2] [Bug 375149] Kmail deletes emails from folder after switching to folder

[Vytautas]

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

--- Comment #12 from Vytautas  ---
Interesting, that filter logs doesn't show no suspicious activity.

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

[kdevelop] [Bug 376319] Projects base directory not saved

[Anton Anikin]

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

Anton Anikin  changed:

   What|Removed |Added

 CC||anton.ani...@htower.ru

--- Comment #2 from Anton Anikin  ---
> In my opinion we should make it a global setting again.
+1

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

[neon] [Bug 377091] New: Installation option missing in 2017-03-01 images

[teefax]

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

Bug ID: 377091
   Summary: Installation option missing in 2017-03-01 images
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: isk...@posteo.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

The live/installation images from 2017-03-01 of both the User and the User LTS
edition seem to be missing an installer. The system boots into the live
desktop, but there is no icon on the desktop or an entry in the application
menu to start the installation.

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

[umbrello] [Bug 123633] new diagram type: object diagram

[Ralf Habacker]

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

--- Comment #7 from Ralf Habacker  ---
Git commit 576a4346ba591796142d716b2dab00fc86ae5708 by Ralf Habacker.
Committed on 02/03/2017 at 06:48.
Pushed by habacker into branch 'master'.

Refactor UMLInstance to be more UML and XMI 1.4 compatible.

- Create classifier instance on construction if not present
  and save it internal instead to be a non sharable classifier.
  Class UMLInstance itself stays to be derived from UMLClassifier
  because of the usage of UMLAttribute representing instance
  attributes.
- Save and load 'classifier' attribute to be xmi 1.4 compatible

M  +0-2CMakeLists.txt
M  +1-1umbrello/CMakeLists.txt
M  +1-1umbrello/cmds.h
R  +13   -14   umbrello/cmds/generic/cmdrenameumlinstancetype.cpp [from:
umbrello/cmds/generic/cmdrenameumlinstance.cpp - 056% similarity]
R  +17   -13   umbrello/cmds/generic/cmdrenameumlinstancetype.h [from:
umbrello/cmds/generic/cmdrenameumlinstance.h - 055% similarity]
M  +4-5umbrello/dialogs/pages/classgeneralpage.cpp
M  +98   -17   umbrello/uml1model/instance.cpp
M  +11   -4umbrello/uml1model/instance.h
M  +1-2umbrello/umlwidgets/associationwidget.cpp
M  +23   -9umbrello/umlwidgets/classifierwidget.cpp
M  +3-0umbrello/umlwidgets/widget_factory.cpp

https://commits.kde.org/umbrello/576a4346ba591796142d716b2dab00fc86ae5708

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working

[Jesse]

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

--- Comment #5 from Jesse  ---
@Wegwerf, Yes, I went to Add Clip, then selected all of the images in the
dialog box, then checked the "import images as sequence", then clicked OK. They
imported with the duration I'd put in settings for single still images, leading
me to believe Kdenlive was recognizing them as single images during import.

@farid, sorry for the delay in my replies -- been super busy with some new
virtual reality projects. Cool stuff, but I don't want to let it sway my
devotion to Kdenlive and free video editing. :) I'll try to be more prompt in
my replies.

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

[gwenview] [Bug 202414] allow to hide status bar and toolbar

[bugzilla_noreply]

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

un4tt3n...@live.com changed:

   What|Removed |Added

 CC||un4tt3n...@live.com

--- Comment #5 from un4tt3n...@live.com ---
Was surprised that this can't be done. It is very important for an image viewer
to be able to take the focus away from itself and put it on the picture.

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

[kpat] [Bug 377090] New: Sounds quit working 3 to 5 minutes into game

[Steve Ebey]

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

Bug ID: 377090
   Summary: Sounds quit working 3 to 5 minutes into game
   Product: kpat
   Version: 3.6
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: sde...@pldi.net
CC: kde-games-b...@kde.org
  Target Milestone: ---

Running fedora 25, kernel 4.9.12, 16gb ram, amd 6 core 3.5Ghz, Nvidia GTX970,
Creative 7.1 surround sound.  Starts game, sound for care movement, then after
3 to 5 minutes, sometimes less, sound quits, no notification, no crash. Exit
and start again, sound is back, for around 3 to 5 minutes.  All other sound
related programs work fine.

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

[kwin] [Bug 377074] Unreliable caps lock key with Xwayland

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Fixed in XWayland 1.19. I told neon a million times that this needs upgrading.

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

[plasmashell] [Bug 377088] Plasmashell crashing

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash
 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck  ---
The OpenCV package is compiled against Qt4, but is loaded via VLC into a Qt5
application. Please report this issue to the bug tracker of your distribution.

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

[kdenlive] [Bug 376494] Bin effect parameters do not reset properly

[farid]

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

farid  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||snd.no...@gmail.com
Version|16.12.1 |16.12.2

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

[kdenlive] [Bug 376495] Bin effects expand when changing anything in the effect stack

[farid]

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

--- Comment #1 from farid  ---
I reproduce this in archlinux as well...

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

[kdenlive] [Bug 376495] Bin effects expand when changing anything in the effect stack

[farid]

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

farid  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||snd.no...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working

[farid]

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

--- Comment #4 from farid  ---
Could you please provide some feedback?

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

[kdenlive] [Bug 376954] overwrite mode crash

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
That screenshot doesn't mean you have the latest version. You can go to the
Help menu and click About and there you'll see which version you have. In case
it isn't the latest you can go here and follow the instructions on how to
install it: https://kdenlive.org/download/

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

[kdevelop] [Bug 377089] New: Centos7 x86_64

[Jetur]

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

Bug ID: 377089
   Summary: Centos7 x86_64
   Product: kdevelop
   Version: 5.0.80
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Build tools: CMake
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: plfl...@163.com
  Target Milestone: ---

Steps to Reproducd:
1. Create a Cmake project with a CMakeLists.txt like:
project(project)
...
add_subdirectory(project1)
add_subdirectory(project2)
add_subdirectory(project3)
...
2. Right-click the subdirection(such as project1) target and choose `Build
Selection`

Expected Results:
KDevelop builds the subdirectory(such as project1) target.

Actual Results:
KDevelop builds all subdirectory. Same `Build All`.

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

[plasmashell] [Bug 377088] New: Plasmashell crashing

[Rick]

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

Bug ID: 377088
   Summary: Plasmashell crashing
   Product: plasmashell
   Version: master
  Platform: openSUSE RPMs
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rick_ree...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

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

Thread 8 (Thread 0x7f58c1191700 (LWP 6685)):
#0  0x7f59896a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f598a59734b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f598e4b41cb in ?? () from /usr/lib64/libQt5Quick.so.5
#3  0x7f598e4b4663 in ?? () from /usr/lib64/libQt5Quick.so.5
#4  0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f5989ea402d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f58d57ef700 (LWP 6673)):
#0  0x7f59896a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f598a59734b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f598e4b41cb in ?? () from /usr/lib64/libQt5Quick.so.5
#3  0x7f598e4b4663 in ?? () from /usr/lib64/libQt5Quick.so.5
#4  0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f5989ea402d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f58d6398700 (LWP 6671)):
#0  0x7f598a7c8a63 in ?? () from /usr/lib64/libQt5Core.so.5
#1  0x7f59865784ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f5986578d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f5986578f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f598a7c8d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f598a76fd53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f598a59161a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f598e441282 in ?? () from /usr/lib64/libQt5Quick.so.5
#8  0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f5989ea402d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f595e27b700 (LWP 6669)):
#0  0x7f59896a903f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f599007486b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f5990074899 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5989ea402d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f595fbbd700 (LWP 6668)):
#0  0x7f5989e97ccd in read () from /lib64/libc.so.6
#1  0x7f5982015f55 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.101
#2  0x7f59865b9b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f5986578999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f5986578df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f5986578f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f598a7c8d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#7  0x7f598a76fd53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f598a59161a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#9  0x7f598d8a5e18 in ?? () from /usr/lib64/libQt5Qml.so.5
#10 0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5
#11 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0
#12 0x7f5989ea402d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f59654c4700 (LWP 6667)):
#0  0x7f598657858b in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f5986578d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5986578f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f598a7c8d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f598a76fd53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f598a59161a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f598d8a5e18 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f5989ea402d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f59717b0700 (LWP )):
#0  0x7f59865761c9 in ?? () from /usr/lib64/libglib-2.0.so.0

[frameworks-modemmanager-qt] [Bug 346527] plasmashell keeps on crashing after login

[Rick]

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

Rick  changed:

   What|Removed |Added

 CC||rick_ree...@yahoo.com

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

[kmymoney4] [Bug 377087] New: Investment Share quantity limited to one hundredths

[bugzilla_noreply]

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

Bug ID: 377087
   Summary: Investment Share quantity limited to one hundredths
   Product: kmymoney4
   Version: 4.8.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: lnx...@westlot.net
  Target Milestone: ---

I have two stocks where I reinvest the dividends each quarter, which results in
fractional shares up into the hundred thousandths of a share.  KMyMoney rounds
share quantities to one hundredths which results in incorrect value of
investment.  In both cases I have set the fraction to 1/10 in the
Investment Detail wizard.  KMyMoney continues to round the quantity to one
hundredths and fill the last three places with zeros.  I have tried setting
Price entry to 'Total for all shares' and 'Price per share' to no avail.

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

[kdevelop] [Bug 377045] On Windows, KDevelop fails to recognize the c++ standard library

[bugzilla_noreply]

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

--- Comment #3 from icze...@gmail.com ---
OK. Are there any plans to detect the compiler's STL include directory in the
future?

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

[dolphin] [Bug 377086] New: Terminal Panel opens empty - no terminal is available on Ubuntu 16.04

[pavelbrilliant]

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

Bug ID: 377086
   Summary: Terminal Panel opens empty - no terminal is available
on Ubuntu 16.04
   Product: dolphin
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: terminal
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pavel.brilli...@gmail.com
  Target Milestone: ---

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

OS Ubuntu 16.04
dolphin was installed via 
"sudo apt-get install dolphin"

When I open the terminal (either via the menu option or via the Dolphin
shortcut) - the empty panel appears at the bottom of Dolphin, and no terminal
opens.

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

[kded-appmenu] [Bug 377078] Plasma crash when clicking on duplicated app menu buttons

[Filzmaier Josef]

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

Filzmaier Josef  changed:

   What|Removed |Added

 CC||j.filzma...@gmx.at

--- Comment #1 from Filzmaier Josef  ---
I can confirm this behaviour on Arch Linux.

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

[plasmashell] [Bug 377085] New: Glitches and crash

[bugzilla_noreply]

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

Bug ID: 377085
   Summary: Glitches and crash
   Product: plasmashell
   Version: 5.8.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: masterofn...@protonmail.ch
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.6.2
Frameworks Version: 5.29.0
Operating System: Linux 4.9.9-100.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

Some glitches in the panel (overlaps, delays). Seen a couple of times before -
reload obviously helps.

The crash can be reproduced sometimes.

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

Thread 15 (Thread 0x7fa38cff9700 (LWP 1988)):
#0  0x7fa469ab9bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa46b37203a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fa3adbfd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fa3adc01a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fa3adbfca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fa3adc01ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fa3adbfca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fa3adbff909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fa46b3719ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fa469ab45ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fa46a7650ed in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fa38d7fa700 (LWP 1987)):
#0  0x7fa469ab9bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa46b37203a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fa3adbfd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fa3adc01a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fa3adbfca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fa3adc01ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fa3adbfca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fa3adbff909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fa46b3719ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fa469ab45ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fa46a7650ed in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fa38dffb700 (LWP 1986)):
#0  0x7fa469ab9bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa46b37203a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fa3adbfd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fa3adc01a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fa3adbfca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fa3adc01ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fa3adbfca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fa3adbff909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fa46b3719ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fa469ab45ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fa46a7650ed in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fa38e7fc700 (LWP 1985)):
#0  0x7fa469ab9bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa46b37203a in QWaitCondition::wait(QMutex*, unsigned long) () at

[konqueror] [Bug 377084] New: WebEnginePart does not render kio output (kio_help, kio_man, ...)

[Luigi Toscano]

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

Bug ID: 377084
   Summary: WebEnginePart does not render kio output (kio_help,
kio_man, ...)
   Product: konqueror
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: luigi.tosc...@tiscali.it
  Target Milestone: ---

The WebEnginePart (default rendered) does not render the output from kioslaves
like kio_help, kio_man, kio_gopher, and probably all of the others which
renders HTML. The error printed is:

---
This site can’t be reached

The webpage at  might be temporarily down or it may have moved
permanently to a new web address.
ERR_UNKNOWN_URL_SCHEME
--

This is not a Konqueror issue, as the "KHTML" view mode renders correctly those
contents.
This issue is visible in from Applications 16.12 up to the last git master.

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

[krita] [Bug 376682] the cursor keeps disappearing

[akuk]

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

--- Comment #2 from akuk  ---
graphic card:


Name: Intel(R) HD Graphics 3000

Manufacturer: Intel Corporation

Chip Type: Intel(R) HD Graphics family

DAC Type: Internal

Approx. Total Memory: 1696 MB

Current Display Mode: 1366 x 768 (32 bit) (40Hz)

Monitor: Generic PNP monitor


Drivers:


Driver Provider: Intel Corporation

Driver date: 5/26/2015

Driver Version: 9.17.10.4229

Digital Signer:Microsoft Windows Hardware Compatibility Publisher
System Type: 64-bit operating system

Canvas:
All of the canvas have the same issue ( but all setting are used for both the
animaton and custom document)

Predefined: A3(600 ppi
width: 11 inches
Lenght: 16 inches
Resolution: 600 ppi
Model: RGB /Alpha
Depth: 8-bit interger/channel
Profile: sRGB-elle-V2-srgbtrc.icc (Default)


Linux:
I am not sure what the Linux is or if I have it, I am sorry about that
inconvenience




I am not sure I gave t too much information or the right info . If there is an
issue regarding the information I gave please contact me as soon as possible.


From: wolthera 
Sent: February 21, 2017 9:51 PM
To: sandyponce...@hotmail.com
Subject: [krita] [Bug 376682] the cursor keeps disappearing

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
Which graphics card and drivers do you have, what type of canvas are you
working on, and which version of Linux are you using?

--
You are receiving this mail because:
You reported the bug.

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

[plasmashell] [Bug 377083] New: Plasma crash

[Ian Snow]

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

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

Application: plasmashell (5.9.3)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.11-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Clicking the vertical Default button in top left hand corner causes Plasma to
crash

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f2d97051700 (LWP 6188)):
#0  0x7f2e5b46a4ed in read () at /usr/lib/libc.so.6
#1  0x7f2e562d0aa0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f2e5628c26e in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f2e5628c744 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f2e5628c8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f2e5bd9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f2e5bd3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f2e5bb5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f2d999230a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#9  0x7f2e5bb626d8 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f2e5aa2d454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f2e5b4777df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f2daccf5700 (LWP 6182)):
#0  0x7f2e5628bdbe in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f2e5628c6cb in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f2e5628c8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f2e5bd9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f2e5bd3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f2e5bb5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f2e5f84afd6 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f2e5bb626d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f2e5aa2d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f2e5b4777df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f2e377ba700 (LWP 6181)):
#0  0x7f2e5aa3310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2e6153f234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f2e6153f279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f2e5aa2d454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2e5b4777df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f2e41533700 (LWP 6180)):
#0  0x7f2e5b46a4ed in read () at /usr/lib/libc.so.6
#1  0x7f2e562d0aa0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f2e5628c26e in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f2e5628c744 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f2e5628c8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f2e5bd9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f2e5bd3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f2e5bb5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f2e5ec97025 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f2e5bb626d8 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f2e5aa2d454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f2e5b4777df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f2e437c8700 (LWP 6179)):
#0  0x7f2e5b46e48d in poll () at /usr/lib/libc.so.6
#1  0x7f2e5628c7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f2e5628c8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f2e5bd9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f2e5bd3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f2e5bb5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f2e5ec97025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f2e5bb626d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f2e5aa2d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f2e5b4777df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f2e493ef700 (LWP 6178)):
#0  0x7f2e5b46e48d in poll () at /usr/lib/libc.so.6
#1  0x7f2e5628c7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f2e5628c8bc in g_main_context_iteration () at

[konqueror] [Bug 377082] New: konqueror browser crashes while using split screen

[Kurt Seebauer]

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

Bug ID: 377082
   Summary: konqueror browser crashes while using split screen
   Product: konqueror
   Version: 5.0.97
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: kurt_seeba...@yahoo.de
  Target Milestone: ---

Application: konqueror (5.0.97)

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

-- Information about the crash:
- What I was doing when the application crashed:
open konqueror with vertically split screen and open heise.de and golem.de in
them

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5b29b90940 (LWP 22294))]

Thread 27 (Thread 0x7f5a57c49700 (LWP 22567)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f5a66ffd700 (LWP 22556)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f5a677fe700 (LWP 22554)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f5a67fff700 (LWP 22553)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f5a6c86d700 (LWP 22552)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f5a6d06e700 (LWP 22551)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f5a8affd700 (LWP 22550)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f5af1f06700 (LWP 22549)):
#0  0x7f5b1eefb4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5b23d672b6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5b23d62ae2 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5b23d664c8 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5b1eef5454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5b2943437f in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f5a8b7fe700 (LWP 22467)):
#0  0x7f5b1eefb4b8 in 

[kdevelop] [Bug 377027] KDevelop could feature a Designer UI

[Kevin Funk]

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

--- Comment #4 from Kevin Funk  ---
Huh? You can simply open a .ui file in designer by right-clicking the file in
the project tree view -> Open With -> Qt Designer

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

[Discover] [Bug 377081] New: Icons squashed horizontally in Discover

[Alex]

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

Bug ID: 377081
   Summary: Icons squashed horizontally in Discover
   Product: Discover
   Version: 5.9.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ene...@gmail.com
  Target Milestone: ---

Created attachment 104308
  --> https://bugs.kde.org/attachment.cgi?id=104308=edit
Gif showing squashed icons

All is visible on gif, nothing important, just it will look better.

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

[digikam] [Bug 377072] Cannot read video metadata

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Metadata from video is supported through Exiv2 shared library.

The Exiv2 0.25, the last stable have serious problems with video files. This
feature is optional in Exiv2 and certainly disabled at compilation time by
packager.

Next 0.26 (not yet released) will be better so far, and we use it in digiKam
bundle as ApppImage for Linux. You can try 5.5.0 pre release with Exiv2 0.26
here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Note : depending of video format, some files cannot be read by Exiv2 yet. Look
in Exiv2 web site for details.

Gilles Caulier

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

[plasmashell] [Bug 377080] New: PlasmaShell Crash (libnvidia-glcore.so.378.13)

[Michael Chinn]

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

Bug ID: 377080
   Summary: PlasmaShell Crash (libnvidia-glcore.so.378.13)
   Product: plasmashell
   Version: 5.9.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: michael.ch...@simpleprecision.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.2)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.11-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:  Desktop idle. Turned monitor
off. Left for 1 hr. Turned on. Crash

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

Thread 33 (Thread 0x7f005c7f9700 (LWP 28266)):
#0  0x7f019e4de4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f017b14be44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7f0179e69394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f017b14b12c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 32 (Thread 0x7f005cffa700 (LWP 28265)):
#0  0x7f019e4de10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f019f60e58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01a3367665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f01a3367f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f019f60d6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 31 (Thread 0x7f005d7fb700 (LWP 24580)):
#0  0x7f019e4de4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f017b14be44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7f0179e69394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f017b14b12c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 30 (Thread 0x7f005dffc700 (LWP 24579)):
#0  0x7f019e4de10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f019f60e58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01a3367665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f01a3367f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f019f60d6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 29 (Thread 0x7f005e7fd700 (LWP 24341)):
#0  0x7f019e4de4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f017b14be44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7f0179e69394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f017b14b12c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 28 (Thread 0x7f00667fc700 (LWP 24340)):
#0  0x7f019e4de10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f019f60e58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01a3367665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f01a3367f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f019f60d6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 27 (Thread 0x7f005f7ff700 (LWP 23717)):
#0  0x7f019e4de4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f017b14be44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7f0179e69394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f017b14b12c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7f019e4d8454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f019ef227df in clone () at /usr/lib/libc.so.6

Thread 26 (Thread 0x7f00677fe700 (LWP 23716)):
#0  0x7f019e4de10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f019f60e58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01a3367665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f01a3367f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f019f60d6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f019e4d8454 in start_thread 

[digikam] [Bug 377039] Network Collections cause hang on "Reading Database"

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #14 from caulier.gil...@gmail.com ---
No need to check 5.4.0 in this case. 5.5.0 fix it, it's perfect. A lots of
changes have changed with database interface that can explain the dysfunction.

Gilles Caulier

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

[kontact] [Bug 377079] New: Crash after saving contact with new category

[rainer]

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

Bug ID: 377079
   Summary: Crash after saving contact with new category
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@munin-soft.de
  Target Milestone: ---

Application: kontact (5.4.2)

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

-- Information about the crash:
I edited an existing contact. I wanted to add a category and as the desired one
was not existing, I added it in the dialog and selected it for the contact.
Shortly after concluding my change with 'OK', Kontact crashed, I guess while
syncing with Akonadi

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f292965fe00 (LWP 6638))]

Thread 45 (Thread 0x7f2749ffb700 (LWP 1403)):
#0  0x7ffe4bee8949 in  ()
#1  0x7ffe4bee8bd9 in clock_gettime ()
#2  0x7f29260aa216 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f2749ffa9e0) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f2926a4c771 in qt_gettime() (ts=0x7f2749ffa9e0, clock=) at tools/qelapsedtimer_unix.cpp:109
#4  0x7f2926a4c771 in qt_gettime() (frac=,
sec=) at tools/qelapsedtimer_unix.cpp:164
#5  0x7f2926a4c771 in qt_gettime() () at tools/qelapsedtimer_unix.cpp:173
#6  0x7f2926bc8e09 in QTimerInfoList::updateCurrentTime()
(this=this@entry=0x7f28d4004350) at kernel/qtimerinfo_unix.cpp:91
#7  0x7f2926bc93b5 in QTimerInfoList::timerWait(timespec&)
(this=0x7f28d4004350, tm=...) at kernel/qtimerinfo_unix.cpp:388
#8  0x7f2926bca75e in timerSourcePrepare(GSource*, gint*)
(timeout=0x7f2749ffaab4, src=) at
kernel/qeventdispatcher_glib.cpp:132
#9  0x7f2926bca75e in timerSourcePrepare(GSource*, gint*)
(source=, timeout=timeout@entry=0x7f2749ffaab4) at
kernel/qeventdispatcher_glib.cpp:165
#10 0x7f291fd1bd7d in g_main_context_prepare
(context=context@entry=0x7f28d4004230, priority=priority@entry=0x7f2749ffab40)
at gmain.c:3501
#11 0x7f291fd1c7bb in g_main_context_iterate
(context=context@entry=0x7f28d4004230, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3909
#12 0x7f291fd1c9ac in g_main_context_iteration (context=0x7f28d4004230,
may_block=may_block@entry=1) at gmain.c:3990
#13 0x7f2926bcb18b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f28d4005b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7f2926b74aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f2749ffac80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#15 0x7f29269a2813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#16 0x7f29269a74c8 in QThreadPrivate::start(void*) (arg=0x842fb80) at
thread/qthread_unix.cpp:368
#17 0x7f2921f36454 in start_thread (arg=0x7f2749ffb700) at
pthread_create.c:333
#18 0x7f292609d37f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 44 (Thread 0x7f27818cb700 (LWP 1378)):
#0  0x7f291fd1b7ce in g_main_context_acquire (context=0x7f274c024000) at
gmain.c:3286
#1  0x7f291fd1c745 in g_main_context_iterate
(context=context@entry=0x7f274c024000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3879
#2  0x7f291fd1c9ac in g_main_context_iteration (context=0x7f274c024000,
may_block=may_block@entry=1) at gmain.c:3990
#3  0x7f2926bcb18b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f274c01f7f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f2926b74aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f27818cac80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f29269a2813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f29269a74c8 in QThreadPrivate::start(void*) (arg=0x58cb750) at
thread/qthread_unix.cpp:368
#7  0x7f2921f36454 in start_thread (arg=0x7f27818cb700) at
pthread_create.c:333
#8  0x7f292609d37f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 43 (Thread 0x7f274a7fc700 (LWP 29724)):
#0  0x7f292609466d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f291fd1c896 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f27340055f0, timeout=, context=0x7f27340008c0)
at gmain.c:4228
#2  0x7f291fd1c896 in g_main_context_iterate
(context=context@entry=0x7f27340008c0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3924
#3  0x7f291fd1c9ac in g_main_context_iteration (context=0x7f27340008c0,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f2926bcb18b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f273400a860, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5 

[kded-appmenu] [Bug 377078] New: Plasma crash when clicking on duplicated app menu buttons

[avlas]

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

Bug ID: 377078
   Summary: Plasma crash when clicking on duplicated app menu
buttons
   Product: kded-appmenu
   Version: 5.9.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: export
  Assignee: plasma-b...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

This seem to happen (at least) in Kontact: e.g. when I move (internally within
Kontact) from akregator to contacts then App Menu fails to remove the old set
of buttons (from akregator) and simply add the new ones (from contact). Then,
if I try to click on one of the old buttons, plasma crashes.

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

[kdenlive] [Bug 377075] transition checkboxes do not save checked state

[lukefromdc]

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

--- Comment #1 from lukefromdc  ---
All these tests are with movit enabled if that makes any difference.

MLT from current git master caused kdenlive to crash on adding transitions or
resizing clips, presuming this a problem in MLT. Thus no retest with current
MLT master possible right now. This was true with new build around MLT from
3-1-2017 pull, with either Nov 22 or current Movit.

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

[kdevelop] [Bug 377027] KDevelop could feature a Designer UI

[Ian Haber]

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

Ian Haber  changed:

   What|Removed |Added

 CC||master.ha...@gmail.com

--- Comment #3 from Ian Haber  ---
I just created an external script to automatically run the file i want in
designer by clicking on it in kdevelop.

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

[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"

[Lukas Tines]

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

--- Comment #17 from Lukas Tines  ---
Deleting Shortcuts section from ~/.config/kdeglobals and then log out / log in
seems to fix the issue for me. You will loose all custom shortcuts i guess. 

I had a lot of duplicated shortcuts in mine.

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

[ksysguard] [Bug 376917] ksysguard SensorDisplay.cpp compile problem

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 377077] New: Systemsettings5 sometimes crashes when I make modifications in some settings

[VaryHeavy]

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

Bug ID: 377077
   Summary: Systemsettings5 sometimes crashes when I make
modifications in some settings
   Product: systemsettings
   Version: 5.8.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: anvar...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.4.0-65-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

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

- Modify GTK appearance settings.
- Modify window decoration.
- Modify workspace theming.

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7f1f5e879700 (LWP 2089)):
#0  0x7f1f9c569b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f976a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f5e878d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x1be8a20) at
thread/qthread_unix.cpp:368
#7  0x7f1f9977a6ba in start_thread (arg=0x7f1f5e879700) at
pthread_create.c:333
#8  0x7f1f9c57582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f1f6cfd2700 (LWP 2086)):
#0  0x7f1f9c569b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f976a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f6cfd1d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x1cd3960) at
thread/qthread_unix.cpp:368
#7  0x7f1f9977a6ba in start_thread (arg=0x7f1f6cfd2700) at
pthread_create.c:333
#8  0x7f1f9c57582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f1f6f7fe700 (LWP 2085)):
#0  0x7f1f976e8a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1f976a3f2a in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a43f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f6f7fdce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f1f9b5c0bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x18f44b0) at
thread/qthread_unix.cpp:368
#9  0x7f1f9977a6ba in start_thread (arg=0x7f1f6f7fe700) at
pthread_create.c:333
#10 0x7f1f9c57582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1f868ca700 (LWP 2081)):
#0  0x7f1f9c569b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f976a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f88c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f868c9cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f1f9ff8d735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x7f1fa0001d60) at
thread/qthread_unix.cpp:368
#8  0x7f1f9977a6ba in start_thread (arg=0x7f1f868ca700) at
pthread_create.c:333
#9  0x7f1f9c57582d in clone () at

[kolourpaint] [Bug 377002] Scan button grayed out.

[bugzilla_noreply]

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

--- Comment #2 from the.real.mrdens...@gmail.com ---
My package manager says nothing about Ksane... however I've went
   through and installed many KDE graphic module parts, and the *sane
   stuff...
   kolourpaint dependencies
lv.png


   02/28/17 21:16:26, Christoph Feck < bugzilla_nore...@kde.org[1]>:

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

 Christoph Feck  changed:

 What |Removed |Added


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

 --- Comment #1 from Christoph Feck  ---
 Could you check if your package is actually compiled against the
 KSane
 dependency? Please ask in a forum of your distribution how to
 check
 dependencies.

 --
 You are receiving this mail because:
 You reported the bug.=



   1. mailto:bugzilla_nore...@kde.org

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

[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"

[Andrej M .]

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

Andrej M.  changed:

   What|Removed |Added

 CC||andr...@ubuntu.si

--- Comment #31 from Andrej M.  ---
I didn't have this problem with KMail from applications 4.14.1 but now in
applications 16.04.3 I'm experiencing it and it's extremely annoying. KMail
doesn't completely freeze, but it takes a minute or two to load folder
contents.

I'm using Debian Stretch.

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

[kmail2] [Bug 376216] Error on boot

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
To further investigate this issue, KDE developers need the information
requested in comment #1. If you can provide it, or need help with finding that
information, please add a comment.

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

[kmail2] [Bug 377070] Kmail emptied inbox, all emails deleted!!!

[William L . Thomson Jr .]

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

--- Comment #1 from William L. Thomson Jr.  ---
If you all continue on with adonadi, aside from not deleting emails on disk
during any sync or other operation. You should STOP using mysql, and use a
reliable database which has MUCH better support for embedded usage,
Firebird

I am not sure if this data loss comes from mysql or akonadi, or something
between then. I know akonadi deleted the emails on disk as kmail has no access.
Nor does mysql.

Furthermore if using a db backend, emails should be stored in the database.
That way there is NO chance of losing sync with emails in database and on disk
if they are all in the database to begin with. Trying to use a db for indexing
and meta data leaving emails on disk is just asking for problems. Much of which
I have experienced first hand and will continue to exist as long as these
horrible methods are used.

Don't use a db backend for on disk stuff. If you are going to index that, move
all data into the database. If none of that, then at least never have akonadi
delete emails. If it has syncing issues, it should rebuild from what is on
disk. NEVER deleting what is on disk

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

[Akonadi] [Bug 345379] Emails lost after filter is applied

[William L . Thomson Jr .]

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

William L. Thomson Jr.  changed:

   What|Removed |Added

 CC||wlt...@o-sinc.com

--- Comment #1 from William L. Thomson Jr.  ---
Grayed out emails have the imap T flag set. Kmail has issues handling these.
For me they remain and I have to delete from disk manually. But I have
experienced lost emails as well.

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

[muon] [Bug 377076] New: Package descriptions missing first character.

[bugzilla_noreply]

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

Bug ID: 377076
   Summary: Package descriptions missing first character.
   Product: muon
   Version: 5.6
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: swagfortr...@gmail.com
CC: silh...@gmail.com
  Target Milestone: ---

The details tab for any given package shows the package description without the
first character. For example, 0ad's description is:

  "real-time strategy game of ancient warfare..."

, but it's printed as

  "eal-time strategy game of ancient warfare..."

OS: neon User Editon 5.9

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

[krusader] [Bug 326440] Krusader crashes on completion synchronize

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net
  Component|general |synchronize

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

[krusader] [Bug 328027] No way to focus fullscreen embedded terminal emulator.

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #1 from Alex Bikadorov  ---
Cannot confirm. Escape key seems to cause loosing focus (the next key input is
ignroed) but the cursor does not change and after typing the terminal is
focused again.
Please try again with Krusader 2.5.0 and reopen if you have still issues. But
this was probably fixed together with bug 309300.

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

[kdenlive] [Bug 377075] New: transition checkboxes do not save checked state

[lukefromdc]

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

Bug ID: 377075
   Summary: transition checkboxes do not save checked state
   Product: kdenlive
   Version: git-master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: directact...@hushmail.com
  Target Milestone: ---

checkboxes for "reverse" and "invert" in transitions do not work in current GIT
master (anything recent, just confirmed with a 3-1-2017 pull). The default
settings on first setting up a transition are "sane defaults" that work, but
the checkboxes "remember" these defaults rather than applying and saving any
changes.

In other words, if the "reverse transition" box is checked by default for a
transition to a lower track, one would expect that unchecking it would make the
transition run back to the upper (previous)track and that this state would be
saved. Instead, the change is not applied, and if the transition is deselected
and selected again on the timeline, the checkbox will be back in its original
default state: checked if it was checked by default, unchecked if it was not
checked by default. Any user changes will be gone.

Thus, it is not possible to do things like a "reverse clock" transition or use
anything but the default settings until this is fixed. 

To duplicate this, build and install kdenlive from git master (now 17.03.70)
and open kdenlive. Add two clips to the project and put them both on the
timeline with an overlap. Create a transition. Now select that transition and
try to edit the direction. The "wipe" transition will show two checkboxes,
"dissolve" will show one. The settings are a sane default and usually OK. Check
an unchecked checkbox or uncheck a checked on. Select anything else on the
timeline, then select the same transition again. You will see that your change
has not been saved.

Using kdenlive from GIT master over MLT 6.5.0 build from Nov 22, 2016. That's a
bit old so will try a current build and report that result

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

[krusader] [Bug 325613] tabs colors are inverted

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #1 from Alex Bikadorov  ---
Cannot confirm. On KDE5 the tab bar uses the value "Window Background" for
active tabs and a (auto generated) darker version of it for inactive tabs.
Please tray again with Krusader 2.5.0.
If there are still problems its probably related to Qt/GTK theme conversion. I
cannot find anything in the code that the default tab colors are changed.

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

[kwin] [Bug 377074] New: Unreliable caps lock key with Xwayland

[idoitprone]

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

Bug ID: 377074
   Summary: Unreliable caps lock key with Xwayland
   Product: kwin
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: monkeyboy...@yahoo.com
  Target Milestone: ---

I am just here to report that CAPS Key behave quite strangely on Xwayland.

lsb_release -a
No LSB modules are available.
Distributor ID: neon
Description:KDE neon Developer Edition
Release:16.04
Codename:   xenial


Xwayland 2:1.18.4-0ubuntu0.2   amd64 

No third party ppas

Steps to reproduce:

1. Start plasma wayland
2. Turn on caps lock
3. open a new xwayland window like firefox
4. type something in the xwayland windows

Result:

You notice the input presses that the key presses is lower case instead of
upper case.

Turn off caps lock changes the input to upper case while the rest of the system
is lower case.



Desired result:

Xwayland windows should be upper case

Notes: this bug is semi unreliable to reproduce. I can reproduce it more often
if I use the caps lock before opening an xwayland windows.

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

[muon] [Bug 376999] Muon searchbox not working

[Nico Dorn]

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

--- Comment #2 from Nico Dorn  ---
May be related to https://bugs.kde.org/show_bug.cgi?id=372343.

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

[muon] [Bug 376999] Muon searchbox not working

[Nico Dorn]

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

Nico Dorn  changed:

   What|Removed |Added

 CC||nicod...@posteo.de

--- Comment #1 from Nico Dorn  ---
Confirmed, makes muon unusable, a real pitty.

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

[kwin] [Bug 377073] Br

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
no idea what this bug report should tell me.

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

[kwin] [Bug 376317] Active screen corners/edges don't work on wayland

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
> I pushed pretty hard into the corner. I'll have to retest on both my
> Radeon and

Graphics card should not matter

> Intel hardware. May I ask why it's so hard to trigger them on wayland?

I think it's a bug in our input handling.

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

[kwin] [Bug 376320] Task switcher themes not working under wayland

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||Wayland+

--- Comment #3 from Martin Gräßlin  ---
Those switchers are technically not part of KWin, they are just addons
distributed with kdeplasma-addons. I can confirm that they do not work at all.

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

[kwin] [Bug 377073] New: Br

[idoitprone]

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

Bug ID: 377073
   Summary: Br
   Product: kwin
   Version: 5.9.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: monkeyboy...@yahoo.com
  Target Milestone: ---

lsb_release -a
No LSB modules are available.
Distributor ID: neon
Description:KDE neon Developer Edition
Release:16.04
Codename:   xenial

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

[keditbookmarks] [Bug 324950] bookmark editor: adding entry in empty folder does not update "quick edit" controls

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

Product|krusader|keditbookmarks
  Component|general |general
Version|Git |unspecified
   Assignee|m...@fork.pl  |konq-b...@kde.org
 CC||alex.bikado...@kdemail.net

--- Comment #1 from Alex Bikadorov  ---
The bookmarks editor is not part of Krusader.

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

[krusader] [Bug 328944] Use Shift+Delete for delete or move selected files to trash

[Alex Bikadorov]

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

--- Comment #1 from Alex Bikadorov  ---
Git commit dfc4abb00ffaa1508056e172a42c7d074b08870a by Alexander Bikadorov.
Committed on 01/03/2017 at 19:34.
Pushed by abikadorov into branch 'master'.

Panel: DEL+CTRL always inverts default delete mode (move to trash vs. real
deletion)

M  +2-2krusader/Panel/krpopupmenu.cpp
M  +2-2krusader/Panel/krview.cpp
M  +2-2krusader/Panel/krview.h
M  +1-1krusader/Panel/listpanel.cpp
M  +1-1krusader/Panel/listpanelactions.cpp
M  +8-4krusader/Panel/panelfunc.cpp
M  +2-1krusader/Panel/panelfunc.h

https://commits.kde.org/krusader/dfc4abb00ffaa1508056e172a42c7d074b08870a

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

[ksysguard] [Bug 376917] ksysguard SensorDisplay.cpp compile problem

[Vladislav Dembskiy]

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

Vladislav Dembskiy  changed:

   What|Removed |Added

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

--- Comment #4 from Vladislav Dembskiy  ---
I could not repruce the problem any more\

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

[ksysguard] [Bug 376917] ksysguard SensorDisplay.cpp compile problem

[Vladislav Dembskiy]

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

--- Comment #3 from Vladislav Dembskiy  ---
Yes, they were installed.
Nevertheless, please close the issue because I have compiled and installed
plasma-5.9.3 without any problems.

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Bazilio]

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

Bazilio  changed:

   What|Removed |Added

 CC||x.bazi...@gmail.com

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

[kwin] [Bug 376363] Disable application launcher on meta key when "Sticky Keys" enabled.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Product|plasmashell |kwin
   Target Milestone|1.0 |---
  Component|Application Launcher|input
   |(Kickoff)   |
   Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org

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

[neon] [Bug 376793] Dependencies not met for winehq-devel in Neon User non LTS

[Alex]

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

--- Comment #2 from Alex  ---
It works fine after update to 5.9.3

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

[krusader] [Bug 322619] Cannot run shell script if path contains space

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #1 from Alex Bikadorov  ---
Cannot confirm. Please try again with Krusadser 2.5.0 and reopen if you have
still problems.

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

[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations

[bugzilla_noreply]

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

--- Comment #11 from martin@gmx.de ---
I can confirm this bug on KDE Neon with Plasma 5.9.3.
Deleting one or many fonts also results in a crash or (in some cases) a
systemsettings freeze. If you kill the systemsettings5-process because of the
freeze, the font-configuration table is empty afterwards.

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

[plasmashell] [Bug 376363] Disable application launcher on meta key when "Sticky Keys" enabled.

[Till Schäfer]

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

Till Schäfer  changed:

   What|Removed |Added

Version|5.8.0   |5.9.3

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

[krusader] [Bug 318034] Trailing spaces are not removed from file or directory name

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Severity|normal  |wishlist
 CC||alex.bikado...@kdemail.net
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 376363] Disable application launcher on meta key when "Sticky Keys" enabled.

[Till Schäfer]

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

Till Schäfer  changed:

   What|Removed |Added

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

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

[digikam] [Bug 377072] New: Cannot read video metadata

[Fiona]

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

Bug ID: 377072
   Summary: Cannot read video metadata
   Product: digikam
   Version: 5.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Editor
  Assignee: digikam-de...@kde.org
  Reporter: fionabeat...@gmail.com
  Target Milestone: ---

I just downloaded digiKam and imported several MP4 video. The video metadata
isn't displayed and therefore I cannot embed my tags into the metadata. Is
there a method for doing this in digiKam? 

Thanks

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

[krusader] [Bug 297394] Krusader crash

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #1 from Alex Bikadorov  ---
Backtrace does not show anything related to Krusader. Please try Krusader 2.5.0
and reopen if this happens again.

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

[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations

[bugzilla_noreply]

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

martin@gmx.de changed:

   What|Removed |Added

 CC||martin@gmx.de

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

[krusader] [Bug 318022] Pressing Ctrl+Shift+End while editing file name - selects files

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

   Priority|NOR |VLO
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||alex.bikado...@kdemail.net

--- Comment #1 from Alex Bikadorov  ---
well, yes. Then don't do it :)

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

[kmail2] [Bug 371826] Kmail new mail systray icon invisible unless hovered

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

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

[kdeconnect] [Bug 377071] Wrong button label if request for pairing is desired.

[Gerhard Dittes]

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

--- Comment #2 from Gerhard Dittes  ---
...sorry, it seems that I accidentally saved my first comment (bug description)
before being finished.


Now more in detail what's the problem:

After adding a device you want to connect, you get a message, informing you
that the device is (still) unconnected/unpaired. You also see button, which
gives you the ability to request the mentioned connection (or pairing).

But the button label is quite confusing as it tells you that the request is
already in progress.

Unfortunately I've only the German version of kdeconnect available but I assume
that the problem exists for other languages, too.

Please have a look at the attached screenshot. The solution (for the German
case) would be:

"VERBINDUNG ANFORDERN" (instead of "VERBINDUNG ANGEFORDERT").


Thanks for this great software & regards, Gerhard

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

[plasmashell] [Bug 376643] Can't run web address when translation is used

[Alex]

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

--- Comment #3 from Alex  ---
I've checked and works fine in 5.9.3

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

[kdeconnect] [Bug 377071] Wrong button label if request for pairing is desired.

[Gerhard Dittes]

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

--- Comment #1 from Gerhard Dittes  ---
Created attachment 104306
  --> https://bugs.kde.org/attachment.cgi?id=104306=edit
Wrong/confusing button label (German).

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

[kwin] [Bug 376317] Active screen corners/edges don't work on wayland

[Michael D]

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

--- Comment #2 from Michael D  ---
I pushed pretty hard into the corner. I'll have to retest on both my Radeon and
Intel hardware. May I ask why it's so hard to trigger them on wayland?

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

[kwin] [Bug 376320] Task switcher themes not working under wayland

[Michael D]

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

--- Comment #2 from Michael D  ---
Perhaps I filed this in the wrong spot, but under kcm's task switcher settings
under Visualization, there is a large list of themes including cover switch,
flip switch, breeze, breeze dark, informative, text only, etc. In a wayland
session, nearly none of these themes work except the ones I mentioned earlier.

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

[kdeconnect] [Bug 377071] New: Wrong button label if request for pairing is desired.

[Gerhard Dittes]

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

Bug ID: 377071
   Summary: Wrong button label if request for pairing is desired.
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Android 7.x
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: g-...@web.de
  Target Milestone: ---

Hi,

when you

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

[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons

[Gerhard Dittes]

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

--- Comment #19 from Gerhard Dittes  ---
Cool news, thanks!

Please, please consider applying this fix to Plasma 5.8 (LTS), too! Please! :-)

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

[kmail2] [Bug 377070] New: Kmail emptied inbox, all emails deleted!!!

[William L . Thomson Jr .]

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

Bug ID: 377070
   Summary: Kmail emptied inbox, all emails deleted!!!
   Product: kmail2
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wlt...@o-sinc.com
  Target Milestone: ---

KMail Version 5.4.2
KDE Frameworks 5.31.0
Qt 5.7.1 (built against 5.7.1)

This is NOT the 1st time this has happened. Every email in my inbox was deleted
for NO reason. This seems to be some issue between the emails on disk and what
ever is in the akanodi database. I am SO sick of issues with Kmail2 and email.
This whole using a db backend is NOT working and needs to end. People should
have a choice on using akonadi, mysql, and any db. Emails that are on DISK
should NEVER be deleted unless I am deleting them. Funny enough emails in my
trash remain till I empty the trash. I have lots of folders, lots of filters,
lots of emails. I have not had this problem with other folders. I have had
other issues with emails from day 1 using kmail2. I am about to go back to
gnome and evolution. Kmail is complete garbage

I am a database person. I have worked with database for years. There is NO
reason to be integrating email with a database. For all the problems I am
experience it is NOT worth any benefit on search etc. I have grep and other
fast things if I need to search. My contacts are all messed up because of
something that associates names with emails, and does it incorrectly. At ever
angle there are problems from the software trying to do things it need not.
Features that CANNOT be turned off.

This needs to stop!!! Kmail2 needs to be decoupled from this horrible mess that
is akonadi. Emails on disk should not disappear and be removed due to some
syncing or other issue that clearly comes from the database. Nothing else would
remove emails like that. I saw them flashing and re-indexing. I saw that happen
to other folders before but never lost emails. Clearly seeing stuff resulting
from integration with on disk emails into some sort of database.

I do not care what is done with akonadi, but it should NEVER delete emails as
part of its syncing operations. This is really unacceptable. I am very
displeased all around at how people are doing experimental things with software
people will heavily rely on for business, to make a living, etc.

An email client should NEVER delete emails unless a person does that or its
part of a filter etc. Such serious bugs should NEVER exist. That they result
from some database integration and some needless features is unacceptable. The
entire point of email software is to receive and store email. If it cannot do
that simple function the rest is completely pointless and moot.

The most important feature of any email client is to maintain email. No change
should ever be made to kmail that could potentially delete an email without a
users interaction, unless from a user created filter. There needs to be some
serious code review and much better QA.

This is the WORST email software I have ever used. If I did not have so many
folders, filters, etc I would switch. Plus to switch means I likely need to
switch desktops envs. Only reason I am even running kmail is I left gnome. But
I kept using evolution for a while, and wish I never migrated to kmail.

I used evolution for over a decade and NEVER once did I have any issue. Nor
with Thunderbird ever. I have been using kmail since ~2011. I have hated it
ever day since. Many on Gentoo have stopped using it including many developers
who maintain KDE on Gentoo.

I do like many aspects of kmail. But I absolutely HATE akonadi, any
integration, etc. That NEEDS to be optional seriously. This joke about rapidly
developing PIM applications etc. It is pointless. There are no other KDE PIM
based email clients. The one that was developed as an example in 2008 never
went further and there has been no others in almost a decade. Please reconsider
this direction.

Akonadi and any efforts there are NOT improving the quality of Kmail. They are
in fact making it horrible unreliable, deleting emails, corrupting others as I
have reported in other bugs. So many issues that would not exist if it was not
for this akonadi bs.  This failed experiment that is akonadi needs to come to
an end.

If kmail continues to be developed using akonadi and no option to not use a DB
backend and just stick to plain files on disk. Then I will definitely move back
to evolution or thunderbird. These sorts of problems really should not exist. I
have never experienced them or others till kmail.

Unacceptable, and needs to change radically

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

[kscreenlocker] [Bug 374289] multiscreen locks stealing focus

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/ksc
   ||reenlocker/f8043de10b5dd94b
   ||9b931a92f3aa7167188786c9
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Fabian Vogt  ---
Git commit f8043de10b5dd94b9b931a92f3aa7167188786c9 by Fabian Vogt.
Committed on 01/03/2017 at 17:48.
Pushed by fvogt into branch 'Plasma/5.8'.

Implement manual focus on click

Summary:
Currently only the first created screenlock window gets focus.
On clicks, no focus events are sent, which makes it impossible to input
passwords. This patch now makes it possible to focus to a different
screenlock window (on a different monitor, for example) using a mouse
button press.
This should also fix newly created screenlock windows stealing the focus
of already displayed ones as only the first window gains automatic focus.
Related: bug 348789

Test Plan:
Locked the screen, now I can use the password input on the secondary screen
as well.

Reviewers: #plasma, graesslin, broulik

Reviewed By: #plasma, graesslin

Subscribers: hein, plasma-devel

Tags: #plasma

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

M  +0-1greeter/greeterapp.cpp
M  +24   -2x11locker.cpp
M  +2-0x11locker.h

https://commits.kde.org/kscreenlocker/f8043de10b5dd94b9b931a92f3aa7167188786c9

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

[kscreenlocker] [Bug 348789] kscreenlocker_greet not grabbing input

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/ksc
   ||reenlocker/f8043de10b5dd94b
   ||9b931a92f3aa7167188786c9
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from Fabian Vogt  ---
Git commit f8043de10b5dd94b9b931a92f3aa7167188786c9 by Fabian Vogt.
Committed on 01/03/2017 at 17:48.
Pushed by fvogt into branch 'Plasma/5.8'.

Implement manual focus on click

Summary:
Currently only the first created screenlock window gets focus.
On clicks, no focus events are sent, which makes it impossible to input
passwords. This patch now makes it possible to focus to a different
screenlock window (on a different monitor, for example) using a mouse
button press.
This should also fix newly created screenlock windows stealing the focus
of already displayed ones as only the first window gains automatic focus.
Related: bug 374289

Test Plan:
Locked the screen, now I can use the password input on the secondary screen
as well.

Reviewers: #plasma, graesslin, broulik

Reviewed By: #plasma, graesslin

Subscribers: hein, plasma-devel

Tags: #plasma

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

M  +0-1greeter/greeterapp.cpp
M  +24   -2x11locker.cpp
M  +2-0x11locker.h

https://commits.kde.org/kscreenlocker/f8043de10b5dd94b9b931a92f3aa7167188786c9

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

[kopete] [Bug 231941] Kopete crashed on closing a chat window

[Pali Rohár]

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

Pali Rohár  changed:

   What|Removed |Added

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

--- Comment #4 from Pali Rohár  ---
closing per previous comment

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

[kopete] [Bug 376733] Started a conversation, pushed the OTR button, then suddenly Kopete crashed.

[Pali Rohár]

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

Pali Rohár  changed:

   What|Removed |Added

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

--- Comment #1 from Pali Rohár  ---
Already fixed in Kopete 1.11.0

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

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

[kopete] [Bug 349596] Kopete crashes after OTR keys generation

[Pali Rohár]

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

Pali Rohár  changed:

   What|Removed |Added

 CC||andre.ock...@xs4all.nl

--- Comment #12 from Pali Rohár  ---
*** Bug 376733 has been marked as a duplicate of this bug. ***

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

[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation

[Pali Rohár]

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

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #14 from Pali Rohár  ---
I will close this bug as invalid as buttons are there and their visibility is
related to some KDE settings, not to Kopete.

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

[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation

[Pali Rohár]

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

Pali Rohár  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation

[Pali Rohár]

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

--- Comment #13 from Pali Rohár  ---
It is not by default and it is some (central?) default KDE settings. Also linux
distributions provides their own defaults, so maybe this is reason...

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

[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation

[Tristan Miller]

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

--- Comment #12 from Tristan Miller  ---
Yes, Ctrl+M brings up a pull-down menu bar, and there are OTR commands listed. 
I wonder why this menu wasn't displayed by default, though.  Is it like this
for everyone?

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

[plasmashell] [Bug 377055] some icons cannot be pinned to panel on wayland

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #1 from Eike Hein  ---
Those are probably XWayland apps without a proper Wayland appid.

I'd need access to their X11 WM_CLASS and then refactor the code to use the
heuristic from XWindowTasksModel also on Wayland for XWayland windows. Wayland
also needs the pid code still for the pid fallback in that heuristic.

Or we ignore XWayland and wait for apps to get ported.

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

[kwin] [Bug 376320] Task switcher themes not working under wayland

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|effects-tabbox  |tabbox

--- Comment #1 from Martin Gräßlin  ---
which "other"? KWin does not ship any tabbox themes at all.

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

[krita] [Bug 377060] Scale Down 50% is blurry with Linear Filter

[Paul Geraskin]

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

--- Comment #11 from Paul Geraskin  ---
I have just googled "Box vs Linear" a bit.

https://www.google.ru/search?q=box+vs+linear=1=2=1920=961=lnms=isch=X=0ahUKEwiPgJeg57XSAhUBECwKHbMiB7EQ_AUIBigB#newwindow=1=isch=box+vs+linear+filter&*=S5KTEsiHTB1dGM:


https://www.google.ru/search?q=box+vs+linear=1=2=1920=961=lnms=isch=X=0ahUKEwiPgJeg57XSAhUBECwKHbMiB7EQ_AUIBigB#newwindow=1=isch=box+vs+linear+filter&*=uHvEJXRJx-nO_M:

And from the last link above:
http://i.imgur.com/hLWzQwh.png

I hope this will help.

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

[plasmashell] [Bug 376866] Can't write anything into plasma dialogues, can into KDE apps.

[Tom Kijas]

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

--- Comment #9 from Tom Kijas  ---
Another strange behaviour... can be connected.
When I have opened qapt, installing app, I can write nowhere, doesn't matter
whether in KDE/GTK/Plasma. After I close it, it is as I stated here.

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

[plasmashell] [Bug 377055] some icons cannot be pinned to panel on wayland

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|kwin|plasmashell
  Component|wayland-generic |Icons-only Task Manager
   Target Milestone|--- |1.0
   Assignee|kwin-bugs-n...@kde.org  |h...@kde.org
 CC||plasma-b...@kde.org

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

[kwin] [Bug 376317] Active screen corners/edges don't work on wayland

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||Wayland+
  Component|general |input

--- Comment #1 from Martin Gräßlin  ---
They do work, but it is more difficult to trigger them.

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

[drkonqi] [Bug 373099] Login button not enabled

[Szczepan Hołyszewski]

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

Szczepan Hołyszewski  changed:

   What|Removed |Added

 CC||rula...@wp.pl

--- Comment #1 from Szczepan Hołyszewski  ---
Same issue here. It might be relevant that the program that crashed (KUser) was
run as root with kdesu.

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

[plasmashell] [Bug 376363] Disable application launcher on meta key when "Sticky Keys" enabled.

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin  ---
The intention is that on sticky keys the modifier only short cut does not
trigger. At least for Wayland I tried to implement that, unfortunately I
utterly failed figuring out how to enable sticky keys.

On X11 the problem is that we actually ignore the keyboard layout. I hope that
once we have https://phabricator.kde.org/T5222 implemented this would resolve
this issue.

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

[kopete] [Bug 371269] No (obvious) way to end or restart a private conversation

[Pali Rohár]

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

--- Comment #11 from Pali Rohár  ---
Seems to hide main menu in chat window. Press CTRL+M to toggle visibility of
main menu. And then you should have Tools menu in main menu.

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