April 9, 2023
Operating System: Ubuntu 22.04
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-10005-tuxedo (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1901609
Title:
signond causes qprocess crash
Status in signon package in Ubuntu:
Fix Released
Status in signon source
April 9, 2023
Operating System: Ubuntu 22.04
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-10005-tuxedo (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa
This bug was fixed in the package signon -
8.59+17.10.20170606-0ubuntu2.20.04.1
---
signon (8.59+17.10.20170606-0ubuntu2.20.04.1) focal; urgency=medium
* Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd
break compatibility with QProcess (LP: #1901609)
* Build
** Changed in: signon (Ubuntu Focal)
Status: Incomplete => Opinion
** Changed in: signon (Ubuntu Focal)
Status: Opinion => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
On 14/12/2020 18:48, Łukasz Zemczak wrote:
> Sadly I cannot release the focal SRU as it seems that the signon package
> FTBFS on ppc64el there:
>
> https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793
>
> It seems to have built fine previously. Can
Sadly I cannot release the focal SRU as it seems that the signon package
FTBFS on ppc64el there:
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793
It seems to have built fine previously. Can someone take a look?
** Changed in: signon (Ubuntu Focal)
This bug was fixed in the package signon -
8.59+17.10.20170606-0ubuntu2.20.10.1
---
signon (8.59+17.10.20170606-0ubuntu2.20.10.1) groovy; urgency=medium
* Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd
break compatibility with QProcess (LP: #1901609)
* Build
Tested 8.59+17.10.20170606-0ubuntu2.20.10.1 on groovy and the test
scenario outlined in the description is working now. The auth dialog no
longer crashes singond.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You
Sorry read the message only partially on my phone at the time. Here is
the requisite info:
Tested on Ubuntu 20.04 (KDE Neon, the only way this bug manifests
currently, as it only affects systems running Qt >= 5.19.0)
Updated the package and it successfully fixes the bug, using package in
I can confirm that the updated packages work for me. After adding them
to my system using -proposed as suggested, I am now able to get the
window to open asking for my google credentials when selecting to add a
new Google account.
As far as I'm concerned this fixes it for me. Thanks to all for
Hello Sandro, or anyone else affected,
Accepted signon into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Also uploaded to groovy and focal as
8.59+17.10.20170606-0ubuntu2.20.10.1 and
8.59+17.10.20170606-0ubuntu2.20.04.1 respectively
** Changed in: signon (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: signon (Ubuntu Groovy)
Status: Confirmed => In Progress
--
You
This bug was fixed in the package signon - 8.59+17.10.20170606-0ubuntu3
---
signon (8.59+17.10.20170606-0ubuntu3) hirsute; urgency=medium
* Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd
break compatibility with QProcess (LP: #1901609)
* Build depend on quilt
I have tested with the patch applied in this upload to hirsute:
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu3
That fixes the crash for me.
** Changed in: signon (Ubuntu Hirsute)
Status: Confirmed => Fix Committed
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: signon (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: signon (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: signon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
** Changed in: signon (Ubuntu Focal)
Assignee: (unassigned) => Rik Mills (rikmills)
** Changed in: signon (Ubuntu Groovy)
Assignee: (unassigned) => Rik Mills (rikmills)
** Changed in: signon (Ubuntu Hirsute)
Assignee: (unassigned) => Rik Mills (rikmills)
--
You received this bug
** Description changed:
- I'm reporting this bug upstream from where I found it, since I've
- learned that the signond package in KDE Neon is sourced from Ubuntu
- focal.
+ [Impact]
+
+ Without the patch users are unable to add google accounts because signond
crashes.
+ This prevents users from
I have simply concluded this will never be fixed and telepathy should
simply be removed from KDE entirely. Its currently useless and has had
the same or similar issues going back to 2015. Further no one wants to
assume responsibility for fixing it. There are dozens or more bug
reports from here,
Seriously. Wtf is the reason for a 5 year bug in Ububtu... you guys
aren't making enough money to fix stuff? If this was a volunteer system
I would be a little less frustrated but Ubuntu gets a pile of dough from
many sources and its still not fixed. Unbelieveable!!
--
You received this bug
I have posted on debian bug reports and manjaro and arch. Manjaro didn't
respond even when I followed up, arch did the same thing simply not
responding even with multiple posts and follow ups and debian pointed me
to kde bug forums thats why I posted my initial bug report here... seems
everyone is
23 matches
Mail list logo
