https://bugs.kde.org/show_bug.cgi?id=417615
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #10 from Forest
https://bugs.kde.org/show_bug.cgi?id=417615
--- Comment #11 from Forest ---
> unable to communicate with the first paired instance
The word "paired" should have been in parentheses. I don't know what ate them.
To be clear, only one user has paired KDE Connect with the An
https://bugs.kde.org/show_bug.cgi?id=449727
--- Comment #4 from Forest ---
Yes. I reproduced it with several different themes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465399
--- Comment #7 from Forest ---
Another log capture with slightly different messages:
Feb 13 04:38:14 neon pulseaudio[1306]: GetManagedObjects() failed:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote
https://bugs.kde.org/show_bug.cgi?id=464869
Forest changed:
What|Removed |Added
CC|fores...@sonic.net |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=433059
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=433059
--- Comment #14 from Forest ---
Worth noting:
Plasma 5.20 (which is currently used in Debian Stable) has a built-in theme
with clearly different active/inactive window titlebar colors, called Breeze
High Contrast.
That theme is gone in Plasma 5.26.90
https://bugs.kde.org/show_bug.cgi?id=455809
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=465353
Bug ID: 465353
Summary: Please decouple title bar color from header color
Classification: Applications
Product: systemsettings
Version: 5.26.90
Platform: Other
OS: All
https://bugs.kde.org/show_bug.cgi?id=465356
Bug ID: 465356
Summary: "Appearance" text color is not updated when switching
to Breeze Dark theme
Classification: Applications
Product: systemsettings
Version: 5.26.90
Platfo
https://bugs.kde.org/show_bug.cgi?id=465399
Bug ID: 465399
Summary: Live image: screen goes black and will not wake up
after about 10 minutes idle
Classification: Plasma
Product: Powerdevil
Version: 5.26.90
Platform: Ne
https://bugs.kde.org/show_bug.cgi?id=465399
--- Comment #1 from Forest ---
Note: Waking the screen immediately will not reproduce the problem. Let it stay
idle for 20 seconds or so after the screen turns black.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465399
Forest changed:
What|Removed |Added
Summary|Live image: screen goes |Live image: screen goes
|black and
https://bugs.kde.org/show_bug.cgi?id=465399
Forest changed:
What|Removed |Added
Summary|Live image: screen goes |Live image: screen will not
|black
https://bugs.kde.org/show_bug.cgi?id=465353
--- Comment #2 from Forest ---
> No need to reiterate it here. :)
Sorry if my wording made this seem like a duplicate report. I filed this one
because the reports you linked seem focused on the labeling of the existing
options, without addressing
https://bugs.kde.org/show_bug.cgi?id=465399
--- Comment #3 from Forest ---
VM live session: bug is present
VM installed: unknown (I'll try to find time to test this, but I have no ETA)
Bare metal live session: bug does not occur on my hardware
Bare metal installed: unknown (I do not hav
https://bugs.kde.org/show_bug.cgi?id=465353
--- Comment #4 from Forest ---
> changing that would be unwelcome for those color schemes.
Gotcha.
> we also intentionally didn't add Header colors to all color schemes, or
> require it or anything like that.
For the record, the only
https://bugs.kde.org/show_bug.cgi?id=465353
--- Comment #6 from Forest ---
> there used to be no difference in titlebar color for active vs inactive
> windows at all!
> You used to have to notice the difference purely due to the lightness of the
> titlebar text changing
Heh... Yes
https://bugs.kde.org/show_bug.cgi?id=465452
Bug ID: 465452
Summary: System Settings crash when applying global theme
Classification: Applications
Product: systemsettings
Version: 5.26.90
Platform: Neon
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=464869
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #1 from Forest ---
I
https://bugs.kde.org/show_bug.cgi?id=465399
Forest changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=465399
--- Comment #5 from Forest ---
Created attachment 156056
--> https://bugs.kde.org/attachment.cgi?id=156056&action=edit
powerdevil stack trace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465399
Forest changed:
What|Removed |Added
Summary|Live image: screen will not |Screen will not wake up
|wake up
https://bugs.kde.org/show_bug.cgi?id=449727
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #2 from Forest ---
I
https://bugs.kde.org/show_bug.cgi?id=465452
--- Comment #2 from Forest ---
That bug is against Wayland, while I was using X11. Also, the linked commit
seems to be about drag&drop, which I was not doing at all. Do you still think
it's a duplicate?
> fixed by a backported patch i
https://bugs.kde.org/show_bug.cgi?id=471552
Forest changed:
What|Removed |Added
CC||fores...@nom.one
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=415295
Forest changed:
What|Removed |Added
CC||fores...@nom.one
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=415295
--- Comment #5 from Forest ---
I just had this happen in Plasma 5.27.5 / Frameworks 5.103.0.
It seems inconsistent. I'm sure it worked a month or two ago. The only thing I
remember changing between then and now is applying Android security up
https://bugs.kde.org/show_bug.cgi?id=423502
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #1 from Forest
https://bugs.kde.org/show_bug.cgi?id=417615
--- Comment #13 from Forest ---
Alternative workaround step 2, leaving system config files untouched:
Copy /usr/share/dbus-1/services/org.kde.kdeconnect.service to
~/.local/share/dbus-1/services/ and change the Exec= line of the copy to
Exec=/usr/bin
https://bugs.kde.org/show_bug.cgi?id=417615
--- Comment #12 from Forest ---
I found some (ugly) workarounds for the unwanted kdeconnectd autostart.
The process seems to be launched at session startup time from two distinct
places:
1. /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop
This
https://bugs.kde.org/show_bug.cgi?id=451375
Bug ID: 451375
Summary: SMS delivery reports are unavailable for messages sent
via KDE Connect
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=331429
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #8 from Forest
https://bugs.kde.org/show_bug.cgi?id=451640
Bug ID: 451640
Summary: loses all connections when another virtual console /
desktop session is active
Product: konversation
Version: 1.8.21123
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=451978
Bug ID: 451978
Summary: Kate Build plugin does not recognize pylint command
output
Product: kate
Version: 20.12.2
Platform: Debian stable
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=442876
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #1 from Forest ---
I
https://bugs.kde.org/show_bug.cgi?id=442876
--- Comment #2 from Forest ---
I measured the lag at about 1/3 of a second, which is a lot of lost frames.
Method: Pressing Kronometer's Start key and Spectacle's Capture Active Window
key at the same time. This was on an idle system with
https://bugs.kde.org/show_bug.cgi?id=456840
Bug ID: 456840
Summary: Misleading screen displayed with connected device:
This paired device is not reachable
Product: kdeconnect
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=456893
Bug ID: 456893
Summary: need a way to disable menu animations
Product: Haruna
Version: 0.8.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=440882
Bug ID: 440882
Summary: Screen Energy Saving does not respect
SimulateUserActivity when XWayland is used
Product: Powerdevil
Version: unspecified
Platform: Other
O
https://bugs.kde.org/show_bug.cgi?id=440882
Forest changed:
What|Removed |Added
Summary|Screen Energy Saving does |Screen Energy Saving does
|not
https://bugs.kde.org/show_bug.cgi?id=440882
--- Comment #2 from Forest ---
I don't know if it works in a full wayland session. I don't have a test
environment for that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440882
Forest changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=439312
Bug ID: 439312
Summary: SimulateUserActivity doesn't unlock the screen, even
unlocking without password is enabled
Product: kscreenlocker
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=439312
Forest changed:
What|Removed |Added
Summary|SimulateUserActivity|SimulateUserActivity
|doesn&#
https://bugs.kde.org/show_bug.cgi?id=439312
Forest changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #29 from Forest ---
> maybe also make the triangle filter toggleable? As it makes no sense with
> categories sidebar placed on the right side.
It can be reoriented such that it makes sense on either side, and the approach
I'm u
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #32 from Forest ---
Created attachment 161269
--> https://bugs.kde.org/attachment.cgi?id=161269&action=edit
draft: Kickoff sidebar automatically on the right (Plasma 5.27)
I have been working with Nate (KDE developer) to get this
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #33 from Forest ---
Strangely, a few people have given my merge request a thumbs-down, with no
valid criticism beyond having to adapt their muscle memory to a positioning
change. It seems those people think a one-time inconvenience to them
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #36 from Forest ---
>"Your account has been blocked. Please contact your GitLab administrator if you
>think this is an error."
>
>Not sure why. I can login to my KDE Identity account.
I suspect the bug tracker doesn&
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #37 from Forest ---
Er, I mean the Gitlab instance.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #40 from Forest ---
Max wrote:
> People who thumbed down probably are not satisfied for the same reason this
> bug report was created — not having an option toggle in settings.
Good point. I had updated the title to "place sid
https://bugs.kde.org/show_bug.cgi?id=443082
Forest changed:
What|Removed |Added
Attachment #160376|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=383404
--- Comment #4 from Forest ---
Created attachment 159874
--> https://bugs.kde.org/attachment.cgi?id=159874&action=edit
Akregator 22.12.3 theme dark patch
Akregator 22.12.3 changed its grantleetheme HTML, so continuing to use
AlexandreBo
https://bugs.kde.org/show_bug.cgi?id=471553
Bug ID: 471553
Summary: Mark Feeds as Read on a folder doesn't repaint article
titles until the mouse moves
Classification: Applications
Product: akregator
Version: 5.22.3
Pla
https://bugs.kde.org/show_bug.cgi?id=461459
Forest changed:
What|Removed |Added
CC||fores...@nom.one
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443082
Forest changed:
What|Removed |Added
CC||fores...@nom.one
--- Comment #19 from Forest ---
>
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #20 from Forest ---
> It was hoped that the triangle filter would alleviate complaints about
> unintended category switching,
> and so far it has done so.
I'm afraid not. Here comes yet another complaint about unint
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #25 from Forest ---
Created attachment 160376
--> https://bugs.kde.org/attachment.cgi?id=160376&action=edit
Kickoff from Plasma 5.27.5, patched with configurable sidebar position
I feel strongly that this should be configurabl
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #26 from Forest ---
*both Plasma 5.27 and Plasma 6.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443082
Forest changed:
What|Removed |Added
Attachment #160376|Kickoff from Plasma 5.27.5, |draft: Kickoff from Plasma
description|patched
https://bugs.kde.org/show_bug.cgi?id=417615
--- Comment #15 from Forest ---
(In reply to Bernd Steinhauser from comment #14)
> I'd say the better fix would be to [...]
> instead provide a systemd user unit that starts kdeconnect.
Not everyone uses, or even wants, systemd. (Or linu
https://bugs.kde.org/show_bug.cgi?id=425557
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #4 from Forest ---
I
https://bugs.kde.org/show_bug.cgi?id=425557
--- Comment #5 from Forest ---
Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 6.0.0-0.deb11.6-amd64
Graphics Processor: AMD Radeon RX 480 Graphics
--
You are
https://bugs.kde.org/show_bug.cgi?id=426937
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=422111
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448797
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=85624
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #7 from Forest ---
Yes
https://bugs.kde.org/show_bug.cgi?id=383404
Forest changed:
What|Removed |Added
CC||fores...@sonic.net
--- Comment #3 from Forest
https://bugs.kde.org/show_bug.cgi?id=371130
Forest changed:
What|Removed |Added
CC||forestc...@ixio.org
--- Comment #10 from Forest
https://bugs.kde.org/show_bug.cgi?id=451978
--- Comment #5 from Forest ---
I haven't had a chance to test this. Please don't auto-close it.
(FWIW, I strongly dislike auto-close bots in issue trackers.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451978
Forest changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=401846
Bug ID: 401846
Summary: Unhandled instruction bytes: 0x48 0xF 0xC7 0xF1 0x73
0x14 0x48 0x89
Product: valgrind
Version: 3.11.0
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=401846
--- Comment #1 from Forest Rouse ---
Looks like the stack trace is from grpc:
==2889== valgrind: Unrecognised instruction at address 0xabefcc.
==2889==at 0xABEFCC: ??? (in
/home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0
https://bugs.kde.org/show_bug.cgi?id=401846
--- Comment #2 from Forest Rouse ---
==2889== valgrind: Unrecognised instruction at address 0xabefcc.
==2889==at 0xABEFCC: ??? (in
/home/forest/.cache/bazel/_bazel_forest/fed0d7792e44cc42f318618a90761ed0/execroot/__main__/bazel-out/k8-opt/bin/ui/pe
https://bugs.kde.org/show_bug.cgi?id=401846
--- Comment #3 from Forest Rouse ---
Created attachment 116728
--> https://bugs.kde.org/attachment.cgi?id=116728&action=edit
Valgrind log file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401846
Forest Rouse changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #5 from Forest Rouse
77 matches
Mail list logo
