https://bugs.kde.org/show_bug.cgi?id=457141
chazzy changed:
What|Removed |Added
Version Fixed In||5.27
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=457141
chazzy changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #13 from chazzy ---
Took a bit
https://bugs.kde.org/show_bug.cgi?id=457141
chazzy changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #11 from chazzy ---
(In reply to
https://bugs.kde.org/show_bug.cgi?id=457141
chazzy changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=463619
--- Comment #4 from chazzy ---
(In reply to Vlad Zahorodnii from comment #3)
> Git commit f8e036be315c63a8b1646c4e93a000674da41187 by Vlad Zahorodnii.
> Committed on 24/01/2023 at 09:18.
> Pushed by vladz into branch 'cherry
https://bugs.kde.org/show_bug.cgi?id=463619
Bug ID: 463619
Summary: [Regression] Unable to change desktop resolution
beyond natively supported resolutions on Wayland
Classification: Plasma
Product: KScreen
Version: 5.26.4
https://bugs.kde.org/show_bug.cgi?id=457141
--- Comment #6 from chazzy ---
Hmm, one possible factor not considered is that this bug affects my laptop
which uses Nvidia Prime. It has both an igpu and dedicated gpu. Specifically, a
gtx1660 ti. I'm not the specifics of the others though.
--
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #10 from chazzy ---
(In reply to Nate Graham from comment #8)
> Yep.
It's been a while, and I think this should be revisited. I mean, looking at the
context, how could this not be a plasma issue? the wine version didn'
https://bugs.kde.org/show_bug.cgi?id=459238
chazzy changed:
What|Removed |Added
Resolution|UPSTREAM|FIXED
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #9 from chazzy ---
(In reply to Nate Graham from comment #8)
> Yep.
Ok. Well I believe you, but what could be affecting it? It worked before the
update, so I'm a bit confused I guess as to why it's not working anymore. Same
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #7 from chazzy ---
(In reply to Nate Graham from comment #6)
> If it dies on GNOME too, that rules out anything in our code. At this point
> I would recommend reporting the issue to the Electron folks, since it's
> failing in
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #5 from chazzy ---
(In reply to chazzy from comment #4)
> I'm gonna update my steps to reproduce to include xfce4 as a control since
> it works.
>
> 1. Have an up to date plasma workspace on X11 or wayland.
> 2. Hav
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #4 from chazzy ---
I'm gonna update my steps to reproduce to include xfce4 as a control since it
works.
1. Have an up to date plasma workspace on X11 or wayland.
2. Have an up to date wine-staging.
3. Run America's cardroom f
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #3 from chazzy ---
Ok. I did a little more testing. I can say that gnome3 has the same bug present
in it, but xfce4 works. I will also say that this bug is present on both X11
and wayland versions of Plasma. Furthmore, drkonqi can be
https://bugs.kde.org/show_bug.cgi?id=459238
--- Comment #2 from chazzy ---
(In reply to Nicolas Fella from comment #1)
> > I want to clarify that this is not a wine/proton issue. These applications
> > worked fine under the same wine/proton versions in previous plasma
> > ve
droom, Conan Exile's launcher all have the same issue)
3. Launch from desktop shortcut, gui wrapper(such as steam), or sh
script.(fails to open)
OBSERVED RESULT
Plasmashell error:
"Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: net.js:329
Sep 16 13:29:58 chazzy-aero15sa plasmashell[125
16 matches
Mail list logo
