Follow-up: I don't think the bug report actually went through. I was never brought to the website like before.
Should I attempt to post a new bug for this, or did the request send through my user acc around the time I depicted steps and mentioned sending it? Sent with Proton Mail secure email. ------- Original Message ------- On Thursday, December 1st, 2022 at 11:38 PM, ke7in.dev <ke7in....@proton.me> wrote: > Side note: I hit ctrl+c to cancel terminal after and got this: > > ``` > ^CException ignored in: <module 'threading' from > '/usr/lib/python3.10/threading.py'> > > Traceback (most recent call last): > File "/usr/lib/python3.10/threading.py", line 1567, in _shutdown > lock.acquire() > KeyboardInterrupt: > ``` > > > > > Sent with Proton Mail secure email. > > > ------- Original Message ------- > On Thursday, December 1st, 2022 at 11:34 PM, ke7in.dev ke7in....@proton.me > wrote: > > > > > Steps to achieve hang (or crash on the 1st attempt, before updating system > > packages -- not sure if that's unrelated to the change in the behavior or > > not, but worth mentioning): > > > > 1. type 'ubuntu-bug' in konsole > > > > 2. click audio related > > > > 3. click "It's not listed here" > > > > 4. don't click "OK", click "Cancel" > > > > These are the same exact steps to achieve issue 3x now. > > > > This last time I did the commands on my 2nd system to the same effect. > > > > I ran "ubuntu-bug --hanging 4675" in the same konsole as the original req > > and my cursor went to a new line (that is blank, no pathnames) > > > > I checked the /var/crash folder and no new .crash files have been created. > > > > I followed up with the same command in a new konsole, bug report is being > > sent (YES!), however, this is on a different machine than the inital bug > > report, should I also run this bug report on the original? > > > > Sent with Proton Mail secure email. > > > > ------- Original Message ------- > > On Thursday, December 1st, 2022 at 12:35 PM, Benjamin Drung > > 1998...@bugs.launchpad.net wrote: > > > > > 1. I can confirm this behavior. You can run "ubuntu-bug <package>". If > > > > > > you want to suggest a different behavior, please open a separate bug > > > report for it. > > > > > > 2. Can you recreate the hang? Then run "ubuntu-bug --hanging <pid>" > > > > > > where <pid> is the process ID of the hanging ubuntu-bug. > > > > > > -- > > > You received this bug notification because you are subscribed to the bug > > > report. > > > https://bugs.launchpad.net/bugs/1998309 > > > > > > Title: > > > attempted to report a few of the bugs I'm experiencing using 22.10 > > > (I'm using on 2 machines)...and the bug reporter crashed when I tried > > > to exit / redo. > > > > > > Status in apport package in Ubuntu: > > > Incomplete > > > > > > Bug description: > > > 1. Ubuntu 22.10 (studio install) > > > > > > 2. 2.23.1-0ubuntu3 500 > > > > > > 3. I was on generic bug selection screen and picked the "best fitting" > > > one (konsole popped up 1319), but realized there were no great options > > > and went to 'x' it out to dig a little more... > > > > > > 4. crash. > > > > > > ProblemType: Bug > > > DistroRelease: Ubuntu 22.10 > > > Package: apport-kde 2.23.1-0ubuntu3 > > > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > > > Uname: Linux 5.19.0-1009-lowlatency x86_64 > > > ApportVersion: 2.23.1-0ubuntu3 > > > Architecture: amd64 > > > CasperMD5CheckResult: unknown > > > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > > > -0500:2022-11-30 02:13:35.548841973 > > > -0500:/var/crash/_usr_bin_avplayer.1000.crash > > > CurrentDesktop: KDE > > > Date: Wed Nov 30 03:11:50 2022 > > > InstallationDate: Installed on 2022-11-29 (0 days ago) > > > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > > > (20221017.1) > > > PackageArchitecture: all > > > SourcePackage: apport > > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
