!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

219 Members
59 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
12 Mar 2025
@k900:0upti.meK900 ⚡️So probably two staging cycles from now19:16:27
@aidalgol:matrix.orgaidalgolIs that Qt/KDE staging cycles, or nixpkgs staging cycles?19:19:21
@aidalgol:matrix.orgaidalgolAnd for future reference, what does "FF" mean in the "Fix version" field on Qt's Jira?19:19:40
@k900:0upti.meK900 ⚡️nixpkgs staging cycles19:23:44
@k900:0upti.meK900 ⚡️Qt/KDE don't have those19:23:47
@k900:0upti.meK900 ⚡️Not sure what FF means19:24:37
@aktaboot:tchncs.deaktabootAnyone has KDE choke when right-click-> Configure Panel19:40:06
@aktaboot:tchncs.deaktabootlike it's just not responding19:40:22
@aktaboot:tchncs.deaktabootbut i can launch stuff19:40:30
@aktaboot:tchncs.deaktaboot(on nixpkgs-unstable)19:41:11
@aktaboot:tchncs.deaktaboot* but i can launch stuff with shortcuts19:41:30
@aktaboot:tchncs.deaktabootcan't restart it the dbus seems to have died?19:46:37
@k900:0upti.meK900 ⚡️Uhhh19:47:01
@k900:0upti.meK900 ⚡️If your dbus has died, you have bigger problems19:47:06
@aktaboot:tchncs.deaktabootokay it worked with systemctl19:47:18
@aktaboot:tchncs.deaktaboot
❄ ❯kquitapp6 plasmashelll

"Quitting application plasmashell failed. Error reported was:\n\n     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."
19:47:49
@aktaboot:tchncs.deaktabootok now it works, i guess it was just a one time thing19:48:50
13 Mar 2025
@ilya-fedin:matrix.org𝙼𝚛. 𝙱𝚘𝚠𝚕𝚎𝚛 𝚠𝙷𝚊𝚝
In reply to @aidalgol:matrix.org
And for future reference, what does "FF" mean in the "Fix version" field on Qt's Jira?
Feature Freeze
07:22:14

Show newer messages


Back to Room ListRoom Version: 9