qdbus - is this still working in 5.19?

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

qdbus - is this still working in 5.19?

ianseeks-4
Hi

I use this to display progress of my backup script during logout but it no longer displays anything (i used to use kdialog).  I am having other issues with the logout process since installing tumbleweed:20200609 in that its completely changed how it works so it may be linked to that.

regards

Ian
--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Donnerstag, 11. Juni 2020, 18:33:25 schrieb Ianseeks:
> I use this to display progress of my backup script during logout but it no
> longer displays anything (i used to use kdialog).

qdbus is part of Qt4, which was dropped from Tumbleweed in Autumn last year,
so you probably don't have it installed anymore.

I don't know what you are doing exactly, but unless something else changed,
you should be able to use qdbus-qt5 instead (or dbus-send, but that has a
different syntax).

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

ianseeks-4
On Friday, 12 June 2020 16:00:51 BST Wolfgang Bauer wrote:
> Am Donnerstag, 11. Juni 2020, 18:33:25 schrieb Ianseeks:
> > I use this to display progress of my backup script during logout but it no
> > longer displays anything (i used to use kdialog).
>
> qdbus is part of Qt4, which was dropped from Tumbleweed in Autumn last year,
> so you probably don't have it installed anymore.
It worked upto 5.19 update.
 
> I don't know what you are doing exactly, but unless something else changed,
> you should be able to use qdbus-qt5 instead (or dbus-send, but that has a
> different syntax).
All i'm doing is backing up folders and I display which folder is about to be backed up.  I'll update my script to qdbus-qt5 and see how that goes.

Thanks for the info.

> Kind Regards,
> Wolfgang
>
>


--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 16:56:37 schrieb Ianseeks:
> All i'm doing is backing up folders and I display which folder is about to
> be backed up.  I'll update my script to qdbus-qt5 and see how that goes.

Ok, but how exactly are you displaying the folder?

qdbus(-qt5) is just a tool to send messages via D-BUS to some application, it
doesn't really do anything by itself.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

ianseeks-4
On Friday, 12 June 2020 17:07:31 BST Wolfgang Bauer wrote:
> Am Freitag, 12. Juni 2020, 16:56:37 schrieb Ianseeks:
> > All i'm doing is backing up folders and I display which folder is about to
> > be backed up.  I'll update my script to qdbus-qt5 and see how that goes.
>
> Ok, but how exactly are you displaying the folder?
Its just text i'm sending to the screen. I used to use kdialog directly but when that stopped working, i was given qdbus as a replacement way of displaying text on the screen after logout so i can see progress. I can't find the original email where i was told about how to do it.
This is how i was doing it with "qdbus"

dbusRef=`kdialog --progressbar "Starting Back up procedure" 4`
sleep 1
qdbus $dbusRef Set "Starting Back up procedure" value 1
rsync ......
qdbus $dbusRef Set "" value 1
qdbus $dbusRef setLabelText "1.4. Backing up /home/me/Documents"


> qdbus(-qt5) is just a tool to send messages via D-BUS to some application, it
> doesn't really do anything by itself.
>
> Kind Regards,
> Wolfgang
>
>


--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 17:15:08 schrieb Ianseeks:
> dbusRef=`kdialog --progressbar "Starting Back up procedure" 4`
> sleep 1
> qdbus $dbusRef Set "Starting Back up procedure" value 1
> rsync ......
> qdbus $dbusRef Set "" value 1
> qdbus $dbusRef setLabelText "1.4. Backing up /home/me/Documents"
>
So you are in fact using kdialog, and try to update its progressbar and text
later on via D-BUS. ;-)

This is wrong though:
$ qdbus $dbusRef Set "Starting Back up procedure" value 1
Error: org.freedesktop.DBus.Error.UnknownInterface
Interface Starting Back up procedure was not found in object /ProgressDialog

It should probably be just:
$ qdbus $dbusRef value 1
(or whatever value you want to set)

The setLabelText line should be fine though.

Although, as mentioned, you'd probably better use qdbus-qt5 instead.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

ianseeks-4
On Friday, 12 June 2020 18:36:59 BST Wolfgang Bauer wrote:

> Am Freitag, 12. Juni 2020, 17:15:08 schrieb Ianseeks:
> > dbusRef=`kdialog --progressbar "Starting Back up procedure" 4`
> > sleep 1
> > qdbus $dbusRef Set "Starting Back up procedure" value 1
> > rsync ......
> > qdbus $dbusRef Set "" value 1
> > qdbus $dbusRef setLabelText "1.4. Backing up /home/me/Documents"
> >
> So you are in fact using kdialog, and try to update its progressbar and text
> later on via D-BUS. ;-)
yes, a long time ago it used to work without using D-BUS

> This is wrong though:
> $ qdbus $dbusRef Set "Starting Back up procedure" value 1
> Error: org.freedesktop.DBus.Error.UnknownInterface
> Interface Starting Back up procedure was not found in object /ProgressDialog
>
> It should probably be just:
> $ qdbus $dbusRef value 1
> (or whatever value you want to set)
Thanks.
 
> The setLabelText line should be fine though.
>
> Although, as mentioned, you'd probably better use qdbus-qt5 instead.
Yes, i've now updated to qdbus-qt5 and it now works as it used to.

>
> Kind Regards,
> Wolfgang
>
>
 thanks again for replying and getting it working again.

regards
Ian

--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 18:54:51 schrieb Ianseeks:
> yes, a long time ago it used to work without using D-BUS
Kdialog does work without using D-BUS, but then you cannot update the
progressbar value or text... ;-)

> Yes, i've now updated to qdbus-qt5 and it now works as it used to.
The actual problem was the wrong command though. In principle it works the
same with Qt4's qdbus, but as I said that's not available anymore in
Tumbleweed.

Btw, I just tested with an old KDE4 version of kdialog (15.04.3, self-
compiled) as well, and it gave the same error.
 
>  thanks again for replying and getting it working again.
You're welcome.

Hint: it's always a good idea trying to interactively run the commands in
konsole in such a case, to see what's going wrong... ;-)

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 20:02:53 schrieb Wolfgang Bauer:
> Am Freitag, 12. Juni 2020, 18:54:51 schrieb Ianseeks:
> > Yes, i've now updated to qdbus-qt5 and it now works as it used to.
>
> The actual problem was the wrong command though. In principle it works the
> same with Qt4's qdbus, but as I said that's not available anymore in
> Tumbleweed.

Although, it might be that qdbus (and maybe Qt4 as a whole) broke or got
uninstalled after the whole distribution was rebuilt with gcc 10.

Would explain why it stopped working *now*, I suppose...

That one line was still wrong though, and certainly didn't work before either.
Even if you might not have noticed it. ;-)

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

ianseeks-4
On Friday, 12 June 2020 19:24:43 BST Wolfgang Bauer wrote:

> Am Freitag, 12. Juni 2020, 20:02:53 schrieb Wolfgang Bauer:
> > Am Freitag, 12. Juni 2020, 18:54:51 schrieb Ianseeks:
> > > Yes, i've now updated to qdbus-qt5 and it now works as it used to.
> >
> > The actual problem was the wrong command though. In principle it works the
> > same with Qt4's qdbus, but as I said that's not available anymore in
> > Tumbleweed.
>
> Although, it might be that qdbus (and maybe Qt4 as a whole) broke or got
> uninstalled after the whole distribution was rebuilt with gcc 10.
i didn't think about gcc 10.

> Would explain why it stopped working *now*, I suppose...
Just discovered that it still doesn't display on logout although the backup works fine.  It displays okay in konsole where i was testing it.
I'm also getting a few coredumps for each logout - kdialog, drkonqi, plasmashell, qdbus-qt5, i don't get them when I test in konsole.
I've got a problem with logout since 5.19 and it may be part of the problem of not displaying. https://bugs.kde.org/show_bug.cgi?id=422834

> That one line was still wrong though, and certainly didn't work before either.
> Even if you might not have noticed it. ;-)

I didn't notice, the backup worked and the display seemed okay.  :)

> Kind Regards,
> Wolfgang
>
>


--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 19:39:32 schrieb Ianseeks:
> On Friday, 12 June 2020 19:24:43 BST Wolfgang Bauer wrote:
> > Would explain why it stopped working *now*, I suppose...
>
> Just discovered that it still doesn't display on logout although the backup
> works fine.  It displays okay in konsole where i was testing it. I'm also
> getting a few coredumps for each logout - kdialog, drkonqi, plasmashell,
> qdbus-qt5, i don't get them when I test in konsole. I've got a problem with
> logout since 5.19 and it may be part of the problem of not displaying.
> https://bugs.kde.org/show_bug.cgi?id=422834

Hm, I don't think I have that problem here.
I'm using Leap though (that may explain a difference), but I might just not
have noticed it (on Leap, coredumps are disabled by default, and I didn't
enable them).

> > That one line was still wrong though, and certainly didn't work before
> > either. Even if you might not have noticed it. ;-)
>
> I didn't notice, the backup worked and the display seemed okay.  :)

Yeah, if that was the only wrong line, it would just not set the initial value
to 1, and the rest may have worked fine.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 20:51:37 schrieb Wolfgang Bauer:

> Am Freitag, 12. Juni 2020, 19:39:32 schrieb Ianseeks:
> > I'm also
> > getting a few coredumps for each logout - kdialog, drkonqi, plasmashell,
> > qdbus-qt5, i don't get them when I test in konsole. I've got a problem
> > with
> > logout since 5.19 and it may be part of the problem of not displaying.
> > https://bugs.kde.org/show_bug.cgi?id=422834
>
> Hm, I don't think I have that problem here.
> I'm using Leap though (that may explain a difference), but I might just not
> have noticed it (on Leap, coredumps are disabled by default, and I didn't
> enable them).
PS: what widget style are you using?

There is a "bug" in Oxygen 5.19.0 that causes applications to crash on exit.
Breeze was affected as well (in 5.19 beta), but there it was fixed in time for
the 5.19.0 release.
https://bugs.kde.org/show_bug.cgi?id=421434

Although, that probably shouldn't cause qdbus-qt5 to crash at least...
And I didn't see the crash with kdialog now either.

Maybe it would help if you provided a backtrace.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

ianseeks-4
On Friday, 12 June 2020 20:03:57 BST Wolfgang Bauer wrote:

> Am Freitag, 12. Juni 2020, 20:51:37 schrieb Wolfgang Bauer:
> > Am Freitag, 12. Juni 2020, 19:39:32 schrieb Ianseeks:
> > > I'm also
> > > getting a few coredumps for each logout - kdialog, drkonqi, plasmashell,
> > > qdbus-qt5, i don't get them when I test in konsole. I've got a problem
> > > with
> > > logout since 5.19 and it may be part of the problem of not displaying.
> > > https://bugs.kde.org/show_bug.cgi?id=422834
> >
> > Hm, I don't think I have that problem here.
> > I'm using Leap though (that may explain a difference), but I might just not
> > have noticed it (on Leap, coredumps are disabled by default, and I didn't
> > enable them).
> PS: what widget style are you using?

I'm using Breeze for everything
 
> There is a "bug" in Oxygen 5.19.0 that causes applications to crash on exit.
> Breeze was affected as well (in 5.19 beta), but there it was fixed in time for
> the 5.19.0 release.
> https://bugs.kde.org/show_bug.cgi?id=421434
>
> Although, that probably shouldn't cause qdbus-qt5 to crash at least...
> And I didn't see the crash with kdialog now either.
>
> Maybe it would help if you provided a backtrace.
i've never been presented with the option to generate a backtrace.
 
> Kind Regards,
> Wolfgang
>
>


--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
Am Freitag, 12. Juni 2020, 20:45:11 schrieb Ianseeks:
> On Friday, 12 June 2020 20:03:57 BST Wolfgang Bauer wrote:
> > PS: what widget style are you using?
>
> I'm using Breeze for everything

Ok, that was just a thought, but wouldn't have explained all crashes anyway as
mentioned...

> > Maybe it would help if you provided a backtrace.
>
> i've never been presented with the option to generate a backtrace.
No, but you say they are listed, by coredumpctl I suppose.
So you should be able to extract via coredumpctl as well.

See https://www.freedesktop.org/software/systemd/man/coredumpctl.html or
https://wiki.archlinux.org/index.php/Core_dump#Examining_a_core_dump

I don't have it installed here currently (and it's been a few years since I
last used it), but IIRC this should do:
coredumpctl info "coredump identifier"

or

coredumpctl gdb "coredump identifier"
bt

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Knurpht-openSUSE
Op vrijdag 12 juni 2020 21:57:55 CEST schreef Wolfgang Bauer:

> Am Freitag, 12. Juni 2020, 20:45:11 schrieb Ianseeks:
> > On Friday, 12 June 2020 20:03:57 BST Wolfgang Bauer wrote:
> > > PS: what widget style are you using?
> >
> > I'm using Breeze for everything
>
> Ok, that was just a thought, but wouldn't have explained all crashes anyway
> as mentioned...
>
> > > Maybe it would help if you provided a backtrace.
> >
> > i've never been presented with the option to generate a backtrace.
>
> No, but you say they are listed, by coredumpctl I suppose.
> So you should be able to extract via coredumpctl as well.
>
> See https://www.freedesktop.org/software/systemd/man/coredumpctl.html or
> https://wiki.archlinux.org/index.php/Core_dump#Examining_a_core_dump
>
> I don't have it installed here currently (and it's been a few years since I
> last used it), but IIRC this should do:
> coredumpctl info "coredump identifier"
>
> or
>
> coredumpctl gdb "coredump identifier"
> bt
>
> Kind Regards,
> Wolfgang
Wolfgang, could nouveau be playing a role here?  Just wondering.

--
Gertjan Lettink a.k.a. Knurpht
openSUSE Forums Team


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

ianseeks-4
In reply to this post by Wolfgang Bauer
On Friday, 12 June 2020 20:57:55 BST Wolfgang Bauer wrote:

> Am Freitag, 12. Juni 2020, 20:45:11 schrieb Ianseeks:
> > On Friday, 12 June 2020 20:03:57 BST Wolfgang Bauer wrote:
> > > PS: what widget style are you using?
> >
> > I'm using Breeze for everything
>
> Ok, that was just a thought, but wouldn't have explained all crashes anyway as
> mentioned...
>
> > > Maybe it would help if you provided a backtrace.
> >
> > i've never been presented with the option to generate a backtrace.
> No, but you say they are listed, by coredumpctl I suppose.
> So you should be able to extract via coredumpctl as well.
>
> See https://www.freedesktop.org/software/systemd/man/coredumpctl.html or
> https://wiki.archlinux.org/index.php/Core_dump#Examining_a_core_dump

I'll check that out and see what i can get but it'll have to be tomorrow

> I don't have it installed here currently (and it's been a few years since I
> last used it), but IIRC this should do:
> coredumpctl info "coredump identifier"
>
> or
>
> coredumpctl gdb "coredump identifier"
> bt
>
> Kind Regards,
> Wolfgang
>
>
thanks

--
opensuse:tumbleweed:20200610
Qt: 5.15.0 KDE Frameworks: 5.70.0 - KDE Plasma:  5.19.0 - kwin 5.19.0
kmail2 5.14.1 (20.04.0) - akonadiserver 5.14.1 (20.04.0) - Kernel:  5.6.14-1-default  - xf86-video-nouveau:  1.0.16



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: qdbus - is this still working in 5.19?

Wolfgang Bauer
In reply to this post by Knurpht-openSUSE
Am Freitag, 12. Juni 2020, 22:02:41 schrieb Knurpht-openSUSE:
> Wolfgang, could nouveau be playing a role here?  Just wondering.
Maybe, I was actually wondering that myself already.

I don't really know though.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]