[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)

2020-02-13 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=416358

Theresa  changed:

   What|Removed |Added

 CC||rockprinz...@gmail.com

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-05-14 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

--- Comment #18 from Theresa <rockprinz...@gmail.com> ---
I can confirm that the problem is fixed with Android 7.x
Alas my phone (Oneplus One) only has Android 6.
Is there any chance of fixing this also for Android 6 devices?

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-04-23 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

--- Comment #16 from Theresa <rockprinz...@gmail.com> ---
@Albert/Matt: any idea what's causing my connection drops?!

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-04-19 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #12 from Theresa <rockprinz...@gmail.com> ---
Hi Jan,

it seems KWalletManager5 is able to store the passwords, if I click on "Show
values" the password is stored there. That's the way it should work, right?

If I click on the "Applications" tab in KWalletManager5 then it lists the
following applications that are authorized to access the wallet:

*) Kwalletmanager5
*) ksshaskpass
*) Google Chrome
*) kded5

so it seems kded5 (plasma-nm) should be able to access the wallet.

The only workaround that works at the moment is "kill all kded5 processes" and
then start kded5 by running /usr/bin/kded5

I've found this error in the debug mode:

plasma-nm: Unhandled active connection state change:  1
plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const
NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&,
uint)
plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/1"
plasma-nm: Setting name: "802-11-wireless-security"
plasma-nm: Hints: ()
plasma-nm: Flags: 1
Pass a valid window to KWallet::Wallet::openWallet().
plasma-nm: bool SecretAgent::processGetSecrets(SecretsRequest&) const Waiting
for the wallet to open

Is this worrying?

cheers,
theresa

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-04-19 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #11 from Theresa <rockprinz...@gmail.com> ---
Created attachment 105103
  --> https://bugs.kde.org/attachment.cgi?id=105103=edit
KWalletManager5

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-04-16 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

--- Comment #15 from Theresa <rockprinz...@gmail.com> ---
Also, I forgot to mention which versions I'm running.

On Ubuntu: 1.0.3
On Android: 1.6.2 Beta 2 (but it appeared in previous versions as well, just
thought the beta might fix the problem)

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-04-16 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

--- Comment #14 from Theresa <rockprinz...@gmail.com> ---
Created attachment 105051
  --> https://bugs.kde.org/attachment.cgi?id=105051=edit
Device paired momentarily

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-04-16 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

--- Comment #13 from Theresa <rockprinz...@gmail.com> ---
Created attachment 105050
  --> https://bugs.kde.org/attachment.cgi?id=105050=edit
Discovery of one device after hitting refresh

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-04-16 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

--- Comment #12 from Theresa <rockprinz...@gmail.com> ---
Created attachment 105049
  --> https://bugs.kde.org/attachment.cgi?id=105049=edit
Empty devices list

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

2017-04-16 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=368438

Theresa <rockprinz...@gmail.com> changed:

   What|Removed |Added

 CC||rockprinz...@gmail.com

--- Comment #11 from Theresa <rockprinz...@gmail.com> ---
Hi,

I can confirm this I *think* I have the same problem. I'm pairing my phone
with my computer, for the time I'm actively using my phone (e.g remote control
with the touchpad on my android phone), it works.
After a couple of minutes (sometimes even seconds) it loses the connection and
then says "Device not paired. Request pairing."
The list of connected devices is empty, unless I click the refresh button (on
my laptop).
This is odd, because kdeconnect used to work perfectly fine on my setup.

I'm using Ubuntu 16.04.2 LTS (KDEConnect: 
and
Android 6.0.1

Are there any logs that I could provide that would help identify the issue?

Please, find attached my screenshots that prove it's actually working.
It seeems the pairing between the devices is not persistent.

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-04-14 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #9 from Theresa <rockprinz...@gmail.com> ---
Hi Jan,

please find attached the request debug.
The first output is from enabling the debugging and re-starting kded5 again.
It automatically restarted the network manager and tried to re-connect to the
wifi, but failed. (hopefully you can see something).

The second output is from me killing all kded5 processes and re-starting kded5.
Interestingly this time it asked me if I allowed KWallet-Manager to allow to
save the passwords, and afterwards it asked for the Wi-Fi password. Exactly the
way I wanted it to be, and then it worked, yay!!

However, I then rebooted my machine to see if it was boot-persistent and then
it didn't work again anymore, until I killed all kded5 processes and restarted
it. (It didn't ask for KWallet or Wifi password) but it still worked, I'm now
connected to the wifi.

This is odd, seems like it wouldn't start properly after starting a Plasma
session, right?
Hopefully, you can see something from the debug log...

Jan, thanks for all your help so far :)

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-04-14 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #8 from Theresa <rockprinz...@gmail.com> ---
Created attachment 105026
  --> https://bugs.kde.org/attachment.cgi?id=105026=edit
kded5 debug

Hi Jan,

please find attached the request debug.
The first output is from enabling the debugging and re-starting kded5 again.
It automatically restarted the network manager and tried to re-connect to the
wifi, but failed. (hopefully you can see something).

The second output is from me killing all kded5 processes and re-starting kded5.
Interestingly this time it asked me if I allowed KWallet-Manager to allow to
save the passwords, and afterwards it asked for the Wi-Fi password. Exactly the
way I wanted it to be, and then it worked, yay!!

However, I then rebooted my machine to see if it was boot-persistent and then
it didn't work again anymore, until I killed all kded5 processes and restarted
it. (It didn't ask for KWallet or Wifi password) but it still worked, I'm now
connected to the wifi.

This is odd, seems like it wouldn't start properly after starting a Plasma
session, right?
Hopefully, you can see something from the debug log...

Jan, thanks for all your help so far :)

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-04-12 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #6 from Theresa <rockprinz...@gmail.com> ---
Hi Jan,

unfortunately this is not the case as Kwallet is running:

tm1913 1  0 21:27 ?00:00:00 /usr/bin/kwalletd5
tm2253 1  0 21:27 ?00:00:00 /usr/bin/kwalletd5 --pam-login
15 18
tm2463  2355  0 21:27 ?00:00:00 /usr/bin/kwalletmanager5
-session 10e065726500014888287600034130029_1492025218_888983

Also, I was asked by KWallet if I wanted to allow the access from
NetworkManager

However, doing a tail on /var/log/syslog shows the following
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5414] device
(wlp58s0): No agents were available for this request.
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5415] device
(wlp58s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5420] device
(wlp58s0): Activation: failed for connection 'Wifi'
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5426] device
(wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 12 21:29:44 herex kernel: [  137.607891] IPv6: ADDRCONF(NETDEV_UP):
wlp58s0: link is not ready
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7890] device
(wlp58s0): Activation: starting connection 'Wifi'
(79a71c8c-a898-4012-b631-7f14d00bc068)
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7891] audit:
op="connection-activate" uuid="79a71c8c-a898-4012-b631-7f14d00bc068"
name="Wifi" pid=2410 uid=1001 result="success"
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7892] device
(wlp58s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7896] device
(wlp58s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7898] device
(wlp58s0): Activation: (wifi) access point 'Wifi' has security, but secrets are
required.
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7898] device
(wlp58s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8085] device
(wlp58s0): No agents were available for this request.
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8085] device
(wlp58s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8089] device
(wlp58s0): Activation: failed for connection 'Wifi'
Apr 12 21:31:55 herex kernel: [  268.880993] IPv6: ADDRCONF(NETDEV_UP):
wlp58s0: link is not ready
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8095] device
(wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0]

plasma-nm keeps saying "Waiting for authorization".

Unencrypted passwords workbut what's the point, right?

Is there any other way how we could troubleshoot this?

cheers,
theresa

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-03-17 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #4 from Theresa <rockprinz...@gmail.com> ---
Hi Jan,

any advice on how to fix this?

Best,
theresa

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-03-14 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #2 from Theresa <rockprinz...@gmail.com> ---
Created attachment 104568
  --> https://bugs.kde.org/attachment.cgi?id=104568=edit
plasma-network-manager debug

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

2017-03-14 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

--- Comment #3 from Theresa <rockprinz...@gmail.com> ---
Hi Jan,

yes it definitely seems so:

systemctl status kded5
● kded5.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

should this be the service that you were talking about?

how would I start it? it doesn't seem to load through 
systemctl start kded5

please find attached other information that was requested from the link you've
provided.

best,
theresa

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

[plasma-nm] [Bug 377473] New: Plasma-nm doesn't store connection passwords encrypted anymore

2017-03-10 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=377473

Bug ID: 377473
   Summary: Plasma-nm doesn't store connection passwords encrypted
anymore
   Product: plasma-nm
   Version: 5.8.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: editor
  Assignee: jgrul...@redhat.com
  Reporter: rockprinz...@gmail.com
  Target Milestone: ---

Hi,

I'm currently running kubuntu 16.04.2 with plasma-nm
(4:5.8.5-0ubuntu1~ubuntu16.04~ppa1) and it seems I can no longer store
passwords (WiFi and VPN) in my connect-manager

the only workaround that solves the problem is when I go into Wi-Fi security
and select "Store password and make it available for all users (unencrypted)".
The same thing goes for credentials (password) for VPN connections.

If encrypted it says "Waiting for authorization" until it gives in and says "No
secrets were provided". When I then go into the connection editor there are
really no credentials/password stored. It's empty, although it was there before
I tried to connect.

Syslog says:
Mar 10 20:56:49 herex NetworkManager[970]:   [1489175809.8764] device
(wlp58s0): No agents were available for this request.
Mar 10 20:56:49 herex NetworkManager[970]:   [1489175809.8764] device
(wlp58s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Mar 10 20:56:49 herex NetworkManager[970]:   [1489175809.8768] device
(wlp58s0): Activation: failed for connection 'we_can_hear_you_FUCK'
Mar 10 20:56:49 herex NetworkManager[970]:   [1489175809.8801] device
(wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 10 20:56:49 herex kernel: [ 1492.145831] IPv6: ADDRCONF(NETDEV_UP):
wlp58s0: link is not ready

Is there anything else I could check? Why it's no longer working in the
encrypted mode? I feel rather uneasy now :(

cheers,
theresa

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

[KScreen] [Bug 372225] black screen when booting with external monitors

2016-11-08 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=372225

Theresa <rockprinz...@gmail.com> changed:

   What|Removed |Added

 CC||rockprinz...@gmail.com

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

[KScreen] [Bug 372225] New: black screen when booting with external monitors

2016-11-08 Thread Theresa
https://bugs.kde.org/show_bug.cgi?id=372225

Bug ID: 372225
   Summary: black screen when booting with external monitors
   Product: KScreen
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: rockprinz...@gmail.com
  Target Milestone: ---

Whenever I boot with my external monitors plugged into my laptop (no docking
station in between) I get a black screen. No login-manager, just a black
screen.

Workaround:
Unplug the cables of the monitors in my laptop and boot just the laptop. I
automatically see the login manager and can log into my system. As soon as I'm
logged in, I can plug the cables in again.

What I also noticed since a few days I can no longer see files on my desktop
(folders view) instead I see only the "Desktop" view...

I'm happy to provide any logs or configs that would help resolve the problem.

thank you very much in advance!
cheers
theresa

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2016-03-22 Thread Theresa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356225

Theresa <rockprinz...@gmail.com> changed:

   What|Removed |Added

 CC||rockprinz...@gmail.com

--- Comment #53 from Theresa <rockprinz...@gmail.com> ---
I am affected by this bug as well.
Although my problem seems to be a bit different.

I have my laptop connected to a HDMI monitor as well, as soon as I press the
"power off" button when I take a break/lunch break... the panel/taskbar
disappears. If I'm lucky to panel is moved to the VGA monitor which I sometimes
also connect. If the VGA monitor is disconnected then the panel is completely
gone, until I log out/reboot.
This definitely doesn't seem like normal behaviour to me, when I just power-off
the monitor (I am not even unplugging the cable).

Is there a workaround for this problem?

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