[Bug 2006590] Re: gdm3 crashes with SIGTRAP on startup

[Allen]

*** This bug is a duplicate of bug 1717878 ***
https://bugs.launchpad.net/bugs/1717878

  sudo apt install --reinstall ubuntu-session

worked for me as well

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2006590

Title:
  gdm3 crashes with SIGTRAP on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006590/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Allen]

Got it, thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060575

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Allen]

Same issue here. I don't understand the status, "Won't fix"?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060575

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060743] [NEW] crashed when it started wiiting files to disk, displayed install.py stopped unexpectedly. I

[Allen Boehm]

Public bug reported:

The ssd I was attempting to install had a fresh win 10 installed and
updated. This is a brand new system, I used memory and ssd's from the
old system.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.20
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.470.2
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 16:34:27 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060743

Title:
  crashed when it started wiiting files to disk, displayed install.py
  stopped unexpectedly. I

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2060743/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random whole system lockups on Lenovo ThinkStation P350 Tiny

[Allen]

Should I still submit logs?

I think I'll just buy a new PC w/o NVIDIA and re-purpose this one...

Here is the latest

Lockup 070244 - SSL not avail

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5758328/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random whole system lockups on Lenovo ThinkStation P350 Tiny

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

I see the status change of the bug. Did the logs finally show anything?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

17:15:47 - SSL not avail

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5757691/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Got it. Testing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

9:14:36 No SSL Possible. Attached.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5756414/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Trying to upload the latest file. It's 1.3 G


Uh oh!
Something has gone wrong. We're sorry!

If we are in the middle of an update, Launchpad will be back in a couple
of minutes. Otherwise, we are working to fix the unexpected problems.
Check @launchpadstatus on Twitter or @launchpadstatus@ubuntu.social on
Mastodon for updates.

If the problem persists, let us know in the #launchpad IRC channel on
libera.chat.

Technically, the load balancer took too long to connect to an
application server.

Reload this page or try again in a few minutes

No one on Launchpad chat responds to me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

I'm not sure how to do this:

"drm.debug=0xff loglevel=8"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Came in this morning and it was locked up. NO SSH.

Going to move back to 6.5

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755959/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

What kernel do you suggest.
Disabling NVIDA isn't an option. I need all 4 monitors.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

130538 full lockup, no ssh available.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755711/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

110230 - Locked up, but instead of staying locked up the desktop crashed
and took me to the login screen.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755691/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

uname -r
5.19.17-051917-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Still lockups- No ssh
18:08:04 attached

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755386/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Ok, running 6.8.

uname -r
6.8.0-060800rc7-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Newest or a specific one?

Never locks up if I run Windows and passes all hardware testing
(repeated testing for overnight/ several passes)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Should I continue to report this? Is there anything else?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Ssh works fine until it freezes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

And another. Crash at 85128

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754304/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Here is the latest crash file.
Unresponsive - even trying ssh won't work

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754028/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

I am running the x.org X server Nouveau display driver now. I will
advise.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Use x.org X server Nouveau dissplay drivers?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Latest lockup - 14:22:51
Non responsive k/b & mouse
Can't SSH in after the computer locked up.

It's 100% locked up.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5753901/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Will do.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

11:51:05 is latest crash.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5753421/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

8:06:14 was time of crash.

I ran the commands.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

I spoke too soon. Here is the latest file. I will continue with your
instructions now.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5753367/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

The mouse freezes as well.

Currently, I am using 545 proprietary. So far I have 18:48 of uptime. I
am going to continue to run to see if it crashes before deleting
extensions. I'll report back.

Of course in the meantime there have also been some small updates as
well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

4:49:41 with NVIDIA 545 Driver (open kernel)


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752838/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

BIOS Update didn't resolve anything.

New lockup at 21:13:20

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752677/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Looks like there is a new BIOS available for this PC. I updated to
M3JKT3DA/1.0.0.61.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

19:31:51

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752648/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

19:27

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752647/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

18:44:29
Sadly, issue persists.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752623/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

In UBUNTU IRC Chat two things were suggested:
Uninstall Brave Browser
Disable hardware acceleration on Firefox browser. (The browser I am using).

I was using Chrome and had tried disabling hardware acceleration on it
to troubleshoot. That didn't help which is why I switched to Firefox.

It never locks up when I am not using the PC. Only when I am using it.
In other words, I never come into the office from it being on overnight
and finding it locked up.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

18:13:11

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752622/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

1724 / 1725

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752611/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

11:51:23
Attached file

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752524/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Is any of this helpful? Is there anything else I can do? (Other than
buying a new computer without an NVIDIA card!?!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

17:45 or 17:46. I didn't get the exact time.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752214/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Ubuntu on Wayland still crashes. I have tried various different versions
of the NVIDIA drivers before and it makes no difference. Here is another
prevboot.txt file.

Lockup at 17:50:44

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5751748/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Unplugging the 4 TB HD didn't stop the freezes.
Now running Ubuntu on Wayland.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Ok, I have unplugged the WD 4TB drive.

I am going to be having surgery tomorrow so you may not hear back from
me for a couple of days. As soon as I can report back I will. Thanks for
your help.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

And another...

16:27:38
I waited over 30 seconds.
I pressed ALT + PrtSc + S several times.

Here is the log.

Still nothing in /var/crash


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749883/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

16:11:59
I waited over 30 seconds.
I pressed ALT + PrtSc + S several times.

Here is the log

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749882/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

I can try that, however, every time it has locked up in the past, it is
100% unresponsive. I have run extensive hardware diagnostics and nothing
is wrong. I ran Windows just to test things and no lockups. So it's for
sure something not 100% compatible with Linux.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

1 - 14:38:34
2 - Done
3 - Done
4 - Attached - See above
5 - /var/crash is empty

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749577/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054121] Re: Random Freezing

[Allen]

Prevboot

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749206/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121

Title:
  Random Freezing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054932] [NEW] Xorg freeze

[Allen]

Public bug reported:

Random freezes

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 25 10:28:36 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-24 (1 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=3ea98830-6da6-49cf-b34a-00412e832e62 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze mantic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054932

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2054932/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054882] [NEW] Xorg freeze

[Allen]

Public bug reported:

Nothing more. Just freezes all the time.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 09:37:57 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-24 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=3ea98830-6da6-49cf-b34a-00412e832e62 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze mantic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054882

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2054882/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973093] [NEW] xmessage loses text area as buttons are added and -g

[Ian! D. Allen]

Public bug reported:

xmessage text gets obscured with option combinations using buttons and
geometry specifications.

Quick background: xmessage creates a new grey window with a white text
box inside it.  Without -buttons, the white text box usually spans the
full width of the grey window that contains it, leaving no margins.
Things start going wrong when you start specifying -buttons or -g
(geometry), and text can end up being obscured.

Problem #1:

If the width of all the buttons you specify makes the grey window wider
than the text, the white text box does not increase in width to match.
You end up with an undesirable wide grey margin on the right side of the
white text box.  If you resize the window, making it less wide, the grey
margin does not narrow; it moves in and covers and obscures the text,
even though there is plenty of room for the text.

Suggested Fix #1: The white text box must always be created the same width
as the window that contains it, with no useless grey margin to the right.
Narrowing the width of the window should not cause text to be obscured
by a wide and useless fixed grey margin.

Reproduce:

xmessage -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20
"123456789"

Problem #2:

If you add a -g (geometry) option and specify just the width (not the
height) for a window with buttons wider than the text box, the obscuring
grey margin persists.

If you add a "-g NNN" option, where NNN is the width that xmessage would
have chosen itself, then you get exactly the same unpleasant behaviour
as Problem #1 above.

If you increase the NNN to be wider that what xmessage would have used,
then both the window and the text box width are created increased by
that amount, as if you had resized the window with a mouse.  The useless
grey margin to the right of the text box stays the same width, just as
in Problem #1.

If you decrease the NNN to be narrower that what xmessage would have used,
then both the window and the text box width are created decreased by that
amount, as if you had resized the window with a mouse.  Not all buttons
will show; this is expected.  What is not expected is that the useless
grey margin to the right of the text box stays the same width, and so
it now overwrites and obscures the text, even though there is plenty
of room for the text.  If you resize the window back so that all the
buttons show, all the text also shows and we're back to Problem #1 above.

Suggested Fix #2: Same as above.

Reproduce (width 541 is my xmessage chosen width for font "fixed"):

xmessage -g 400 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"
xmessage -g 541 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"
xmessage -g 700 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"

Problem #3:

If you add a -g option and specify both the width *and* the height for
a window with buttons wider than the text, things get much worse.

If you add a "-g NNNx55" option, where NNN is the width that xmessage
would have chosen itself and "55" is about the same height, you would
expect to get exactly the same results as if you didn't specify any
geometry at all.  That's not what happens.  You get a fixed-width text
window about 12 characters wide, with a huge grey margin on the right.
It doesn't matter what size text you specify; the white text box will be
created about 12 characters wide and any text to the right of that will
be masked and obscured by the wide grey margin.  Changing the width of
the window has all the problems of Problems #1 and #2 above.

Suggested Fix #3: Same as above.
Specifying a geometry that is identical to what xmessage would have chosen
itself should create an identical window.  Text should not be obscured.

Reproduce (width 541 is my xmessage chosen width for font "fixed"):

xmessage -g 541x55 -buttons
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789-123 YOU
DON'T SEE THIS"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: x11-utils 7.7+5build2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 17:12:52 2022
DistUpgraded: 2022-04-04 16:21:26,723 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.5, 5.15.0-29-generic, x86_64: installed
 v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated 
Graphics Controller [10cf:15f5]
InstallationDate: Installed on 2020-09-08 (610 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 

[Bug 1971750] Re: lsusb shows wrong/duplicate product name

[Ian! D. Allen]

This bug is fixed in the GIT repository at
https://github.com/gregkh/usbutils

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971750

Title:
  lsusb shows wrong/duplicate product name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbutils/+bug/1971750/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971750] [NEW] lsusb shows wrong/duplicate product name

[Ian! D. Allen]

Public bug reported:

lsusb incorrectly labels a device using the product name from a previous
device.

In the listing below, the incorrect product name on the second 04d8:fee9
device ("Microsoft® LifeCam HD-5000") is a copy of the product name
of the first device in the list:

$ lsusub -s 3:

Bus 003 Device 002: ID 045e:076d Microsoft Corp. LifeCam HD-5000
Bus 003 Device 009: ID 090c:6300 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Kingston  Reader
Bus 003 Device 007: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 019: ID 04d8:fee9 Microchip Technology, Inc.
Bus 003 Device 011: ID 04d8:fee9 Microchip Technology, Inc. Microsoft® 
LifeCam HD-5000
Bus 003 Device 006: ID 03eb:0902 Atmel Corp. 4-Port Hub
Bus 003 Device 013: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Device 04d8:fee9 is not a Microsoft device.

Below is a verbose listing of the device that displays the wrong product
name.  You can see that "Microsoft" doesn't appear anywhere in the
verbose listing, except incorrectly on the title line.  Perhaps lsusb is
forgetting to clear the product title string before listing each device,
so a device that is busy or doesn't report a string gets a previous
device's string?

$ lsusb -v -s 3:11

Bus 003 Device 011: ID 04d8:fee9 Microchip Technology, Inc. Microsoft® 
LifeCam HD-5000
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass 0
  bDeviceProtocol   255
  bMaxPacketSize0 8
  idVendor   0x04d8 Microchip Technology, Inc.
  idProduct  0xfee9
  bcdDevice1.00
  iManufacturer   1 Clearly Open
  iProduct2 PengAlert module
  iSerial 3 1
  bNumConfigurations  2
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0012
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  4 Default
bmAttributes 0xc0
  Self Powered
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  4 (error)
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0020
bNumInterfaces  1
bConfigurationValue 2
iConfiguration  5 (error)
bmAttributes 0xc0
  Self Powered
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  4 (error)
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0020
bNumInterfaces  1
bConfigurationValue 2
iConfiguration  5 (error)
bmAttributes 0xc0
  Self Powered
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  5 (error)
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch 

[Bug 1969959] Re: Weird colors after startup (Ubuntu 22.04)

[Allen Lowe]

I'm having the same issue with an RTX 2080. If I start up in safe
graphics mode, it works. But of course then I get degraded graphics.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969959

Title:
  Weird colors after startup (Ubuntu 22.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968735] [NEW] App shuts down completely on any keystroke while the app has focus

[Chris Allen]

Public bug reported:

Apr 12 14:55:05 desktoppc systemd[10265]: 
snap.slack.slack.d05ba551-36a5-48a1-b9c7-e694c5e1256d.scope: Failed to add PIDs 
to scope's control group: Permission denied
Apr 12 14:55:05 desktoppc systemd[10265]: 
snap.slack.slack.d05ba551-36a5-48a1-b9c7-e694c5e1256d.scope: Failed with result 
'resources'.
Apr 12 14:55:05 desktoppc systemd[10265]: Failed to start 
snap.slack.slack.d05ba551-36a5-48a1-b9c7-e694c5e1256d.scope.
Apr 12 14:55:05 desktoppc kernel: [1128006.058742] audit: type=1400 
audit(1649771705.589:43735): apparmor="DENIED" operation="rmdir" 
profile="snap.slack.slack" name="/media/bigdrive/Music/" pid=13492 comm="rmdir" 
requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
Apr 12 14:55:05 desktoppc kernel: [1128006.150002] audit: type=1400 
audit(1649771705.681:43736): apparmor="DENIED" operation="open" 
profile="snap.slack.slack" name="/home/folder/.config/font-manager/conf.d/" 
pid=13518 comm="slack" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Apr 12 14:55:05 desktoppc kernel: [1128006.150019] audit: type=1400 
audit(1649771705.681:43737): apparmor="DENIED" operation="open" 
profile="snap.slack.slack" name="/home/folder/.config/font-manager/select.conf" 
pid=13518 comm="slack" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Apr 12 14:55:05 desktoppc kernel: [1128006.151302] audit: type=1400 
audit(1649771705.681:43738): apparmor="DENIED" operation="open" 
profile="snap.slack.slack" 
name="/home/folder/.local/share/font-manager/Library/" pid=13518 comm="slack" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Apr 12 14:55:05 desktoppc kernel: [1128006.151347] audit: type=1400 
audit(1649771705.681:43739): apparmor="DENIED" operation="open" 
profile="snap.slack.slack" 
name="/home/folder/.local/share/font-manager/Library/" pid=13518 comm="slack" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Apr 12 14:55:05 desktoppc kernel: [1128006.151359] audit: type=1400 
audit(1649771705.681:43740): apparmor="DENIED" operation="open" 
profile="snap.slack.slack" 
name="/home/folder/.local/share/font-manager/Library/" pid=13518 comm="slack" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Apr 12 14:55:05 desktoppc kernel: [1128006.155384] audit: type=1326 
audit(1649771705.685:43741): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
pid=13518 comm="slack" exe="/snap/slack/61/usr/lib/slack/slack" sig=0 
arch=c03e syscall=330 compat=0 ip=0x7fc8555304e7 code=0x5
Apr 12 14:55:06 desktoppc kernel: [1128006.552145] audit: type=1400 
audit(1649771706.081:43742): apparmor="DENIED" operation="open" 
profile="snap.slack.slack" name="/etc/" pid=13518 comm="slack" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 12 14:55:06 desktoppc kernel: [1128006.559533] audit: type=1326 
audit(1649771706.089:43743): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
pid=13518 comm="slack" exe="/snap/slack/61/usr/lib/slack/slack" sig=0 
arch=c03e syscall=92 compat=0 ip=0x7fc85551f3b7 code=0x5
Apr 12 14:55:06 desktoppc kernel: [1128006.639815] audit: type=1107 
audit(1649771706.169:43744): pid=1559 uid=105 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=13518 label="snap.slack.slack"
Apr 12 14:55:06 desktoppc kernel: [1128006.639815]  exe="/usr/bin/dbus-daemon" 
sauid=105 hostname=? addr=? terminal=?'
Apr 12 14:55:06 desktoppc dbus-daemon[10397]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="ListActivatableNames" mask="send" 
name="org.freedesktop.DBus" pid=13518 label="snap.slack.slack" 
peer_label="unconfined"
Apr 12 14:55:06 desktoppc gnome-shell[10625]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.3835/org/ayatana/NotificationItem/Slack1
Apr 12 14:55:09 desktoppc gnome-shell[10625]: [AppIndicatorSupport-WARN] 
Attempting to re-register :1.3835/org/ayatana/NotificationItem/Slack1; 
resetting instead
Apr 12 14:55:09 desktoppc gnome-shell[10625]: [AppIndicatorSupport-WARN] Item 
:1.3835/org/ayatana/NotificationItem/Slack1 is already registered
Apr 12 14:55:09 desktoppc gnome-shell[10625]: [AppIndicatorSupport-FATAL] 
unable to lookup icon for Slack1_1
Apr 12 14:55:09 desktoppc gnome-shell[10625]: [AppIndicatorSupport-FATAL] 
unable to lookup icon for Slack1_1
Apr 12 14:55:09 desktoppc gnome-shell[10625]: [AppIndicatorSupport-WARN] 
Attempting to re-register :1.3835/org/ayatana/NotificationItem/Slack1; 
resetting instead
Apr 12 14:55:09 desktoppc gnome-shell[10625]: [AppIndicatorSupport-WARN] Item 
:1.3835/org/ayatana/NotificationItem/Slack1 is already registered
Apr 12 14:55:10 desktoppc gnome-shell[10625]: [AppIndicatorSupport-FATAL] 
unable to lookup icon for Slack1_3
Apr 12 14:55:13 desktoppc kernel: [1128013.860999] kauditd_printk_skb: 14 
callbacks suppressed
Apr 

[Bug 1967824] [NEW] using --reduce-factor disables --except

[Ian! D. Allen]

Public bug reported:

This is a bug in both version `1.0.4` and version `1.0.5_master`.
See https://github.com/firehol/iprange/issues/31

First, set up two test files:

~
$ cat out
$ iprange in --diff out
1.2.3.4/31
1.2.3.6
~

Using any value of `--reduce-factor` causes the `--except` to be
ignored:

~
$ iprange in --except except --reduce-factor 0 >out
$ iprange in --diff out
$ iprange in --except except --reduce-factor 10 >out
$ iprange in --diff out
$ iprange in --except except --reduce-factor 90 >out
$ iprange in --diff out
$ diff in out
$
~

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iprange 1.0.4+ds-2
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Apr  5 00:37:04 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (544 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: iprange
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: iprange (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967824

Title:
  using --reduce-factor disables --except

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iprange/+bug/1967824/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

I am not arguing about the behaviour, which is correct and apparently hasn't 
changed.
I'm complaining about the unannounced change in message from "is uptodate" to 
"is newer".

Three problems:

1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is uptodate".  My scripts that look for "is
newer" are all broken, because now every file is flagged as newer, even
when the file is not newer.

2. I expect that a name flagged as "is newer" will be transferred when I
remove the --update option, and that does not happen because the file is
*NOT* newer; the message is wrong and no transfer happens.

3. The message changes with and without the --update option.  If rsync
says "is uptodate" without the --update option, why does that change to
"is newer" when you add the option?  Either the file is newer *OR* it is
uptodate; it can't be both.  Adding the --update option should not
change "is uptodate" to "is newer".  It is not newer; don't say it is.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965076

Title:
  rsync --update incorrectly reports file "is newer" than itself

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965076] [NEW] rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

Public bug reported:

rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be "is uptodate" in all cases.
This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

$ touch foo
$ rsync -avv --update foo .
delta-transmission disabled for local transfer or --whole-file
foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
total: matches=0  hash_hits=0  false_alarms=0 data=0
sent 38 bytes  received 96 bytes  268.00 bytes/sec
total size is 0  speedup is 0.00

$ rsync -avv foo .
delta-transmission disabled for local transfer or --whole-file
foo is uptodate  <=== THIS IS CORRECT
total: matches=0  hash_hits=0  false_alarms=0 data=0
sent 41 bytes  received 106 bytes  294.00 bytes/sec
total size is 0  speedup is 0.00

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: rsync 3.2.3-4ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 15 22:47:44 2022
InstallationDate: Installed on 2022-03-16 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: rsync (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965076

Title:
  rsync --update incorrectly reports file "is newer" than itself

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.

[Ian! D. Allen]

Description:Ubuntu 20.04.4 LTS
Linux linux 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

Mar 11 10:43:28 linux kernel: [1.578010] usb usb6: We don't know the 
algorithms for LPM for this host, disabling LPM.
Mar 11 10:43:28 linux kernel: [1.578061] usb usb6: New USB device found, 
idVendor=1d6b, idProduct=0003, bcdDevice= 5.13
Mar 11 10:43:28 linux kernel: [1.578066] usb usb6: New USB device strings: 
Mfr=3, Product=2, SerialNumber=1
Mar 11 10:43:28 linux kernel: [1.578070] usb usb6: Product: xHCI Host 
Controller
Mar 11 10:43:28 linux kernel: [1.578074] usb usb6: Manufacturer: Linux 
5.13.0-35-generic xhci-hcd
Mar 11 10:43:28 linux kernel: [1.578077] usb usb6: SerialNumber: 
:08:00.0
Mar 11 10:43:28 linux kernel: [1.578207] hub 6-0:1.0: USB hub found
Mar 11 10:43:28 linux kernel: [1.578223] hub 6-0:1.0: 4 ports detected

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804592

Title:
  usb usb2: We don't know the algorithms for LPM for this host,
  disabling LPM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958005] [NEW] rsyslogd mishandles startswith_i against $programname

[Ian! D. Allen]

Public bug reported:

The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname.  Details follow:

Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):

if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}

Restart rsyslog:

# /etc/init.d/rsyslog restart

Run these four tests:

$ logger -t 'test' "This is: test"
$ logger -t 'foo' "This is: foo"
$ logger -t 'FOO' "This is: FOO"
$ logger -t '/junk' "This is /junk"

Expected and correct result:

The file /var/log/syslog contains three lines (correct):

Jan 14 23:08:09 ubuntu20 test: This is: test
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk

The file /var/log/idallen-cron.log contains just one line (correct):

Jan 14 23:08:09 ubuntu20 foo: This is: foo


Now make this change: In the 10-idallen.conf file change "startswith"
to "startswith_i".  Restart rsyslog.  Run the four tests.  Here are the
unexpected and incorrect results:

The file /var/log/syslog contains just one line (should be two):

Jan 14 23:08:09 ubuntu20 test: This is: test

The file /var/log/idallen-cron.log contains three lines (should be two):

Jan 14 23:08:09 ubuntu20 foo: This is: foo
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE

The '/junk' line should *NOT* be matched using "startswith_i 'foo'".

The same bug happens using '[junk' as the tag.  Any number of blanks
may precede the / or the [ character and still cause the bug.

$ logger -t '   /anything' "This also triggers the bug."
$ logger -t '   [anything' "This also triggers the bug."

The bug did not appear when matching against $syslogtag:

# This does not show the bug:
if ( $syslogtag startswith_i 'foo' ) then {
/var/log/idallen-cron.log
stop
}

I tried to use "startswith" and "startswith_i" to match against the
"$msg" instead of against "$programname" or "$syslogtag" but could not
get any match at all no matter what I used as my logger message text:

# This never matches anything:
if ( $msg startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rsyslog 8.2001.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 15 02:02:24 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (464 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logrotate.d.rsyslog: [modified]
mtime.conffile..etc.logrotate.d.rsyslog: 2020-12-27T12:21:35.307395

** Affects: rsyslog (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958005

Title:
  rsyslogd mishandles startswith_i against $programname

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1958005/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957863] [NEW] coding errors in update-motd-fsck-at-reboot script

[Ian! D. Allen]

Public bug reported:

The script /usr/lib/update-notifier/update-motd-fsck-at-reboot contains some 
coding errors.
One of the errors hides the other error:

1. It sets two variables NEEDS_FSCK_CHECK and NEED_FSCK_CHECK (missing
'S') but only checks one of them (NEEDS_FSCK_CHECK).  Because of this
error, the script doesn't always initialize the value of
NEEDS_FSCK_CHECK at the start of the script, so whatever value might
happen to be passed in from the environment of the script could force a
check even if the script would not itself do so.

Rename variable NEED_FSCK_CHECK to NEEDS_FSCK_CHECK and always run your
Bourne shell scripts with the "-u" (check for undefined variables)
option enabled:  #!/bin/sh -u

2. It sets the variables with values "no" and "yes", but *any* value set in the 
variables means "yes".  (It doesn't check that the value is actually "yes", so 
even "no" means "yes".)  Because of coding error #1, this coding error #2 has 
no effect on the script operation, so if you fix coding error #1 without fixing 
this one, the script will incorrectly always run.  You have to fix both.
Change:

if [ -n "$NEEDS_FSCK_CHECK" ]; then

to actually check for a "yes":

if [ "$NEEDS_FSCK_CHECK" = 'yes' ]; then

P.S. This script uses dumpe2fs that waits for all the disks on your
system to spin up, which can significantly delay an ssh login to your
system, as well as cause unnecessary wear on all your normally idle
disks since the script seems to run frequently.  If you don't like this
behaviour (and don't need the fsck information it generates), you can
render the script inactive by adding this line to /etc/crontab:

01 * * * * root f=/var/lib/update-notifier/fsck-at-reboot ; test -e
$f && touch $f

It would be nice if there were a cleaner way (perhaps something in
/etc/default/?) to disable all this disk-spin-up activity, but that
would be a different bug report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-notifier-common 3.192.30.10
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 13 23:40:37 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (463 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: update-notifier
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-10-08T05:49:47.646282

** Affects: update-notifier (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957863

Title:
  coding errors in update-motd-fsck-at-reboot script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1957863/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873920] Re: default vi on focal emits escape sequences unrecognized by bionic's terminal?

[Allen McIntosh]

Now that I think of it, that's qualitatively no different than running
"vim.tiny"...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873920

Title:
  default vi on focal emits escape sequences unrecognized by bionic's
  terminal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1873920/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873920] Re: default vi on focal emits escape sequences unrecognized by bionic's terminal?

[Allen McIntosh]

Workaround:

ex file

visual
("visual" can be abbreviated as "vi")

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873920

Title:
  default vi on focal emits escape sequences unrecognized by bionic's
  terminal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1873920/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1274320] Re: Error: diskfilter writes are not supported

[Allen Lee]

Confirmed on Ubuntu Focal (Kubuntu 20.04) installed on LVM disk, with
GRUB_SAVEDEFAULT=true

This bug triggers whenever a boot option other than the first is being
selected in the grub menu. grub won't be able to save that selection.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274320

Title:
  Error: diskfilter writes are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942063] Re: /usr/man symlink breaks apropos man -k due to fsstnd

[Ian! D. Allen]

If you could at least document what "/fsstnd" is (when the mandb man
page says FSSTND should use /var/catman not /fsstnd), and why /usr/man
and /usr/share/man are different and must look in different places in
the MANDB_MAP, then maybe the current behaviour wouldn't look like a bug
but a feature.  I don't know why /usr/man and /usr/share/man aren't
exactly the same in the manpath.config file; any documentation help you
can provide would make the current odd behaviour seem less odd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942063

Title:
  /usr/man symlink breaks apropos man -k due to fsstnd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1942063/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942063] [NEW] /usr/man symlink breaks apropos man -k due to fsstnd

[Ian! D. Allen]

Public bug reported:

In the old days, man pages were stored under /usr/man.  Now, they are
stored under /usr/share/man.  Ubuntu systems no longer have a /usr/man,
so all our really old scripts and reflexes that look under /usr/man fail
unless you think to add the helpful symlink "ln -s share/man /usr/man".

But making that helpful symlink breaks "apropos" and "man -k" because
in /etc/manpath.config are these two different locations for the "mandb" 
index database:

MANDB_MAP   /usr/man/var/cache/man/fsstnd
MANDB_MAP   /usr/share/man  /var/cache/man

If you add the symlink for /usr/man, then the index.db file created 
by "mandb" ends up under a sub-directory /var/cache/man/fsstnd where
"apropos" and "man -k" can't find it.

Of course you can add another helpful symlink "ln -s fsstnd/index.db 
/var/cache/index.db" to work-around the "apropos" problem, or you can
set your "MANPATH=/usr/man", but surely it doesn't need to be a problem
in the first place.

1. Please make "apropos" and "man -k" smarter.  Either they could look 
in both /var/cache/man and /var/cache/man/fsstnd, or else "mandb" could
resolve the symlink /usr/man to its absolute version /usr/share/man before
looking it up in the manpath.config file and thus not create the unhelpful
"/fsstnd" sub-directory that breaks "apropos".

2. The man page for "mandb" and the manpath.config file make no 
mention of the reason for the extra "/fsstnd" sub-directory.  The
manpath.config file says the "FHS compliant" index.db location should
be /var/cache/man/index.db and the "FSSTND compliant" location is under 
/var/catman  Either remove the mysterious "/fsstnd" or explain it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: man-db 2.9.1-1
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug 30 04:37:46 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (326 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: man-db
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: man-db (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942063

Title:
  /usr/man symlink breaks apropos man -k due to fsstnd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1942063/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942056] [NEW] /etc/cron.monthly/acct fails if wtmp not rolled monthly

[Ian! D. Allen]

Public bug reported:

The /etc/cron.monthly/acct cron script is run monthly by cron or anacron
to "perform monthly login accounting" with the /var/log/wtmp file.

The cron script only works correctly if the wtmp file is rolled exactly
monthly and gives errors otherwise.  Fixing the script to do monthly
accounting on a wtmp file that is rolled on a schedule other than monthly
is non-trivial, because as written, the cron script makes three invalid
assumptions:

1. That accounting is rolled over exactly monthly.

The actual number of days of account data being saved before rolling is
settable by the local sysadmin.  It could be any number of days, not only
a month.  If the number of days is shorter than a month, the cron script
will lose data and incorrectly under-report the monthly login accounting.
If the number of days is longer than a month, the cron script incorrectly
looks for the data in the rolled file name wtmp.1 or wtmp.1.gz instead
of in the actual wtmp file where it is still accumulating.

2. That the rolled accounting file is present as wtmp.1 or wtmp.1.gz

If the number of days of account data being saved before rolling is
longer than a month, then the file doesn't roll over on every month end 
and on a new system no rolled wtmp.1 or wtmp.1.gz file may exist when
the cron script runs and an error is generated about the missing file:

From: Anacron 
Subject: Anacron job 'cron.monthly'
/etc/cron.monthly/acct:
couldn't open file '': No such file or directory
last: cannot open : No such file or directory
  
The data is still accumulating in the /var/log/wtmp file and that is
where the cron script must look.

3. That only one month of accounting data is in the wtmp.1 or wtmp.1.gz
file.

The cron script assumes that only one exact month of accounting data are
saved in the rotated wtmp.1 or wtmp.1.gz file, because the cron script
processes the whole rotated file with no date range.  if log rolling is
longer one month (e.g. one year), then the current month's accounting data
will usually still be accumulating in the wtmp file, not in the wtmp.1 or
wtmp.1.gz file, and if the wtmp.1 or wtmp.1.gz file exists it will contain
more than a month worth of accounting (e.g. part or all of a year).
A begin and end date must be used to extract just the current month, and
the correct file name wtmp or wtmp.1 or wtmp.1.gz must be used to do it.

Fixing the above three problems in the cron script is non-trivial because
it will involve knowing the frequency of log rotation and then determining
whether the current month of accounting data are in the wtmp, wtmp.1,
or wtmp.1.gz files (or a combination, if log rolling is more frequent
than monthly) and using date ranges to extract just the current month.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: acct 6.6.4-2
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Aug 29 18:15:12 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (326 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: acct
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.acct: 2021-07-18T04:14:33.822817

** Affects: acct (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942056

Title:
  /etc/cron.monthly/acct fails if wtmp not rolled monthly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acct/+bug/1942056/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

[Ian! D. Allen]

I'm now getting radeon GPU lockup with the Ubuntu 5.11.0-25 and 5.11.0-27 
kernels.
The 5.8.0-63 kernel and all previous work fine.

$ lspci | grep ATI
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 
GL [FirePro 2450]
06:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 GL 
[FirePro 2450]

I use three (of four possible) 1600x1200 LCD monitors on the four
FirePro outputs.

Selected lines from /var/log/syslog are attached.  These are the actual
repeating lockup lines:

Aug 17 15:20:44 linux kernel: [ 7403.029720] radeon :06:00.0: GPU lockup 
(current fence id 0x0001 last fence id 0x0002 on ring 0)
Aug 17 15:20:44 linux kernel: [ 7403.541687] radeon :06:00.0: ring 0 
stalled for more than 11304msec

The last two lines "GPU lockup" and "ring 0 stalled" repeat over and
over.  The keyboard and the X11 display won't respond.  I can ssh into
the machine, and I can type "reboot", but it hangs somewhere in the
shutdown (or else it is waiting for something longer than I'm willing to
wait).  The system reboots when I type ALT-SYSRQ-B on the keyboard, and
I select the 5.8.0-63 kernel and everything is fine.


** Attachment added: "Selected drm and radeon lines from syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5518846/+files/radeon.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863390

Title:
  GPU lockup ring 0 stalled for more than X msec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937097] [NEW] atopacctd and atop break acct by moving pacct file

[Ian! D. Allen]

Public bug reported:

The Debian people tell me this bug was fixed Upstream six months ago.

Ubuntu 20.04 LTS systems have the atop/acct conflict problem where if
you install acct it wants the pacct file in one place
(/var/log/account/pacct) and then if you install atop it starts
atopacctd that decides it should be in a different place
(/run/pacct_source) and the two fight it out every time the accounting
reloads, making a real mess.

If you disable atopacctd to stop it from stealing the pacct file, then
if you ever run atop as root, atop itself will steal the pacct file and
start storing it in /var/cache/atop.d/atop.acct, because atop expects to
find the pacct file under /var/account/pacct and that directory doesn't
exist on Ubuntu, so atop thinks no accounting is in use and creates its
own location, breaking the acct package again.  Disabling atopacctd
isn't sufficient.

The Debian people tell me this bug was fixed Upstream six months ago.

Please install the Debian fix.

As a work-around on Ubuntu 20.04, I replaced /usr/sbin/atopacctd with a
"sleep d" script that will prevent it from ever grabbing the
accounting file (at least until the next atop package update), and I
made a symlink so that atop finds the Ubuntu accounting file and doesn't
itself grab the accounting file:

# ln -s log/account /var/account

Now atop and acct coexist on Ubuntu LTS, at least until the next package
update.

Reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=94

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: atop 2.4.0-3 [modified: usr/sbin/atopacctd]
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jul 21 10:43:28 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (286 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: atop
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: atop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937097

Title:
  atopacctd and atop break acct by moving pacct file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1937097/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716186] Re: log retention time period should not be hardcoded

[Ian! D. Allen]

In Ubuntu 20.04 LTS the script /etc/init.d/atop calls
/usr/share/atop/atop.daily which does read /etc/default/atop and uses
the variable LOGGENERATIONS=28.  Systemd
/usr/local/lib/systemd/system/atop.service also calls
/usr/share/atop/atop.daily.

Confusingly, the file /etc/default/atop says not to use it:

# /etc/default/atop
# this file is no longer used and will be removed in a future release

Someone who knows better needs to decide how and where these
configurable numbers should be set and either use the /etc/default/atop
file or remove the misleading comment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716186

Title:
  log retention time period should not be hardcoded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1716186/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937091] [NEW] ts -r does not parse all perl Date::Parse formats

[Ian! D. Allen]

Public bug reported:

"ts -r" does not recognize three of the eleven example formats given in
the man page for Perl Date::Parse.  In particular, it doesn't recognize
the standard ISO-8601 format "1995:01:24T09:08:17.1823213":

$ ts -r
1995:01:24T09:08:17.1823213
1995:01:24T09:08:17.1823213
1995-01-24T09:08:17.1823213
1995-01-24T09:08:17.1823213
1999 10:02:18 "GMT"
1999 10:02:18 "GMT"

$ man ts
...
  If the -r switch is passed, it instead converts existing timestamps in
  the input to relative times, such as "15m5s ago". Many common timestamp
  formats are supported. Note that the Time::Duration and Date::Parse
  perl modules are required for this mode to work.

$ man Date::Parse
...
EXAMPLE DATES
1995:01:24T09:08:17.1823213   ISO-8601
1995-01-24T09:08:17.1823213
...
1999 10:02:18 "GMT"

$ perl -w -e 'use Date::Parse; print str2time("1995:01:24T09:08:17.1823213"), 
"\n";'
790956497.182321

$ perl -w -e 'use Date::Parse; print str2time("1995-01-24T09:08:17.1823213"), 
"\n";'
790956497.182321

$ perl -w -e 'use Date::Parse; print str2time("1999 10:02:18 \"GMT\""),
 "\n";'
932551338

"ts -r" also doesn't recognize other simple date formats that are
recognized by Date::Parse, e.g.

$ ts -r
2000/01/02 03:04
2000/01/02 03:04
2000-01-02 03:04
2000-01-02 03:04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: moreutils 0.63-1
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jul 21 09:56:10 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (286 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: moreutils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: moreutils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937091

Title:
  ts -r does not parse all perl Date::Parse formats

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/moreutils/+bug/1937091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937019] [NEW] FIDO2 tokens not supported on this build

[Timothy Allen]

Public bug reported:

I'm trying to test systemd-cryptenroll with FIDO2 keys in the new
systemd version 248 on impish.

Running "systemd-cryptenroll --fido2-device=list" results in the
message:

FIDO2 tokens not supported on this build.

Would it be possible to build systemd with FIDO support in time for the
impish release?

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: systemd (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #991129
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991129

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991129
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937019

Title:
  FIDO2 tokens not supported on this build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85] Re: We need a way to publish translators' email address

[David Allen Arteaga]

** Changed in: launchpad
 Assignee: Carlos Perelló Marín (carlos) => (unassigned)

** Changed in: launchpad
 Assignee: (unassigned) => David Allen Arteaga (dirty-alpha-85)

** Also affects: ubuntu
   Importance: Undecided
   Status: New

** Also affects: ubuntu-leb
   Importance: Undecided
   Status: New

** Changed in: ubuntu
 Assignee: (unassigned) => David Allen Arteaga (dirty-alpha-85)

** Changed in: ubuntu-leb
 Assignee: (unassigned) => David Allen Arteaga (dirty-alpha-85)

** Also affects: sphinx
   Importance: Undecided
   Status: New

** Changed in: sphinx
 Assignee: (unassigned) => David Allen Arteaga (dirty-alpha-85)

** Changed in: ubuntu
   Status: New => Fix Released

** Changed in: ubuntu-leb
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/85

Title:
  We need a way to publish translators' email address

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/85/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930920] [NEW] gdb crashes connecting to remote session in layout split

[Donovan Allen]

Public bug reported:

release:
Description:Ubuntu 20.04.2 LTS  

 
Release:20.04 

gdb:
  Installed: 9.2-0ubuntu1~20.04
  Candidate: 9.2-0ubuntu1~20.04
  Version table:
 *** 9.2-0ubuntu1~20.04 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 9.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

GDB crashes when attempting to connect to a remote session while in
`layout split`. If I connect to the remote session first it works,
however if I already changed my view I get a core dump.

My steps to reproduce crash:
 - Run iso using `qemu-system-i386 -cdrom MyIso.iso -gdb tcp::26000 -S -monitor 
stdio`
 - open gdb in seperate tab
 - run `layout split`
 - run `target remote localhost:26000`
 - Crash

I was previously able to do this without crash using:
release:
Description:Ubuntu 18.04.5 LTS  

 
Release:18.04 

gdb:
  Installed: 8.1.1-0ubuntu1
  Candidate: 8.1.1-0ubuntu1
  Version table:
 *** 8.1.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 8.1-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930920

Title:
  gdb crashes connecting to remote session in layout split

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1930920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04

[Stephen Allen]

I wonder if the recent Gnome 3.38.5 update addresses this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922353

Title:
  Overview sometimes fails to appear or disappear in 21.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927725] Re: PID file no longer created

[Timothy Allen]

There seems to have been some issue during the upgrade that blocked the
creation of the PID file. Manually killing the exim process and re-
starting it seems to have fixed the issue.

Apologies for the noise!

** Changed in: exim4 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927725

Title:
  PID file no longer created

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1927725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927725] [NEW] PID file no longer created

[Timothy Allen]

Public bug reported:

Since the latest release, no PID file is created in /run/exim4/exim.pid
when Exim is run.

No local configuration changes have been made between the working and
non-working versions. The command line arguments are '/usr/sbin/exim4
-bd -q30m', and there are no PID-related configuration arguments set.

Setting SMTPLISTENEROPTIONS='-oP /run/exim4/exim.pid' in
/etc/default/exim produces the correct command-line arguments, but also
does not create the specified PID file.

I presume this is related to the fix for CVE-2020-28014: 'An attacker
who obtained the privileges of the "exim" user can abuse the -oP
override_pid_file_path option to create (or overwrite) an arbitrary
file, as root'.

If this new behaviour is intentional, then the documentation may need
updating.

This is on Ubuntu 20.04, exim version 4.93-13ubuntu1.5. Version
4.93-13ubuntu1.1 (released in May 2020) works correctly.

Thanks!

** Affects: exim
 Importance: Unknown
 Status: Unknown

** Affects: exim4 (Ubuntu)
 Importance: Undecided
 Status: New

** Bug watch added: bugs.exim.org/ #2738
   http://bugs.exim.org/show_bug.cgi?id=2738

** Also affects: exim via
   http://bugs.exim.org/show_bug.cgi?id=2738
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927725

Title:
  PID file no longer created

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1927725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1910688] [NEW] package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-kernel-common-460 package post-installation script subprocess returned error

[Allen Cotton]

Public bug reported:

sudo apt upgrade went not according to plan

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: nvidia-kernel-common-460 460.32.03-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jan  8 11:45:43 2021
ErrorMessage: installed nvidia-kernel-common-460 package post-installation 
script subprocess returned error exit status 127
InstallationDate: Installed on 2020-12-06 (32 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.1
SourcePackage: initramfs-tools
Title: package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.10.1 failed to 
install/upgrade: installed nvidia-kernel-common-460 package post-installation 
script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package groovy package-from-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910688

Title:
  package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.10.1 failed to
  install/upgrade: installed nvidia-kernel-common-460 package post-
  installation script subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1910688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Damn doesn't seem to be a close or delete option. Daniel could you
please do the honours?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Daniel I was pretty sure that the problem existed in my home directory. So, 
rather than go through all the gnome gnome settings one by one, with subsequent 
reboots, I cleaned out my home directory of all gnome specific settings at once 
this am, and rebooted and problem is gone - I'm now in XWayland.
 
This would have taken a long time to troubleshoot, so I took the quick route it 
was a Fool's errand to try to figure out which setting was creating the 
problem, because I have backed up my home directory for over 10 years 
continuously, and I had a lot of cruft in there, so it was time to clean it 
out.I'm going to close this bug now, thanks for all your help Daniel I didn't 
want to waste any more of your time. Cheers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Regarding Item #3: Didn't know /var/crash existed, thanks for the heads
up with the article too.

I browsed /var/crash, there are quite a few files (18) from yesterday
and today. Now none dated Jan 04 matched XWayland, however 2 from
yesterday. The more recent ones (Jan 04) mention 'Blueman Applet' only.
Do you want both? According to the article referenced, it seems to
indicate using ubuntu-bug to run on the most recent files in
/var/log/crash — were you meaning that I should do that in the future?
Anywho, will touch base in the morning EST.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Thanks Daniel, yes I meant a crash, just different wording.

OK Attached is the file with all extensions disabled. If I'm reading the
file correctly it seems to be a snap issue with an app not autostarting?
Anyway lots of errors but when I scrolled down to the bottom showing the
most recent boot up using XWayland, only two errors, relating to a snap
launch.

** Attachment added: "journalctl log file"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+attachment/5449337/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  Gnome Wayland session starts, then quits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909946] Re: XWayland session starts, then quits.

[Stephen Allen]

Some more details: Using both gnome-wayland & ubuntu-wayland sessions,
the common major errors are the following:

12:22:45 PM gnome-shell: Can't create a GtkStyleContext without a display 
connection
12:22:23 PM gdm-session-wor: gkr-pam: unable to locate daemon control file


It happens when the desktop appears after about maybe 10 seconds or so. So I 
can't see PAM being involved as PAM is invoked during login — isn't it?

Anyway hope this helps.

Oh, I reinstalled from a backup image, (I have the system on a separate
hard drive to my home directory) that was working correctly on Wayland.
And with nothing added to the image, the same behaviour happened. So,
I'm thinking this is probably a setting in my home directory — but which
one?

Suggestions to troubleshoot this are welcome — I'll put in the time to
help figure this out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  XWayland session starts, then quits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909946] [NEW] XWayland session starts, then quits.

[Stephen Allen]

Public bug reported:

So, this started about a week ago after an update from Ubuntu. I can
initially login with XWayland, but something loading after the desktop
appears, causes the session to exit. The only thing I can find relevant
in the logs at the timestamp this occurred are the following:

-gkr-pam: unable to locate daemon control file

-Failed to start Process error reports when automatic reporting is
enabled.

-A start job for unit UNIT has failed

I hope this helps track down the issue. Thanks for reading.

BTW I have to submit this as a bug on something else, launchpad keeps
telling me that XWayland doesn't exist.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xwayland 2:1.20.9-2ubuntu1.1
Uname: Linux 5.9.16-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan  3 19:33:28 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 
OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
InstallationDate: Installed on 2020-04-25 (253 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: groovy pam xwayland

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946

Title:
  XWayland session starts, then quits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908527] [NEW] Core Dumps

[Stephen Allen]

Public bug reported:

Since this is from the Universe repo, should I report this upstream
instead of here? Please advise. App was fine 24 hours ago, so recent
updates might have a bearing on this.

Running from a shell:

:~$ tootle
[INFO 08:17:28.652378] Application.vala:156: Tootle version: 0.2.0
[INFO 08:17:28.652391] Application.vala:158: Kernel version: 5.9.15-xanmod1
[INFO 08:17:28.665785] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 08:17:28.665865] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 08:17:28.667197] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 08:17:28.669197] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public:local
[INFO 08:17:28.670017] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public
[INFO 08:17:29.642091] Watchlist.vala:23: Reloading
[INFO 08:17:29.642104] Watchlist.vala:34: Watching for 0 users and 0 hashtags
**
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Bail out! 
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: tootle 0.2.0-2ubuntu1
Uname: Linux 5.9.15-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Dec 17 08:18:52 2020
InstallationDate: Installed on 2020-04-25 (235 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: tootle
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tootle (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy third-party-packages wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908527

Title:
  Core Dumps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tootle/+bug/1908527/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908025] [NEW] export var=~root does not expand ~root to /root

[Ian! D. Allen]

Public bug reported:

Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.

$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Dec 14 00:14:44 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (67 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dash (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908025

Title:
  export var=~root does not expand ~root to /root

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1908025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902938] [NEW] Tootle Core Dump

[Stephen Allen]

Public bug reported:

When run from terminal:

tootle
[INFO 14:53:00.814180] Application.vala:156: Tootle version: 0.2.0
[INFO 14:53:00.814200] Application.vala:158: Kernel version: 5.9.1-xanmod1
[INFO 14:53:00.826796] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 14:53:00.828244] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=user
[INFO 14:53:00.830316] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public:local
[INFO 14:53:00.831146] Notificator.vala:40: Starting: 
/api/v1/streaming/?stream=public
[INFO 14:53:01.828317] Watchlist.vala:23: Reloading
[INFO 14:53:01.828339] Watchlist.vala:34: Watching for 0 users and 0 hashtags
**
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Bail out! 
ERROR:../../src/API/NotificationType.vala:43:tootle_notification_type_from_string:
 code should not be reached
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: tootle 0.2.0-2ubuntu1
Uname: Linux 5.9.1-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Wed Nov  4 14:53:57 2020
InstallationDate: Installed on 2020-04-25 (192 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: tootle
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tootle (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902938

Title:
  Tootle Core Dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tootle/+bug/1902938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices

[Allen Gooch]

This problem persists with Ubuntu 20.10 released today.

The modprobe/rmmod/modprobe method above still works there, however it
is very inconvenient to have to perform those steps after each reboot.
Unfortunate, as Ubuntu has been the distro that I've used and
recommended to others for the last four years based on "it just works".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895202

Title:
  touchpad suddenly not detected, appearing as PS/2 mouse in devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884295] Re: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor'

[Todd Allen]

Seems we need that downstream too, then?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884295

Title:
  AttributeError: 'QWebEngineProfile' object has no attribute
  'setUrlRequestInterceptor'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1884295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

I'm using the distro version from Ubuntu Focal.

Actually the problem is solved up for me — Don't know when, (I don't use
manual directory scans often) but when running one last night, I didn't
have hidden items showing afterwards.

On Mon, Aug 17, 2020 at 6:05 AM Dave M <1876...@bugs.launchpad.net>
wrote:

> @Stephen Allen (stephen-d-allen),
>
> Are you using snaps or debs? I'm wondering if the snap structure is
> different and would account for you not having it in that location.
>
> Can you try something like:
>
> sudo dpkg -L clamtk
>
> Thanks,
> Dave M
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1876497
> <https://mailtrack.io/trace/link/d6aa519db0fa9e10714aa160478253f01323183a?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1876497=1758692=d4c2d6c9b3b1d783>
>
> Title:
>   clamtk scan checks ' Show Hidden Files ' checkbox automatically
>
> Status in ClamTk:
>   Confirmed
> Status in clamtk package in Ubuntu:
>   Confirmed
>
> Bug description:
>   every time i perform a ' Scan a directory ' scan via ClamTK the hidden
>   files in the Home folder become automatically visible.
>
>   the ' Show Hidden Files ' checkbox gets automatically checked.
>
>   am running 'buntu fossa 20.04.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/clamtk/+bug/1876497/+subscriptions
> <https://mailtrack.io/trace/link/a6827340b752b31934aecdb1113babb2645874fa?url=https%3A%2F%2Fbugs.launchpad.net%2Fclamtk%2F%2Bbug%2F1876497%2F%2Bsubscriptions=1758692=0aaafa3474ffdec0>
>


-- 
"It is through science that we prove, but through intuition that we
discover."

- Henri Poincare

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/clamtk/+bug/1876497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

Yeah ... not there either. I'll get back to it later on this evening.

On Sun, Aug 16, 2020 at 10:30 AM Dave M <1876...@bugs.launchpad.net>
wrote:

> Ok, on Ubuntu 18.04 it's this:
>
> /usr/share/perl5/ClamTk/
>
> I don't have 20.04 installed yet.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1876497
> 
>
> Title:
>   clamtk scan checks ' Show Hidden Files ' checkbox automatically
>
> Status in ClamTk:
>   Confirmed
> Status in clamtk package in Ubuntu:
>   Confirmed
>
> Bug description:
>   every time i perform a ' Scan a directory ' scan via ClamTK the hidden
>   files in the Home folder become automatically visible.
>
>   the ' Show Hidden Files ' checkbox gets automatically checked.
>
>   am running 'buntu fossa 20.04.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/clamtk/+bug/1876497/+subscriptions
> 
>


-- 
"It is through science that we prove, but through intuition that we
discover."

- Henri Poincare

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/clamtk/+bug/1876497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876497] Re: clamtk scan checks ' Show Hidden Files ' checkbox automatically

[Stephen Allen]

On Ubuntu LTS 20.04 I don't have that path - see screengrab. Thanks.


** Attachment added: "screengrab of my Perl5 directory"
   
https://bugs.launchpad.net/clamtk/+bug/1876497/+attachment/5401948/+files/Aug16-2020.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876497

Title:
  clamtk scan checks ' Show Hidden Files ' checkbox automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/clamtk/+bug/1876497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884295] Re: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor'

[Todd Allen]

I have also encountered this issue:

Parsing all content...
CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [9:11: $]
CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [16:12: $]
CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [18:12: $]
34% Running transforms on e-book...
Merging user specified metadata...
Detecting structure...
Flattening CSS and remapping font sizes...
Source base font size is 12.0pt
Removing fake margins...
Cleaning up manifest...
Trimming unused files from manifest...
Creating PDF Output...
67% Running PDF Output plugin
The cover image has an id != "cover". Renaming to work around bug in Nook Color
68% Parsed all content for markup transformation
70% Completed markup transformation
WebEngineContext used before QtWebEngine::initialize() or OpenGL context 
creation failed.
Traceback (most recent call last):
  File "/usr/bin/ebook-convert", line 20, in 
sys.exit(main())
  File "/usr/lib/calibre/calibre/ebooks/conversion/cli.py", line 401, in main
plumber.run()
  File "/usr/lib/calibre/calibre/ebooks/conversion/plumber.py", line 1274, in 
run
self.output_plugin.convert(self.oeb, self.output, self.input_plugin,
  File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line 
188, in convert
self.convert_text(oeb_book)
  File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line 
253, in convert_text
convert(
  File "/usr/lib/calibre/calibre/ebooks/pdf/html_writer.py", line 1195, in 
convert
manager = RenderManager(opts, log, container.root)
  File "/usr/lib/calibre/calibre/ebooks/pdf/html_writer.py", line 279, in 
__init__
ans.setUrlRequestInterceptor(self.interceptor)
AttributeError: 'QWebEngineProfile' object has no attribute 
'setUrlRequestInterceptor'

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884295

Title:
  AttributeError: 'QWebEngineProfile' object has no attribute
  'setUrlRequestInterceptor'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1884295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888073] [NEW] ubunt 20.4 lts desktop intaller crashed

[Allen L Malsbary Jr]

Public bug reported:

I was installing Ubuntu from usb stick and it crashed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
CasperVersion: 1.445
Date: Sat Jul 18 11:27:48 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888073

Title:
  ubunt 20.4 lts desktop intaller crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1888073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883484] [NEW] package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1

[Allen Carvallo]

Public bug reported:

Configuring phpmyadmin ├──┐
 │ │ 
 │ An error occurred while installing the database:  
 │   
 │ mysql said: ERROR 1819 (HY000) at line 1: Your password does not  
 │ satisfy the current policy requirements . Your options are:   
 │  * abort - Causes the operation to fail; you will need to 
 │ downgrade,
 │reinstall, reconfigure this package, or otherwise manually 
 │ intervene 
 │to continue using it. This will usually also impact your   
 │ ability to
 │install other packages until the installation failure is   
 │ resolved. 
 │  * retry - Prompts once more with all the configuration questions 
 │(including ones you may have missed due to the debconf priority
 │setting) and makes another attempt at performing the operation.
 │  * retry (skip questions) - Immediately attempts the operation
 │ again,
 │skipping all questions. This is normally useful only if you
 │ have  
 │solved the underlying problem since the time the error 
 │ occurred.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: phpmyadmin 4:4.9.5+dfsg1-2
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jun 12 21:54:35 2020
ErrorMessage: installed phpmyadmin package post-installation script subprocess 
returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: phpmyadmin
Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed 
phpmyadmin package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: phpmyadmin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883484

Title:
  package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade:
  installed phpmyadmin package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1883484/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1755305] Re: .xsession-errors filled with entries

[Todd Allen]

I am encountering the same issue in 20.04. The message is repeating
approximately every three seconds, resulting in log files of hundreds of
gigabytes. It also makes the system log nearly useless for any other
use; it is near-impossible to even open the file, and causes logrotate
to hang up for hours every time it attempts to run since it attempts
compression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755305

Title:
  .xsession-errors filled with entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1755305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1755305] Re: .xsession-errors filled with entries

[Todd Allen]

Example of errors:

Jun  1 18:27:41 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:29:47 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755305

Title:
  .xsession-errors filled with entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1755305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs