[systemsettings] [Bug 426627] Ability re-arrange existing virtual desktops

2024-03-14 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=426627

Vishal Subramanyam  changed:

   What|Removed |Added

 CC||vishalsubramanyam@outlook.c
   ||om

--- Comment #12 from Vishal Subramanyam  ---
+1 for interest

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep

2023-09-15 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=448866

Vishal Subramanyam  changed:

   What|Removed |Added

 CC||vishalsubramanyam@outlook.c
   ||om

--- Comment #12 from Vishal Subramanyam  ---
I'm facing the same issue on the following system:
Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-32-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz
Memory: 15.4 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 473983] New: Setting NVIDIA PRIME OFFLOAD in startup script causes black screen

2023-08-31 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=473983

Bug ID: 473983
   Summary: Setting NVIDIA PRIME OFFLOAD in startup script causes
black screen
Classification: Plasma
   Product: kwin
   Version: 5.27.7
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: vishalsubraman...@outlook.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

STEPS TO REPRODUCE
1.  Set up the following environment variables in a KWin startup script
export __NV_PRIME_RENDER_OFFLOAD=1
export __VK_LAYER_NV_optimus=NVIDIA_only
export __GLX_VENDOR_LIBRARY_NAME=nvidia
2.  Start plasma on wayland


What was my objective in doing this? I have an Optimus setup with NVIDIA and
Intel graphics. On Wayland, I wanted to use NVIDIA as primary GPU. There was no
option for doing this. Instead, the prime-run script is the only option for
launching individual programs on the GPU. The script essentially sets the above
variables before starting a program. So I thought I could do the same in a KWin
script, so that anything spawned after that uses the NVIDIA GPU for offloading.


OBSERVED RESULT
Black screen with a mouse cursor appears. Can open applications using keyboard
shortcuts (for example, Konsole using Ctrl+Alt+T), and can start other
applications from Konsole. Application windows are visible, but everything else
is black.

EXPECTED RESULT
A functioning desktop with all the panels, wallpapers, etc.

Operating System: Arch Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.12-arch1-1 (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 450915] [wayland / nvidia proprietary] - dock does not appear

2023-02-27 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=450915

Vishal Subramanyam  changed:

   What|Removed |Added

 CC||vishalsubramanyam@outlook.c
   ||om

--- Comment #13 from Vishal Subramanyam  ---
I'm facing this on 5.27, with Wayland, NVIDIA proprietary drivers (525).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 465115] Firefox hangs when windows are placed in different virtual desktops while using NVIDIA-specific hardware acceleration in Firefox on Wayland

2023-02-13 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=465115

--- Comment #5 from Vishal Subramanyam  ---
I will file a report with NVIDIA.
But I also think this bug might be affecting Xorg, not just Wayland. I'm trying
to use Brave browser on Xorg, and when I have multiple Brave windows open on
multiple desktops, GUI events such as scrolling, etc, are not displayed to the
user immediately. I have to move the mouse around or something to get the GUI
to be redrawn. This happens until I bring the Brave windows back to the same
desktop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 465115] Firefox hangs when windows are placed in different virtual desktops

2023-02-04 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=465115

--- Comment #2 from Vishal Subramanyam  ---
I have narrowed down this issue to NVIDIA-specific hardware acceleration in
Firefox on Wayland. Happens only when I use NVIDIA as my primary GPU.
This is related to hardware acceleration. 
This issue does NOT occur in the following situations.
1. When I disable hardware acceleration in Firefox
2. When I use hardware acceleration but with the primary GPU set as Intel
integrated graphics.

When I set NVIDIA as my primary GPU by using the following env variable:
KWIN_DRM_DEVICES="/dev/dri/card1:/dev/dri/card0",
this issue occurs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 465115] Firefox hangs when windows are placed in different virtual desktops

2023-02-04 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=465115

--- Comment #1 from Vishal Subramanyam  ---
Happens only in Wayland, not in X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 465115] Firefox hangs when windows are placed in different virtual desktops

2023-02-01 Thread Vishal Subramanyam
https://bugs.kde.org/show_bug.cgi?id=465115

Vishal Subramanyam  changed:

   What|Removed |Added

 CC||vishalsubramanyam@outlook.c
   ||om

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 465115] Firefox hangs when windows are placed in different virtual desktops

2023-02-01 Thread Vishal Subramanyam Rajesh
https://bugs.kde.org/show_bug.cgi?id=465115

Vishal Subramanyam Rajesh  changed:

   What|Removed |Added

 OS|All |Linux

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 465115] New: Firefox hangs when windows are placed in different virtual desktops

2023-02-01 Thread Vishal Subramanyam Rajesh
https://bugs.kde.org/show_bug.cgi?id=465115

Bug ID: 465115
   Summary: Firefox hangs when windows are placed in different
virtual desktops
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Kubuntu
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: vishalsubraman...@outlook.com
  Target Milestone: ---

SUMMARY
Kubuntu 22.10 - Plasma 5.26.5 - If I have multiple Firefox windows, and if I
place some of them in a different virtual desktop, Firefox hangs until I bring
back all windows to the same virtual desktop.

STEPS TO REPRODUCE
1. Create two different virtual desktops
2. Open two Firefox windows in the same virtual desktop.
3. Move one of them to another virtual desktop by using Overview without
changing your current virtual desktop.
4. Switch to the other desktop to the shifted Firefox window, you'll observe
the Firefox window does not respond to mouse clicks, keyboard events, etc
5. Switch back to the original desktop and you'll observe the same with the old
one.
6. Move both Firefox windows to the same virtual desktop, and they start
working again. The keyboard and mouse events that were made during the hang
were actually executed, the GUI didn't reflect the changes until they were
brought to the same Virt. Desktop

OBSERVED RESULT
Firefox windows hang, don't respond visually to keyboard and mouse event until
all of them are brought to the same virtual desktop.

EXPECTED RESULT
Firefox windows function normally even when placed in different virtual
desktops.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.10
(available in About System)
KDE Plasma Version:  5.26.5
KDE Frameworks Version:  5.101.0
Qt Version: 5.15.6

-- 
You are receiving this mail because:
You are watching all bug changes.