[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #63 from jackdinn --- (In reply to Donovan Hoare from comment #62) > Created attachment 102252 [details] > attachment-4199-0.html > > The bug ha been there for years now, with no one fixing it. > I would advise you stop hassling yourself and just switch to another > email client > > Im using thunderbird, even though i prefer kontact. > After some tweeks it works rather well. > > Donovan Hoare Id love to but http://www.linuxquestions.org/questions/linux-software-2/cant-find-an-email-client-that-works-4175593341/ Its more like stop trying to use KDE by the looks of it. Thx -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #67 from jackdinn --- some info regarding progress with kmail/kontacts here https://ubuntuforums.org/showthread.php?t=2341803&p=13564260#post13564260 so might be some movement going on. Ignore this if its already in the backport, i dont know how to check that really without switching it on. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #114 from jackdinn --- I have the same issue. I have read the thread, but the link for the apk is outdated and no longer available. I am desperate to fix this, but I am not an expert. It is marked as resolved/fixed HOW? PLEASE. KDE Connect works well, except for when I click on "SMS messages". The GUI opens, but the message history never appears, and the window just hangs with a spinning logo. Device Information: Manjaro KDE HUAWEI P30 lite Please advise. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #20 from jackdinn --- I was just wondering if this might be the cause of my loss of Umount icon for all my network mounts? I do need them. https://forum.manjaro.org/t/where-did-the-mount-unmount-icons-on-dolphin-go/115426 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #26 from jackdinn --- (In reply to Norbert from comment #25) > Additionally on my system the icon is not shown but I can click it, and it > asks for password. > > KDE Plasma Version: 5.25.2 > KDE Frameworks Version: 5.95.0 > Qt Version: 5.15.5 Yes, and the tooltip is also still there if you hover in the area where the button/icon used to be. (well is on my KDE Dolphin). So the umount button is actually still there, it's just hidden?? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 472160] New: Whole x11 display freezes when open/close (only when 100% width/height)
https://bugs.kde.org/show_bug.cgi?id=472160 Bug ID: 472160 Summary: Whole x11 display freezes when open/close (only when 100% width/height) Classification: Applications Product: yakuake Version: 23.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: j...@jackdinn.co.uk Target Milestone: --- SUMMARY *** Everything seems to freeze for roughly 10 to 60 seconds before continuing as normal. I believe it is just the x11 display that is frozen because i can still hear notifications etc happening in the background. It happens when the Yakuake window is at 100% width. When you open or close (with F12). It also happens when you try to adjust the window size slider in the Yakuake configurations. It has only just started doing this after the full system update for Manjaro yesterday. I have tried rolling back Yakuake to the previous version but it had no effect on this bug, it was still doing it. STEPS TO REPRODUCE 1. Set window to 100% wide. 2. Set window to 100% height. 3. Open/close window via hotkey (F12). It does not freeze every time you open/close the window, but id say about 80% of the time it does freeze. 4. It will also freeze when sliding the window width slider in the Yakuake configurations. OBSERVED RESULT Everything seems to freeze for roughly 10 to 60 seconds before continuing as normal. EXPECTED RESULT SOFTWARE/OS VERSIONS System: Host: greg-inspiron5767 Kernel: 5.15.120-1-MANJARO arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.6 Distro: Manjaro Linux Machine: Type: Laptop System: Dell product: Inspiron 5767 v: N/A serial: Mobo: Dell model: 03XWWJ v: A00 serial: UEFI-[Legacy]: Dell v: 1.5.0 date: 06/11/2021 Battery: ID-1: BAT0 charge: 42.0 Wh (100.0%) condition: 42.0/42.0 Wh (100.0%) CPU: Info: dual core Intel Core i5-7200U [MT MCP] speed (MHz): avg: 3100 min/max: 400/3100 Graphics: Device-1: Intel HD Graphics 620 driver: i915 v: kernel Device-2: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2 driver: X: loaded: modesetting dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.0.4 renderer: Mesa Intel HD Graphics 620 (KBL GT2) Network: Device-1: Intel Wireless 3165 driver: iwlwifi Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 Device-3: Intel Bluetooth wireless interface driver: btusb type: USB Drives: Local Storage: total: 931.51 GiB used: 183.75 GiB (19.7%) Info: Processes: 219 Uptime: 54m Memory: total: 16 GiB note: est. available: 15.45 GiB used: 3.5 GiB (22.6%) Shell: fish inxi: 3.3.28 ADDITIONAL INFORMATION The only thing that is added into journalctl during this "freeze" is the following. I do often use multiple tabs for SSH connections but i have closed all them now. I cant see this being connected to this bug but as it is the only entry that was added during the "freezes" i shall paste it here. kwin_x11[11453]: Could not get Interfaces. "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." -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 472160] Whole x11 display freezes when open/close (only when 100% width/height)
https://bugs.kde.org/show_bug.cgi?id=472160 jackdinn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from jackdinn --- Ok, after 24 hours of searching and very nearly reinstalling i found a couple of posts which i have linked below. The remedy was simple when you know. It was the ~/.config/kwinrc file that was causing the problem. It seems that after system updates it has been known to do this, causing all sorts of problems. I renamed it, rebooted, sorted out the settings that had now been set back to default, and it was all working again! Phew, that was close ^^. https://forum.manjaro.org/t/missing-menu-for-all-windows-after-stable-update/104235 https://forum.manjaro.org/t/custom-shortcuts-not-working-after-update/106934 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 171366] add bookmarks on dolphin
https://bugs.kde.org/show_bug.cgi?id=171366 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #36 from jackdinn --- Just WOW, 10 years and still no hierarchical bookmarks/favorites! A file browser with no bookmarks/favorites except a minimal, unstructured, max of about 20 before you need to scroll through reams and reams of single entries which just don't count. Maybe i can find a service or something, shall keep looking. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390890] All entries disappear from the systemtray settings after modifying an entry's hidden state
https://bugs.kde.org/show_bug.cgi?id=390890 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #25 from jackdinn --- There is a thread on the Manjaro forums regarding this bug. https://forum.manjaro.org/t/kde-tray-bug-after-using-system-tray-settings/56984 I have experienced this problem on many KDE distros (not just Manjaro) for a couple of years. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378032] Remember history of notifications like on KDE4
https://bugs.kde.org/show_bug.cgi?id=378032 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #25 from jackdinn --- +1 yes very annoying that i have regressed in this regard since installing plasma 5. But as usual when i look up why things are missing etc i find a bug thread thats years and years long without progress :( -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #70 from jackdinn --- hmm , where exactly is that option ? https://i.sli.mg/OBcKSF.png -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #72 from jackdinn --- Cheers, but did not work. I still have to write at least 1 letter in the TO field and then rub it out before it will auto fill the address from my personal address book :( Just had a large update for kmail, akonadi, pim etc etc so thought it might be fixed but unfortunately not in my case. mint 18 plasma 5.8.4 framework 5.28.0 QT 5.6.1 kernal 4.4.0-53 Kmail 5.2.3 But thx. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #73 from jackdinn --- Ops , my mistake. It had removed ALL my personal address after cache reset & reboot so i re-imported them again and seems to work now. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494804] With Qt 6.8 controls to log in or unlock screen are non-functional on some monitors when using the Breeze SDDM or Plasma theme ("TypeError: [thing] is not a function" error)
https://bugs.kde.org/show_bug.cgi?id=494804 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #89 from jackdinn --- I have tested with a brand new installation of manjaro KDE, fully up to date and blank. but it now crashes plasma even just by issuing a `xrandr` command or even a `inxi`, it also crashes plasma if i try to load pycharm. I have been tearing my hair out on this one. I cant use my computer at all without plasma crashing all the time. GTP says [quote] That long log suggests that Plasma’s display management (via KScreen) is receiving confusing or incomplete information about your monitor. In your case, X reports that the HDMI-1 output is “disconnected” but still assigns it a resolution and (more importantly) a physical size of 0 mm—which is not realistic. When KScreen tries to use that data, it ends up crashing Plasma. [/quote] Things i have tried: Reset KScreen Configuration: Renamed the folder ~/.local/share/kscreen to force Plasma to regenerate its display settings. Result: Plasma still crashed, and xrandr reported HDMI‑1 with a 0 mm × 0 mm size. Xorg Configuration Tweaks: Created /etc/X11/xorg.conf.d/10-monitor.conf to force a correct physical size, DPI, and preferred mode for HDMI‑1: Added settings like DisplaySize 344 194, Option "DPI" "96 x 96", and Option "PreferredMode" "3840x2160". Expanded the file to include a Screen section with a forced mode. Result: xrandr still showed HDMI‑1 with 0 mm dimensions, and Plasma continued to crash when display commands (like xrandr or inxi) were run. Disabling KScreen Autostart: Tried overriding KScreen’s autostart by creating a user-level autostart file (~/.config/autostart/org.kde.kscreen.desktop) with Hidden=true. Also added [Module-KScreen] autoload=false to ~/.config/kded5rc. Result: Neither method prevented KScreen from launching—Plasma still crashed. Forcing X to Ignore EDID: Updated the Xorg config to include Option "UseEDID" "false" in the Monitor section. Result: This did not change the reported 0 mm physical size, and Plasma still crashed. Additional Considerations: We also discussed switching to another desktop environment or Wayland, or downgrading Plasma/the kernel, but these were not acceptable due to personal preferences and hardware issues (e.g., trackpad non-functionality on Wayland). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crash on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #4 from jackdinn --- I have been having the same issue, but with Manjaro KDE. Reported here:- https://forum.manjaro.org/t/plasma-is-crashing-after-suspend-since-last-big-update/171347 Hopefully it can be tracked down as it looks like a very hard one to diagnose. There is nothing obvious in the journal that i can see. At least it's not too intermittent, it happens almost every suspend wake cycle (with a good while between the sleep and wake). ``` Operating System: Manjaro Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.12.1-4-MANJARO (64-bit) Graphics Platform: X11 Processors: 20 × 13th Gen Intel® Core™ i9-13900H Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Micro Computer (HK) Tech Limited Product Name: Venus Series ``` ``` ❱inxi -b System: Host: greg-venusseries Kernel: 6.12.1-4-MANJARO arch: x86_64 bits: 64 Desktop: KDE Plasma v: 6.2.4 Distro: Manjaro Linux Machine: Type: Desktop System: Micro (HK) Tech product: Venus Series v: N/A serial: Mobo: Shenzhen Meigao Equipment model: AHWSA serial: UEFI: American Megatrends LLC. v: AHWSA.1.22 date: 03/12/2024 CPU: Info: 14-core (6-mt/8-st) 13th Gen Intel Core i9-13900H [MST AMCP] speed (MHz): avg: 756 min/max: 400/5200:5400:4100 Graphics: Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X: loaded: modesetting dri: iris gpu: i915 resolution: 3840x2160~60Hz API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-arch1.1 renderer: Mesa Intel Graphics (RPL-P) Network: Device-1: Intel Ethernet I226-V driver: igc Device-2: Intel Ethernet I226-LM driver: igc Device-3: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e Drives: Local Storage: total: 1.84 TiB used: 171.85 GiB (9.1%) Info: Memory: total: 32 GiB note: est. available: 31.07 GiB used: 7.89 GiB (25.4%) Processes: 424 Uptime: 2d 18h 56m Shell: fish inxi: 3.3.36 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crash on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #7 from jackdinn --- Actually i have seen the same log errors as reported by others so i guess they may well point to the problem My journalctl at wake when plasma has crashed:- Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: XRandROutput 66 update m_connected: 0 m_crtc XRandRCrtc(0x5be7d4e726c0) CRTC: 62 MODE: 72 Connection: 1 Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: Output 66 : connected = false , enabled = true Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: XRandROutput 66 update m_connected: 1 m_crtc XRandRCrtc(0x5be7d4e726c0) CRTC: 62 MODE: 72 Connection: 1 Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: Output 66 : connected = false , enabled = true Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1 Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1 Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1 Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1 Dec 10 15:36:01 greg-venusseries joplin-desktop[299538]: [299538:1210/153601.476790:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Dec 10 15:36:01 greg-venusseries kdeconnectd[299431]: 2024-12-10T15:36:01 org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor" Dec 10 15:36:01 greg-venusseries kded6[299207]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] [Wayland] Plasmashell crash on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #12 from jackdinn --- Why changed title to [Wayland] ?, many people including me are using X11 not Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #23 from jackdinn --- Has there been any movement on this yet? I got so peeved off with it I reinstalled the OS but it still does it. So I built a script to automate watching the panel (taskbar), if it is not visible then it restarts plasma. It's a terrible resolution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #28 from jackdinn --- Updated to 6.13.0-1-MANJARO as someone had posted that it seemed to be fixed after this kernel update but unfortunately its not :( ``` Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1 Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1 Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1 Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #47 from jackdinn --- yes, iv just updated to plasmashell 6.3.4 but the bug is still there unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204
--- Comment #45 from jackdinn ---
i just made a rough and ready hackup bash script to watch the panel. Its been
working for me since this whole thing started (some time around X-mas).
```
❱cat /home/greg/bash/monitor_plasma_panel.sh
#!/bin/bash
sleep 15
# Log file path
LOG_FILE="/home/greg/bash/monitor_plasma_panel.log"
# Command to restart Plasma
RESTART_COMMAND="plasmashell --replace &"
# Panel window properties
PANEL_NAME="plasmashell"
PANEL_HEIGHT=48
# Function to log messages
log_message() {
echo "$(date '+%Y-%m-%d %H:%M:%S') - $1" >> "$LOG_FILE"
}
# Function to check the panel status
check_panel_status() {
local panel_info
panel_info=$(xwininfo -name "$PANEL_NAME" 2>/dev/null)
if [[ -z "$panel_info" ]]; then
log_message "Panel not found."
return 1
fi
# Extract the height of the panel
local current_height
current_height=$(echo "$panel_info" | awk '/Height:/ {print $2}')
if [[ -z "$current_height" ]]; then
log_message "Unable to determine panel height."
return 1
fi
if [[ "$current_height" -lt 3 ]]; then
log_message "Panel height less than 3: $current_height (expected
$PANEL_HEIGHT)."
return 2
fi
# log_message "Panel is running normally with height $current_height."
return 0
}
# Monitoring loop
while true; do
check_panel_status
status=$?
if [[ $status -ne 0 ]]; then
log_message "Panel issue detected. Restarting Plasma..."
eval "$RESTART_COMMAND"
sleep 5 # Wait for Plasma to restart
fi
# Adjust the monitoring interval as needed (in seconds)
sleep 10
done
```
However, i have disabled it atm because i got a system update today including
plasmashell 6.3.4, so we shall see how 6.3.4 goes but im not holding my breath.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #41 from jackdinn --- Its still got the same fault on plasmashell 6.3.2. No change noticeable. Still crashes plasma on resume. (Manjaro KDE) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497204] Plasmashell crashes in qDeleteAll on monitor wake
https://bugs.kde.org/show_bug.cgi?id=497204 --- Comment #35 from jackdinn --- (In reply to TraceyC from comment #34) > (In reply to netrunner1197 from comment #33) > > Seems to be fixed as of a full system update on endeavourOS as of this past > > week > > That's great news. Is anyone else still experiencing this bug on Plasma > 6.3.1? Cant say , that version of plasma is not going to be pushed until maybe next month for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504193] Default wallet can not be opened
https://bugs.kde.org/show_bug.cgi?id=504193 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #27 from jackdinn --- i think i have the same problem, i dont know what to do and im not getting any suggestions on the manjaro forum I’m running Manjaro with Plasma 6.3.5 and I’ve hit an issue where Dolphin hangs for a long time when trying to open an SFTP bookmark. I also noticed KWalletManager hangs or fails to open. Digging into it, I found this error: An error occurred when connecting to the KWallet service: 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. I checked the process: ps -ef | grep kwalletd It shows kwalletd6 is running, but when I run it manually with debugging: KWALLET_DAEMON_DEBUG=1 kwalletd6 …I get repeating messages like: libsecret-CRITICAL **: secret_service_load_collections_sync: assertion 'paths != NULL' failed kf.wallet.kwalletd: "Could not connect to Secret Service" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504193] Default wallet can not be opened
https://bugs.kde.org/show_bug.cgi?id=504193 --- Comment #29 from jackdinn --- (In reply to michaelk83 from comment #28) > (In reply to jackdinn from comment #27) > > Hangs are a different problem than the one discussed in this bug report. > Since your kwalletd6 is running, and the hanging apps are not > Chromium-based, this doesn't look like bug 504014, but might be bug 458085 > or a separate bug. Please post a separate issue with the full details, > including your kwalletrc. ok, thx.i shall post something. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #77 from jackdinn --- ❱busctl --user status org.freedesktop.secrets PID=98412 PIDFD=yes PPID=1219 TTY=n/a UID=1000 EUID=1000 SUID=1000 FSUID=1000 OwnerUID=1000 GID=1001 EGID=1001 SGID=1001 FSGID=1001 SupplementaryGIDs=3 90 98 108 956 991 998 1000 1001 1001 Comm=gnome-keyring-d Exe=/usr/bin/gnome-keyring-daemon CommandLine=/usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring CGroup=/user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service Unit=user@1000.service Slice=user-1000.slice UserUnit=gnome-keyring-daemon.service UserSlice=app.slice Session=n/a AuditLoginUID=1000 AuditSessionID=2 UniqueName=:1.136 EffectiveCapabilities= PermittedCapabilities= InheritableCapabilities=cap_wake_alarm BoundingCapabilities=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend cap_audit_read cap_perfmon cap_bpf cap_checkpoint_restore ⎼⎼ /home/greg ⎼⎼ ❱yay -Qs keepass 1 ⎼⎼ /home/greg ⎼⎼ ❱yay -Qs keepassxc 1 ⎼⎼ /home/greg ⎼⎼ ❱yay -Qs gnome-keyring 1 ⎼⎼ /home/greg ⎼⎼ ❱cat .config/kwalletrc [KSecretD] Enabled=false [Wallet] Close When Idle=false Close on Screensaver=false Enabled=true First Use=false Idle Timeout=10 Launch Manager=true Leave Manager Open=false Leave Open=true Prompt on Open=false Use One Wallet=true [org.freedesktop.secrets] apiEnabled=true ⎼⎼ /home/greg ⎼⎼ ❱ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #78 from jackdinn --- I noticed it has Exe=/usr/bin/gnome-keyring-daemon CommandLine=/usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring CGroup=/user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service Unit=user@1000.service But iv never had gnome-keyring installed, ever. Maybe im misunderstanding, but it certainly looks curious. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #79 from jackdinn --- ok well i just removed any gnome-keyring stuff i could/might find. systemctl --user stop gnome-keyring-daemon.service systemctl --user disable gnome-keyring-daemon.service systemctl --user mask dbus-org.freedesktop.secrets.service systemctl --user stop gnome-keyring-daemon.socket systemctl --user disable gnome-keyring-daemon.socket systemctl --user mask gnome-keyring-daemon.socket rm -f ~/.config/autostart/gnome-keyring*.desktop sudo rm -f /etc/xdg/autostart/gnome-keyring*.desktop systemctl --user daemon-reexec I rebooted. now my busctl --user status org.freedesktop.secrets shows Failed to get credentials: No such device or address 1 the sftp does not hang still and i can use it fine. But i still get a blank kwalletmanger window. I have tried to create a new wallet, which it did seem to let me do, i named it and applied it, but still no wallets show up anywhere at all & the kwalletmanger is still a blank window. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #71 from jackdinn --- I'm not sure if this is exactly the same issue as this Bug, but I’m reporting it anyway because it seems closely related. System: OS: Manjaro Linux (Stable branch) KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel: 6.13.12-2-MANJARO Graphics: Mesa Intel Iris Xe CPU: Intel Core i9-13900H Packages: kwallet 6.14.0-2 kwallet-pam 6.3.5-2 kwalletmanager 25.04.1-1 Problem: After my last update (just yesterday). When trying to open an SFTP bookmark in Dolphin, it hangs indefinitely. KWalletManager also fails to open and freezes. Here's the DBus error I receive: An error occurred when connecting to the KWallet service: 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. kwalletd6 is running. When launched manually with debug output: KWALLET_DAEMON_DEBUG=1 kwalletd6 …it outputs repeatedly: libsecret-CRITICAL **: secret_service_load_collections_sync: assertion 'paths != NULL' failed kf.wallet.kwalletd: "Could not connect to Secret Service" Checking who owns the org.freedesktop.secrets DBus name: busctl --user status org.freedesktop.secrets …it shows: Exe=/usr/bin/ksecretd Comm=ksecretd So ksecretd is running and registered as the Secret Service provider, but any call to it hangs — including secret-tool store, kwalletmanager, and SFTP connections in Dolphin. I’ve also confirmed with Manjaro forum administrators that downgrading kwallet is no longer viable since all of KDE Frameworks 6.14.0 has now landed. At this point, I'm not sure if ksecretd is simply non-functional or if it's a configuration issue, but as it stands it effectively breaks all applications relying on Secret Service. I am stuck, i don't know what to do. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #75 from jackdinn --- I dont know if i was using GPG, i assume i was. I tried adding no-allow-external-cache :- ❱cat .gnupg/gpg-agent.conf default-cache-ttl 900 max-cache-ttl 99 no-allow-external-cache i logged out and back in but i still can load the wallet manager and it still hangs when using dolphin sftp bookmarks. However, someone has just suggested adding the following to .config/kwalletrc (mine does not have KSecretD at all) and although the walletmanager still shows a blank window, it does not hang any more, neither does my access of the sftp on dolphin. I dont know what all this means. [KSecretD] Enabled=false As for using a different Secret Service provider, i have never to my knowledge changed the default kde wallet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #72 from jackdinn --- EDIT:- "When trying to open an SFTP bookmark in Dolphin, it hangs for about 60 seconds" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656 --- Comment #6 from jackdinn --- Ah, well if only the manjaro admin had not said that a downgrade of kwallet would NOT work, i would have tried it ages ago. I just tried it as nothing else to loose and boom, its working again. ❱yay -Qi kwallet Name: kwallet Version : 6.12.0-1 Description : Secure and unified container for user passwords Architecture: x86_64 URL : https://community.kde.org/Frameworks Licenses: LGPL-2.0-only LGPL-3.0-only Groups : kf6 Provides: org.freedesktop.secrets Depends On : gcc-libs glibc gpgme kcolorscheme kconfig kcoreaddons kcrash kdbusaddons ki18n knotifications kwidgetsaddons kwindowsystem libgcrypt qca-qt6 qt6-base Optional Deps : kwalletmanager: Configuration GUI [installed] Required By : kaccounts-integration kio ksshaskpass kwallet-pam kwalletmanager libksane okular plasma-nm plasma-workspace signon-kwallet-extension Optional For: git libsecret vlc Conflicts With : None Replaces: None Installed Size : 2.60 MiB Packager: Tomaz Canabrava Build Date : Sat 15 Mar 2025 12:44:23 GMT Install Date: Thu 22 May 2025 13:19:00 BST Install Reason : Installed as a dependency for another package Install Script : No Validated By: Signature I hope you guys fix this before to long, but until then im going to just lock this package for now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656 --- Comment #9 from jackdinn --- Well yes, I've always had a wallet that has no name, I was never sure where it came from originally I suppose I must have accidentally created it but these wallets have been with me for many years now so I don't remember. However, the previous version kwallet was/is happy to have such a wallet (heres a screenshot) https://jackdinn.co.uk/s/GdRNgnrLrdE2FJq/preview So you think if i remove the blank wallet from here and then update it might work? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #11 from jackdinn ---
Unfortunately, no.
❱journalctl -b | grep kwallet
May 22 18:09:58 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:auth): pam_kwallet5: pam_sm_authenticate
May 22 18:09:58 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Couldn't get password (it is
empty)
May 22 18:09:58 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Empty or missing password,
doing nothing
May 22 18:09:58 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
May 22 18:09:59 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
May 22 18:09:59 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without
kwallet5_key
May 22 18:09:59 greg-venusseries systemd[1258]: Started Unlock kwallet from pam
credentials.
May 22 18:10:15 greg-venusseries systemd[1258]: Created slice Slice
/app/dbus-:1.2-org.kde.kwalletd6.
May 22 18:10:15 greg-venusseries systemd[1258]: Started
dbus-:1.2-org.kde.kwalletd6@0.service.
May 22 18:10:41 greg-venusseries systemsettings[3345]: Couldn't start kwalletd:
QDBusError("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.")
May 22 18:10:41 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Error
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"
May 22 18:10:41 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Could
not connect to Secret Service"
May 22 18:11:06 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Error
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"
May 22 18:11:06 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Could
not connect to Secret Service"
May 22 18:11:06 greg-venusseries kwalletd6[3418]: QThreadStorage: entry 8
destroyed before end of thread 0x6370107641f0
May 22 18:11:30 greg-venusseries systemd[1]: Created slice Slice
/system/dbus-:1.2-org.kde.kcontrol.kcmkwallet5.
May 22 18:11:30 greg-venusseries systemd[1]: Started
dbus-:1.2-org.kde.kcontrol.kcmkwallet5@0.service.
May 22 18:11:31 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Error
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"
May 22 18:11:31 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Could
not connect to Secret Service"
May 22 18:11:35 greg-venusseries polkitd[791]: Operator of unix-session:1
successfully authenticated as unix-user:greg to gain TEMPORARY authorization
for action org.kde.kcontrol.kcmkwallet5.save for system-bus-name::1.68
[/usr/bin/systemsettings] (owned by unix-user:greg)
May 22 18:11:45 greg-venusseries systemd[1]:
dbus-:1.2-org.kde.kcontrol.kcmkwallet5@0.service: Deactivated successfully.
May 22 18:12:11 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Error
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"
May 22 18:12:11 greg-venusseries kwalletd6[3406]: kf.wallet.kwalletd: "Could
not connect to Secret Service"
May 22 18:12:30 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_close_session
May 22 18:12:30 greg-venusseries sddm-helper[1254]:
pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
May 22 18:12:35 greg-venusseries sddm-helper[4235]: pam_kwallet5(sddm:auth):
pam_kwallet5: pam_sm_authenticate
May 22 18:12:35 greg-venusseries sddm-helper[4235]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
May 22 18:12:35 greg-venusseries sddm-helper[4235]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
May 22 18:12:35 greg-venusseries sddm-helper[4242]: pam_kwallet5: final socket
path: /run/user/1000/kwallet5.socket
May 22 18:12:36 greg-venusseries systemd[1258]: Started Unlock kwallet from pam
credentials.
May 22 18:12:36 greg-venusseries pam_kwallet_init[4328]: 2025/05/22 18:12:36
socat[4328] W address is opened in read-write mode but only supports read-only
May 22 18:12:47 greg-venusseries systemd[1258]: Started
dbus-:1.2-org.kde.kwalletd6@1.service.
May 22 18:13:12 greg-venusseries kwalletd6[6204]: kf.wallet.kwalletd: "Error
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"
May 22 18:13:12 greg-venusseries kwalletd6[6204]: kf.wallet.kwalletd: "Could
not connect to Secret Service"
May 22 18:13:37 greg-venusseries kwalletd6[6204]: kf.wallet.kwalletd: "Error
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"
May 22 18:13:37 greg-venusseries kwalletd6[6204]: kf.wallet.kwalletd: &q
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656 --- Comment #13 from jackdinn --- You are talking about the "Use KWallet for the Secret Service interface" tick box? As i said "I tried both with and without the "use secret service interface" ticked and unticked." -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656 --- Comment #14 from jackdinn --- Ohh, sorry i see now. [KSecretD] Enabled=true This setting is NOT the tickbox "Use KWallet for the Secret Service interface" Its completely something else. Yes it is now working. But why did it not set that setting when i install it if it needs to be that way ? Last time i updated ,(every time i update it) the [KSecretD] Enabled=false, it was only by manually changing it in the text rc file that it is now working. I was assuming that at least one of the tickboxes on the GUI were setting this setting. Anyhow, i think it looks like its all ok now. Sorry i misunderstood you, and thank you for your time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656 --- Comment #16 from jackdinn --- Yes to all, thank you. Yea, it must have been the blank wallet name in the main because i did try many many times editing the walletrc file and just pasting your setting and saving it, so it was still failing with [KSecretD] Enabled=true before, After i deleted the nameless wallet and i set the rc file correctly again it is all working again. So yes, 6.14 is all working and i have access to my recovered wallet (btrfs) & all passwords, thank you :) p.s. there were no passwords in the nameless wallet, it was never used and was not needed at all but i never had the need to delete it, it caused no problems. (i think i did try to delete it once in the GUI but it would not go so i just left it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #82 from jackdinn --- I need help, i cant even login to my wifi either it says it can't save the password and i don't know what to do. The system is falling apart without the wallet. If i roll back my system to before the kwallet update its works so its definitely the last update that caused it. I really need help. @ Network Management = Failed to get secrets for TP-Link_E013 No agents were available for this request. Failed to get secrets for TP-Link_E013 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504656] KWalletManager and other calls to ksecretd hang with kwallet 6.14 (kwallet is ENABLED).
https://bugs.kde.org/show_bug.cgi?id=504656 jackdinn changed: What|Removed |Added CC||j...@jackdinn.co.uk --- Comment #4 from jackdinn --- But Aragorn the admin on manjaro forums said a downgrade would not work? https://forum.manjaro.org/t/plasma-6-kwallet-hangs-and-dolphin-sftp-fails-missing-secret-service-backend/178130/12?u=jackdinn Would downgrading kwallet work still? No, not anymore now that Frameworks has been updated. Iv already lost all my keys, to much messing around. I have found that if i delete ~/.local/share/kwalletd and ~/.config/kwalletrc and reboot i get one chance to create a new wallet, but if its on GPG i get this error Seems that your system has no keys suitable for encryption. Please set-up at least one encryption key, then try again. but i know full well that i have PGP keys. The previous wallet used one of them. ❱gpg --list-keys [keyboxd] - pub rsa2048 2017-09-19 [SCEA] 082D1DA52FABBE31A59E61DBF7D443B0486C8554 uid [ultimate] traderjoe sub rsa2048 2017-09-19 [SEA] pub rsa4096 2014-11-02 [SC] 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D uid [ unknown] Ned Deily (Python release signing key) uid [ unknown] Ned Deily (Python release signing key) uid [ unknown] Ned Deily uid [ unknown] keybase.io/nad sub rsa4096 2014-11-02 [E] pub dsa1024 2001-01-05 [SCA] 1528635D8053A57F77D1E08630A59377A7763BE6 uid [ unknown] Sam Lantinga sub elg1024 2001-01-05 [E] pub rsa2048 2014-01-10 [SC] [expired: 2025-04-29] 20EE325B86A81BCBD3E56798F04367096FBA95E8 uid [ expired] Dain Nilsson pub rsa4096 2022-05-14 [SC] 662E3CDD6FE329002D0CA5BB40339DD82B12EF16 uid [ unknown] LibreWolf Maintainers sub rsa4096 2022-05-14 [S] sub rsa4096 2022-05-14 [S] sub rsa4096 2022-05-14 [E] pub rsa4096 2016-01-16 [SCA] AFE402238DAC43C08554DBD34BD1106720D8126B uid [ultimate] jackdinn sub rsa4096 2016-01-16 [E] pub rsa4096 2013-10-09 [SC] C01E1CAD5EA2C4F0B8E3571504C367C218ADD4FF uid [ unknown] Benjamin Peterson uid [ unknown] Benjamin Peterson uid [ unknown] Benjamin Peterson sub rsa4096 2013-10-09 [E] pub rsa4096 2015-05-11 [SC] [expires: 2061-03-06] E3FF2839C048B25C084DEBE9B26995E310250568 uid [ unknown] Łukasz Langa (GPG langa.pl) uid [ unknown] Łukasz Langa uid [ unknown] Łukasz Langa uid [ unknown] Łukasz Langa uid [ unknown] Łukasz Langa uid [ unknown] Łukasz Langa (Work e-mail account) uid [ unknown] [jpeg image of size 24479] pub rsa1024 2016-02-17 [SCA] F1E61107B53B720CE37FC6C7E220A3F1D2C058FD uid [ultimate] AOL sub rsa1024 2016-02-17 [E] I tried creating a blowfish wallet and it did look like it had created a new wallet but nothing will store in it. I tried to connect to a new wifi and it just says waiting for conformation or something like that. If i fail to create a wallet or try to cancel the wallet creation process then it all just starts hanging for 60 secs with everything related to the wallet again and i can not even attempt to create another wallet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #81 from jackdinn --- Ok i set :- [KSecretD] Enabled=true [Wallet] Close When Idle=false Close on Screensaver=false Enabled=true First Use=false Idle Timeout=10 Launch Manager=true Leave Manager Open=false Leave Open=true Prompt on Open=false Use One Wallet=true [org.freedesktop.secrets] apiEnabled=false i rebooted, but now its just gone back to hanging for 60 secs when i try to open my NAS or open the kde wallet or kwalletmanager The kwalletmanger window has the following error:- An error occurred when connecting to the KWallet service: 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. and iv got ❱journalctl --since -5m | grep ksecretd May 21 16:31:41 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "/org/freedesktop/secrets/collection/" May 21 16:31:41 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:31:41 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:32:06 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:32:06 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:32:31 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:32:31 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:32:56 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:32:56 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:33:21 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:33:21 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:33:46 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:33:46 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:34:11 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:34:11 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:34:36 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:34:36 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:35:01 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:35:01 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments May 21 16:35:27 greg-venusseries ksecretd[3459]: QDBusObjectPath: invalid path "" May 21 16:35:27 greg-venusseries ksecretd[3459]: qt.dbus.integration: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path passed in arguments ⎼⎼ /home/greg ⎼⎼ -- You are receiving this mail because: You are watching all bug changes.
