https://bugs.kde.org/show_bug.cgi?id=426034
hd2021 changed:
What|Removed |Added
CC||song...@foxmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426034
Borja changed:
What|Removed |Added
CC|erja...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=426034
Bug Janitor Service changed:
What|Removed |Added
Priority|NOR |HI
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426034
techgo changed:
What|Removed |Added
CC||ad...@kuta.bid
--- Comment #48 from techgo ---
April
https://bugs.kde.org/show_bug.cgi?id=426034
Rafael Linux User changed:
What|Removed |Added
CC||rafael.linux.u...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #46 from Max ---
Just tried to add Google account, and the login window opened - which I guess
is a huge success!
However, after entering all credentials and confirming the login on mobile
device, I get an empty 'Web authentification for
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #45 from Manuel Geißer ---
The problem is finally fixed with the new signond packages from focal-proposed.
Many thanks to anyone who has contributed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #44 from Manuel Geißer ---
Hopefully the Ubuntu teams does something about this issue soon, because it
means no Neon/Kubuntu 20.04 users can currently profit from kio-gdrive (that
is, without making a bigger effort).
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=426034
Nicolas Fella changed:
What|Removed |Added
CC||geisse...@gmail.com
--- Comment #43 from
https://bugs.kde.org/show_bug.cgi?id=426034
Nicolas Fella changed:
What|Removed |Added
CC||erja...@gmail.com
--- Comment #42 from Nicolas
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #41 from zaile...@gmail.com ---
I know. Others have told me the same thing. The signind fix in arch does fix
the auth issue. I just don't feel like filing 500 different bug reports with
different services and different forums and 275
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #40 from Bart Ribbers ---
You're confused though, this issue IS NOT ABOUT MESSAGING. It's literally just
about adding a Google account to the "Online accounts" section in the system
settings. Anything else is out of the scope of this issue.
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #39 from zaile...@gmail.com ---
Read the thread and comments here:
https://bugs.kde.org/show_bug.cgi?id=426034
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #38 from zaile...@gmail.com ---
Signond does fix the authentication issue for Google but the messaging itself
doesn't work. Further its only for Google, not all the other services of which
very few work.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #37 from Bart Ribbers ---
As a note, I reported this issue originally for Alpine Linux (not KDE Neon). It
was a bug in signond that has been fixed already, but that package didn't get a
new release since 2 years ago.
In the case of Alpine
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #36 from Sandro ---
To be clear, regarding my last comment, this is because it's a Neon package
bug, which has correctly been designated an upstream bug. If you are using any
other distro and you do not have the updated signond package,
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #35 from Sandro ---
In Comment #17 , I linked to where I opened a bug against the upstream signond
package in ubuntu. Your frustrations are valid. Your energy should be posted
in that bug however. As we learned here (or at least I did),
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #34 from Christoph Feck ---
If I understand you correctly, you are looking at a wrong bug report. This
ticket is about login to Google services, not about messaging systems. I don't
know which one you are using, but Google changes them
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #33 from Nicolas Fella ---
The issues you are mentioning are unrelated to this particular bug report, so
nobody claims they are all fixed (or even present).
The only issue that was discussed and declared fixed is "When trying to add a
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #32 from zaile...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #31 from Christoph Feck ---
When new versions of packages are released by distributions is decided by the
distribution maintainers. Some release very quickly, with only days or weeks
between an upstream fix and the fix rolling out to users,
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #30 from zaile...@gmail.com ---
I certainly did which it clearly states its not a fix... and it will lead to a
broken package system and further dependency hell. Thus my previous post that
its not fixed and by the looks of things never
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #29 from Christoph Feck ---
Did you read comment 23? It has the links to the source code.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #28 from zaile...@gmail.com ---
I don't have a rpm based system running right now so I will spin up a full
system with CentOS and get it working there and create a .rpm and write
instructions. This way I'll be able to do .deb, .rpm and I
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #27 from zaile...@gmail.com ---
Nicholas, this is great news! I will gladly build from source if I had the
link to the necessary code and some basic instructions to compile. I have
several VM's as well as test beds i can do this on and
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #26 from Nicolas Fella ---
This particual issue literally has been fixed. I can't magically place a fixed
binary on your harddrive though
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #25 from zaile...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=426034
Nicolas Fella changed:
What|Removed |Added
CC||a.gi...@mclink.it
--- Comment #24 from Nicolas
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #23 from Sandro ---
To answer the question as you asked:
Source is available at gitlab for signond [1]. You'll also need to use
signon-plugin-oauth2 [2] - thanks to Nicolas Fella for uncovering that.
[1]
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #22 from zaile...@gmail.com ---
If someone could simply let us/me know where the code can he downloaded from
that would be great.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #21 from zaile...@gmail.com ---
How do I apply this fix?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
Nicolas Fella changed:
What|Removed |Added
CC||hlo...@gmail.com
--- Comment #20 from Nicolas
https://bugs.kde.org/show_bug.cgi?id=426034
Nicolas Fella changed:
What|Removed |Added
CC||nicolas.fe...@gmx.de
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #18 from zaile...@gmail.com ---
it looks like this bug is confirmed on OpenSuse, Alpine Linux (as indicated on
this ticket), Debian sid (but this could be caused by other issues on Debian),
and KDE Neon. Submitting a bug report for Ubuntu
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #17 from Sandro ---
Thanks Patrick for that clarification. I opened an upstream bug:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609
Looks like it hasn't really been updated since ~Bionic, nothing but repackaging
since
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #15 from Sandro ---
The bug was open for hours in my browser before I got back to it and I forced
through my comment when the conflict warning showed, because I was banging it
out quickly between tasks and needed to get back to work...
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #16 from Patrick Silva ---
on neon, signond package comes from ubuntu repositories.
Therefore, if it does not contain the bug fix, this issue must be reported in
ubuntu bug tracker.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=426034
Sandro changed:
What|Removed |Added
CC||liq...@liquidonline.ca
--- Comment #14 from Sandro
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #13 from zaile...@gmail.com ---
So with kubuntu (I just booted into live usb i still had from earlier) it pops
up the login window for Google but its blank. If you right click and reload
that window it brings up the Google login. I did not
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #12 from zaile...@gmail.com ---
(In reply to Antonio Rojas from comment #10)
> (In reply to Bart Ribbers from comment #8)
> > Building signond with CONFIG+=rtti did not make a difference for me. Note
> > that this happens on multiple
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #11 from Bart Ribbers ---
Well I reported this for an Alpine Linux system, so it happens at least on
Alpine and KDE Neon (which is multiple ;))
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
Antonio Rojas changed:
What|Removed |Added
CC||aro...@archlinux.org
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #9 from Patrick Silva ---
Humm. I can't reproduce this problem on Arch Linux running Plasma 5.20.1.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
Bart Ribbers changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|DOWNSTREAM
https://bugs.kde.org/show_bug.cgi?id=426034
Patrick Silva changed:
What|Removed |Added
Resolution|DUPLICATE |DOWNSTREAM
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #7 from Patrick Silva ---
*** Bug 427063 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
Patrick Silva changed:
What|Removed |Added
CC||zaile...@gmail.com
--- Comment #5 from Patrick
https://bugs.kde.org/show_bug.cgi?id=426034
Patrick Silva changed:
What|Removed |Added
CC||technicaluse...@gmail.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=426034
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=426034
Antonio Rojas changed:
What|Removed |Added
CC|aro...@archlinux.org|
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=426034
--- Comment #3 from Antonio Rojas ---
signond needs to be built with CONFIG+=rtti
https://gitlab.com/accounts-sso/signond/-/merge_requests/27
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426034
Antonio Rojas changed:
What|Removed |Added
Component|KCM |Packages User Edition
52 matches
Mail list logo
