| Summary: | Connecting to Wifi takes a long time and there are multiple other issues with likely the same root cause | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Lucia Mrenica <lucia.mrenica> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | gudvinr+kde, kde, lucia.mrenica, nate, nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Lucia Mrenica
2023-04-30 12:14:15 UTC
Switching my wifi from "stored for this user (encrypted)" to "stored for everyone (unencrypted)" fixes the issue with wifi taking a long time to connect but not the other issues (meaning apps still can't be started for a while after the session starts). Also I tried disabling kwallet entirely but that doesn't make a difference. Can you run: qdbus org.kde.kded5 /org/kde/plasmanetworkmanagement and confirm if you get a list of methods and signals out immediately, or an error /delay Sounds like it could be https://bugs.kde.org/show_bug.cgi?id=458085 (In reply to David Edmundson from comment #2) > Can you run: > > qdbus org.kde.kded5 /org/kde/plasmanetworkmanagement > > and confirm if you get a list of methods and signals out immediately, or an > error /delay Even if I am already connected (from a previous log in) I get this (not imediatelly but after some time): Error: org.freedesktop.DBus.Error.NoReply Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. After a while when everything is working already I get: method void org.kde.plasmanetworkmanagement.addBluetoothConnection(QString bdAddr, QString service, QString connectionName) method bool org.kde.plasmanetworkmanagement.bluetoothConnectionExists(QString bdAddr, QString service) method void org.kde.plasmanetworkmanagement.unlockModem(QString modem) signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString interface_name, QVariantMap changed_properties, QStringList invalidated_properties) method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name) method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString interface_name) method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value) method QString org.freedesktop.DBus.Introspectable.Introspect() method QString org.freedesktop.DBus.Peer.GetMachineId() method void org.freedesktop.DBus.Peer.Ping() (In reply to Nicolas Fella from comment #3) > Sounds like it could be https://bugs.kde.org/show_bug.cgi?id=458085 But If I disabled kwallet entirely this issue would disappear which is not the case, right? Both my systems have this issue but no one else? What info should I provide to help fix this issue? I also have this issue. After desktop shell loads, there's noticeable delay until autostart apps launched and wireless connection is waiting for authentication in that period too. It was not an issue before, although I can't say exactly when it started to happen. Another thing I noticed is that proton mail fails due to inability to connect to secret service (it checks for existence of dbus service I believe). That and wifi authentication issues makes me think that something funny going on with kwallet. Another thing I noticed is that component responsible for screen handling is delayed too. It is very noticeable because I have screen rotated 90° and it takes a while for it to rotate to correct position. *** This bug has been marked as a duplicate of bug 458085 *** |