https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #41 from Sebastian E. ---
No, it needs to be done in preparation.
All commands except the last one are for building the modified pulseaudio-qt
binary (i.e. with extra logging). You only need to do that once, unless some
other dependencies
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #29 from Sebastian E. ---
Uhm... not really. I only tested each case twice yesterday, and got the
presumed result each time. Today I repeated each case 5 times and only got the
presumed result 3 out of 5 times. So it's something els
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #28 from Sebastian E. ---
@Eugene:
You posted the specs of an "old test notebook" where you do *not* have the
issue. I'd like to know the specs of the affected workstation (the video looks
like there are some professional aud
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #21 from Sebastian E. ---
Updating from Fedora 40 to 41 also involves updating from Kernel 6.10 to
6.11.1. I'll try downgrading my kernel when I find a reliable way to reproduce
it. It's quite random and I don't play a
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #19 from Sebastian E. ---
Does it always happen? For me volume keys are working normally until they
suddenly don't. Volume is then stuck between what it was +/- 5%.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #17 from Sebastian E. ---
Created attachment 174389
--> https://bugs.kde.org/attachment.cgi?id=174389&action=edit
Audio volume popup with duplicated devices
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #16 from Sebastian E. ---
Created attachment 174388
--> https://bugs.kde.org/attachment.cgi?id=174388&action=edit
Audio volume popup with duplicated devices
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #15 from Sebastian E. ---
@Eugene Savitsky: I already tried restarting pipewire.service as well as
pipewire-pulse.service, but it doesn't help. In fact, it might trigger the
issue.
@Harald Sitter:
I think only logging the name might n
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #6 from Sebastian E. ---
Is there any way to restart the audio volume control? Restarting plasmashell
doesn't seem to help.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493990
Bug ID: 493990
Summary: App crashes immediately with SecurityException
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Android
OS: Android 14.x
https://bugs.kde.org/show_bug.cgi?id=493962
--- Comment #2 from Sebastian E. ---
Oh, and Linux 6.10.10 -> 6.11.1.
I'm not absolutely sure, but I think I first encountered the issue after the
kernel update, and not during the 3 or 4 days between Pipewire/Qt updates and
kernel update.
--
https://bugs.kde.org/show_bug.cgi?id=493962
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=15329
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--- Comment #99 from
https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #96 from Sebastian E. ---
Is there a follow-up issue for the underlying cause, i.e. the deleted windows
that shouldn't exist in the first place? Those which are presumably caused by
any of the window open/close animations?
--
Yo
https://bugs.kde.org/show_bug.cgi?id=481736
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #75 from Sebastian E. ---
Thanks, vm, for keeping digging and figuring this out!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #65 from Sebastian E. ---
Unfortunately, that bug will probably be resolved as duplicate of
https://youtrack.jetbrains.com/issue/JBR-6921, which is already resolved as
third-party problem.
I reproduced the issue using the method
https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #48 from Sebastian E. ---
And "xev -root", at least on X11.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #47 from Sebastian E. ---
The output of "xwininfo -root -all" could be useful. But you need to check it
for personal information, it contains Window titles.
By the way, there's an issue at the Jetbrains issue trac
https://bugs.kde.org/show_bug.cgi?id=483162
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=478556
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482899
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=450268
--- Comment #11 from Sebastian E. ---
(In reply to guimarcalsilva from comment #10)
> The right thing to do here is to fix the speed factor of the animation in
> the code so it has the same speed as all other animations. If it's too slow
&g
https://bugs.kde.org/show_bug.cgi?id=450268
--- Comment #9 from Sebastian E. ---
(In reply to guimarcalsilva from comment #8)
> If there's a problem with the animation itself, then that should be fixed
> instead of leaving it up to the user to work around the issue by manually
&g
https://bugs.kde.org/show_bug.cgi?id=450268
--- Comment #7 from Sebastian E. ---
Premik said that the last pixels take too long to scroll. That's the effect of
easing, not a bug. The animation slows down towards the end. Windows that
overflow to another screen are indeed invisible on that s
https://bugs.kde.org/show_bug.cgi?id=450268
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=452782
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443723
--- Comment #8 from Sebastian E. ---
Yet another feature dropped. :/
I skimmed through the scripting documentation
(https://develop.kde.org/docs/extend/plasma/scripting/api/), and need some
hints. How can I register a listener for window events like
https://bugs.kde.org/show_bug.cgi?id=449842
Bug ID: 449842
Summary: Snap helper no longer displays window geometry
Product: kwin
Version: 5.24.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Seve
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #26 from Sebastian E. ---
KSysGuard and KDE System Monitor are system utilities, and as such should first
and foremost display system information as it is. Any processing that helps to
better dig through and display that information is a
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #19 from Sebastian E. ---
What about k10temp? I have a Pie Chart System Monitor Sensor in my bottom panel
which used to display Tctl, until it unfortunately stopped working after an
update. I left it there, hoping it would work again after
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #16 from Sebastian E. ---
(In reply to Felipe Kinoshita from comment #15)
> Sure, also why you don't make this change, seems like you have been studying
> this code a lot recently, just create a merge request and I can take a l
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #14 from Sebastian E. ---
@Felipe Kinoshita
Could you please revert or fix your commit that broke it?
https://invent.kde.org/plasma/plasma-workspace/-/commit/6befb657dd9fd811160e0369913d769cfff7f02d
Your commit reintroduced a change that
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #12 from Sebastian E. ---
Wondering why it crashes in PopupProxy::parent(), and not in
KlipperPopup::rebuild()... Calling methods on null objects may work until
"this" is actually accessed, which doesn't happen before Pop
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #11 from Sebastian E. ---
Alignment at bottom is not sufficient to reproduce the issue. There also must
be no screen at the top left of the virtual geometry.
https://invent.kde.org/plasma/plasma-workspace/-/blob
https://bugs.kde.org/show_bug.cgi?id=438318
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #4 from Sebastian E. ---
Also, my secondary left display is smaller than my primary right display and
aligned to the bottom. When I align the left screen to the top, it works, too.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #3 from Sebastian E. ---
Probably only happens with multiple displays.
Workaround:
* Disable secondary display (or all except one).
* Invoke shortcut. Plasma will crash once, but then it will work. Just
restarting Plasma would probably do
https://bugs.kde.org/show_bug.cgi?id=438277
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--- Comment #2 from
39 matches
Mail list logo
