| Summary: | Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine. | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Keith Finnie <keith.finnie> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.4 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
result #1 of coredumpctl
coredumpctl result #2 coredumpctl gdb 2017.txt coredumpctl gdb 1291.txt attachment-13824-0.html coredump1.txt coredump2.txt attachment-11839-0.html attachment-13421-0.html |
||
|
Description
Keith Finnie
2022-07-15 06:50:19 UTC
Are you using the Wayland session, or the X11 session? if you're using Wayland, then KWin crashed. If you're using X11, then the X server crashed. In either case, we'll need a backtrace of the relevant process (kwin_wayland or xorg). You can probably use the command-line `coredumpctl` utility to retrieve it, and paste the contents here. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Created attachment 150691 [details]
result #1 of coredumpctl
as per instructions.
Created attachment 150692 [details]
coredumpctl result #2
as per instructions.
Coredumps provided. Created attachment 150693 [details] coredumpctl gdb 2017.txt Hi Nate, I attached two files with coredumpctl results to the ticket. I've also attached them to this email. Keith On Fri, 15 Jul 2022 at 13:15, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > Severity|normal |crash > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Are you using the Wayland session, or the X11 session? if you're using > Wayland, > then KWin crashed. If you're using X11, then the X server crashed. > > In either case, we'll need a backtrace of the relevant process > (kwin_wayland or > xorg). You can probably use the command-line `coredumpctl` utility to > retrieve > it, and paste the contents here. See > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > > -- > You are receiving this mail because: > You reported the bug. Created attachment 150694 [details]
coredumpctl gdb 1291.txt
Relevant parts:
> Stack trace of thread 2017:
> #0 0x00007f2f1429c176 n/a (KSC_XRandR.so + 0xc176)
> #1 0x00007f2f1429c409 n/a (KSC_XRandR.so + 0xc409)
> #2 0x00005648002a4b63 n/a (kscreen_backend_launcher + 0x5b63)
> #3 0x00005648002a5611 n/a (kscreen_backend_launcher + 0x6611)
Unfortunately this is missing symbols. Can you install debug symbols for the kscreen package, reproduce the crash, and attach a new backtrace? Thanks!
Created attachment 150751 [details] attachment-13824-0.html Can you advise on the command I use to install debug symbols for kscreen package? Thx, Keith On Tue, 19 Jul 2022 at 08:40, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Product|systemsettings |KScreen > Assignee|plasma-bugs@kde.org |kscreen-bugs-null@kde.org > Resolution|WAITINGFORINFO |BACKTRACE > Component|general |common > > --- Comment #7 from Nate Graham <nate@kde.org> --- > Relevant parts: > > > Stack trace of thread 2017: > > #0 0x00007f2f1429c176 n/a (KSC_XRandR.so + 0xc176) > > #1 0x00007f2f1429c409 n/a (KSC_XRandR.so + 0xc409) > > #2 0x00005648002a4b63 n/a (kscreen_backend_launcher + > 0x5b63) > > #3 0x00005648002a5611 n/a (kscreen_backend_launcher + > 0x6611) > > Unfortunately this is missing symbols. Can you install debug symbols for > the > kscreen package, reproduce the crash, and attach a new backtrace? Thanks! > > -- > You are receiving this mail because: > You reported the bug. Instructions can be found at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 Created attachment 150914 [details] coredump1.txt Hi Nate, I followed the instructions on the link you provided (to the best of my ability). The dumps are attached. Keith On Wed, 20 Jul 2022 at 06:54, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > --- Comment #9 from Nate Graham <nate@kde.org> --- > Instructions can be found at > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 > > -- > You are receiving this mail because: > You reported the bug. Created attachment 150915 [details]
coredump2.txt
OK, it looks like specifically kscreen_backend_launcher is crashing. I'm afraid we need even more debug symbols, but we're on the right track! Can you install debug symbols for kscreen and get a new backtrace? Thanks! Created attachment 151032 [details] attachment-11839-0.html Hi Nate, I'm getting the following error when trying to sudo apt update to get debug symbols: keith@Studio-One:~$ sudo apt update Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://apt.insync.io/ubuntu jammy InRelease Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:5 http://ddebs.ubuntu.com jammy InRelease Hit:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Ign:7 http://ddebs.ubuntu.com jammy-updates InRelease Hit:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Ign:9 http://ddebs.ubuntu.com jammy-security InRelease Ign:10 http://ddebs.ubuntu.com jammy-proposed InRelease Get:11 http://ddebs.ubuntu.com jammy Release [40.4 kB] Hit:12 http://ddebs.ubuntu.com jammy-updates Release Err:14 http://ddebs.ubuntu.com jammy-security Release 404 Not Found [IP: 91.189.91.49 80] Get:16 http://ddebs.ubuntu.com jammy-proposed Release [40.5 kB] Reading package lists... Done E: The repository 'http://ddebs.ubuntu.com jammy-security Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Keith On Tue, 26 Jul 2022 at 08:00, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > --- Comment #12 from Nate Graham <nate@kde.org> --- > OK, it looks like specifically kscreen_backend_launcher is crashing. I'm > afraid > we need even more debug symbols, but we're on the right track! Can you > install > debug symbols for kscreen and get a new backtrace? Thanks! > > -- > You are receiving this mail because: > You reported the bug. Created attachment 151033 [details] attachment-13421-0.html After installing the latest system updates (I do this every day), the problem is resolved. Thanks! Keith On Sun, 31 Jul 2022 at 12:07, Keith Finnie <keith.finnie@gmail.com> wrote: > Hi Nate, > > I'm getting the following error when trying to sudo apt update to get > debug symbols: > > keith@Studio-One:~$ sudo apt update > Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease > Hit:2 http://apt.insync.io/ubuntu jammy InRelease > > Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease > > > Hit:4 http://archive.ubuntu.com/ubuntu jammy InRelease > > Ign:5 http://ddebs.ubuntu.com jammy InRelease > Hit:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease > Ign:7 http://ddebs.ubuntu.com jammy-updates InRelease > Hit:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease > Ign:9 http://ddebs.ubuntu.com jammy-security InRelease > Ign:10 http://ddebs.ubuntu.com jammy-proposed InRelease > Get:11 http://ddebs.ubuntu.com jammy Release [40.4 kB] > Hit:12 http://ddebs.ubuntu.com jammy-updates Release > Err:14 http://ddebs.ubuntu.com jammy-security Release > 404 Not Found [IP: 91.189.91.49 80] > Get:16 http://ddebs.ubuntu.com jammy-proposed Release [40.5 kB] > Reading package lists... Done > E: The repository 'http://ddebs.ubuntu.com jammy-security Release' does > not have a Release file. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > > Keith > > On Tue, 26 Jul 2022 at 08:00, Nate Graham <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=456741 >> >> --- Comment #12 from Nate Graham <nate@kde.org> --- >> OK, it looks like specifically kscreen_backend_launcher is crashing. I'm >> afraid >> we need even more debug symbols, but we're on the right track! Can you >> install >> debug symbols for kscreen and get a new backtrace? Thanks! >> >> -- >> You are receiving this mail because: >> You reported the bug. > > OK great, thanks for following up! |