#dbus — Public Fediverse posts

If you use #Linux on your desktop, forget about the Linux foundation. The foundation you *should* care about is the @XOrgFoundation AKA freedesktop.org. The X.Org foundation oversees:

- #X11
- #Wayland
- #Mesa
- #Noveau
- #DBus
- #GRUB
- #GStreamer
- #PulseAudio
- #PipeWire
- #NetworkManager
- the Linux kernel graphics subsystem
- the #XDG base directory specification
- and more!

Also, development of what would later become #Flatpak started here.

These projects have a way stronger impact on your day-to-day computing experience than anything managed by the Linux foundation.

If you use #Linux on your desktop, forget about the Linux foundation. The foundation you *should* care about is the @XOrgFoundation AKA freedesktop.org. The X.Org foundation oversees:

- #X11
- #Wayland
- #Mesa
- #Noveau
- #DBus
- #GRUB
- #GStreamer
- #PulseAudio
- #PipeWire
- #NetworkManager
- the Linux kernel graphics subsystem
- the #XDG base directory specification
- and more!

Also, development of what would later become #Flatpak started here.

These projects have a way stronger impact on your day-to-day computing experience than anything managed by the Linux foundation.

If you use #Linux on your desktop, forget about the Linux foundation. The foundation you *should* care about is the @XOrgFoundation AKA freedesktop.org. The X.Org foundation oversees:

- #X11
- #Wayland
- #Mesa
- #Noveau
- #DBus
- #GRUB
- #GStreamer
- #PulseAudio
- #PipeWire
- #NetworkManager
- the Linux kernel graphics subsystem
- the #XDG base directory specification
- and more!

Also, development of what would later become #Flatpak started here.

These projects have a way stronger impact on your day-to-day computing experience than anything managed by the Linux foundation.

If you use #Linux on your desktop, forget about the Linux foundation. The foundation you *should* care about is the @XOrgFoundation AKA freedesktop.org. The X.Org foundation oversees:

- #X11
- #Wayland
- #Mesa
- #Noveau
- #DBus
- #GRUB
- #GStreamer
- #PulseAudio
- #PipeWire
- #NetworkManager
- the Linux kernel graphics subsystem
- the #XDG base directory specification
- and more!

Also, development of what would later become #Flatpak started here.

These projects have a way stronger impact on your day-to-day computing experience than anything managed by the Linux foundation.

If you use #Linux on your desktop, forget about the Linux foundation. The foundation you *should* care about is the @XOrgFoundation AKA freedesktop.org. The X.Org foundation oversees:

- #X11
- #Wayland
- #Mesa
- #Noveau
- #DBus
- #GRUB
- #GStreamer
- #PulseAudio
- #PipeWire
- #NetworkManager
- the Linux kernel graphics subsystem
- the #XDG base directory specification
- and more!

Also, development of what would later become #Flatpak started here.

These projects have a way stronger impact on your day-to-day computing experience than anything managed by the Linux foundation.

@impromptux bien vu.
La doc dit que #dbus le faisait déjà.

Je ne vois pas de soucis en soit. Le problème vient des usages. Même chose pour les TPM.

@impromptux bien vu.
La doc dit que #dbus le faisait déjà.

Je ne vois pas de soucis en soit. Le problème vient des usages. Même chose pour les TPM.

@impromptux bien vu.
La doc dit que #dbus le faisait déjà.

Je ne vois pas de soucis en soit. Le problème vient des usages. Même chose pour les TPM.

@impromptux bien vu.
La doc dit que #dbus le faisait déjà.

Je ne vois pas de soucis en soit. Le problème vient des usages. Même chose pour les TPM.

Не отдам Gpick! Он хороший! Но крутить педали придётся…

Уже давно весьма огорчаюсь тем, что в моём любимом Gpick отвалилась пипетка с тех пор, как KDE со своей Плазмой прочно переехали на Wayland. Если раньше я ещё мирился с GTK-шностью Gpick (про KDE, плазму и вяленого — поручик, молчать!), то теперь совсем взгрустнулось…

https://habr.com/ru/articles/1060500/

#wayland #colorpicker #xdgdesktopportal #gpick #kde_plasma #dbus #python #пипетка #выбор_цвета #автоматизация

Не отдам Gpick! Он хороший! Но крутить педали придётся…

Уже давно весьма огорчаюсь тем, что в моём любимом Gpick отвалилась пипетка с тех пор, как KDE со своей Плазмой прочно переехали на Wayland. Если раньше я ещё мирился с GTK-шностью Gpick (про KDE, плазму и вяленого — поручик, молчать!), то теперь совсем взгрустнулось…

https://habr.com/ru/articles/1060500/

#wayland #colorpicker #xdgdesktopportal #gpick #kde_plasma #dbus #python #пипетка #выбор_цвета #автоматизация

Не отдам Gpick! Он хороший! Но крутить педали придётся…

Уже давно весьма огорчаюсь тем, что в моём любимом Gpick отвалилась пипетка с тех пор, как KDE со своей Плазмой прочно переехали на Wayland. Если раньше я ещё мирился с GTK-шностью Gpick (про KDE, плазму и вяленого — поручик, молчать!), то теперь совсем взгрустнулось…

https://habr.com/ru/articles/1060500/

#wayland #colorpicker #xdgdesktopportal #gpick #kde_plasma #dbus #python #пипетка #выбор_цвета #автоматизация

Ubuntu is hopping aboard a modern system message bus, with 26.10 replacing dbus-daemon with dbus-broker – years after other Linux distros did the same. Users won't notice much (if any) difference, but that's a good thing.

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker?v1

#Linux #Ubuntu #Dbus

Ubuntu is hopping aboard a modern system message bus, with 26.10 replacing dbus-daemon with dbus-broker – years after other Linux distros did the same. Users won't notice much (if any) difference, but that's a good thing.

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker?v1

#Linux #Ubuntu #Dbus

Ubuntu is hopping aboard a modern system message bus, with 26.10 replacing dbus-daemon with dbus-broker – years after other Linux distros did the same. Users won't notice much (if any) difference, but that's a good thing.

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker?v1

#Linux #Ubuntu #Dbus

Ubuntu is hopping aboard a modern system message bus, with 26.10 replacing dbus-daemon with dbus-broker – years after other Linux distros did the same. Users won't notice much (if any) difference, but that's a good thing.

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker?v1

#Linux #Ubuntu #Dbus

Ubuntu is hopping aboard a modern system message bus, with 26.10 replacing dbus-daemon with dbus-broker – years after other Linux distros did the same. Users won't notice much (if any) difference, but that's a good thing.

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker?v1

#Linux #Ubuntu #Dbus

Wasn't even aware #dbus broker was replacing dbus daemon on #ubuntu.

Very very nice. 😎 Getting everything to use one bus may sound simple, but it's really not. So MANY failure cases. Glad this is on 26.10. Cause time will be needed for bugs. 😅

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker

Wasn't even aware #dbus broker was replacing dbus daemon on #ubuntu.

Very very nice. 😎 Getting everything to use one bus may sound simple, but it's really not. So MANY failure cases. Glad this is on 26.10. Cause time will be needed for bugs. 😅

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker

Wasn't even aware #dbus broker was replacing dbus daemon on #ubuntu.

Very very nice. 😎 Getting everything to use one bus may sound simple, but it's really not. So MANY failure cases. Glad this is on 26.10. Cause time will be needed for bugs. 😅

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker

Wasn't even aware #dbus broker was replacing dbus daemon on #ubuntu.

Very very nice. 😎 Getting everything to use one bus may sound simple, but it's really not. So MANY failure cases. Glad this is on 26.10. Cause time will be needed for bugs. 😅

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker

Wasn't even aware #dbus broker was replacing dbus daemon on #ubuntu.

Very very nice. 😎 Getting everything to use one bus may sound simple, but it's really not. So MANY failure cases. Glad this is on 26.10. Cause time will be needed for bugs. 😅

https://www.omgubuntu.co.uk/2026/07/ubuntu-26-10-dbus-broker

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

Am I getting this right that #dbus considers installing two desktop environments that ship their own separate conflicting implementations for basic user session services such as org.freedesktop.Notifications to be entirely undefined behaviour with no way to specify which desktop session should use which implementation?

#freedesktop

Am I getting this right that #dbus considers installing two desktop environments that ship their own separate conflicting implementations for basic user session services such as org.freedesktop.Notifications to be entirely undefined behaviour with no way to specify which desktop session should use which implementation?

#freedesktop

Am I getting this right that #dbus considers installing two desktop environments that ship their own separate conflicting implementations for basic user session services such as org.freedesktop.Notifications to be entirely undefined behaviour with no way to specify which desktop session should use which implementation?

#freedesktop

Am I getting this right that #dbus considers installing two desktop environments that ship their own separate conflicting implementations for basic user session services such as org.freedesktop.Notifications to be entirely undefined behaviour with no way to specify which desktop session should use which implementation?

#freedesktop

#Lua #dbus #lgi #gobjectintrospection
Я, Матье Бал.
Короче, что я сделал, чтобы заработало это говно?
Пообщался вновь с ИИ. Она дала идею выбросить йухан ваш vtable, ибо он не нужон.
А ещё и понадабавил парочку хуйни. ссылка

Итог:

(luajjit:<pid>): Lgi-WARNING **: <HH:MM:SS.ms>: Error raised while calling 'lgi.cbk (function: 0x7fdb3946c940): GObject': /usr/share/lua/5.1/lgi/override/GLib-Variant.lua:97: bad argument #2 to '?' (string expected, got nil)

#Lua #dbus #lgi #gobjectintrospection
Я, Матье Бал.
Короче, что я сделал, чтобы заработало это говно?
Пообщался вновь с ИИ. Она дала идею выбросить йухан ваш vtable, ибо он не нужон.
А ещё и понадабавил парочку хуйни. ссылка

Итог:

(luajjit:<pid>): Lgi-WARNING **: <HH:MM:SS.ms>: Error raised while calling 'lgi.cbk (function: 0x7fdb3946c940): GObject': /usr/share/lua/5.1/lgi/override/GLib-Variant.lua:97: bad argument #2 to '?' (string expected, got nil)

#Lua #dbus #lgi #gobjectintrospection
Я, Матье Бал.
Короче, что я сделал, чтобы заработало это говно?
Пообщался вновь с ИИ. Она дала идею выбросить йухан ваш vtable, ибо он не нужон.
А ещё и понадабавил парочку хуйни. ссылка

Итог:

(luajjit:<pid>): Lgi-WARNING **: <HH:MM:SS.ms>: Error raised while calling 'lgi.cbk (function: 0x7fdb3946c940): GObject': /usr/share/lua/5.1/lgi/override/GLib-Variant.lua:97: bad argument #2 to '?' (string expected, got nil)

#Lua #D-Bus #dbus #GTK #gobjectintrospection
@[email protected] @[email protected]

Ребят, нужна помощь с написанием кода.
Задача: Хочу написать на Lua простой скрипт, создающий D-Bus службу (В идеале org.kde.StatusNotifierWatcher) , к которой можно достучаться через dbus-send или gdbus. Пробовал через ИИ, который даже написал, но... Сталкиваюсь с нккоторыми ошибками, а именно:
1)

luajit: ./proxyserver.lua:62: bad argument #5 to 'bus_own_name' (GObject.Closure expected, got function)
stack traceback:
    [C]: in function 'bus_own_name'
    ./proxyserver.lua:62: in function 'start'
    main.lua:25: in main chunk
    [C]: at 0x55b22012ed70

    Gio.bus_own_name(
        Gio.BusType.SESSION,
        interface_name,
        Gio.BusNameOwnerFlags.NONE,
        on_bus_acquired,
        on_name_acquired,
        on_name_lost

(luajit:30598): Lgi-WARNING **: 00:28:04.678: Error raised while calling 'lgi.cbk (function: 0x7f4efadd87c0): GObject': ./proxyserver.lua:51: bad argument #4 to 'register_object' (GObject.Closure expected, got userdata) 

    local on_bus_acquired = function(connection, name)
        connection:register_object('/org/example/MyObject', iface, vtable)
    end

dbus-send --session --print-reply \
    --dest=org.example.MyInterface \
    /org/example/MyObject \
    org.example.MyInterface.SayHello

gdbus call --session \
    --dest org.example.MyInterface \
    --object-path /org/example/MyObject \
    --method org.example.MyInterface.SayHello

(luajit:25911): Lgi-WARNING **: HH:MM:SS.ms : Error raised while calling 'lgi.cbk (function :0x7f5b60662de0): GObject': /usr/share/lua/5.1/lgi/override/GObject-Closure.lua:286: attempt to call upvalue 'target' (a userdata value)

dbus-glib 0.114-1
dbus 1.16.2-1.1
lua-lgi 0.9.2-14
lua51-lgi 0.9.2-14
glib2 2.88.0-1
gobject-introspection 1.86.0-2

dbus 1.16.2_2
lua51-lgi 0.9.2_6
glib2 2.88.0_1
gobject-introspection 1.86.0_2

#Lua #D-Bus #dbus #GTK #gobjectintrospection
@[email protected] @[email protected]

Ребят, нужна помощь с написанием кода.
Задача: Хочу написать на Lua простой скрипт, создающий D-Bus службу (В идеале org.kde.StatusNotifierWatcher) , к которой можно достучаться через dbus-send или gdbus. Пробовал через ИИ, который даже написал, но... Сталкиваюсь с нккоторыми ошибками, а именно:
1)

luajit: ./proxyserver.lua:62: bad argument #5 to 'bus_own_name' (GObject.Closure expected, got function)
stack traceback:
    [C]: in function 'bus_own_name'
    ./proxyserver.lua:62: in function 'start'
    main.lua:25: in main chunk
    [C]: at 0x55b22012ed70

    Gio.bus_own_name(
        Gio.BusType.SESSION,
        interface_name,
        Gio.BusNameOwnerFlags.NONE,
        on_bus_acquired,
        on_name_acquired,
        on_name_lost

(luajit:30598): Lgi-WARNING **: 00:28:04.678: Error raised while calling 'lgi.cbk (function: 0x7f4efadd87c0): GObject': ./proxyserver.lua:51: bad argument #4 to 'register_object' (GObject.Closure expected, got userdata) 

    local on_bus_acquired = function(connection, name)
        connection:register_object('/org/example/MyObject', iface, vtable)
    end

dbus-send --session --print-reply \
    --dest=org.example.MyInterface \
    /org/example/MyObject \
    org.example.MyInterface.SayHello

gdbus call --session \
    --dest org.example.MyInterface \
    --object-path /org/example/MyObject \
    --method org.example.MyInterface.SayHello

(luajit:25911): Lgi-WARNING **: HH:MM:SS.ms : Error raised while calling 'lgi.cbk (function :0x7f5b60662de0): GObject': /usr/share/lua/5.1/lgi/override/GObject-Closure.lua:286: attempt to call upvalue 'target' (a userdata value)

dbus-glib 0.114-1
dbus 1.16.2-1.1
lua-lgi 0.9.2-14
lua51-lgi 0.9.2-14
glib2 2.88.0-1
gobject-introspection 1.86.0-2

dbus 1.16.2_2
lua51-lgi 0.9.2_6
glib2 2.88.0_1
gobject-introspection 1.86.0_2

#Lua #D-Bus #dbus #GTK #gobjectintrospection
@[email protected] @[email protected]

Ребят, нужна помощь с написанием кода.
Задача: Хочу написать на Lua простой скрипт, создающий D-Bus службу (В идеале org.kde.StatusNotifierWatcher) , к которой можно достучаться через dbus-send или gdbus. Пробовал через ИИ, который даже написал, но... Сталкиваюсь с нккоторыми ошибками, а именно:
1)

luajit: ./proxyserver.lua:62: bad argument #5 to 'bus_own_name' (GObject.Closure expected, got function)
stack traceback:
    [C]: in function 'bus_own_name'
    ./proxyserver.lua:62: in function 'start'
    main.lua:25: in main chunk
    [C]: at 0x55b22012ed70

    Gio.bus_own_name(
        Gio.BusType.SESSION,
        interface_name,
        Gio.BusNameOwnerFlags.NONE,
        on_bus_acquired,
        on_name_acquired,
        on_name_lost

(luajit:30598): Lgi-WARNING **: 00:28:04.678: Error raised while calling 'lgi.cbk (function: 0x7f4efadd87c0): GObject': ./proxyserver.lua:51: bad argument #4 to 'register_object' (GObject.Closure expected, got userdata) 

    local on_bus_acquired = function(connection, name)
        connection:register_object('/org/example/MyObject', iface, vtable)
    end

dbus-send --session --print-reply \
    --dest=org.example.MyInterface \
    /org/example/MyObject \
    org.example.MyInterface.SayHello

gdbus call --session \
    --dest org.example.MyInterface \
    --object-path /org/example/MyObject \
    --method org.example.MyInterface.SayHello

(luajit:25911): Lgi-WARNING **: HH:MM:SS.ms : Error raised while calling 'lgi.cbk (function :0x7f5b60662de0): GObject': /usr/share/lua/5.1/lgi/override/GObject-Closure.lua:286: attempt to call upvalue 'target' (a userdata value)

dbus-glib 0.114-1
dbus 1.16.2-1.1
lua-lgi 0.9.2-14
lua51-lgi 0.9.2-14
glib2 2.88.0-1
gobject-introspection 1.86.0-2

dbus 1.16.2_2
lua51-lgi 0.9.2_6
glib2 2.88.0_1
gobject-introspection 1.86.0_2

So, this is now working (small protocol change), but I'm missing the rather important functionality of sending notifications.
The issue seems to be with watching the `org.freedesktop.Notifications` dbus interface, as it's not notifying me.

Specifically, `dbus_watch_get_enabled` returns `false`, which seems wrong… been debugging for a few hours and no luck yet. Do I know anyone who might have a clue about this?

#DBus #Pebble
https://git.allpurposem.at/mat/rockwork/src/branch/mat/qt6/rockworkd/platformintegration/desktop/notificationmonitor.cpp#L293

So, this is now working (small protocol change), but I'm missing the rather important functionality of sending notifications.
The issue seems to be with watching the `org.freedesktop.Notifications` dbus interface, as it's not notifying me.

Specifically, `dbus_watch_get_enabled` returns `false`, which seems wrong… been debugging for a few hours and no luck yet. Do I know anyone who might have a clue about this?

#DBus #Pebble
https://git.allpurposem.at/mat/rockwork/src/branch/mat/qt6/rockworkd/platformintegration/desktop/notificationmonitor.cpp#L293

So, this is now working (small protocol change), but I'm missing the rather important functionality of sending notifications.
The issue seems to be with watching the `org.freedesktop.Notifications` dbus interface, as it's not notifying me.

Specifically, `dbus_watch_get_enabled` returns `false`, which seems wrong… been debugging for a few hours and no luck yet. Do I know anyone who might have a clue about this?

#DBus #Pebble
https://git.allpurposem.at/mat/rockwork/src/branch/mat/qt6/rockworkd/platformintegration/desktop/notificationmonitor.cpp#L293

So, this is now working (small protocol change), but I'm missing the rather important functionality of sending notifications.
The issue seems to be with watching the `org.freedesktop.Notifications` dbus interface, as it's not notifying me.

Specifically, `dbus_watch_get_enabled` returns `false`, which seems wrong… been debugging for a few hours and no luck yet. Do I know anyone who might have a clue about this?

#DBus #Pebble
https://git.allpurposem.at/mat/rockwork/src/branch/mat/qt6/rockworkd/platformintegration/desktop/notificationmonitor.cpp#L293

So, this is now working (small protocol change), but I'm missing the rather important functionality of sending notifications.
The issue seems to be with watching the `org.freedesktop.Notifications` dbus interface, as it's not notifying me.

Specifically, `dbus_watch_get_enabled` returns `false`, which seems wrong… been debugging for a few hours and no luck yet. Do I know anyone who might have a clue about this?

#DBus #Pebble
https://git.allpurposem.at/mat/rockwork/src/branch/mat/qt6/rockworkd/platformintegration/desktop/notificationmonitor.cpp#L293

For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: https://www.openwall.com/lists/oss-security/2026/05/19/1

You might also want to read this article from last year: https://www.linuxjournal.com/content/when-flatpaks-sandbox-cracks-real-life-security-issues-beyond-ideal

cc @Seg

#sandboxing #dbus #xdg #freedesktop #wine

For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: https://www.openwall.com/lists/oss-security/2026/05/19/1

You might also want to read this article from last year: https://www.linuxjournal.com/content/when-flatpaks-sandbox-cracks-real-life-security-issues-beyond-ideal

cc @Seg

#sandboxing #dbus #xdg #freedesktop #wine

For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: https://www.openwall.com/lists/oss-security/2026/05/19/1

You might also want to read this article from last year: https://www.linuxjournal.com/content/when-flatpaks-sandbox-cracks-real-life-security-issues-beyond-ideal

cc @Seg

#sandboxing #dbus #xdg #freedesktop #wine

For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: https://www.openwall.com/lists/oss-security/2026/05/19/1

You might also want to read this article from last year: https://www.linuxjournal.com/content/when-flatpaks-sandbox-cracks-real-life-security-issues-beyond-ideal

cc @Seg

#sandboxing #dbus #xdg #freedesktop #wine

For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: https://www.openwall.com/lists/oss-security/2026/05/19/1

You might also want to read this article from last year: https://www.linuxjournal.com/content/when-flatpaks-sandbox-cracks-real-life-security-issues-beyond-ideal

cc @Seg

#sandboxing #dbus #xdg #freedesktop #wine

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis

I've released KDE Desktop Operations - a D-Bus event-to-command daemon for KDE Plasma. I've tried to bring back the feature "Run a command" in #kde but the MR didn't move anywhere in more than a year. So I created a daemon in rust you run as a user which can do the same and more.

https://codeberg.org/cryptomilk/kdo

#plasma #dbus #zbus

I've released KDE Desktop Operations - a D-Bus event-to-command daemon for KDE Plasma. I've tried to bring back the feature "Run a command" in #kde but the MR didn't move anywhere in more than a year. So I created a daemon in rust you run as a user which can do the same and more.

https://codeberg.org/cryptomilk/kdo

#plasma #dbus #zbus

I've released KDE Desktop Operations - a D-Bus event-to-command daemon for KDE Plasma. I've tried to bring back the feature "Run a command" in #kde but the MR didn't move anywhere in more than a year. So I created a daemon in rust you run as a user which can do the same and more.

https://codeberg.org/cryptomilk/kdo

#plasma #dbus #zbus

I've released KDE Desktop Operations - a D-Bus event-to-command daemon for KDE Plasma. I've tried to bring back the feature "Run a command" in #kde but the MR didn't move anywhere in more than a year. So I created a daemon in rust you run as a user which can do the same and more.

https://codeberg.org/cryptomilk/kdo

#plasma #dbus #zbus

I've released KDE Desktop Operations - a D-Bus event-to-command daemon for KDE Plasma. I've tried to bring back the feature "Run a command" in #kde but the MR didn't move anywhere in more than a year. So I created a daemon in rust you run as a user which can do the same and more.

https://codeberg.org/cryptomilk/kdo

#plasma #dbus #zbus

github-monitor is now forgewatch!

I rebranded my PR monitoring daemon. The old name locked it to a single platform, but the vision has always been broader than that. "forgewatch" better reflects what the app is really about: watching over your code forge, wherever it lives.

Why the rename? Two reasons:

1. It's more general. The architecture doesn't depend on GitHub specifically, and I want to grow it to support GitLab, Gitea, and other forges over time.
2. It's more descriptive. "forgewatch" tells you exactly what it does -- it watches your forge for pull requests and keeps you notified via D-Bus and desktop notifications on Linux.

The daemon is async Python, runs as a systemd user service, and comes with an optional system tray indicator. Give it a look if you're a Linux dev who juggles PRs across repos.

https://github.com/dvoraj75/forgewatch
https://pypi.org/project/forgewatch/

#forgewatch #opensource #python #linux #devtools #foss #github #gitlab #gitea #asyncio #dbus #systemd

github-monitor is now forgewatch!

I rebranded my PR monitoring daemon. The old name locked it to a single platform, but the vision has always been broader than that. "forgewatch" better reflects what the app is really about: watching over your code forge, wherever it lives.

Why the rename? Two reasons:

1. It's more general. The architecture doesn't depend on GitHub specifically, and I want to grow it to support GitLab, Gitea, and other forges over time.
2. It's more descriptive. "forgewatch" tells you exactly what it does -- it watches your forge for pull requests and keeps you notified via D-Bus and desktop notifications on Linux.

The daemon is async Python, runs as a systemd user service, and comes with an optional system tray indicator. Give it a look if you're a Linux dev who juggles PRs across repos.

https://github.com/dvoraj75/forgewatch
https://pypi.org/project/forgewatch/

#forgewatch #opensource #python #linux #devtools #foss #github #gitlab #gitea #asyncio #dbus #systemd

#Ubuntu: "We'll comply without a fight and put the #AgeVerification into #dbus."
Users of Linux: "Now installing no-age-dbus."