[plasmashell] [Bug 368933] Plasma crashed after clicking system tray icon

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #2 from Franco Pellegrini  ---
Unfortunately, I am unable to reproduce it...

Can you tell me which plasma packages to install, so I have them if it happens
again? when dr. konqi came up I clicked the button that should install all the
needed dbg packages, but it said all packages were already installed...

Do you know if there's a way to recover the old crash and try to get more
information after installing the dbg packages?

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

[plasmashell] [Bug 368933] New: Plasma crashed after clicking system tray icon

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 368933
   Summary: Plasma crashed after clicking system tray icon
   Product: plasmashell
   Version: 5.6.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: frap...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.5)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-36-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

After configuring the entries to show in the system tray, I saved the settings.
Afterwards, I clicked in the icon for themounted devices, and Plasma crashed
and restarted.

Could not reproduce it and settings were saved fine.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5f222bc8c0 (LWP 2458))]

Thread 12 (Thread 0x7f5e3cc7f700 (LWP 3368)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5f2030e92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f5f2030f1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1c1076fa in start_thread (arg=0x7f5e3cc7f700) at
pthread_create.c:333
#6  0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f5e3ede6700 (LWP 3190)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5f2030e92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f5f2030f1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1c1076fa in start_thread (arg=0x7f5e3ede6700) at
pthread_create.c:333
#6  0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f5e5248f700 (LWP 2988)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5f2030e92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f5f2030f1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1c1076fa in start_thread (arg=0x7f5e5248f700) at
pthread_create.c:333
#6  0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f5e532af700 (LWP 2985)):
#0  0x7f5f196a6ae4 in g_mutex_unlock (mutex=0x7f5e4c000990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gthread-posix.c:1347
#1  0x7f5f19661dc9 in g_main_context_check
(context=context@entry=0x7f5e4c000990, max_priority=2147483647,
fds=fds@entry=0x7f5e4c004cc0, n_fds=n_fds@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3679
#2  0x7f5f19662340 in g_main_context_iterate
(context=context@entry=0x7f5e4c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837
#3  0x7f5f196624ac in g_main_context_iteration (context=0x7f5e4c000990,
may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f5f1d26ca9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f1d213dea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5f1d0308a4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5e557c77d7 in KCupsConnection::run() () at
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#8  0x7f5f1d03584e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f5f1c1076fa in start_thread (arg=0x7f5e532af700) at
pthread_create.c:333
#10 0x7f5f1c93eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f5e6b014700 (LWP 2568)):
#0  0x7f5f1c10d3a0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5f1d036aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  

[kontact] [Bug 366380] New: Kontact crashed when doing a search

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 366380
   Summary: Kontact crashed when doing a search
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: frap...@gmail.com

Application: kontact (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-33-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

I was trying to search for an email, then I clicked the "up arrow" next to the
progress bar in the bottom right, in order to see details, and then it crashed

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

Thread 21 (Thread 0x7f1156d92700 (LWP 16086)):
#0  QBasicAtomicOps<8>::testAndSetRelaxed (currentValue=, newValue=0x1, expectedValue=0x0, _q_value=@0x4072c28: 0x0) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#1  QGenericAtomicOps >::testAndSetAcquire (currentValue=, newValue=,
expectedValue=0x0, _q_value=@0x4072c28: 0x0) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:166
#2  QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0,
this=this@entry=0x4072c28) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:276
#3  QBasicMutex::fastTryLock (current=,
this=this@entry=0x4072c28) at thread/qmutex.h:82
#4  QMutex::lock (this=this@entry=0x4072c28) at thread/qmutex.cpp:212
#5  0x7f1226e3701f in QMutexLocker::QMutexLocker (m=0x4072c28,
this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:128
#6  QThreadData::canWaitLocked (this=0x4072c00) at
../../include/QtCore/5.5.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:240
#7  postEventSourcePrepare (s=0x7f1150013840, timeout=0x7f1156d91ac4) at
kernel/qeventdispatcher_glib.cpp:254
#8  0x7f121fb0492d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f121fb052cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f121fb054ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f1226e37a9b in QEventDispatcherGlib::processEvents
(this=0x7f1150005b30, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#12 0x7f1226ddedea in QEventLoop::exec (this=this@entry=0x7f1156d91c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#13 0x7f1226bfb8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#14 0x7f1226c0084e in QThreadPrivate::start (arg=0x40220e0) at
thread/qthread_unix.cpp:331
#15 0x7f122032f6fa in start_thread (arg=0x7f1156d92700) at
pthread_create.c:333
#16 0x7f1226300b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7f1168d34700 (LWP 16050)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f12262f4e82 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f121fb0539c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f121fb054ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1226e37a9b in QEventDispatcherGlib::processEvents
(this=0x7f115c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f1226ddedea in QEventLoop::exec (this=this@entry=0x7f1168d33c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1226bfb8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f1226c0084e in QThreadPrivate::start (arg=0x32a6bf0) at
thread/qthread_unix.cpp:331
#8  0x7f122032f6fa in start_thread (arg=0x7f1168d34700) at
pthread_create.c:333
#9  0x7f1226300b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7f1169936700 (LWP 16047)):
#0  0x7f121fb49ae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f121fb054b6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1226e37a9b in QEventDispatcherGlib::processEvents
(this=0x7f11580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7f1226ddedea in QEventLoop::exec (this=this@entry=0x7f1169935c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f1226bfb8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#5  0x7f1226c0084e in QThreadPrivate::start (arg=0x3e08620) at
thread/qthread_unix.cpp:331
#6  0x7f122032f6fa in start_thread (arg=0x7f1169936700) at
pthread_create.c:333
#7  0x7f1226300b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 

[dolphin] [Bug 361522] Dolphin crashes on opening LibreOffice Calc associated .csv fie

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #1 from Franco Pellegrini  ---
Created attachment 99909
  --> https://bugs.kde.org/attachment.cgi?id=99909=edit
New crash information added by DrKonqi

dolphin (15.12.3) using Qt 5.5.1

- What I was doing when the application crashed:

browse to a folder and clicked a PDF file to open it

-- Backtrace (Reduced):
#6  QWeakPointer::data (this=0x34) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:588
#7  QPointer::data (this=0x34) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:70
#8  QPointer::operator QScreen* (this=0x34) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:76
#9  QPlatformScreen::screen (this=this@entry=0x1dbca40) at
kernel/qplatformscreen.cpp:116
#10 0x7f0ab15637cc in QXcbWindow::create (this=0x2736ed0) at
qxcbwindow.cpp:426

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

[dolphin] [Bug 361522] Dolphin crashes on opening LibreOffice Calc associated .csv fie

[Franco Pellegrini via KDE Bugzilla]

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

Franco Pellegrini  changed:

   What|Removed |Added

 CC||frap...@gmail.com

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

[kontact] [Bug 363899] New: Kontact crashed when clicked "Feeds"

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 363899
   Summary: Kontact crashed when clicked "Feeds"
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: frap...@gmail.com

Application: kontact (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.22.0
Operating System: Linux 4.4.0-23-generic x86_64
Distribution: Ubuntu 16.04 LTS

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

I was reading mails inside of the "Mail" section, and I clicked the "Feeds" to
read my RSS feeds. Kontact crashed instantly.

I re-opened afterwards, and retried, and this time I had no issues.

This same thing occured me some time ago

The crash can be reproduced sometimes.

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

Thread 27 (Thread 0x7fa731c5c700 (LWP 4296)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75276c88b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa75276c8c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa74e52d6fa in start_thread (arg=0x7fa731c5c700) at
pthread_create.c:333
#4  0x7fa7544fcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fa6ee2e3700 (LWP 4297)):
#0  0x7fa74dd47ac9 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa74dd02ddc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa74dd03340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa74dd034ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa755033a9b in QEventDispatcherGlib::processEvents
(this=0x7fa6e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fa754fdadea in QEventLoop::exec (this=this@entry=0x7fa6ee2e2c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fa754df78a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fa754dfc84e in QThreadPrivate::start (arg=0x11522d0) at
thread/qthread_unix.cpp:331
#8  0x7fa74e52d6fa in start_thread (arg=0x7fa6ee2e3700) at
pthread_create.c:333
#9  0x7fa7544fcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fa6e7df7700 (LWP 4298)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75247aa74 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa75279c541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa74e52d6fa in start_thread (arg=0x7fa6e7df7700) at
pthread_create.c:333
#4  0x7fa7544fcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 24 (Thread 0x7fa6e75f6700 (LWP 4299)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75247baa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa75279c541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa74e52d6fa in start_thread (arg=0x7fa6e75f6700) at
pthread_create.c:333
#4  0x7fa7544fcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 23 (Thread 0x7fa6e6df5700 (LWP 4300)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75247baa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa75279c541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa74e52d6fa in start_thread (arg=0x7fa6e6df5700) at
pthread_create.c:333
#4  0x7fa7544fcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fa6e65f4700 (LWP 4301)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa75247baa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa75279c541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa74e52d6fa in start_thread (arg=0x7fa6e65f4700) at
pthread_create.c:333
#4  0x7fa7544fcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fa6cbcc8700 (LWP 4304)):
#0  0x7fa74dd12290 in g_poll () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa74dd0339c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa74dd034ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa755033a9b in QEventDispatcherGlib::processEvents
(this=0x7fa6bc0008c0, flags=...) at 

[plasmashell] [Bug 363897] New: Automatic focus policy should not close plasma applets

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 363897
   Summary: Automatic focus policy should not close plasma applets
   Product: plasmashell
   Version: 5.6.4
  Platform: Ubuntu Packages
   URL: https://www.dropbox.com/s/09ujjq7t04sh0hb/dual_screen.
ogv?dl=0
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: frap...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

In my setup, I have configured the focus to follow my mouse, which I find very
convenient when having an external monitor plugged in, and In the video visible
in the "URL", you can see at 0:15 that when you have to move your mouse across
an application to reach some applet (this also happens with the "Add new
widget" that opens up in the left part of the screen) then the focus would
change and the applet closes.

I understand this behavior when you have "Click to focus", however, when you
are using an automatic focus policy (such as "Focus Follows Mouse"), I don't
think plasma components should be affected.

I think applets should close if:

a) You click again whatever made it to open in the first place
b) Clicking outside of it (Unless the very useful "sticky" button is active for
it)

Changing focus, should be ignored.

Reproducible: Always

Steps to Reproduce:
1. Configure your system to use an automatic focus change policy, such as
"Focus Follows Mouse"
2. Have a window of any application open
3. Open a plasma applet, such as calendar
4. Move your mouse over the application window (Without clicking)

Actual Results:  
The plasma applet closes when the focus changes

Expected Results:  
The plasma applet to remain open

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

[plasmashell] [Bug 363896] New: Plasma components miss their proper screen when external monitor present

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 363896
   Summary: Plasma components miss their proper screen when
external monitor present
   Product: plasmashell
   Version: 5.6.4
  Platform: Ubuntu Packages
   URL: https://www.dropbox.com/s/09ujjq7t04sh0hb/dual_screen.
ogv?dl=0
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: frap...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

In the video I added in the "URL", you can see the upper portion is from an
external monitor, and the portion below, my laptop screen.

0:05 - At this point I click the "Wifi" applet. The icon looks like the list of
wifi connections opened, but it didn't.
0:10 - I have to click again to "close it"
0:12 - I click again to open it, and this time it does show up

This happens with all of them... calendar, bluetooth, etc... You first click,
it shows it opened, but it didn't, you have to close it, and try again.

Once it opens up, it does in the wrong screen. The panel is in my laptop screen
(Primary display), but the applet shows up in the external monitor.

I have configured my system so focus would follow the mouse, so at 0:16, you
can see that when I move over the konsole window, the focus changes (I didn't
click it) and the wifi applet closes. At 0:22 I click again to open it (nothing
happens) at 0:25 I close it, and at 0:26 I click it again and this time it is
visible.

I try with the desktop menu in the upper left (Dunno how you guys call this
menu) at 0:35 and it also opens up in the wrong monitor.

The panel settings and the "Add widget", from 0:45 works fine.

Also, if I move the whole panel to the external monitor, then everything works
fine, opening in the external monitor as well.

Reproducible: Always

Steps to Reproduce:
1. Plug in external monitor
2. Try to open a plasma applet, such as bluetooth or calendar


Actual Results:  
Depending on where the panel is located, the applet may open in the wrong
monitor

Expected Results:  
Everything to be consistent and opening in the actual monitor where it is
visible

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

[krunner] [Bug 354235] KRunner crashed after connecting external monitor (QScreen::availableGeometry)

[Franco Pellegrini via KDE Bugzilla]

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

Franco Pellegrini  changed:

   What|Removed |Added

 CC||frap...@gmail.com

--- Comment #2 from Franco Pellegrini  ---
I can confirm this issue still exists in 

Plasma: 5.6.4
KDE: 5.22.0
QT: 5.5.1
Kubuntu 16.04

Here is the backtrace:

Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fddf69948c0 (LWP 1592))]

Thread 3 (Thread 0x7fdde23d5700 (LWP 1594)):
#0  0x7fddf316ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fddf2653c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fddf26558d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fdde4523629 in QXcbEventReader::run (this=0x1b153f0) at
qxcbconnection.cpp:1253
#4  0x7fddf386084e in QThreadPrivate::start (arg=0x1b153f0) at
thread/qthread_unix.cpp:331
#5  0x7fddf13cf6fa in start_thread (arg=0x7fdde23d5700) at
pthread_create.c:333
#6  0x7fddf3176b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fddda8e6700 (LWP 1605)):
#0  0x7fddf316ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fddf061b39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fddf061b4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fddf3a97a9b in QEventDispatcherGlib::processEvents
(this=0x7fddd40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fddf3a3edea in QEventLoop::exec (this=this@entry=0x7fddda8e5ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fddf385b8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fddf58fe3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fddf386084e in QThreadPrivate::start (arg=0x1d249c0) at
thread/qthread_unix.cpp:331
#8  0x7fddf13cf6fa in start_thread (arg=0x7fddda8e6700) at
pthread_create.c:333
#9  0x7fddf3176b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fddf69948c0 (LWP 1592)):
[KCrash Handler]
#6  QScreen::availableGeometry (this=this@entry=0x0) at kernel/qscreen.cpp:316
#7  0x004076fb in View::positionOnScreen
(this=this@entry=0x7ffea73092b0) at
/build/plasma-workspace-LFQsCW/plasma-workspace-5.6.4/krunner/view.cpp:299
#8  0x00407b99 in View::screenGeometryChanged
(this=this@entry=0x7ffea73092b0) at
/build/plasma-workspace-LFQsCW/plasma-workspace-5.6.4/krunner/view.cpp:272
#9  0x00407cb2 in View::::operator()
(screen=0x3b99310, __closure=) at
/build/plasma-workspace-LFQsCW/plasma-workspace-5.6.4/krunner/view.cpp:114
#10 QtPrivate::FunctorCall,
QtPrivate::List, void, View::View(QWindow*)::
>::call (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#11 QtPrivate::Functor,
1>::call, void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#12 QtPrivate::QFunctorSlotObject, 1,
QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *,
QObject *, void **, bool *) (which=, this_=,
r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:192
#13 0x7fddf3a6fe4f in QtPrivate::QSlotObjectBase::call (a=0x7ffea73089f0,
r=0x7ffea73092b0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#14 QMetaObject::activate (sender=0x7ffea7309240, signalOffset=,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffea73089f0)
at kernel/qobject.cpp:3698
#15 0x7fddf3a707d7 in QMetaObject::activate (sender=,
m=m@entry=0x7fddf41c4460 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffea73089f0)
at kernel/qobject.cpp:3578
#16 0x7fddf3d79422 in QGuiApplication::screenAdded (this=,
_t1=0x3b99310) at .moc/moc_qguiapplication.cpp:341
#17 0x7fddf3d6f680 in QPlatformIntegration::screenAdded (this=, ps=, isPrimary=) at
kernel/qplatformintegration.cpp:459
#18 0x7fdde45239ce in QXcbConnection::createScreen
(this=this@entry=0x1b09550, virtualDesktop=virtualDesktop@entry=0x1b17840,
outputChange=..., outputInfo=outputInfo@entry=0x7fdddc005200) at
qxcbconnection.cpp:324
#19 0x7fdde4524b58 in QXcbConnection::updateScreens
(this=this@entry=0x1b09550, event=event@entry=0x2009920) at
qxcbconnection.cpp:236
#20 0x7fdde45259f3 in QXcbConnection::handleXcbEvent
(this=this@entry=0x1b09550, event=event@entry=0x2009920) at
qxcbconnection.cpp:1160
#21 0x7fdde4525e53 in QXcbConnection::processXcbEvents (this=0x1b09550) at
qxcbconnection.cpp:1532
#22 0x7fddf3a70ea1 

[Breeze] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #22 from Franco Pellegrini  ---
Why is this marked as fixed? did you commit the icons from your comment #17 ?
(I cannot see them from the commits.kde.org link) If so, as Kai points out,
they are clearly not intuitive icons for knowing if a device is mounted or
not... They are confusing

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #16 from Franco Pellegrini  ---
No problem, we are all trying to make this software better :)

Just to be clear... the notification is valid and it shows up when you try to
mount an encrypted drive and you provide a wrong password...

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #13 from Franco Pellegrini  ---
What do you mean with "stupid notification" ? it's the regular "Device
notifier" that pops up when you plug in a new USB drive, etc...

I'm on Kubuntu 16.04, using Plasma 5.5.5  and QT 5.5.1

HTH

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #11 from Franco Pellegrini  ---
In my Personal opinion, it is better but still not 100% intuitive... This are
my thoughts:

- The orange icon means "unmount", not "unmounted"
- I notice that the green icon is a plug, after being told it was a plug...
maybe remove the connection between the pins?

What about doing something like:

- An icon like this
https://upload.wikimedia.org/wikipedia/commons/thumb/5/59/Plug-in_Noun_project_4032.svg/2000px-Plug-in_Noun_project_4032.svg.png
for when the device is not mounted

- The same icon but "plugged", when the device has been mounted successfully

- Just the male part of that for the "mount" action (Like the green one from
your attachment, but without the union between the pins)

- An icon like the orange one in your attachment for "unmount" action


Just my 2 cents...

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

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #60 from Franco Pellegrini  ---
Also, to confirm, going to EGL in favor of GLX, does not seem to help at all
for me... I have to Alt+Shift+F12 to disable effects in order to restore
drawing

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

[Oxygen] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

Franco Pellegrini  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|LATER   |---

--- Comment #6 from Franco Pellegrini  ---
You are correct, this is Breeze, not Oxygen.

Attaching new screenshot and reassigning after I post this comment.

I'm talking about the Icon that shows up in the notification... Unless you stop
and read "Could not mount" is not obvious that it failed... Maybe it should
show a big red X or something that makes it very clear that whatever you were
trying to do, it failed... (btw, this is the very same icon that is used in
oxygen)

As a side note, from the device notifier menu, having that green icon is not
very intuitive that it means "just mount the unit"...

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #7 from Franco Pellegrini  ---
Created attachment 96994
  --> https://bugs.kde.org/attachment.cgi?id=96994=edit
Device Notifier and Error notification

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

[Breeze] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

Franco Pellegrini  changed:

   What|Removed |Added

  Component|icons   |Icons
 CC||kain...@gmail.com
Product|Oxygen  |Breeze

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

[Oxygen] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #2 from Franco Pellegrini  ---
Created attachment 96984
  --> https://bugs.kde.org/attachment.cgi?id=96984=edit
Device notifier

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

[Oxygen] [Bug 358925] New: Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 358925
   Summary: Icon for mount error is missleading
   Product: Oxygen
   Version: 5.5.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: icons
  Assignee: n...@oxygen-icons.org
  Reporter: frap...@gmail.com

When entering a wrong password for a LUKS partition in an external link, you
get an icon that looks as if the partition was mounted or everything went fine,
when it was not the case.

Also the icon from the device notifier is unrelated with the action "mount".

Attaching screenshots

Reproducible: Always

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

[Oxygen] [Bug 358925] Icon for mount error is missleading

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #1 from Franco Pellegrini  ---
Created attachment 96983
  --> https://bugs.kde.org/attachment.cgi?id=96983=edit
Error on mount

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

[kontact] [Bug 358920] New: Kontact crashed when opening an entry from akregator

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 358920
   Summary: Kontact crashed when opening an entry from akregator
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: frap...@gmail.com

Application: kontact (5.0.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-27-generic x86_64
Distribution: Ubuntu 15.10

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

Was checking the RSS feed, and when I clicked an entry, the whole application
crashed

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

Thread 7 (Thread 0x7f0e073e9700 (LWP 23869)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e29dfcfeb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f0e29dfd029 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f0e255566aa in start_thread (arg=0x7f0e073e9700) at
pthread_create.c:333
#4  0x7f0e2acd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f0dc3f8c700 (LWP 23870)):
#0  0x7f0e2ace38dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0e248d91ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0e248d92fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0e2b82850b in QEventDispatcherGlib::processEvents
(this=0x7f0dbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f0e2b7cf50a in QEventLoop::exec (this=this@entry=0x7f0dc3f8bd40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f0e2b5ebac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f0e2b5f0a6e in QThreadPrivate::start (arg=0x1fb7300) at
thread/qthread_unix.cpp:331
#7  0x7f0e255566aa in start_thread (arg=0x7f0dc3f8c700) at
pthread_create.c:333
#8  0x7f0e2acd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f0dc256e700 (LWP 23871)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e29b0b0d4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f0e29e2cea1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f0e255566aa in start_thread (arg=0x7f0dc256e700) at
pthread_create.c:333
#4  0x7f0e2acd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f0dc1d4e700 (LWP 23872)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e29b0c103 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f0e29e2cea1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f0e255566aa in start_thread (arg=0x7f0dc1d4e700) at
pthread_create.c:333
#4  0x7f0e2acd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f0dc154d700 (LWP 23873)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e29b0c103 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f0e29e2cea1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f0e255566aa in start_thread (arg=0x7f0dc154d700) at
pthread_create.c:333
#4  0x7f0e2acd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f0dc0d4c700 (LWP 23874)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e29b0c103 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f0e29e2cea1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f0e255566aa in start_thread (arg=0x7f0dc0d4c700) at
pthread_create.c:333
#4  0x7f0e2acd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0e0f59b880 (LWP 23867)):
[KCrash Handler]
#6  0x7f0da7cd2200 in qt_meta_stringdata_MessageList__Core__SortOrder ()
from /usr/lib/x86_64-linux-gnu/libmessagelist.so.5
#7  0x7f0e0ef91684 in QXcbWindow::mapToNative (this=,
rect=..., screen=0x1e88600) at qxcbwindow.cpp:197
#8  0x7f0e0ef980b3 in QXcbWindow::setGeometry (this=0x1f89ab0, rect=...) at
qxcbwindow.cpp:718
#9  0x7f0e2c0fd062 in QWidgetPrivate::show_sys (this=this@entry=0x1f57910)
at kernel/qwidget.cpp:7886
#10 0x7f0e2c10650e in QWidgetPrivate::show_helper
(this=this@entry=0x1f57910) at kernel/qwidget.cpp:7824
#11 0x7f0e2c109085 in QWidget::setVisible (this=0x1f4d930,
visible=) at kernel/qwidget.cpp:8108
#12 

[krunner] [Bug 344328] krunner is not visible when using multiple monitors

[Franco Pellegrini via KDE Bugzilla]

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

Franco Pellegrini  changed:

   What|Removed |Added

 CC||frap...@gmail.com

--- Comment #16 from Franco Pellegrini  ---
Same problem here Kubuntu 15.10 KDE 5.4.3

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

[korganizer] [Bug 358249] Remote ICS file does not populate calendar

[Franco Pellegrini via KDE Bugzilla]

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

--- Comment #1 from Franco Pellegrini  ---
Sorry, I'm using Kubuntu 15.10 and the actual KOrganizer version is 15.08.3

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

[korganizer] [Bug 358249] New: Remote ICS file does not populate calendar

[Franco Pellegrini via KDE Bugzilla]

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

Bug ID: 358249
   Summary: Remote ICS file does not populate calendar
   Product: korganizer
   Version: 15.08.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: frap...@gmail.com

I have a remote ics file from the Office 365 Calendar. I go to KOrganizer,
right click in the calendars list, "Add Calendar" -> "ICal Calendar File".
Then, in "Filename" I enter the complete public URL for my calendar. The
"Enable file monitoring" is blurred out, so it does recognize it is a remote
resource.
Click "Ok".

None of the events are added to the calendar...

I then go to a terminal, wget the same URL, and then go and add the
calendar.ics file that was downloaded.

All of the expected events are now visible in the calendar view.

Reproducible: Always

Steps to Reproduce:
1. Add remote ics file

Actual Results:  
No events show up in the calendar view

Expected Results:  
My events to show up in the calendar view

It does work with the same ics file if it was previously downloaded

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

[kdelibs] [Bug 355011] Plasma Add-On Installer cannot update widgets after restart

[Franco Pellegrini via KDE Bugzilla]

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

Franco Pellegrini  changed:

   What|Removed |Added

 CC||frap...@gmail.com

--- Comment #3 from Franco Pellegrini  ---
I confirm this problem as well... After I install a widget, if I come back
right away, I see the "Uninstall", however if I restart and come back again, I
cannot "Uninstall" a previously installed widget.

Kubuntu 15.10

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