https://bugs.kde.org/show_bug.cgi?id=497426
Raman Gupta changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=497426
Bug ID: 497426
Summary: Telephone links cannot be sent to the phone
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=496003
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--- Comment #2 from Raman
https://bugs.kde.org/show_bug.cgi?id=496773
--- Comment #1 from Raman Gupta ---
Also: the reason I created this as a clock widget issue is that KOrganizer
appears to sync with calendar quite quickly. However, even though KOrganizer
shows the correct events, the digital clock widget does not
https://bugs.kde.org/show_bug.cgi?id=397629
--- Comment #6 from Raman Gupta ---
I started getting this error recently, after an update and reboot to the
version shown below. Periodically over a period of about 4 hours, I would get
about 8 popups on the screen with the message in the OP. However
https://bugs.kde.org/show_bug.cgi?id=496773
Bug ID: 496773
Summary: Slow event synchronization in digital clock applet
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status
https://bugs.kde.org/show_bug.cgi?id=397629
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #46 from Raman Gupta ---
Just installed 6.2 on Fedora 40… works great! Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #100 from Raman Gupta ---
I've been beta testing early release versions of JetBrains IntelliJ IDEA IDE on
native Wayland. My experience with trying to use Window Rules for my IDEA IDE
windows completely failed. Many of the popup windows
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #42 from Raman Gupta ---
(In reply to Nate Graham from comment #41)
> https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/720
To summarize the reply from wireplumber upstream here:
* Description is upstream's intended f
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #39 from Raman Gupta ---
(In reply to Nate Graham from comment #38)
> You're saying you think this is a Wireplumber bug that they should fix
> rather than us working around it?
Whether identical nicks are an upstream problem or
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #33 from Raman Gupta ---
(In reply to Zastrix Arundell from comment #32)
> I've seen the commit and it does seem it would resolve this issue. Although
> I would personally prefer that the description were the default, rather than
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #31 from Raman Gupta ---
(In reply to David Roth from comment #30)
> Visually a source and a sink are already differentiated in the applet by a
> line separator splitting sinks and sources.
Ooh, I see the separator now. I completely
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #29 from Raman Gupta ---
(In reply to Harald Sitter from comment #28)
> Git commit eae94ed4f1eb62276fd27c4477347efe17127d90 by Harald Sitter.
> Committed on 31/08/2024 at 02:40.
> Pushed by sitter into branch 'master'.
https://bugs.kde.org/show_bug.cgi?id=429408
--- Comment #33 from Raman Gupta ---
Based on the output of
while sleep .1; do ps aux | grep slack | grep -v grep | grep magic; done
It appears that the magic links are still being created in upper case, and
being passed to the Slack command in lower
https://bugs.kde.org/show_bug.cgi?id=429408
--- Comment #32 from Raman Gupta ---
I don't know if its a change in KDE, Slack, or Chrome, but at least Slack links
open for me now.
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
K
https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #96 from Raman Gupta ---
(In reply to Raman Gupta from comment #94)
> (In reply to Nate Graham from comment #82)
> > FWIW, as a workaround while this feature remains unimplemented, you should
> > be able to use Window Rule
https://bugs.kde.org/show_bug.cgi?id=490050
Bug ID: 490050
Summary: Window rules present screens as opaque numeric values
Classification: Plasma
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=490049
Bug ID: 490049
Summary: [Feature] Make it possible to test window rules
Classification: Plasma
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=470107
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=481927
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=487658
--- Comment #26 from Raman Gupta ---
Same problem here. The node.description field is much better, but even that
isn't necessarily sufficient to distinguish between source and sink devices.
In the following output, `node.nick` is what is curr
https://bugs.kde.org/show_bug.cgi?id=487658
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=383555
--- Comment #35 from Raman Gupta ---
My issue is solved by running Yakuake on Wayland. Positioning is correct on all
3 monitors.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #94 from Raman Gupta ---
(In reply to Nate Graham from comment #82)
> FWIW, as a workaround while this feature remains unimplemented, you should
> be able to use Window Rules on Wayland to manually force windows to appear
> where
https://bugs.kde.org/show_bug.cgi?id=401053
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=476370
Raman Gupta changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=476370
--- Comment #1 from Raman Gupta ---
Created attachment 162763
--> https://bugs.kde.org/attachment.cgi?id=162763&action=edit
Video of screen corruption
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476370
Bug ID: 476370
Summary: Rectangular region corrupts screen content: view seems
to be duplicated and shifted
Classification: Applications
Product: Spectacle
Version: 23.08.1
Pl
https://bugs.kde.org/show_bug.cgi?id=383555
--- Comment #34 from Raman Gupta ---
(In reply to Davide Cavestro from comment #33)
> (In reply to Raman Gupta from comment #32)
> > (In reply to Davide Cavestro from comment #31)
> > > Switching yakuake to full screen, it works on al
https://bugs.kde.org/show_bug.cgi?id=383555
--- Comment #32 from Raman Gupta ---
(In reply to Davide Cavestro from comment #31)
> Switching yakuake to full screen, it works on all monitors even if stacked
> vertically
Using full screen does not fix it for me. Still only shows on 2/3 mo
https://bugs.kde.org/show_bug.cgi?id=429408
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #81 from Raman Gupta ---
In https://bugs.kde.org/show_bug.cgi?id=470318#c1 Nate explained that X11 apps
are allowed to save and restore their own window positions. So I'm guessing
that this bug has been open for almost 23 years because
https://bugs.kde.org/show_bug.cgi?id=470318
--- Comment #2 from Raman Gupta ---
(In reply to Nate Graham from comment #1)
> Per the X11 spec, windows are allowed to place themselves on the screen--but
> they aren't required to. If a window doesn't, then KWin places it acc
https://bugs.kde.org/show_bug.cgi?id=470318
Bug ID: 470318
Summary: Wayland: window positioning lost on application
restart
Classification: Plasma
Product: plasmashell
Version: 5.27.4
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=461822
--- Comment #18 from Raman Gupta ---
Ok, so someone on Redditt found the root cause here by pointing me to
https://bugs.kde.org/show_bug.cgi?id=463527 -- my kscreen2 background service
was not running. I recalled I had disabled it some time ago because
https://bugs.kde.org/show_bug.cgi?id=469115
--- Comment #10 from Raman Gupta ---
Ok, so someone on Redditt found the root cause here by pointing me to
https://bugs.kde.org/show_bug.cgi?id=463527 -- my kscreen2 background service
was not running. I recalled I had disabled it some time ago because
https://bugs.kde.org/show_bug.cgi?id=461822
--- Comment #17 from Raman Gupta ---
Another problem which I suspect is related... I've been trying to switch over
to Wayland and have this issue on Wayland as well. Plus on Wayland I have
another problem, which is that the per-monitor scaling
https://bugs.kde.org/show_bug.cgi?id=469115
Raman Gupta changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=469115
--- Comment #6 from Raman Gupta ---
Also, any settings (such as Scale configuration) are lost for the monitor that
switches inputs.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469115
--- Comment #5 from Raman Gupta ---
In Wayland, starting output of `kscreen-doctor -a`:
Output: 1 DP-1 enabled connected priority 2 DisplayPort Modes: 0:3840x2160@60*!
1:3840x2160@60 2:3840x2160@60 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25
6
https://bugs.kde.org/show_bug.cgi?id=469115
Raman Gupta changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=469115
Raman Gupta changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=361623
--- Comment #14 from Raman Gupta ---
(In reply to Nate Graham from comment #13)
> That sounds like something different. Would be best to get a new bug report
> for it, especially if it's consistently reproducible.
It is consistently reprodu
https://bugs.kde.org/show_bug.cgi?id=469115
Bug ID: 469115
Summary: Notification positioning becomes "lost" if the primary
monitor switches off temporarily
Classification: Plasma
Product: plasmashell
Version: 5.27.4
Pla
https://bugs.kde.org/show_bug.cgi?id=361623
--- Comment #12 from Raman Gupta ---
Nate, in my case I found that notifications would be misplaced after my primary
monitor turned off for a moment (for example, when switching inputs). The
notifications went back to normal after switching the primary
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Version|5.27.3 |5.27.4
--- Comment #16 from Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=446349
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Version|5.27.0 |5.27.3
--- Comment #15 from Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=361623
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--- Comment #10 from Raman
https://bugs.kde.org/show_bug.cgi?id=383555
--- Comment #29 from Raman Gupta ---
One other detail: when opening on the left monitor, yakuake opens according to
my settings: horizontally centered. But when opening on the middle monitor,
yakuake opens horizontally left-aligned to screen edge, and
https://bugs.kde.org/show_bug.cgi?id=383555
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--- Comment #28 from Raman
https://bugs.kde.org/show_bug.cgi?id=461822
--- Comment #14 from Raman Gupta ---
Here is the new `kscreen-doctor -o` output with my new hardware:
Output: 84 DisplayPort-0 enabled connected priority 2 DisplayPort Modes:
89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30
93
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Version|5.26.5 |5.27.0
--- Comment #13 from Raman Gupta ---
So
https://bugs.kde.org/show_bug.cgi?id=462307
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Version|5.26.2 |5.26.5
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Ever confirmed|0 |1
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=461927
--- Comment #4 from Raman Gupta ---
(In reply to Nate Graham from comment #3)
> Better now?
Yep.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461927
--- Comment #2 from Raman Gupta ---
(In reply to Nate Graham from comment #1)
> Right now filtering is per-screen. So you have to move focus over to the
> other screen if you want to filter the windows on that screen.
I'm not sure this
https://bugs.kde.org/show_bug.cgi?id=455974
Raman Gupta changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=461927
Raman Gupta changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=461927
Bug ID: 461927
Summary: Present windows: cannot select windows on non-active
monitors with typing and keyboard
Classification: Plasma
Product: kwin
Version: 5.26.2
Platform: F
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=461822
--- Comment #9 from Raman Gupta ---
(In reply to Nate Graham from comment #7)
> Thanks. There's probably a bug in the detection algorithm that's causing it
> to incorrectly take into account the connector name when it doesn't need
https://bugs.kde.org/show_bug.cgi?id=461822
--- Comment #6 from Raman Gupta ---
Created attachment 153812
--> https://bugs.kde.org/attachment.cgi?id=153812&action=edit
Display Configuration view
Attached a view of the Display Configuration kcm, with the monitor models and
serial
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=461822
--- Comment #5 from Raman Gupta ---
(In reply to Nate Graham from comment #4)
> Ok, so the problem is that the display connector ID that KScreen thinks each
> screen is connected to is reversing on login. On one boot, your intended
> primar
https://bugs.kde.org/show_bug.cgi?id=461822
Raman Gupta changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=407519
--- Comment #5 from Raman Gupta ---
(In reply to Nate Graham from comment #3)
> Raman, can you also open a new bug report with your issue?
Done so here: https://bugs.kde.org/show_bug.cgi?id=461822.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=461822
Bug ID: 461822
Summary: Primary display setting does not persist
Classification: Plasma
Product: KScreen
Version: 5.25.5
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=455974
--- Comment #21 from Raman Gupta ---
(In reply to Kirby from comment #19)
> This is still an issue where a search a for an application via Present
> Windows finds the window after filtering on the other monitor but is unable
> to select it us
https://bugs.kde.org/show_bug.cgi?id=403563
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--- Comment #16 from Raman
https://bugs.kde.org/show_bug.cgi?id=450068
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=456210
--- Comment #45 from Raman Gupta ---
On 5.25.4 with u2f PAM (Yubikey), not even the `unlock-sessions` workaround
worked. Doing unlock sessions just resulted in a black screen with a block
cursor moving and a random character in green on the screen. No
https://bugs.kde.org/show_bug.cgi?id=456210
--- Comment #44 from Raman Gupta ---
Same problem here, using u2f PAM with a Yubikey to login. Have 3 monitors,
using X11. Like other users, `/usr/lib/kscreenlocker_greet --testing` has the
same behavior.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=456210
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=455974
Raman Gupta changed:
What|Removed |Added
Version|5.25.2 |5.25.4
--- Comment #13 from Raman Gupta ---
Man
https://bugs.kde.org/show_bug.cgi?id=455974
--- Comment #10 from Raman Gupta ---
The other related behavior that has changed is that when doing "Toggle Present
Windows (Window class)", it used to show all the windows, but only if they were
on the same desktop.
i.e.: old (and I
https://bugs.kde.org/show_bug.cgi?id=455974
--- Comment #9 from Raman Gupta ---
Same problem here on:
Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.3
Kernel Version: 5.18.11-200.fc36.x86_64 (64-bit)
Graphics Platform: X11
This is a
https://bugs.kde.org/show_bug.cgi?id=455974
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=407519
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--- Comment #2 from Raman
https://bugs.kde.org/show_bug.cgi?id=455066
--- Comment #6 from Raman Gupta ---
Please make sure this handles the use case I mentioned in
https://bugs.kde.org/show_bug.cgi?id=456681 in which multiple screens are
turned off and on in a very short period of time, which might cause multiple
screen
https://bugs.kde.org/show_bug.cgi?id=456681
Bug ID: 456681
Summary: Kscreen is too eager with changing display
configuration and moving windows around
Product: KScreen
Version: 5.25.2
Platform: Other
OS: Lin
https://bugs.kde.org/show_bug.cgi?id=453280
--- Comment #13 from Raman Gupta ---
(In reply to Raman Gupta from comment #11)
> On Fedora, kded appears to run via systemd user unit, so the "right" way to
> do it appears to be :
>
> systemd --user restart plasma-kded
https://bugs.kde.org/show_bug.cgi?id=453280
--- Comment #11 from Raman Gupta ---
(In reply to kdebugs from comment #8)
> (In reply to Mikiya Okuno from comment #7)
> > The problem is really irritating. I have to restart my machine every time
> > when the session is running out. Si
https://bugs.kde.org/show_bug.cgi?id=453280
--- Comment #5 from Raman Gupta ---
I believe the issue is more related to monitors going into a power-saving mode
rather than the screen locking -- 5 connections were leaked this morning when
my monitors were woken up, but before the lock screen
https://bugs.kde.org/show_bug.cgi?id=453280
--- Comment #4 from Raman Gupta ---
Just FYI -- my leak *might* also be related to the lock screen and/or monitors
sleeping, but the behavior on my machine seems to be different than with Phil
Hord -- using the same script as in comment #2, with the
https://bugs.kde.org/show_bug.cgi?id=453280
Bug ID: 453280
Summary: kded5 leaks X-Window connections: Maximum number of
clients reached
Product: frameworks-kded
Version: 5.91.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=396359
--- Comment #30 from Raman Gupta ---
The crash (at least the one reported in dup issue
https://bugs.kde.org/show_bug.cgi?id=446993) no longer happens for me on:
Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.2
KDE Frameworks Version
https://bugs.kde.org/show_bug.cgi?id=444742
--- Comment #13 from Raman Gupta ---
The crash (at least the one reported in dup issue
https://bugs.kde.org/show_bug.cgi?id=446993) no longer happens for me on:
Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.2
KDE Frameworks Version
https://bugs.kde.org/show_bug.cgi?id=440825
--- Comment #11 from Raman Gupta ---
(In reply to George Diamantopoulos from comment #10)
> i.e. in my case, hovering over an xwayland window is not enough.
Do you have "Focus follows mouse" enabled? My Window activation policy is
"F
https://bugs.kde.org/show_bug.cgi?id=444742
--- Comment #11 from Raman Gupta ---
(In reply to burneddi from comment #10)
> It still crashes for me even though it runs as a systemd service. Not every
> time, but maybe 70% of the time when my monitors wake up.
I can confirm this as well. I
https://bugs.kde.org/show_bug.cgi?id=357288
Raman Gupta changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=440825
--- Comment #8 from Raman Gupta ---
Same thing here. Interestingly, it does work when the mouse hovers over a
window rendered via XWayland. However, windows rendered by Wayland (or mouse
over the desktop) do not affect the Yakuake window placement
https://bugs.kde.org/show_bug.cgi?id=440825
Raman Gupta changed:
What|Removed |Added
CC||rocketra...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=444742
--- Comment #9 from Raman Gupta ---
(In reply to burneddi from comment #7)
> at least on Fedora the easiest way to restart Plasmashell is with "systemctl
> --user restart plasma-plasmashell"
On Fedora, is this a new approach to run
https://bugs.kde.org/show_bug.cgi?id=444742
--- Comment #8 from Raman Gupta ---
I have a multi-monitor setup also. 3 monitors, all the same resolution. 2/3 are
a different model than the other (though same brand, Dell). In my case the
monitors do wake up at different times as well, though in my
https://bugs.kde.org/show_bug.cgi?id=444742
--- Comment #5 from Raman Gupta ---
One piece of important information, at least in my case, is that the crash
happens when my monitors wake up, not at the actual login.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446993
Raman Gupta changed:
What|Removed |Added
Status|NEEDSINFO |REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=446993
--- Comment #2 from Raman Gupta ---
Created attachment 144584
--> https://bugs.kde.org/attachment.cgi?id=144584&action=edit
Result of `thread apply all backtrace` after SEGFAULT
I have attached the result of `thread apply all backtrace` af
1 - 100 of 194 matches
Mail list logo
