https://bugs.kde.org/show_bug.cgi?id=481400
Bug ID: 481400
Summary: Login using Personal Access Token
Classification: Applications
Product: Ruqola
Version: 1.9.2
Platform: Flatpak
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=481400
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=481400
--- Comment #3 from Daniel Eckl ---
Yes, on my company server I can create PAT and I know they work because they do
with Pidgin RocketChat Plugin (which has other serious issues, so that's no
alternative for me)
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=481400
--- Comment #5 from Daniel Eckl ---
That would be awesome, thank you so much for your work. I will do my very best
to build it from git as soon as a first poc is ready.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481400
--- Comment #7 from Daniel Eckl ---
Oh cool, if you are able to provide flatpak afterwards, this would be
wonderful! Thank you so much
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436240
Daniel Eckl changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=481400
--- Comment #11 from Daniel Eckl ---
I'm using Ruqola nightly right now and PAT Login works flawlessly, thank you so
much!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481400
--- Comment #13 from Daniel Eckl ---
I think the PAT part is absolutely flawless. I noticed that when I add a new
server and enter the server url with a trailing slash like
"https://chat.server.name/"; the interface connects like forev
https://bugs.kde.org/show_bug.cgi?id=436240
--- Comment #17 from Daniel Eckl ---
I'm not 100 confident if my issue is the same bug. My freezes are not as long
as the OP describes. Mine feel like just a few milliseconds. Thus I can't tell
for sure if mouse and keyboard are affect
https://bugs.kde.org/show_bug.cgi?id=485306
--- Comment #1 from Daniel Eckl ---
bluetoothctl also shows it not connected, but shows battery level, just like
Plasma does. So maybe this is an underlying problem not connected to Plasma?
bluetoothctl info "70:BF:92:D7:FB:63"
Device 70:B
https://bugs.kde.org/show_bug.cgi?id=485306
Bug ID: 485306
Summary: Bluetooth tray icon showing not connected, but device
works
Classification: Plasma
Product: Bluedevil
Version: 5.27.11
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=436240
Daniel Eckl changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=436240
Daniel Eckl changed:
What|Removed |Added
Platform|openSUSE|Manjaro
Version|5.21.4
https://bugs.kde.org/show_bug.cgi?id=451125
Daniel Eckl changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=445673
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=444536
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=436240
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=433664
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--- Comment #14 from Daniel
https://bugs.kde.org/show_bug.cgi?id=343803
Daniel Eckl changed:
What|Removed |Added
CC|daniel.e...@gmx.de |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=442241
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--- Comment #10 from Daniel
https://bugs.kde.org/show_bug.cgi?id=461947
Bug ID: 461947
Summary: Klipper option "Keep selection and clipboard the same"
has no effect
Classification: Plasma
Product: plasmashell
Version: 5.26.3
Platform: Manjaro
https://bugs.kde.org/show_bug.cgi?id=353983
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=376344
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=343803
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=352177
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #82 from Daniel Eckl ---
I have quite the opposite result, my issues began with the update to Yakkety.
I'm using nvidia-340.98 with disabled compositor. My konsole sessions were
crashing so fast (and always took all existing windows
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #84 from Daniel Eckl ---
You are right, my issue does not match the topic, but crashes have been
discussed here, too. I will reconsider and search for other bugs on this
tracker. Thank you for pointing this out.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=342201
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=343803
--- Comment #86 from Daniel Eckl ---
I absolutely have this issue, too, using Kubuntu 16.10 Yakkety Yak and
nvidia-340.98.
After I tried to reproduce my (supposedly unrelated) konsole crash issue I
closed every konsole window. There was no 100
https://bugs.kde.org/show_bug.cgi?id=344433
Daniel Eckl changed:
What|Removed |Added
CC||daniel.e...@gmx.de
--
You are receiving this
30 matches
Mail list logo
