[kmymoney4] [Bug 340158] Some discrepancies between stocks displayed in Ledgers and on Institutions screen

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||lukasz.wojnilow...@gmail.co
   ||m

--- Comment #5 from NSLW  ---
Could you provide your .kmy file?

(In reply to Nick Elliott from comment #0)
> I have an investment account called 'Shares' which belongs to an Institution
> called 'Stocks and Shares'.
> 
> The ledger for 'Shares' contains shareholdings (Stocks) in 5 different
> companies.
> 
> However on the 'Institutions' screen only 3 of the stocks are listed in the
> 'Shares' account and the other 2 are listed directly under 'Stock and
> Shares' (see URL attachment).
> 
> This has happened to one other of my Institutions/Investment accounts, many
> others are displayed correctly.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Upgrade from version 4.6.6 to 4.7.0
> 2.
> 3.
> 
> 
> Expected Results:  
> In KMyMoney 4.6.6 all 5 shares correctly appeared under the Shares account
> which meant that the correct total value of the account was displayed on
> screen.

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

[plasmashell] [Bug 378355] 'Desktop Switcher' in Panel does not update highlighted desktop when user has switched to a another.

[Rick Stockton]

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

Rick Stockton  changed:

   What|Removed |Added

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

--- Comment #1 from Rick Stockton  ---
Looking more carefully, it *is* working. The too-subtle-for-me-to-see
highlighting would be a theme issue, if we see a bunch of duplicate reports in
the future.

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

[Breeze] [Bug 375825] Please include 1920x1200 size wallpaper

[Ken Vermette]

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

Ken Vermette  changed:

   What|Removed |Added

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

--- Comment #1 from Ken Vermette  ---
For Plasma 5.10 and beyond I've added 1900x1200 wallpapers to the build/sizing
script.

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

[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper

[Ken Vermette]

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

--- Comment #6 from Ken Vermette  ---
Shoot, just replied to the wrong bug. Either way, 4k wallpapers are included
now anyways.

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

[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper

[Ken Vermette]

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

Ken Vermette  changed:

   What|Removed |Added

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

--- Comment #5 from Ken Vermette  ---
For Plasma 5.10 and beyond I've added 1900x1200 wallpapers to the build/sizing
script. For the SVG stuff I think I'll defer that until later, as if we switch
to SVG at some point, it limits what we can do in the future... And it's
off-topic anyway.

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

[kdevelop] [Bug 378357] New: Kdevelop crashed when i clicked the PROBLEM IN SYMENTIC ANALSYS "Solution(1): Open Project"

[YOON GUN]

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

Bug ID: 378357
   Summary: Kdevelop crashed when i clicked the PROBLEM IN
SYMENTIC ANALSYS "Solution(1): Open Project"
   Product: kdevelop
   Version: 5.1.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cfr...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.1.0)

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

-- Information about the crash:
- Actually the another bugs occured too. Directory under project (named Source)
is not shown even it created in ide itself. RELOAD, DELETE and CREATE again,
UPGRADE was not effective

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

Thread 14 (Thread 0x7f66b3fff700 (LWP 19941)):
#0  0x7f671d387756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f67150de234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f67150de279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f671d3812e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f672397354f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f66b2d43700 (LWP 19911)):
#0  0x7f672428f894 in  () at /usr/lib/libQt5Core.so.5
#1  0x7f671b133c8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f671b1346cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f671b1348bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f672429006b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f672423989a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f672405ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f6721b897df in  () at /usr/lib/libKDevPlatformLanguage.so.10
#8  0x7f67240606d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f671d3812e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f672397354f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f66d0ff9700 (LWP 19904)):
#0  0x7f671d387756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f672406158b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f67187441d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f67187489d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7f6718748a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#18 0x7f6718743263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#19 0x7f6718746249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#20 0x7f67240606d8 in  () at /usr/lib/libQt5Core.so.5
#21 0x7f671d3812e7 in start_thread () at /usr/lib/libpthread.so.0
#22 0x7f672397354f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f66d17fa700 (LWP 19903)):
#0  0x7f671d387756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f672406158b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f67187441d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at 

[plasmashell] [Bug 378341] Missing desktop icons and taskbar after update

[jgforbes]

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

--- Comment #5 from jgforbes  ---
I attached the output of running plasmashell after using kquitapp to stop it.

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

[plasmashell] [Bug 378341] Missing desktop icons and taskbar after update

[jgforbes]

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

--- Comment #4 from jgforbes  ---
Created attachment 104845
  --> https://bugs.kde.org/attachment.cgi?id=104845=edit
console output of running plasmashell after quiting it

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

[kwin] [Bug 378356] New: Mouse cursors have abnormally dark pixels around edges

[Ken Vermette]

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

Bug ID: 378356
   Summary: Mouse cursors have abnormally dark pixels around edges
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: verme...@gmail.com
  Target Milestone: ---

Created attachment 104844
  --> https://bugs.kde.org/attachment.cgi?id=104844=edit
Samples as seen by placing the cursor next to the preview in systemsettings.

Most visible when viewing "Breeze" cursors on a white or light background.

Pixels which are white (or light) which are semitransparent will appear
darkened. 

When taking screenshots, if on an X11 system, the cursor will appear 'as it
should' in the screenshot. If on a Wayland system the cursor will faithfully
show the issue in the screenshot. 

This was tested on an X11 machine running Nvidia Prop drivers, and a Wayland
Intel machine. I have seen it on others.

This bug has been present for years, it is not new; it is only because my
Wayland session took an accurate screenshot that I'm able to report this.

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

[plasmashell] [Bug 378355] 'Desktop Switcher' in Panel does not update highlighted desktop when user has switched to a another.

[Rick Stockton]

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

Rick Stockton  changed:

   What|Removed |Added

   Keywords||regression, usability

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

[plasmashell] [Bug 378355] New: 'Desktop Switcher' in Panel does not update highlighted desktop when user has switched to a another.

[Rick Stockton]

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

Bug ID: 378355
   Summary: 'Desktop Switcher' in Panel does not update
highlighted desktop when user has switched to a
another.
   Product: plasmashell
   Version: 5.9.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Dashboard
  Assignee: notm...@gmail.com
  Reporter: rickstock...@reno-computerhelp.com
CC: bhus...@gmail.com
  Target Milestone: 1.0

Using openSUSE Plasma 5.9.4-1 with corresponding kwin5. ("Tumbleweed" latest
and greatest, built 2017-03-21).

When switching desktops within the primary panel's "desktop switcher widget",
and also when switching via shortcut (keyboard or mouse switching), then
"desktop switcher widget" does not show that you have moved to a different
desktop. The highlighted desktop indication is "stuck", and does not move.

With Plasma-5 (or kwin, I don't know where the "responsibility" lies) unable to
provide different desktop back ground images per desktop, the pager becomes
more critical to see "where you are" among your virtual desktops.

The pager works great for moving application windows among desktops - it just
doesn't update the highighted "desktop" correctly.

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

[valgrind] [Bug 377550] No rule to make target

[Rhys Kidd]

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

Rhys Kidd  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Rhys Kidd  ---
Hello Terry,

This is a known bug in Valgrind 3.12 that was fixed in our latest development
version.

To get hold of this code, you can use the instructions found at
http://valgrind.org/downloads/repository.html

See further:
- https://bugs.kde.org/show_bug.cgi?id=374685#c2

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

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

[valgrind] [Bug 374685] Won't Build on Mac OS X 10.11 (El Capitan) - undefined symbol ___bzero

[Rhys Kidd]

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

Rhys Kidd  changed:

   What|Removed |Added

 CC||terryeat...@bigpond.com

--- Comment #5 from Rhys Kidd  ---
*** Bug 377550 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 378341] Missing desktop icons and taskbar after update

[Rex Dieter]

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

--- Comment #3 from Rex Dieter  ---
(sorry, I missed the mention of that already)

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

[plasmashell] [Bug 378341] Missing desktop icons and taskbar after update

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

--- Comment #2 from Rex Dieter  ---
and fyi, don't use 'sudo' with kquitapp

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

[frameworks-knotifications] [Bug 378047] Kmail / Korganiser crashed

[Ákos Szederjei]

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

--- Comment #2 from Ákos Szederjei  ---
Where is the log located which I need to check?
This one was an automatic error report.

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

[krita] [Bug 378354] New: slow response

[bugzilla_noreply]

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

Bug ID: 378354
   Summary: slow response
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: andydreambl...@gmail.com
  Target Milestone: ---

brush unresponsive, when I scroll the software lags before it allows me to zoom
in on the project. Restarting the PC hasn't been working.

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

[juk] [Bug 76338] slow response after startup

[bugzilla_noreply]

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

andydreambl...@gmail.com changed:

   What|Removed |Added

 CC||andydreambl...@gmail.com

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

[systemsettings] [Bug 378353] New: System Settings crash when selecting Multimedia/Audio and Video

[Andrew Morris]

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

Bug ID: 378353
   Summary: System Settings crash when selecting Multimedia/Audio
and Video
   Product: systemsettings
   Version: unspecified
  Platform: Compiled Sources
OS: FreeBSD
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: morrand...@gmail.com
  Target Milestone: ---

Application: systemsettings (4.11.21)
KDE Platform Version: 4.14.10 (Compiled from sources)
Qt Version: 4.8.7
Operating System: FreeBSD 10.3-RELEASE amd64
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
- What I was doing when the application crashed: Opened System Settings then
selected Mutimedia. When I select "Audio and Video Settings," System Settings
crashes about 10 seconds later without going into that settings panel.

I have recently attempted to switch from GStreamer to VLC for audio handling,
and this is likely related to that.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#8  0x00082b468b63 in QMetaObject::className () from
/usr/local/lib/qt5/libQt5Core.so.5
#9  0x00082a598615 in QToolTip::setFont () from
/usr/local/lib/qt5/libQt5Widgets.so.5
#10 0x00082a5ce50c in QDesktopWidget::qt_metacall () from
/usr/local/lib/qt5/libQt5Widgets.so.5
#11 0x00082a8eef72 in QPixmapStyle::qt_metacall () from
/usr/local/lib/qt5/libQt5Widgets.so.5
#12 0x00082a55d17e in _init () from /usr/local/lib/qt5/libQt5Widgets.so.5
#13 0x7fff9fa0 in ?? ()
#14 0x00080061ea9f in r_debug_state () from /libexec/ld-elf.so.1
#15 0x000800623437 in _rtld_is_dlopened () from /libexec/ld-elf.so.1
#16 0x00080061fea0 in dlopen () from /libexec/ld-elf.so.1
#17 0x0008296d01c1 in vlc_timer_getoverrun () from
/usr/local/lib/libvlccore.so.8
#18 0x0008296ba66c in module_list_free () from
/usr/local/lib/libvlccore.so.8
#19 0x0008296baaad in module_list_free () from
/usr/local/lib/libvlccore.so.8
#20 0x0008296ba9de in module_list_free () from
/usr/local/lib/libvlccore.so.8
#21 0x0008296ba7e6 in module_list_free () from
/usr/local/lib/libvlccore.so.8
#22 0x0008296ba27f in module_config_free () from
/usr/local/lib/libvlccore.so.8
#23 0x0008296622bf in libvlc_InternalInit () from
/usr/local/lib/libvlccore.so.8
#24 0x000829924039 in libvlc_new () from /usr/local/lib/libvlc.so.5
#25 0x00082942fd7f in qt_plugin_instance () from
/usr/local/lib/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x000829414de6 in qt_plugin_instance () from
/usr/local/lib/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x000829414a14 in qt_plugin_instance () from
/usr/local/lib/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x00080436f4c1 in QPluginLoader::instance () from
/usr/local/lib/qt4/libQtCore.so.4
#29 0x000809fd5791 in Phonon::Factory::setBackend () from
/usr/local/lib/libphonon.so.4
#30 0x000809fd588a in Phonon::Factory::setBackend () from
/usr/local/lib/libphonon.so.4
#31 0x000809fd5c60 in Phonon::Factory::setBackend () from
/usr/local/lib/libphonon.so.4
#32 0x000809fd69de in Phonon::Factory::backend () from
/usr/local/lib/libphonon.so.4
#33 0x000809fd9206 in Phonon::GlobalConfig::audioOutputDeviceListFor ()
from /usr/local/lib/libphonon.so.4
#34 0x000824815fbe in qt_plugin_instance () from
/usr/local/lib/kde4/kcm_phonon.so
#35 0x000824815f16 in qt_plugin_instance () from
/usr/local/lib/kde4/kcm_phonon.so
#36 0x0008248119f2 in qt_plugin_instance () from
/usr/local/lib/kde4/kcm_phonon.so
#37 0x000824811635 in qt_plugin_instance () from
/usr/local/lib/kde4/kcm_phonon.so
#38 0x000824811d20 in qt_plugin_instance () from
/usr/local/lib/kde4/kcm_phonon.so
#39 0x000803a7085e in KPluginFactory::create () from
/usr/local/lib/libkdecore.so.5
#40 0x000801d4859c in KCModuleLoader::showLastLoaderError () from
/usr/local/lib/libkcmutils.so.4
#41 0x000801d471fe in KCModuleLoader::loadModule () from
/usr/local/lib/libkcmutils.so.4
#42 0x000801d4dd42 in KCModuleProxy::realModule () from
/usr/local/lib/libkcmutils.so.4
#43 0x000801d4db12 in KCModuleProxy::realModule () from
/usr/local/lib/libkcmutils.so.4
#44 0x000801d4ea69 in KCModuleProxy::showEvent () from
/usr/local/lib/libkcmutils.so.4
#45 0x000802c601ef in QWidget::event () from
/usr/local/lib/qt4/libQtGui.so.4
#46 0x000802c1183d in QApplicationPrivate::notify_helper () from
/usr/local/lib/qt4/libQtGui.so.4
#47 0x000802c148c9 in QApplication::notify () from
/usr/local/lib/qt4/libQtGui.so.4
#48 0x000802274a37 in KApplication::notify () from
/usr/local/lib/libkdeui.so.5
#49 0x00080438c596 in QCoreApplication::notifyInternal () from
/usr/local/lib/qt4/libQtCore.so.4
#50 0x000802c5ecfa in 

[kmail2] [Bug 378352] New: KMail Crashed at app start

[Víctor]

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

Bug ID: 378352
   Summary: KMail Crashed at app start
   Product: kmail2
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: mrvi...@gmail.com
  Target Milestone: ---

Application: kmail (5.4.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
I started KMail and configured one account. KMail crashed.
I started KMail again and closed the add account dialog. KMail crashed

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb0dc3be900 (LWP 19611))]

Thread 25 (Thread 0x7faf99f94700 (LWP 19706)):
#0  0x7fb0c9286756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb0cd27b0d9 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0cd27b709 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0cd27b8c0 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0cd278442 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0c92802e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fb0d928c54f in clone () at /usr/lib/libc.so.6

Thread 24 (Thread 0x7fb01bfff700 (LWP 19677)):
#0  0x7fb0c9286756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb0b798d234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fb0b798d279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fb0c92802e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fb0d928c54f in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7fb023fff700 (LWP 19640)):
#0  0x7fb0c9286756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb0cd27b0d9 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0cd27b709 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0cd27b8c0 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0cd278442 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0c92802e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fb0d928c54f in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7fb060ff9700 (LWP 19639)):
#0  0x7fb0d928267d in poll () at /usr/lib/libc.so.6
#1  0x7fb0b3fe2ee1 in  () at /usr/lib/libpulse.so.0
#2  0x7fb0b3fd46f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7fb0b3fd4d8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7fb0b3fd4e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7fb0b3fe2e29 in  () at /usr/lib/libpulse.so.0
#6  0x7fb0abbe8fe8 in  () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#7  0x7fb0c92802e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fb0d928c54f in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7fb0617fa700 (LWP 19638)):
#0  0x7fb0d92990eb in __lll_lock_wait_private () at /usr/lib/libc.so.6
#1  0x7fb0d929ad64 in __fprintf_chk () at /usr/lib/libc.so.6
#2  0x7fb0be5799ee in  () at /usr/lib/libevent-2.0.so.5
#3  0x7fb0be579be4 in event_warn () at /usr/lib/libevent-2.0.so.5
#4  0x7fb0be57e2f8 in  () at /usr/lib/libevent-2.0.so.5
#5  0x7fb0be56836d in event_base_loop () at /usr/lib/libevent-2.0.so.5
#6  0x7fb0cd224aee in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0cd2636c4 in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fb0cd27bbe5 in  () at /usr/lib/libQt5WebEngineCore.so.5
#9  0x7fb0cd27bf04 in  () at /usr/lib/libQt5WebEngineCore.so.5
#10 0x7fb0cd278442 in  () at /usr/lib/libQt5WebEngineCore.so.5
#11 0x7fb0c92802e7 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7fb0d928c54f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7fb0627fc700 (LWP 19637)):
#0  0x7fb0c9286b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb0cd26fb62 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0cd270415 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0cd24d541 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0cd2636c4 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0cd27bbe5 in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7fb0cd27bf04 in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0cd278442 in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fb0c92802e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb0d928c54f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fb061ffb700 (LWP 19636)):
[KCrash Handler]
#6  0x7fb0d91d3a10 in raise () at /usr/lib/libc.so.6
#7  0x7fb0d91d513a in abort () at /usr/lib/libc.so.6
#8  

[Discover] [Bug 378351] New: App title unreadable when discover window is resized

[Alex]

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

Bug ID: 378351
   Summary: App title unreadable when discover window is resized
   Product: Discover
   Version: 5.9.4
  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 104843
  --> https://bugs.kde.org/attachment.cgi?id=104843=edit
resizing discover window

When I make discover main window wider, app list becomes so shallow that app
titles are not readable.

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

[plasmashell] [Bug 378350] Task manager incorrectly recognizes screen after display plugged/unplugged

[Dmitry]

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

Dmitry  changed:

   What|Removed |Added

Summary|Task manager incorrectly|Task manager incorrectly
   |recognize screen after  |recognizes screen after
   |display plugged/unplugged   |display plugged/unplugged

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

[plasmashell] [Bug 378350] New: Task manager incorrectly recognize screen after display plugged/unplugged

[Dmitry]

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

Bug ID: 378350
   Summary: Task manager incorrectly recognize screen after
display plugged/unplugged
   Product: plasmashell
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: dmitry.s.lisov...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell 5.9.3

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.8.0-41-generic x86_64
Tried Ubuntu 16.10 and KDE Neon Developer Edition (Stable branches)

Steps to reproduce (I will describe my typical use case):

1. Given system with two displays (e.g. one laptop and one external, or two
external displays).
2. (Not sure if it's necessary) Set number of virtual desktops to >=2
3. The main display by default has a panel with Task Manager widget on the
bottom. Right click on task manager -> Settings -> Check "Show only tasks from
current screen", "Show only tasks from current desktop" and "Show only tasks
from current activity".
4. Add an empty panel to the other display, add the Task Manager widget to it,
check the same "Show only tasks from current screen", "Show only tasks from
current desktop" and "Show only tasks from current activity" options in its 
settings.

Now we have on each display own Task Manager widget which displays only windows
for current display and virtual desktop. That's what I want, everything's
great.

But if I unplug external display or plug-in a new one, then Task Manager widget
shows no windows until I uncheck "Show only tasks from current screen" option.
But in that case it shows windows from all the screens, and that's not what I
need.

The only workaround is to restart plasmashell (killall plasmashell, kstart
plasmashell), which is tedious and not always works as expected.

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

[plasmashell] [Bug 374825] Feature request: make plasmoids be shippable with translations

[bugzilla_noreply]

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

koffeinfried...@gmail.com changed:

   What|Removed |Added

 CC||koffeinfried...@gmail.com

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

[plasmashell] [Bug 369735] QML Text issues in contents/ui/DigitalClock.qml:443 ("Cannot anchor to a null item" and "Binding loop detected for property "height"")

[Larry]

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

Larry  changed:

   What|Removed |Added

 CC||la...@oisher.net

--- Comment #1 from Larry  ---
I have the same issue.

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

[konversation] [Bug 378349] New: (Request) Add ignore functionality to channel messages

[AC]

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

Bug ID: 378349
   Summary: (Request) Add ignore functionality to channel messages
   Product: konversation
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: arco...@gmail.com
  Target Milestone: ---

Related bug report (not an actual bug):
https://bugs.kde.org/show_bug.cgi?id=373243

Under Settings>Behavior>Ignore, I assumed this allowed you to ignore messages
in channels matching specified words or patterns, but was later informed this
only worked for the hostmask.

I'd really like if this would allow you to ignore normal channel messages
containing certain text.  

In my use case, there are some channels I visit that are run by bots that spam
hundreds of messages every minute, and I'd like to ignore some of the messages
I don't care about.

The current Ignore feature in the settings has checkboxes for
channel/query/notice/ctcp/dcc/invite.. but it doesn't actually filter channel
messages.  Maybe not a bug but an unfinished feature?  I'm not really sure what
the situation is with this.

This would be much appreciated!  Thanks

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

[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action

[Roman Gilg]

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

--- Comment #15 from Roman Gilg  ---
Ok, looking again at the revert
https://cgit.kde.org/plasma-workspace.git/commit/?id=27b1030756002e91b60ba51483efe9c2c477d16e
it's a revert for something else and therefore it's a regression on my commit.

I've already fixed that in https://phabricator.kde.org/D5270, but we could
still try to find a better solution to do a real "left click raises window
instead of only context menu", like it's in XFCE.

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

[konversation] [Bug 373243] Ignore feature seems to do nothing at all

[AC]

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

--- Comment #2 from AC  ---
Oh I see.  Will do, thanks

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

[krita] [Bug 378348] New: Zoom tool is not in sync with images

[bugzilla_noreply]

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

Bug ID: 378348
   Summary: Zoom tool is not in sync with images
   Product: krita
   Version: 3.1.3-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: zoruaspa...@gmail.com
  Target Milestone: ---

The Zoom tool in Krita is not working as it used to before in it's previous
version before the newly release of 3.1.3 alpha. As I try to zoom in with this
tool, the image halts for a couple of seconds (mostly up to 30 or 40)then
returns to normal. This has been happening for the past 5 days in which I
thought it was my computer acing up as I restarted it each and every day hoping
it will work but over time it got worse. This has been happening when I tried
animating. I don't know if this issue works for creating digital art as I use a
different program for that. Please fix this problem or bug. It will help me a
whole lot if I could animate my ideas again in peace and a fluent style instead
of waiting for the program to zoom. I've tried to adjust the zoom setting as
well but that doesn,t work either. Please fix.

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

[kpdf] [Bug 69092] Zoom in and zoom out buttons in toolbar are not in sync with textual zoom

[bugzilla_noreply]

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

zoruaspa...@gmail.com changed:

   What|Removed |Added

 CC||zoruaspa...@gmail.com

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

[karbon] [Bug 309410] CWOP: Zoom tool does not zoom the selected area

[bugzilla_noreply]

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

zoruaspa...@gmail.com changed:

   What|Removed |Added

 CC||zoruaspa...@gmail.com

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

[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action

[Roman Gilg]

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

Roman Gilg  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||subd...@gmail.com
 Resolution|DUPLICATE   |---

--- Comment #14 from Roman Gilg  ---
I reopen this bug report. I proposed a workaround for 5.10 as David mentioned,
but that one was reverted again already back on master branch, because
something else broke. :X

Some facts:
* The problematic apps using libappindicator, an Ubuntu/Unity library, which
doesn't really support left-click-to-open-window, because Unity only opens the
context menu on left click.
* I made a patch https://phabricator.kde.org/D4301, which would at least open
the context menu on left click (since I thought, there is no sane way to open
the window without libappindicator exporting that, but since apparently XFCE
supports it, we should think this over again).
* Currently it's back to doing-nothing-on-left-click because of the revert
https://cgit.kde.org/plasma-workspace.git/commit/?id=27b1030756002e91b60ba51483efe9c2c477d16e,
which states that xembedsniproxy were broken because of my change.
* So how should we move forward? Is there a way to open and raise the window
without using libappindicator? For example could we use KWindowSystem in some
way?

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

[plasmashell] [Bug 378347] New: Plazma crash on close laptop lid

[Paweł]

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

Bug ID: 378347
   Summary: Plazma crash on close laptop lid
   Product: plasmashell
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: peer7...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.4)

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

-- Information about the crash:
- What I was doing when the application crashed:
I update ArchLinux and turn off for some days.
I start computer and log in.
Default monitor was set as laptop screen but should external monitor.
I close the laptop lid.
Plasma panel switch to external monitor, but pulpit was smaler.
Next crush.

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

Thread 10 (Thread 0x7fe39959f700 (LWP 4109)):
#0  0x7fe4762eeb63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe4774344c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe47742fbc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fe4774336d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fe4762e82e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fe476d4654f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fe3adf77700 (LWP 4060)):
#0  0x7fe476d3c67d in poll () at /usr/lib/libc.so.6
#1  0x7fe471b227a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe471b228bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe47766306b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe47760c89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe47742ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe3b09330a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7fe4774336d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe4762e82e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe476d4654f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fe3c25db700 (LWP 3948)):
#0  0x7fe471b21b30 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fe471b226cb in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe471b228bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe47766306b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe47760c89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe47742ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe47b119fd6 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7fe4774336d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe4762e82e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe476d4654f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fe451e97700 (LWP 3915)):
#0  0x7fe4762ee756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe47ce0d234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fe47ce0d279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fe4762e82e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fe476d4654f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fe452f3e700 (LWP 3892)):
#0  0x7fe471b21b3d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fe471b226cb in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe471b228bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe47766306b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe47760c89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe47742ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe4774336d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fe4762e82e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fe476d4654f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fe45db63700 (LWP 3879)):
#0  0x7fe476d3c67d in poll () at /usr/lib/libc.so.6
#1  0x7fe471b227a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe471b228bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe47766306b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe47760c89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe47742ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe47a566025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fe4774336d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe4762e82e7 in 

[akregator] [Bug 378314] Akregator closes every time without any (apparent) reason after some time loading feeds

[Xnake]

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

--- Comment #1 from Xnake  ---
I've tried restoring session, not restoring session and ask me later options
Akregator offers at startup and it crashes no matter what option I choose.

I deleted $HOME/.config/akregatorrc and the problem persists.

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

[kwin] [Bug 378346] New: KWIN random crashes

[billrclarity]

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

Bug ID: 378346
   Summary: KWIN random crashes
   Product: kwin
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: billrclar...@stny.rr.com
  Target Milestone: ---

Application: kwin_x11 (5.8.6)

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

-- Information about the crash:
- What I was doing when the application crashed:
Started Konsole from desktop icon, screen flickered then crash icon appeared in
task bar.  Running suse Leap 42.2 on Lenovo E545, 8 gig of memory.  Crash
occurs a random intervals, usually after clicking on some window.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2158030940 (LWP 15154))]

Thread 7 (Thread 0x7f2135f51700 (LWP 16349)):
#0  0x7ffcba591ada in clock_gettime ()
#1  0x7f215779c806 in clock_gettime () at /lib64/libc.so.6
#2  0x7f2154cd8826 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f2154e3e989 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2154e3ddd1 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#5  0x7f2154e3e527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f2154dedfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f2154c28f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f214f7ba9c8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f2154c2d9e9 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f2157a56734 in start_thread () at /lib64/libpthread.so.0
#11 0x7f215778fd3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f211eac4700 (LWP 15178)):
#0  0x7f2157a5b0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2153da993b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f2153da9969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f2157a56734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f215778fd3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f211fb55700 (LWP 15176)):
#0  0x7f2157788b03 in select () at /lib64/libc.so.6
#1  0x7f2154e3c849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f2154e3e0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f2154e3e527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f2154dedfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2154c28f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f214f7ba9c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f2154c2d9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f2157a56734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f215778fd3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f2120595700 (LWP 15175)):
#0  0x7f2157a5b0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2127988533 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f2127987d57 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f2157a56734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f215778fd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f2137fff700 (LWP 15161)):
#0  0x7f2157788b03 in select () at /lib64/libc.so.6
#1  0x7f2154e3c849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f2154e3e0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f2154e3e527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f2154dedfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2154c28f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f214e98d1d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f2154c2d9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f2157a56734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f215778fd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f213e565700 (LWP 15159)):
#0  0x7f215778749d in poll () at /lib64/libc.so.6
#1  0x7f21569013e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f2156902fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f213f227839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f2154c2d9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f2157a56734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f215778fd3d in clone () 

[plasmashell] [Bug 378345] New: Plasma 5 crash with etx Monitor

[Stephan Dietzel]

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

Bug ID: 378345
   Summary: Plasma 5 crash with etx Monitor
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: stephan.diet...@t-online.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

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

-- Information about the crash:
- What I was doing when the application crashed:
booted after creation of a new activity to resolve the screensaver behaviour
using SuSE Leap 42.2

- Unusual behavior I noticed:
when closing the lid of the laptop screen the ext Monitor was disconnected - no
signal
worked fine with just the default activity, occoured right after creation of a
new activity and reboot
After reboot the login screen was added by a chooser for different window
managers
This chooser appeared twice, just the upper one worked.
Very strange entries in this list, Plasma 5, Plasma Workplace, Plasma Default
and two others.
Which one to choose ?

With just the default activity it worked fine.
I just tried to get rid of the login screen every few minutes.
Really annoying when watching a video.

- Custom settings of the application:
see above.

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7f4811f53700 (LWP 1895)):
#0  0x7f48e1f3849d in poll () from /lib64/libc.so.6
#1  0x7f48de600314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f48de60042c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f48e284532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f48e27f2fdb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f48e262df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f481337b8f7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f48e26329e9 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f48e1741734 in start_thread () from /lib64/libpthread.so.0
#9  0x7f48e1f40d3d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f48195b9700 (LWP 1887)):
#0  0x7f48de6417d4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f48de5ffd99 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f48de6002a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f48de60042c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f48e284532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f48e27f2fdb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f48e262df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f48e26329e9 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f48e1741734 in start_thread () from /lib64/libpthread.so.0
#9  0x7f48e1f40d3d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f4819dba700 (LWP 1885)):
#0  0x7f48de5ff4c0 in g_main_context_release () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f48de6002be in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f48de60042c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f48e284532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f48e27f2fdb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f48e262df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f48e26329e9 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f48e1741734 in start_thread () from /lib64/libpthread.so.0
#8  0x7f48e1f40d3d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f48307ea700 (LWP 1869)):
#0  0x7f48e2845235 in ?? () from /usr/lib64/libQt5Core.so.5
#1  0x7f48de5ff95d in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f48de600230 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f48de60042c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f48e284532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f48e27f2fdb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f48e262df1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f48e64bd632 in ?? () from /usr/lib64/libQt5Quick.so.5
#8  0x7f48e26329e9 in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f48e1741734 in start_thread () from /lib64/libpthread.so.0
#10 

[kmymoney4] [Bug 378164] "No suitable accounts were found at this bank" after successful login to OFX URL

[Thomas Baumgart]

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

--- Comment #6 from Thomas Baumgart  ---
Created attachment 104842
  --> https://bugs.kde.org/attachment.cgi?id=104842=edit
M & T listed by KMyMoney based on ofxhome.org information

The log file's name is ~/ofxlog.txt and not ofx.log. Installing GnuCash does
not help because the file is solely known by the KMyMoney OFX implementation.

M Bank shows up in the KMyMoney list. KMyMoney pulls that list from
ofxhome.org. See attached screen shot.

Can you try to create the log file again? The one you sent only contains the
request but the response is equally important.

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

[systemsettings] [Bug 378344] New: Multimedia settings crashes

[Joe Rutherford]

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

Bug ID: 378344
   Summary: Multimedia settings crashes
   Product: systemsettings
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: killerdragondot...@gmail.com
  Target Milestone: ---

Application: systemsettings (4.11.16)
KDE Platform Version: 4.14.30
Qt Version: 4.8.6
Operating System: Linux 4.4.59-desktop-1.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed: I was opening multimedia
settings. I'm trying to set my hdmi sound output as default. My sound is not
working at this time after updates

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x7f7a3cf36b56 in __strcmp_ssse3 () at /lib64/libc.so.6
#6  0x7f7a154eb486 in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags, QMetaObject const*) () at
/lib64/libQt5Core.so.5
#7  0x7f7a157e174c in _GLOBAL__sub_I_qpaintbuffer.cpp () at
/lib64/libQt5Gui.so.5
#8  0x7f7a3fde923a in call_init.part () at /lib64/ld-linux-x86-64.so.2
#9  0x7f7a3fde934b in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#10 0x7f7a3fded3a1 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#11 0x7f7a3fde90e4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#12 0x7f7a3fdecb33 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#13 0x7f7a33fa3039 in dlopen_doit () at /lib64/libdl.so.2
#14 0x7f7a3fde90e4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#15 0x7f7a33fa369d in _dlerror_run () at /lib64/libdl.so.2
#16 0x7f7a33fa30d1 in dlopen () at /lib64/libdl.so.2
#17 0x7f7a19652e0f in module_Load () at /lib64/libvlccore.so.8
#18 0x7f7a1963833d in module_InitDynamic () at /lib64/libvlccore.so.8
#19 0x7f7a19638638 in AllocatePluginDir () at /lib64/libvlccore.so.8
#20 0x7f7a19638584 in AllocatePluginDir () at /lib64/libvlccore.so.8
#21 0x7f7a19638ae4 in AllocatePluginPath () at /lib64/libvlccore.so.8
#22 0x7f7a19639081 in module_LoadPlugins () at /lib64/libvlccore.so.8
#23 0x7f7a195c07ba in libvlc_InternalInit () at /lib64/libvlccore.so.8
#24 0x7f7a19391deb in libvlc_new () at /lib64/libvlc.so.5
#25 0x7f7a198e2675 in LibVLC::init() () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x7f7a198c8448 in Phonon::VLC::Backend::Backend(QObject*,
QList const&) () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x7f7a198c8fc3 in qt_plugin_instance () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x7f7a3d6222e3 in QPluginLoader::instance() () at /lib64/libQtCore.so.4
#29 0x7f7a19df9a0b in
Phonon::KdePlatformPlugin::createBackend(KSharedPtr) () at
/usr/lib64/kde4/plugins/phonon_platform/kde.so
#30 0x7f7a19dfa183 in Phonon::KdePlatformPlugin::createBackend() () at
/usr/lib64/kde4/plugins/phonon_platform/kde.so
#31 0x7f7a37d87f8e in Phonon::FactoryPrivate::createBackend() () at
/lib64/libphonon.so.4
#32 0x7f7a37d88678 in Phonon::Factory::backend(bool) () at
/lib64/libphonon.so.4
#33 0x7f7a37d8be9a in
Phonon::GlobalConfig::audioOutputDeviceListFor(Phonon::Category, int) const ()
at /lib64/libphonon.so.4
#34 0x7f7a1e878b73 in Phonon::DevicePreference::loadCategoryDevices() () at
/usr/lib64/kde4/kcm_phonon.so
#35 0x7f7a1e879538 in Phonon::DevicePreference::load() () at
/usr/lib64/kde4/kcm_phonon.so
#36 0x7f7a1e872568 in PhononKcm::PhononKcm(QWidget*, QList
const&) () at /usr/lib64/kde4/kcm_phonon.so
#37 0x7f7a1e87284b in QObject* KPluginFactory::createInstance(QWidget*, QObject*, QList const&) () at
/usr/lib64/kde4/kcm_phonon.so
#38 0x7f7a3de3c983 in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) () at /lib64/libkdecore.so.5
#39 0x7f7a3f675d70 in KCModuleLoader::loadModule(KCModuleInfo const&,
KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () at
/lib64/libkcmutils.so.4
#40 0x7f7a3f67b8db in KCModuleProxyPrivate::loadModule() () at
/lib64/libkcmutils.so.4
#41 0x7f7a3f67c5a5 in KCModuleProxy::realModule() const () at
/lib64/libkcmutils.so.4
#42 0x7f7a3f67c9a3 in KCModuleProxy::showEvent(QShowEvent*) () at
/lib64/libkcmutils.so.4
#43 0x7f7a3e321388 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4
#44 0x7f7a3e2d179c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#45 0x7f7a3e2d7e40 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#46 0x7f7a3f00440a in KApplication::notify(QObject*, 

[krita] [Bug 368952] Full screen does not restore to maximized correctly on Windows

[cheteron]

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

cheteron  changed:

   What|Removed |Added

 CC||chete...@gmail.com

--- Comment #12 from cheteron  ---
Same problem. v3.1.3 alpha 2

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

[Breeze] [Bug 360825] LibreOffice menu item radio buttons completely covered with blue color

[Sudhir Khanger]

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

Sudhir Khanger  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Sudhir Khanger  ---
Not reproducible anymore for on Fedora 25 Plasma 5.8.6 with LibreOffice
5.2.6.2.

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

[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||seel...@gmail.com

--- Comment #33 from Kai Uwe Broulik  ---
*** Bug 378306 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 378306] Plasma crashes when 'Desktop' button is clicked

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---


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

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

[plasmashell] [Bug 378321] device notifier not mounting device: problem with polkit

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
Thanks for your analysis, unfortunately I can't see an obvious reason why the
two methods result in different PolicyKit calls.

The "mount" button ends up doing the following:
if (device.is()) {
Solid::StorageAccess *access = device.as();
if (access && !access->isAccessible()) {
access->setup();
}
}

Whereas triggering an action before executing it does the following:
 if (device.is()
&& !device.as()->isAccessible()) {
Solid::StorageAccess *access = device.as();

connect(access, ::StorageAccess::setupDone,
this, ::_k_storageSetupDone);

access->setup();

With _k_storageSetupDone being called once the device is mounted and then the
action is executed. Also, "setup" just asks UDisks on DBus to mount the given
device which then does PolicyKit authentication - that's not somthing we do on
our side.

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

[plasmashell] [Bug 378318] Cannot activate Global Menu.

[Kai Uwe Broulik]

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

--- Comment #6 from Kai Uwe Broulik  ---
Thanks a lot. At a glance I can't find anything unusual in your home directory.
I'll need to try using that as home when I find time to do so.

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

[plasmashell] [Bug 377993] Closing laptop lid no longer blocks session if second screen is connected

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||dvra...@kde.org,
   ||k...@privat.broulik.de

--- Comment #2 from Kai Uwe Broulik  ---
@Dan: You changed it (a while back) so that kscreen just removes the screen
unless PowerDevil suspends, right?

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

[plasmashell] [Bug 378341] Missing desktop icons and taskbar after update

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
Can you run plasmashell from console and paste its output here?

(btw don't run kquitapp with sudo, it needs to be run as your user to find the
dbus service on your session bus)

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

[ksysguard] [Bug 378268] ksysguardd md-sensor (raid) eats filehandles, quits when 1023 are used up.

[bugzilla_noreply]

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

--- Comment #6 from reisenwe...@web.de ---
confirmed to be related to MD sensor in sheet, without any MD sensors the
problem doesn't show

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

[kfile] [Bug 378343] New: Lag/freezing when opening a file dialog

[bugzilla_noreply]

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

Bug ID: 378343
   Summary: Lag/freezing when opening a file dialog
   Product: kfile
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: amelie.luli...@gmail.com
  Target Milestone: ---

I am not sure if this problem is related to kfile. If not, I'm sorry.
When I open a file dialog in Qt applications, all my applications and cursor
lag or even freeze for 5 to 15 seconds before the dialog opens, and when I
close it it lags again, but slightly less.
Reopening the same file dialog immediately after this does not cause any lag,
but opening it a third time causes lag again. (this sometimes doesn't work)
I've tried this in Krita, Kolourpaint and Karbon, and Krita is the application
where it causes the most lag and freezing.

Steps to Reproduce:
1. Start Krita / Kolourpaint / Karbon
2. Open a file using the file dialog

Actual Results:  
System-wide lag or freezing and long wait time for the dialog to open

Expected Results:  
No lag or freezing

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

[frameworks-ktexteditor] [Bug 377562] [PATCH] protecting against accidental zooming

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

Summary|protecting against  |[PATCH] protecting against
   |accidental zooming  |accidental zooming

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

[kimtoy] [Bug 378342] New: Input Method Panel doesn't seem to work

[Nate Graham]

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

Bug ID: 378342
   Summary: Input Method Panel doesn't seem to work
   Product: kimtoy
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: shuizhuyuan...@hotmail.com
  Reporter: pointedst...@zoho.com
CC: wen...@gmail.com
  Target Milestone: ---

Distro: openSUSE Tumbleweed
KDE Plasma version: 5.9.4
plasma5-addons version:  5.9.4
Ibus version: 1.5.14
QT version: 5.7.1

I'm trying to enable some type of systemwisde Emoji input panel, and I ran
across the Input Method Panel widget and figured I'd give it a try.

So I added the Input Method Panel widget to my bottom panel, but it doesn't
seem to work. It has no icon, and left-clicking on it does nothing.
Right-clicking on it brings up a menu with relevant-looking menu items
"Configure input method" "reload config" and "Edit input method". However,
clicking on any of them seems to produce no discernable output or change.

Needless to say, this is a somewhat disappointing user experience.

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

[kimtoy] [Bug 378342] Input Method Panel doesn't seem to work

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 378341] New: Missing desktop icons and taskbar after update

[jgforbes]

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

Bug ID: 378341
   Summary: Missing desktop icons and taskbar after update
   Product: plasmashell
   Version: 5.8.6
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: j...@celticclans.com
  Target Milestone: 1.0

Recent updates to Fedora 25 resulted in a blank desktop. The wallpaper is
there; however, no other graphics are displayed on login.

Right clicking opens the menu; however, configure desktop tab opens a window
titled Floder View Setting -- Plasma, but the window is empty or shows window
that is behind it.

The mouse buttons work at the locations of the desktop icons and the taskbar.

More information:
]$ sudo kquitapp5 plasmashell 
"Application plasmashell could not be found using service org.kde.plasmashell
and path /MainApplication."

]$ sudo kquitapp plasmashell 
kquitapp(5118): "Application plasmashell could not be found using service
org.kde.plasmashell and path /MainApplication."

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

[frameworks-baloo] [Bug 378340] baloo crashs

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.18.0
Product|kde |frameworks-baloo
   Assignee|unassigned-b...@kde.org |pinak.ah...@gmail.com
  Component|general |Baloo File Daemon

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

[knemo] [Bug 378316] High cpu usage in task manager network monitor when "Setting network address" state

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Which plasmashell version? Also, are you really using 'knemo' or Plasma's
network monitor widget?

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

[akregator] [Bug 378317] left click an url => opens new tab and launches FF

[Philippe ROUBACH]

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

--- Comment #1 from Philippe ROUBACH  ---
There is also another problem. I assume it is linked to the problem in
description.

If in kmail in a mail I left click on an URL
then
the URL is opened in FF
and
the URL is opened in a new tab in akregator!

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

[plasmashell] [Bug 377993] Closing laptop lid no longer blocks session if second screen is connected

[Jakub Gocoł]

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

Jakub Gocoł  changed:

   What|Removed |Added

 CC||jakub.go...@gmail.com

--- Comment #1 from Jakub Gocoł  ---
System Settings/Power Management/Energy Saving/
There is option "Even when an external monitor is connected"
Are you sure it is on?

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

[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems

[CnZhx]

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

CnZhx  changed:

   What|Removed |Added

 CC||z...@cnzhx.net

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

[kdenlive] [Bug 368284] There are spaces between the Arab characters and the edges of the characters are not Smooth.

[Safa Alfulaij]

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

--- Comment #8 from Safa Alfulaij  ---
More investigation:
It's not a problem with Arabic or western, it's a problem with overlapping line
segments.
For example, applying the underline attribute to a pure English text inverses
the "filling" in the characters.
For Arabic, the letters aren't spaced (it's the usual and correct look), but
there are overlapping shapes (which is normal) whenever two letters are
"connected" together.
That's why the curve shape at one edge of the break appears, that's how the
letters are made and designed in fonts.

Check: http://i.imgur.com/5Zi45vb.png (Ligatures and kerning is working fine)
Arabic text in edit mode: http://i.imgur.com/4tnefCx.png (It's the same text
but doesn't have that empty areas)

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

[plasma-mycroft] [Bug 377779] Plasmoid could not import Qt.WebSockets 1.0

[christian tacke]

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

--- Comment #2 from christian tacke  ---
(In reply to Aditya Mehra from comment #1)
> Works for me on up to date Fedora 25 x64. Your distribution and plasma
> version?

plasma-desktop 5.8.6-1.fc25

It also worked for me with qt5-qtwebsockets-devel installed. This was needed.

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

[kde] [Bug 378340] New: baloo crashs

[bugzilla_noreply]

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

Bug ID: 378340
   Summary: baloo crashs
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: fa...@tortugalabs.it
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-66-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
baloo crashs when a virtual machine (virtual box) run, or when a cd/dvd is
mounted

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f793002a700 (LWP 5443)):
#0  0x7f7a79210b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7a763e138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7a763e149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7a79e467eb in QEventDispatcherGlib::processEvents
(this=0x7f79280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f7a79dedb4a in QEventLoop::exec (this=this@entry=0x7f7930029bc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00420cd8 in Baloo::FileContentIndexer::run (this=0x10fa680) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/filecontentindexer.cpp:71
#6  0x7f7a79c0c2d3 in QThreadPoolThread::run (this=0x11d31e0) at
thread/qthreadpool.cpp:93
#7  0x7f7a79c0f7be in QThreadPrivate::start (arg=0x11d31e0) at
thread/qthread_unix.cpp:331
#8  0x7f7a788736ba in start_thread (arg=0x7f793002a700) at
pthread_create.c:333
#9  0x7f7a7921c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f7a7b1078c0 (LWP 5052)):
[KCrash Handler]
#6  0x7f7a7794ecb7 in mdb_midl_xmerge () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x7f7a7794676c in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#8  0x7f7a77948754 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x7f7a77948b3a in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x7f7a7794bfa4 in mdb_cursor_put () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#11 0x7f7a7794e260 in mdb_put () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#12 0x7f7a7a2e571a in Baloo::PostingDB::put
(this=this@entry=0x7ffccaadc930, term=..., list=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/postingdb.cpp:78
#13 0x7f7a7a2f6b31 in Baloo::WriteTransaction::commit (this=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:307
#14 0x7f7a7a2ee032 in Baloo::Transaction::commit
(this=this@entry=0x7ffccaadc9d0) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:262
#15 0x0042a02b in Baloo::MetadataMover::moveFileMetadata
(this=0x10f3e60, from=..., to=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:58
#16 0x7f7a79e1ebaf in QtPrivate::QSlotObjectBase::call (a=0x7ffccaadcb30,
r=0x7ffccaadd1f0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#17 QMetaObject::activate (sender=sender@entry=0x10b97d0,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffccaadcb30) at kernel/qobject.cpp:3698
#18 0x7f7a79e1f537 in QMetaObject::activate (sender=sender@entry=0x10b97d0,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffccaadcb30)
at kernel/qobject.cpp:3578
#19 0x0042aaba in KInotify::moved (this=this@entry=0x10b97d0, _t1=...,
_t2=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330
#20 0x0042cbff in KInotify::slotEvent (this=,
socket=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:421
#21 0x7f7a79e1ebaf in QtPrivate::QSlotObjectBase::call (a=0x7ffccaadcdc0,
r=0x10b97d0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#22 QMetaObject::activate (sender=sender@entry=0x11050b0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffccaadcdc0) at kernel/qobject.cpp:3698
#23 0x7f7a79e1f537 in QMetaObject::activate (sender=sender@entry=0x11050b0,
m=m@entry=0x7f7a7a039780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffccaadcdc0)
at kernel/qobject.cpp:3578
#24 0x7f7a79e9e24e in QSocketNotifier::activated
(this=this@entry=0x11050b0, _t1=13) at .moc/moc_qsocketnotifier.cpp:134
#25 0x7f7a79e2b1cb in QSocketNotifier::event (this=0x11050b0, e=) at kernel/qsocketnotifier.cpp:260
#26 0x7f7a79df036c in QCoreApplication::notify (event=0x7ffccaadce80,

[plasmashell] [Bug 378032] Remember history of notifications like on KDE4

[Tom Hardy]

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

--- Comment #18 from Tom Hardy  ---
On further thought, I don't see a problem with treating notifications more like
syslog entries; keep 'em all around for a year or whatever.  Then, the
notification UI would be a matter of what to display and how to display it. 
You could have defaults, application developers could express a preference, but
the user could pull up counts on all their unique "Now Playing" entries, etc.

Syslog facilities could be directly involved, or maybe akonadi would be a
better choice.

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

[Discover] [Bug 378339] New: Crash on remove chars in search text box

[dS810]

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

Bug ID: 378339
   Summary: Crash on remove chars in search text box
   Product: Discover
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: artem.anuf...@live.de
  Target Milestone: ---

Application: plasma-discover (5.9.4)

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

-- Information about the crash:
- What I was doing when the application crashed:
1. Input search term "gim"
2. select a "non application" result for preview
3. select "application" on the left side
--> results will be filtered (OK!)
4. remove a char from your search term "gim" --> "gi"
--> Crash

The crash can be reproduced every time.

-- Backtrace:
Application: Entdecken (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbacb2fe5c0 (LWP 2684))]

Thread 9 (Thread 0x7fba21079700 (LWP 2721)):
#0  0x7fbac67ef67d in poll () at /usr/lib/libc.so.6
#1  0x7fbac140d7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbac140db32 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7fba44530446 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7fbac1435175 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fbac33472e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fbac67f954f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fba2187a700 (LWP 2720)):
#0  0x7fbac67ef67d in poll () at /usr/lib/libc.so.6
#1  0x7fbac140d7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbac140d8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fbac140d901 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fbac1435175 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fbac33472e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fbac67f954f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fba83df9700 (LWP 2696)):
#0  0x7fbac67ef67d in poll () at /usr/lib/libc.so.6
#1  0x7fbac140d7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbac140d8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fbac742906b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fbac73d289a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fbac71f4a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fbac71f96d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fbac33472e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fbac67f954f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fba9b129700 (LWP 2691)):
#0  0x7fbac7428792 in  () at /usr/lib/libQt5Core.so.5
#1  0x7fbac140cc8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fbac140d6cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fbac140d8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fbac742906b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fbac73d289a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fbac71f4a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fbac71f96d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fbac33472e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fbac67f954f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fbaa48d0700 (LWP 2690)):
#0  0x7fbac140d05f in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#1  0x7fbac140d744 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbac140d8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fbac742906b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fbac73d289a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fbac71f4a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fbaca65efd6 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7fbac71f96d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fbac33472e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fbac67f954f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fbaaebe4700 (LWP 2689)):
#0  0x7fbac1452e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fbac140d6be in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbac140d8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fbac742906b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fbac73d289a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fbac71f4a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fbac7d9e025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fbac71f96d8 in  

[Akonadi] [Bug 377656] akonadiserver has an unhandled protocol exception

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

   Version Fixed In||5.6.1
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/ako
   ||nadi/da7070a7facb3c2f91c03b
   ||28c36ba5b929b89a42

--- Comment #7 from Daniel Vrátil  ---
Git commit da7070a7facb3c2f91c03b28c36ba5b929b89a42 by Daniel Vrátil.
Committed on 01/04/2017 at 10:31.
Pushed by dvratil into branch 'Applications/17.04'.

Handle nested exceptions during error handling
FIXED-IN: 5.6.1

M  +30   -4src/server/connection.cpp

https://commits.kde.org/akonadi/da7070a7facb3c2f91c03b28c36ba5b929b89a42

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

[neon] [Bug 378338] All text on installer is invisible if Breeze-Dark is selected as the Desktop Theme

[m712]

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

m712  changed:

   What|Removed |Added

 CC||comeon@getbackinthe.kitchen

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

[neon] [Bug 378338] New: All text on installer is invisible if Breeze-Dark is selected as the Desktop Theme

[m712]

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

Bug ID: 378338
   Summary: All text on installer is invisible if Breeze-Dark is
selected as the Desktop Theme
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Packages Dev Edition [stable]
  Assignee: neon-b...@kde.org
  Reporter: comeon@getbackinthe.kitchen
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 104841
  --> https://bugs.kde.org/attachment.cgi?id=104841=edit
Screenshot showing bug

Hello,

When you select Breeze-Dark as the desktop theme on the KDE Neon LiveCD, and
then run the installer, all text is invisible apart from URLs and selection
widgets. I suspect the Neon installer sets the BG color itself but leaves the
text color to the theme.

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

[neon] [Bug 378326] repository down

[Alexander Vinbæk Strand]

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

--- Comment #2 from Alexander Vinbæk Strand  ---
works here also now..

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

[Breeze] [Bug 364849] Tooltip Text in several qt apps such as Amarok and Krusader is unreadable (white on white) with the Breeze/Breeze Dark color schemes

[Massimo Callegari]

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

Massimo Callegari  changed:

   What|Removed |Added

 CC||massimocalleg...@yahoo.it

--- Comment #4 from Massimo Callegari  ---
Same here. KDE Neon LTS, vanilla settings (default Breeze theme)
All GTK apps (e.g. FileZilla, Inkscape) have white on light gray tooltips,
making it impossible to understand what toolbar icons do.

Screenshot: http://pasteboard.co/Lj6iwlO7E.png

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

[neon] [Bug 378326] repository down

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

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

--- Comment #1 from Harald Sitter  ---
Works here.

Please file a ticket with the KDE sysadmins about the issue
https://go.kde.org/u/systickets

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

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

[bugzilla_noreply]

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

--- Comment #43 from stefanfr...@gmx.net ---
Created attachment 104840
  --> https://bugs.kde.org/attachment.cgi?id=104840=edit
Another crash

a second crash this morning.
That could be more useful.

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

[plasmashell] [Bug 378337] New: Clicking Telegram on systray doesnot open its window

[Michail Vourlakos]

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

Bug ID: 378337
   Summary: Clicking Telegram on systray doesnot open its window
   Product: plasmashell
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: mvourla...@gmail.com
  Target Milestone: 1.0

After the upgrade from 5.9.3 to 5.9.4 clicking on telegram icon in the systray
does not open the telegram window

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

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

[bugzilla_noreply]

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

--- Comment #42 from stefanfr...@gmx.net ---
Hi!
yes I know. But the only text that is displayed is:


--Application: Kontact (kontact), signal: Segmentation fault--


not very useful I think.

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

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

[bugzilla_noreply]

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

--- Comment #41 from stefanfr...@gmx.net ---
Created attachment 104839
  --> https://bugs.kde.org/attachment.cgi?id=104839=edit
Crash

crash

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

[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager

[confused]

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

confused  changed:

   What|Removed |Added

 CC||d.anielsch...@gmx.de

--- Comment #13 from confused  ---
Thanks for working on it :)
Unfortunately, I can still reproduce this bug using version 3.0.3 on Arch
Linux. It still pops up randomly in the panel.
Let me know if you need more information on my setup.

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

[plasmashell] [Bug 378032] Remember history of notifications like on KDE4

[Tom Hardy]

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

--- Comment #17 from Tom Hardy  ---
Just tried 'notify-send -t 0 hello world'.  Yay, my first persistent
notification.  Or was it?  It was gone when I looked a little later.  Is that
expected or reasonable behavior?

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

[kdenlive] [Bug 368284] There are spaces between the Arab characters and the edges of the characters are not Smooth.

[Wegwerf]

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

--- Comment #7 from Wegwerf  ---
Thank you sll for the information. This then would break also ligatures and
kerning in western languages too.

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

[krita] [Bug 375027] Krita Gemini doesn't support the n-trig pen of a surface pro, even if wintab is installed.

[bugzilla_noreply]

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

j...@live.ca changed:

   What|Removed |Added

 CC||j...@live.ca

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

[kdevelop] [Bug 376149] KDevelop crash during background parsing code: assertion=assertion@entry=0x7ff1c72a0070 "DelayedTypos.empty() && \"Uncorrected typos!\"", file=file@entry=0x7ff1c729f9e8

[pavel kropitz]

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

pavel kropitz  changed:

   What|Removed |Added

 CC||univ...@fu-solution.com

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

[plasmashell] [Bug 378032] Remember history of notifications like on KDE4

[Tom Hardy]

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

Tom Hardy  changed:

   What|Removed |Added

 CC||rhardy...@gmail.com

--- Comment #16 from Tom Hardy  ---
[ doubled from https://github.com/blue-systems/plasma-5.4/issues/48 ]

This one needs my two cents, since I've spent a couple hours looking into it
and reading this forum.

I often notice a pop-up with buttons on it, just as it disappears. Was it
important? I can't say, but apparently the developer didn't think so. Can I
refer to the application for a clue? No, because I have no idea what it was
about or what application produced it. This is annoying.

Meanwhile I have yet to see a persistent notification after a year with KF5.
The systray notification icon is apparently there to take up space and get me
to spend time looking into the apparent problem.

This could use a little work.

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

[Akonadi] [Bug 378336] New: KMail resource crash

[Giuseppe Vinci]

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

Bug ID: 378336
   Summary: KMail resource crash
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Mixed Maildir resource
  Assignee: kdepim-b...@kde.org
  Reporter: giuseppe.vi...@gmx.net
CC: kram...@kde.org
  Target Milestone: ---

Application: akonadi_mixedmaildir_resource (4.14)
KDE Platform Version: 4.14.30
Qt Version: 4.8.5
Operating System: Linux 3.12.67-64-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I started manual the mixedmaildir resource named "saved-mails"
- Unusual behavior I noticed:
nothing
- Custom settings of the application:
a) I store most of recived mails in the mixedmaildir resource "saved-mails",
which is on another hard drive partition as /home
b) mail inbox is located in ~/.local/share/local-mail/ as Kmail standard

The crash can be reproduced every time.

-- Backtrace:
Application: saved-mails vom Typ KMail-Mailordner
(akonadi_mixedmaildir_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f7c2ced24c9 in raise () from /lib64/libc.so.6
#7  0x7f7c2ced3958 in abort () from /lib64/libc.so.6
#8  0x7f7c2d7e1204 in qt_message_output (msgType=,
buf=) at global/qglobal.cpp:2323
#9  0x7f7c30d61352 in ~QDebug (this=0x7ffd72a7df70, __in_chrg=) at /usr/include/QtCore/qdebug.h:85
#10 KMIndexReader::readHeader (this=this@entry=0x7ffd72a7e300,
version=version@entry=0x7ffd72a7e00c) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/kmindexreader/kmindexreader.cpp:251
#11 0x7f7c30d61a13 in KMIndexReader::readIndex
(this=this@entry=0x7ffd72a7e300) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/kmindexreader/kmindexreader.cpp:323
#12 0x00426d9d in MaildirContext::readIndexData (this=0x2411940) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/mixedmaildirstore.cpp:461
#13 0x00436159 in MixedMaildirStore::Private::visit (this=0x25528f0,
job=0x257f6f0) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/mixedmaildirstore.cpp:1524
#14 0x00435e2b in MixedMaildirStore::processJob (this=,
job=0x257f6f0) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/mixedmaildirstore.cpp:2311
#15 0x7f7c3092b940 in
Akonadi::FileStore::AbstractLocalStore::Private::processJobs (this=0x258b340,
jobs=...) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/shared/filestore/abstractlocalstore.cpp:300
#16 0x7f7c2d8fed68 in QMetaObject::activate (sender=0x2555db0,
m=m@entry=0x7f7c30b45940
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd72a7e7f0)
at kernel/qobject.cpp:3556
#17 0x7f7c3093c362 in Akonadi::FileStore::AbstractJobSession::jobsReady
(this=, _t1=...) at
/usr/src/debug/kdepim-runtime-4.14.10/build/resources/shared/filestore/moc_session_p.cpp:98
#18 0x7f7c3093b43d in runNextJob (this=) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/shared/filestore/sessionimpls.cpp:142
#19 Akonadi::FileStore::FiFoQueueJobSession::qt_static_metacall (_o=0x139e,
_c=5022, _id=6, _a=0x) at
/usr/src/debug/kdepim-runtime-4.14.10/build/resources/shared/filestore/moc_sessionimpls_p.cpp:49
#20 0x7f7c2d8fed68 in QMetaObject::activate (sender=0x2551b70, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3556
#21 0x7f7c2d902f31 in QObject::event (this=0x2551b70, e=) at
kernel/qobject.cpp:1165
#22 0x7f7c2e2f68ac in QApplicationPrivate::notify_helper
(this=this@entry=0x239c070, receiver=receiver@entry=0x2551b70,
e=e@entry=0x7ffd72a7ed60) at kernel/qapplication.cpp:4562
#23 0x7f7c2e2fce70 in QApplication::notify (this=this@entry=0x7ffd72a7f070,
receiver=receiver@entry=0x2551b70, e=e@entry=0x7ffd72a7ed60) at
kernel/qapplication.cpp:4348
#24 0x7f7c2f00d89a in KApplication::notify (this=0x7ffd72a7f070,
receiver=0x2551b70, event=0x7ffd72a7ed60) at
/usr/src/debug/kdelibs-4.14.30/kdeui/kernel/kapplication.cpp:311
#25 0x7f7c2d8eb0ad in QCoreApplication::notifyInternal
(this=0x7ffd72a7f070, receiver=0x2551b70, event=0x7ffd72a7ed60) at
kernel/qcoreapplication.cpp:949
#26 0x7f7c2d91a83c in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:231
#27 QTimerInfoList::activateTimers (this=0x239c9d0) at
kernel/qeventdispatcher_unix.cpp:636
#28 0x7f7c2d917b21 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:186
#29 0x7f7c290c8316 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#30 0x7f7c290c8668 in ?? () from /usr/lib64/libglib-2.0.so.0
#31 0x7f7c290c870c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#32 0x7f7c2d917d55 in 

[kmymoney4] [Bug 344172] Transactions report by payee with totals only

[NSLW]

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

NSLW  changed:

   What|Removed |Added

   Version Fixed In||5.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmy
   ||money/2e591fa1e8f8ad4b3c92f
   ||c3892a15606df7dad98

--- Comment #1 from NSLW  ---
Git commit 2e591fa1e8f8ad4b3c92fc3892a15606df7dad98 by Łukasz Wojniłowicz.
Committed on 01/04/2017 at 06:16.
Pushed by wojnilowicz into branch 'master'.

Add hide transactions for reports
FIXED-IN:5.0

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

Signed-off-by: Łukasz Wojniłowicz 

M  +5-1kmymoney/dialogs/kreportconfigurationfilterdlg.cpp
M  +5-0kmymoney/html/kmymoney.css
M  +5-2kmymoney/mymoney/mymoneyreport.cpp
M  +10   -0kmymoney/mymoney/mymoneyreport.h
M  +42   -29   kmymoney/reports/listtable.cpp
M  +514  -454  kmymoney/widgets/kmymoneyreportconfigtab3decl.ui
M  +8-0kmymoney/widgets/kmymoneyreportconfigtabimpl.cpp
M  +3-0kmymoney/widgets/kmymoneyreportconfigtabimpl.h

https://commits.kde.org/kmymoney/2e591fa1e8f8ad4b3c92fc3892a15606df7dad98

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

[kmymoney4] [Bug 365177] Changing investment fraction doesn't change rounding behavior

[NSLW]

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

NSLW  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/c6e31c96a03ad5a7ec5e3
   ||695bbfa8336181ab81c
   Version Fixed In||5.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from NSLW  ---
Git commit c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c by Łukasz Wojniłowicz.
Committed on 01/04/2017 at 06:16.
Pushed by wojnilowicz into branch 'master'.

Fix rounding problem with investments

Patch introduces rounding rules per security for fixing bug #372163. It
seems that this broker always rounds amounts down while my broker rounds
amounts depending on the outlying digit, so it couldn't work for both of
us without rules.

Rounding is done in InvestTransactionEditor because it has all needed
informations at hand.

No rounding of shares is done in InvestTransactionEditor::setupPrice.
Transaction from bug #372163 looks as follows:
brokerage:
shares = 1,009 ; value = 1,009
investment:
shares = -1 ; value = 1,009

InvestTransactionEditor::setupPrice causes brokerage to look as follows:
shares = 1,01 ; value = 1,009
As we can see shares and value diverge, which is unacceptable here.

Patch makes assumption that transaction has only single split of
stock/mutual fund/bond.
Related: bug 345655, bug 357784, bug 372163
FIXED-IN:5.0

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

Signed-off-by: Łukasz Wojniłowicz 

M  +32   -15   kmymoney/dialogs/investtransactioneditor.cpp
M  +31   -0kmymoney/kmymoneyutils.cpp
M  +22   -0kmymoney/kmymoneyutils.h
M  +39   -0kmymoney/mymoney/mymoneysecurity.cpp
M  +27   -8kmymoney/mymoney/mymoneysecurity.h
M  +1-0kmymoney/mymoney/storage/mymoneydbdef.cpp
M  +3-0kmymoney/mymoney/storage/mymoneystoragesql.cpp
M  +4-3kmymoney/widgets/transaction.cpp
M  +11   -0   
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpage.cpp
M  +104  -90  
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpagedecl.ui
M  +2-0kmymoney/wizards/newinvestmentwizard/knewinvestmentwizard.cpp

https://commits.kde.org/kmymoney/c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c

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

[kmymoney4] [Bug 345655] Rounding problems between checking and investment account

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In|4.8.0   |5.0
  Latest Commit|http://commits.kde.org/kmym |https://commits.kde.org/kmy
   |oney/dd5bfdd80e64ec30ac10b1 |money/c6e31c96a03ad5a7ec5e3
   |3c6a0dd7aa818bd1d2  |695bbfa8336181ab81c
 Status|REOPENED|RESOLVED

--- Comment #41 from NSLW  ---
Git commit c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c by Łukasz Wojniłowicz.
Committed on 01/04/2017 at 06:16.
Pushed by wojnilowicz into branch 'master'.

Fix rounding problem with investments

Patch introduces rounding rules per security for fixing bug #372163. It
seems that this broker always rounds amounts down while my broker rounds
amounts depending on the outlying digit, so it couldn't work for both of
us without rules.

Rounding is done in InvestTransactionEditor because it has all needed
informations at hand.

No rounding of shares is done in InvestTransactionEditor::setupPrice.
Transaction from bug #372163 looks as follows:
brokerage:
shares = 1,009 ; value = 1,009
investment:
shares = -1 ; value = 1,009

InvestTransactionEditor::setupPrice causes brokerage to look as follows:
shares = 1,01 ; value = 1,009
As we can see shares and value diverge, which is unacceptable here.

Patch makes assumption that transaction has only single split of
stock/mutual fund/bond.
Related: bug 357784, bug 365177, bug 372163
FIXED-IN:5.0

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

Signed-off-by: Łukasz Wojniłowicz 

M  +32   -15   kmymoney/dialogs/investtransactioneditor.cpp
M  +31   -0kmymoney/kmymoneyutils.cpp
M  +22   -0kmymoney/kmymoneyutils.h
M  +39   -0kmymoney/mymoney/mymoneysecurity.cpp
M  +27   -8kmymoney/mymoney/mymoneysecurity.h
M  +1-0kmymoney/mymoney/storage/mymoneydbdef.cpp
M  +3-0kmymoney/mymoney/storage/mymoneystoragesql.cpp
M  +4-3kmymoney/widgets/transaction.cpp
M  +11   -0   
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpage.cpp
M  +104  -90  
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpagedecl.ui
M  +2-0kmymoney/wizards/newinvestmentwizard/knewinvestmentwizard.cpp

https://commits.kde.org/kmymoney/c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c

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

[kmymoney4] [Bug 357784] Buying investments not always displaying correct investment sum

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmy
   ||money/c6e31c96a03ad5a7ec5e3
   ||695bbfa8336181ab81c
   Version Fixed In||5.0
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from NSLW  ---
Git commit c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c by Łukasz Wojniłowicz.
Committed on 01/04/2017 at 06:16.
Pushed by wojnilowicz into branch 'master'.

Fix rounding problem with investments

Patch introduces rounding rules per security for fixing bug #372163. It
seems that this broker always rounds amounts down while my broker rounds
amounts depending on the outlying digit, so it couldn't work for both of
us without rules.

Rounding is done in InvestTransactionEditor because it has all needed
informations at hand.

No rounding of shares is done in InvestTransactionEditor::setupPrice.
Transaction from bug #372163 looks as follows:
brokerage:
shares = 1,009 ; value = 1,009
investment:
shares = -1 ; value = 1,009

InvestTransactionEditor::setupPrice causes brokerage to look as follows:
shares = 1,01 ; value = 1,009
As we can see shares and value diverge, which is unacceptable here.

Patch makes assumption that transaction has only single split of
stock/mutual fund/bond.
Related: bug 345655, bug 365177, bug 372163
FIXED-IN:5.0

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

Signed-off-by: Łukasz Wojniłowicz 

M  +32   -15   kmymoney/dialogs/investtransactioneditor.cpp
M  +31   -0kmymoney/kmymoneyutils.cpp
M  +22   -0kmymoney/kmymoneyutils.h
M  +39   -0kmymoney/mymoney/mymoneysecurity.cpp
M  +27   -8kmymoney/mymoney/mymoneysecurity.h
M  +1-0kmymoney/mymoney/storage/mymoneydbdef.cpp
M  +3-0kmymoney/mymoney/storage/mymoneystoragesql.cpp
M  +4-3kmymoney/widgets/transaction.cpp
M  +11   -0   
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpage.cpp
M  +104  -90  
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpagedecl.ui
M  +2-0kmymoney/wizards/newinvestmentwizard/knewinvestmentwizard.cpp

https://commits.kde.org/kmymoney/c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c

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

[kmymoney4] [Bug 372163] Investment sells giving the wrong result

[NSLW]

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

NSLW  changed:

   What|Removed |Added

   Version Fixed In||5.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kmy
   ||money/c6e31c96a03ad5a7ec5e3
   ||695bbfa8336181ab81c

--- Comment #4 from NSLW  ---
Git commit c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c by Łukasz Wojniłowicz.
Committed on 01/04/2017 at 06:16.
Pushed by wojnilowicz into branch 'master'.

Fix rounding problem with investments

Patch introduces rounding rules per security for fixing bug #372163. It
seems that this broker always rounds amounts down while my broker rounds
amounts depending on the outlying digit, so it couldn't work for both of
us without rules.

Rounding is done in InvestTransactionEditor because it has all needed
informations at hand.

No rounding of shares is done in InvestTransactionEditor::setupPrice.
Transaction from bug #372163 looks as follows:
brokerage:
shares = 1,009 ; value = 1,009
investment:
shares = -1 ; value = 1,009

InvestTransactionEditor::setupPrice causes brokerage to look as follows:
shares = 1,01 ; value = 1,009
As we can see shares and value diverge, which is unacceptable here.

Patch makes assumption that transaction has only single split of
stock/mutual fund/bond.
Related: bug 345655, bug 357784, bug 365177
FIXED-IN:5.0

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

Signed-off-by: Łukasz Wojniłowicz 

M  +32   -15   kmymoney/dialogs/investtransactioneditor.cpp
M  +31   -0kmymoney/kmymoneyutils.cpp
M  +22   -0kmymoney/kmymoneyutils.h
M  +39   -0kmymoney/mymoney/mymoneysecurity.cpp
M  +27   -8kmymoney/mymoney/mymoneysecurity.h
M  +1-0kmymoney/mymoney/storage/mymoneydbdef.cpp
M  +3-0kmymoney/mymoney/storage/mymoneystoragesql.cpp
M  +4-3kmymoney/widgets/transaction.cpp
M  +11   -0   
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpage.cpp
M  +104  -90  
kmymoney/wizards/newinvestmentwizard/kinvestmentdetailswizardpagedecl.ui
M  +2-0kmymoney/wizards/newinvestmentwizard/knewinvestmentwizard.cpp

https://commits.kde.org/kmymoney/c6e31c96a03ad5a7ec5e3695bbfa8336181ab81c

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

[kmymoney4] [Bug 367544] Please add support for CLF currency

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.0
  Latest Commit||https://commits.kde.org/kmy
   ||money/98095cbb39897af8d
   ||6f0a1372a06850df0f9
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from NSLW  ---
Git commit 98095cbb39897af8d6f0a1372a06850df0f9 by Łukasz Wojniłowicz.
Committed on 01/04/2017 at 06:17.
Pushed by wojnilowicz into branch 'master'.

Add support for CLF currency

Webprice quotes won't work for CLPCLF (price = 0.), but works for
CLFCLP, and manual entering works for both.
FIXED-IN:5.0

M  +1-0kmymoney/views/kmymoneyview.cpp

https://commits.kde.org/kmymoney/98095cbb39897af8d6f0a1372a06850df0f9

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