[kscreenlocker] [Bug 360396] kscreenlocker-greet ignores KB and Mouse after screen energy saving activates

[Nils via KDE Bugzilla]

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

Nils  changed:

   What|Removed |Added

 CC||nils.acrim...@gmail.com

--- Comment #26 from Nils  ---
I also have this issue with plasma-desktop 5.7.3-1 on archlinux and
extra/xf86-video-intel 1:2.99.917+688+g49daf5d-1 driver, same than Nick
Shaforostoff.

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

[plasma4] [Bug 309214] Bouncing icon on mouse cursor occasionally remains stuck on after the application has launched

[Nils via KDE Bugzilla]

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

Nils  changed:

   What|Removed |Added

 CC||nils.acrim...@gmail.com

--- Comment #16 from Nils  ---
I can confirm this issue. Easy for me to reproduce, I just have to click on an
email link (in order to send an email) in Firefox while no email client has
been configured. It then try to launch an application but it just does not know
which application it has to launch, so it stay with the busy icon forever.

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

[krunner] [Bug 360505] When starting docker krunner crash

[Nils via KDE Bugzilla]

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

--- Comment #1 from Nils  ---
Created attachment 97884
  --> https://bugs.kde.org/attachment.cgi?id=97884=edit
journalctl of krunner crash

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

[krunner] [Bug 360505] New: When starting docker krunner crash

[Nils via KDE Bugzilla]

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

Bug ID: 360505
   Summary: When starting docker krunner crash
   Product: krunner
   Version: 5.5.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: windows
  Assignee: m...@vhanda.in
  Reporter: nils.acrim...@gmail.com

Created attachment 97883
  --> https://bugs.kde.org/attachment.cgi?id=97883=edit
krunner crash following starting docker

Almost every times I launch docker through "sudo systemctl start docker",
krunner is crashing. 
I have not a lot of data available. I am sending them through attached files.

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

[plasmashell] [Bug 351852] Media player plasmoid does not pilot Spotify client

[Nils via KDE Bugzilla]

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

--- Comment #10 from Nils  ---
You can talk about it here:
https://community.spotify.com/t5/Help-Desktop-Linux-Windows-Web/Linux-Spotify-client-1-x-now-in-stable/td-p/1300404/page/4

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #17 from Nils  ---
Wow, thank you very much! I was afraid to see this bug never solved as it seem
that no one was facing it/able to reproduce it. 
It is the second bug I have reported fixed this week, great job to you. :)

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Nils via KDE Bugzilla]

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

--- Comment #45 from Nils  ---
I am using Nvidia driver, and it says here:
https://bbs.archlinux.org/viewtopic.php?id=198656 that "Nvidia uses their own
implementation of OpenGL, thus DRI3 from Mesa libs has no influence." so I am a
bit puzzled. 
Furthermore, I have no other theme suggested in SDDM graphical user interface
than Breeze. 

Otherwise, has someone reported the issue in xorg? It would be nice to
reference the xorg issue on this ticket.

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #9 from Nils  ---
Well, I tried again with the last updates:
[2016-01-22 15:36] [ALPM] upgraded linux (4.3.3-2 -> 4.3.3-3)
[2016-01-22 15:36] [ALPM] upgraded plasma-framework (5.18.0-1 -> 5.18.0-3)
[2016-01-27 13:51] [ALPM] upgraded kde-cli-tools (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kde-gtk-config (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kdecoration (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded breeze (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded libksysguard (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded libkscreen (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded plasma-workspace (5.5.3-2 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kdeplasma-addons (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kinfocenter (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kmenuedit (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kscreen (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded ksshaskpass (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded ksysguard (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded kwrited (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded plasma-desktop (5.5.3-2 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded plasma-nm (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded plasma-pa (5.5.3-1 -> 5.5.4-1)
[2016-01-27 13:51] [ALPM] upgraded plasma-workspace-wallpapers (5.5.3-1 ->
5.5.4-1)

And I am still facing the issue, below the automated crash error reporter logs:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb8fffe2800 (LWP 1862))]

Thread 14 (Thread 0x7fb8e882c700 (LWP 1879)):
#0  0x7fb8fa61416d in read () from /usr/lib/libc.so.6
#1  0x7fb8f75d5270 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb8f7591aa4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb8f7591f60 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7fb8f75920cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7fb8faf3b56b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7fb8faee257a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7fb8facfebe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7fb8fd617055 in ?? () from /usr/lib/libQt5Qml.so.5
#9  0x7fb8fad03b8e in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7fb8f9e204a4 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7fb8fa62113d in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7fb8e0f7b700 (LWP 1884)):
#0  0x7fb8f75d6614 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7fb8f7591e6d in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb8f75920cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb8faf3b56b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fb8faee257a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fb8facfebe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fb8fd617055 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fb8fad03b8e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fb8f9e204a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb8fa62113d in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7fb8da495700 (LWP 1893)):
#0  0x7fb8f75d65f9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7fb8f7591b46 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#2  0x7fb8f7592020 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fb8f75920cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fb8faf3b56b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fb8faee257a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fb8facfebe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fb8fd617055 in ?? () from /usr/lib/libQt5Qml.so.5
#8  0x7fb8fad03b8e in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7fb8f9e204a4 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fb8fa62113d in clone () from /usr/lib/libc.so.6

Thread 11 (Thread 0x7fb8d8b7f700 (LWP 1902)):
#0  0x7fb8f9e2607f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb8ffa3f934 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7fb8ffa3f979 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7fb8f9e204a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fb8fa62113d in clone () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7fb8d2161700 (LWP 1905)):
#0  0x7fb8f75d65f9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7fb8f7591b46 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#2  0x7fb8f7592020 in ?? () from 

[user-manager] [Bug 346215] Cannot remove user account picture

[Nils via KDE Bugzilla]

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

--- Comment #7 from Nils  ---
Hu... Sorry, I didn't see your answer at that time. 
So, I have installed accountsservice:

➜  ~  sudo pacman -S accountsservice 
warning: accountsservice-0.6.40-1 is up to date -- reinstalling
Packages (1) accountsservice-0.6.40-1
Total Installed Size:  0.84 MiB
Net Upgrade Size:  0.00 MiB
(1/1) reinstalling accountsservice 
[##] 100%

But still no user account & password app in the settings.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Nils via KDE Bugzilla]

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

--- Comment #42 from Nils  ---
I am also facing the issue with my system which is an updated archlinux
distribution. 
I would like an explanation about the bug status which is:  RESOLVED UPSTREAM
I am not sure to understand this status, does it mean that a fix has been
found? Or that the fix will not be found because the bug does not come from the
KDE environment but from Qt because from what I understand, it seems to be a Qt
issue.

But then, do we have any idea when will it be resolved? Is the only available
solution is to downgrade qt5-base from 5.5.1.9 to 5.5.1.8?

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #10 from Nils  ---
PS: While unlocking through this way, the panel disappears from my desktop
environment, while it was configured for the user (which, like I said, has a
password configured & required in order to login).

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Nils via KDE Bugzilla]

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

Nils  changed:

   What|Removed |Added

 CC||nils.acrim...@gmail.com

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #5 from Nils  ---
Created attachment 96755
  --> https://bugs.kde.org/attachment.cgi?id=96755=edit
Hacking KDE session locker by closing the lid several times

So here the full log about my successful KDE hacking by closing the lid. :)

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #6 from Nils  ---
@David Edmundson, 

So I have tested it again on my updated computer and it has not been long
before I have been successfully logged in as root on my computer without typing
any password by just closing the lid several times. 
The people outside looked me like I was crazy. :D

Cheers,

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #8 from Nils  ---
Yes for all the users.

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #2 from Nils  ---
The time indicated is 5 secondes. I have been thinking that first, but when I
try to wiggle the mouse, it does not unlock. Furthermore, the time during which
I do nothing is greater than 5 minutes & 5 secondes (I have not updated these
settings).

It is only by closing the lid that I can unlock my session. 

Another thing really strange (but not sure whether related). When opening for
the first time my session (following a reboot), I need to type several time my
password (rightly). Each time it makes all the SDDM disappears and reboot it.
Until... somehow... it finish by opening my session. 
When I type the bad password it is flag as bad... but when right typed, it just
seems to crash. 

You will find some errors logs on the attached file.

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #3 from Nils  ---
Created attachment 96706
  --> https://bugs.kde.org/attachment.cgi?id=96706=edit
errors when logging for the first time

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

[plasmashell] [Bug 358125] New: the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

Bug ID: 358125
   Summary: the lock-up can be pass through without typing
password
   Product: plasmashell
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: nils.acrim...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

When I let my computer idle for some time, it automatically lock-up, and it
used to be then impossible to use  my computer without knowing my password.

However, I have found a trick which allow me to open the session without typing
any password. 
With my laptop, I first connect my HDMI output to a second screen, then I am
waiting for the idle lock-up to occurs. When it is really locked (not
immediately after the lock-up appears but something like one minute after) I
just have to close the lid and my session is instantaneously reopen without
typing anything.
Also, the panel disappear in the operation.  

Reproducible: Always

Steps to Reproduce:
1. Use a laptop
2. Use a second screen through HDMI
3. Wait for an automatically closed session
4. Then close the lid

Actual Results:  
The session is unlocked

Expected Results:  
The session should still be locked

I am not sure which severity I should choose, and I don't know whether it is
reproducible on another computer. However it seems really serious and not much
reassuring.

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