[Bug 2066035] [NEW] KWM Switch causes logout

[Mark Smith]

Public bug reported:

I have a 2x1 KVM switch between my work laptop (win10) and my Ubuntu
24.04 (noble) desktop.

When I switch from Ubuntu to the work laptop - whether I have locked the
screen or not - the Ubuntu session logs me out.

I had originally thought it was rebooting the desktop, but using the
uptime command, I can see that the machine have been online since my
last manual reboot (this morning - I have rebooted a number of times
over the last few days to try to clear the issue).

Everything worked fine when the desktop was on Ubuntu 23.10.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 17 11:56:54 2024
InstallationDate: Installed on 2024-04-13 (34 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
SourcePackage: meta-gnome3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: meta-gnome3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

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

Title:
  KWM Switch causes logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2066035/+subscriptions


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

[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Mark Smith]

This bug affects me on 24.04 noble too.

It did not on 23.10.

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

Title:
  Artful (17.10) Session logout after screen turned off

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

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

This bug is back in 24.04 (noble).
Same issue - Set the keyboard to UK at install, but the keyboard used is US 
layout so special characters e.g. # & £ are transposed, and therefore doesn't 
work at first login.
(At least I could see the error now)

Tried on a Desktop install from the Beta, and also on a laptop install
using the full release.

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 2063961] [NEW] Microsoft 365 account keeps disconnecting

[Mark Smith]

Public bug reported:

When I use the new (24.04) settings and 'Online Accounts' to connect to 
Microsoft 365, it authenticates, works well for about 5 minutes and then 
disconnects.
I have to remove that account and redo it every time I want to use it.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-settings 24.04.3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 27 19:04:06 2024
InstallationDate: Installed on 2024-04-27 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
PackageArchitecture: all
SourcePackage: ubuntu-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

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

Title:
  Microsoft 365 account keeps disconnecting

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


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

Re: [Bug 1875062] Re: [20.04] Keyboard layout changes during installation before typing username/password

[Mark Smith]

Dag,

Can you confirm you mean 24.04 and not 22.04, please?

On Mon, 15 Apr 2024 at 17:25, Dag Bjerkeli <1875...@bugs.launchpad.net>
wrote:

> I've just tested this, and can confirm that there is a bug regarding
> keyboard layout in 22.04 beta. As this time the error also appears when
> you select the keyboard initially it could a new error.
>
> I also have a preview image of 22.04 dated mars 27th that does not have
> the error, even after updated installer.
>
>
> ** Attachment added: "Entering æøå after selecting Norwegian keyboard does
> not show correct keys"
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+attachment/5765721/+files/not%20norwegian%20in%20install.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1875062
>
> Title:
>   [20.04] Keyboard layout changes during installation before typing
>   username/password
>
> Status in Release Notes for Ubuntu:
>   Fix Released
> Status in ubiquity package in Ubuntu:
>   Fix Released
> Status in ubiquity source package in Focal:
>   Triaged
> Status in ubiquity source package in Hirsute:
>   Won't Fix
>
> Bug description:
>   During a fresh install of Ubuntu 20.04, selecting Norwegian keyboard
>   is provided and keys are responding correctly at that stage. But later
>   when entering user information the keyboard setting is wrong.
>
>   It looks like it have fallen back to English keyboard-layout.
>   I failed to log in after my first install, so a new attempt I tried to
> write some special letters in the name field, and noticed that I got the
> wrong characters for the key.
>
>   The install is done in VMware workstation 15.
>
>   In the attached screendump, the characters (';[":{) after my name
>   should have been (æøåÆØÅ) that is norwegian characters.
>
>   Problem analysis
>   
>
>   * ubiquity installs open-vm-tools.
>   * open-vm-tools calls "udevadm trigger" in it's postinst script (line 8).
>   * udevadm triggers all udev rules which includes all input devices.
>   * gdm-x-session reads /etc/default/keyboard and sets the keyboard layout.
>   * gnome-shell sets the keyboard layout as well.
>
>   ubiquity already sets /etc/default/keyboard, but does not change the
>   keyboard layout in the GNOME session.
>
>   Proposed solution
>   =
>
>   Let ubiquity also configure the GNOME session to use the selected
>   keyboard layout.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 25 19:27:41 2020
>   InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd
> quiet splash --- maybe-ubiquity
>   InstallationDate: Installed on 2020-04-25 (0 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   SourcePackage: ubiquity
>   Symptom: installer
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=ubuntu-release-notes; status=Fix Released;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=ubiquity;
> component=main; milestone=ubuntu-22.04; status=Fix Released;
> importance=High; assignee=lukasz.zemc...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal;
> sourcepackage=ubiquity; component=main; milestone=focal-updates;
> status=Triaged; importance=High; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=hirsute;
> sourcepackage=ubiquity; component=None; milestone=ubuntu-21.04;
> status=Won't Fix; importance=High; assignee=lukasz.zemc...@canonical.com;
> Launchpad-Bug-Tags: amd64 apport-bug focal fr-1091
> id-5ef4c1e222b6324e1c59ad48 iso-testing patch ubiquity-20.04.15
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: bdrung brian-murray coeur-noir dag-e gunnarhj
> janitor jeando jessicavdh juglugs1974 michel.ekimia nm sh-yaron
> shlomzions sil2100 simosx ubuntuqa vorlon xnox
> Launchpad-Bug-Reporter: Dag Bjerkeli (dag-e)
> Launchpad-Bug-Modifier: Dag Bjerkeli (dag-e)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: juglugs1974
>
>

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

Title:
  [20.04] Keyboard layout changes during installation before typing
  username/password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions


-- 

[Bug 1875062] Re: [20.04] Keyboard layout changes during installation before typing username/password

[Mark Smith]

Hi guys,

I'm sorry to say that this bug is back in 24.04 Beta.

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

Title:
  [20.04] Keyboard layout changes during installation before typing
  username/password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions


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

[Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog

[Mark Smith]

Changed from ding to nautilus after reading about nautilus gvfsd-trash
bug

** Package changed: ding (Ubuntu) => nautilus (Ubuntu)

** Summary changed:

- DING causes gvfsd 'Too many files open' error and fills syslog
+ nautilus causes gvfsd-trash 'Too many files open' error and fills syslog

** Description changed:

- My syslog is filled (to >30GB) regularly with these messages. I seem to
- have this thing called DING going on, which maybe causing it?
+ My syslog is filled (to >30GB) regularly with these messages.
  
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: 
(org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer 
connection failed: Unable to create socket: Too many open files. Falling back 
to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server 
at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create 
socket: Too many open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: 

[Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog

[Mark Smith]

Further reading would suggest that it's a bug in Nautilus and the way that 
gvfsd deals with trash:
https://www.reddit.com/r/gnome/comments/l0gg32/a_helpul_tip_for_those_with_gvfsdtrash_hogging/

It runs out that I don't have ding installed, and also no references to
gvfsd.

Yet, if I do as the post above says and kill the gvfsd process when it's
running it stops my root drive filling up with an enormous syslog.

How do I transfer this bug over to Nautilus?

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

Title:
  DING causes gvfsd 'Too many files open' error and fills syslog

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


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

[Bug 1976498] [NEW] DING causes gvfsd 'Too many files open' error and fills syslog

[Mark Smith]

Public bug reported:

My syslog is filled (to >30GB) regularly with these messages. I seem to
have this thing called DING going on, which maybe causing it?

Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: 
(org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer 
connection failed: Unable to create socket: Too many open files. Falling back 
to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at 
address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create 
socket: Too many open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.636: fail: Error accepting connection: Too many 
open files
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.636: fail: Error accepting 
connection: Too many open files]
Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.637: fail: Error accepting connection: 

[Bug 1975487] [NEW] zsys not installed during Kinetic ISO install with ZFS option

[Mark Smith]

Public bug reported:

After following the instructions at:
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
 
on the 20220523 daily build of Kinetic, I used the command

zsysctl show

and was met with the message:

~$ zsysctl show
Command 'zsysctl' not found, but can be installed with:
sudo apt install zsys

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: zsys (not installed)
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 12:33:24 2022
InstallationDate: Installed on 2022-05-23 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522)
SourcePackage: zsys
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1975487/+attachment/5592259/+files/Screenshot%20from%202022-05-23%2012-39-43.png

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

Title:
  zsys not installed during Kinetic ISO install with ZFS option

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


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

[Bug 1967883] Re: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen

[Mark Smith]

No, It was a straight install with me present at the desktop computer
all the way through - no switching or even screen locking.

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

Title:
  [snap] Firefox Nightly Application Icon missing from "Show
  Applications" screen

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


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

[Bug 1967883] [NEW] Application Icons missing from "Show Applications" screen

[Mark Smith]

Public bug reported:

From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox 
(nightly) from Ubuntu Software (as snaps).
Neither of the two icons/graphics show up in the show applications window - 
either in the thumbnails of the groups I have created, or the expanded windows 
(see screenshots).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  5 14:49:04 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-31 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot from 2022-04-05 14-47-30.png"
   
https://bugs.launchpad.net/bugs/1967883/+attachment/5577331/+files/Screenshot%20from%202022-04-05%2014-47-30.png

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

Title:
  Application Icons missing from "Show Applications" screen

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


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

[Bug 1967883] Re: Application Icons missing from "Show Applications" screen

[Mark Smith]

** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png

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

Title:
  Application Icons missing from "Show Applications" screen

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


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

[Bug 1967883] Re: Application Icons missing from "Show Applications" screen

[Mark Smith]

** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png

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

Title:
  Application Icons missing from "Show Applications" screen

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


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

[Bug 1964626] acpidump.txt

[Mark Smith]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568063/+files/acpidump.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] UdevDb.txt

[Mark Smith]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1964626/+attachment/5568061/+files/UdevDb.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] WifiSyslog.txt

[Mark Smith]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568062/+files/WifiSyslog.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] PulseList.txt

[Mark Smith]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568060/+files/PulseList.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] ProcModules.txt

[Mark Smith]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568059/+files/ProcModules.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] ProcInterrupts.txt

[Mark Smith]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568058/+files/ProcInterrupts.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] ProcEnviron.txt

[Mark Smith]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568057/+files/ProcEnviron.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] ProcCpuinfoMinimal.txt

[Mark Smith]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568056/+files/ProcCpuinfoMinimal.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] ProcCpuinfo.txt

[Mark Smith]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568055/+files/ProcCpuinfo.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] PaInfo.txt

[Mark Smith]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1964626/+attachment/5568054/+files/PaInfo.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] Lsusb-v.txt

[Mark Smith]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568053/+files/Lsusb-v.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] CurrentDmesg.txt

[Mark Smith]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568050/+files/CurrentDmesg.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] Lspci-vt.txt

[Mark Smith]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568052/+files/Lspci-vt.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] Lspci.txt

[Mark Smith]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1964626/+attachment/5568051/+files/Lspci.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] CRDA.txt

[Mark Smith]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1964626/+attachment/5568049/+files/CRDA.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] Re: Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

[Mark Smith]

apport information

** Tags added: apport-collected

** Description changed:

  I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple 
of weeks and just updating and upgrading using apt.
  When restarting the VM (VirtualBox), I get the screen in the screenshot 
below. The same thing happens if I select the 5.15.0-22-generic options - 
normal or recovery mode - from the grub list in advanced options.
  I can boot into 5.15.0-18-generic with no issues.
  
  I have attempted to run upgrade-grub to no avail.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 11 18:17:17 2022
  InstallationDate: Installed on 2022-02-26 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu78
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  daisy  1635 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-02-26 (13 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp0s3no wireless extensions.
+ Lsusb:
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Lsusb-t:
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
+ ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-18-generic N/A
+  linux-backports-modules-5.15.0-18-generic  N/A
+  linux-firmware 20220302.gitee0667aa-0ubuntu1
+ RfKill:
+  
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
+ _MarkForUpload: True
+ dmi.bios.date: 12/01/2006
+ dmi.bios.vendor: innotek GmbH
+ dmi.bios.version: VirtualBox
+ dmi.board.name: VirtualBox
+ dmi.board.vendor: Oracle Corporation
+ dmi.board.version: 1.2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Oracle Corporation
+ dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
+ dmi.product.family: Virtual Machine
+ dmi.product.name: VirtualBox
+ dmi.product.version: 1.2
+ dmi.sys.vendor: innotek GmbH

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568048/+files/AlsaInfo.txt

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1964626] [NEW] Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

[Mark Smith]

Public bug reported:

I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple 
of weeks and just updating and upgrading using apt.
When restarting the VM (VirtualBox), I get the screen in the screenshot below. 
The same thing happens if I select the 5.15.0-22-generic options - normal or 
recovery mode - from the grub list in advanced options.
I can boot into 5.15.0-18-generic with no issues.

I have attempted to run upgrade-grub to no avail.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 11 18:17:17 2022
InstallationDate: Installed on 2022-02-26 (13 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot from 2022-03-11 09-58-33.png"
   
https://bugs.launchpad.net/bugs/1964626/+attachment/5568016/+files/Screenshot%20from%202022-03-11%2009-58-33.png

** Description changed:

- I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a few 
weeks and just updating and upgrading using apt.
+ I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple 
of weeks and just updating and upgrading using apt.
  When restarting the VM (VirtualBox), I get the screen in the screenshot 
below. The same thing happens if I select the 5.15.0-22-generic options - 
normal or recovery mode - from the grub list in advanced options.
  I can boot into 5.15.0-18-generic with no issues.
  
  I have attempted to run upgrade-grub to no avail.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 11 18:17:17 2022
  InstallationDate: Installed on 2022-02-26 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

So I then manually changed the password to read Thanks#Brian by using
the US mapping of Shift+3 to get the # symbol as seen in the screenshot.

I let the installer run and logged in successfully using Thanks#Brian
directly as I normally would on my UK keyboard.

So, yes, it looks like Unity isn't picking up the keyboard map selection
in the initial password entry screen (where you have the eyeball icon
now).

Does this then relate to bug #1948716 where I noticed that Unity doesn't
'guess' my keyboard map correctly at the beginning and I have to
manually select UK mapping?

** Attachment added: "Screenshot from 2022-01-29 09-19-59.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948714/+attachment/5558145/+files/Screenshot%20from%202022-01-29%2009-19-59.png

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

I've downloaded and installed using 20220129 which does have the eyeball
icon next to the password field.

As seen in the attached screenshot, the keyboard mapping at the password
stage doesn't go to UK as previously selected - I had tried to type
Thanks#Brian but the keyboard had given me Thanks/Brian.


** Attachment added: "Screenshot from 2022-01-29 09-19-07.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948714/+attachment/5558144/+files/Screenshot%20from%202022-01-29%2009-19-07.png

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

Hi Brian,

Using the latest daily build (20220126), I cannot see the option to
display the password? - see attached screenshot.

I can see your line of thinking as the # symbol is different on US & UK
keyboard mappings (much to the annoyance when I lived in the US for 6
years and had to retrain my muscle memory twice!).

I ran an install using the UK keyboard layout with the # symbol from its own 
key within the password - The issue is still extant.
I tried using the US mapping of Shift+3 to make the # symbol when logging in, 
but it still failed.

I then ran an install using the US keyboard layout with the # symbol
made by pressing Shift+3 within the password - Using the US mapping of
Shift+3, I can log in normally.

Kind regards
Mark


** Attachment added: "Password Entry Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948714/+attachment/5557860/+files/Screenshot%20from%202022-01-27%2019-26-47.png

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1952515] Re: QA Test Ubuntu 22.04 Gnome-shell Crashed

[Mark Smith]

Unable to reproduce in VB environment

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

Title:
  QA Test Ubuntu 22.04 Gnome-shell Crashed

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


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

[Bug 1949523] Re: Disk Encryption Password Not Remembered

[Mark Smith]

Bug not present in build 20211103

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

Title:
  Disk Encryption Password Not Remembered

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


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

[Bug 1949523] [NEW] Disk Encryption Password Not Remembered

[Mark Smith]

Public bug reported:

In two attempts at following the "Install (entire disk with lvm and
encryption) in Ubuntu Desktop amd64 in Jammy Daily" in the 20211102
build, the machine fails to recognise the full disk encryption password
set at install time.

I have tried "lemon" and "Lemon" as the passwords for encryption, but on
both occasions have been unable to unlock the machine after
install/reboot.

Could this be related to bug #1948714 ?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  2 20:29:43 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2021-11-02 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211102)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy ubiquity-21.10.10 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/1949523

Title:
  Disk Encryption Password Not Remembered

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


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

Re: [Bug 1948716] Re: Proposed Keyboard is Incorrect

[Mark Smith]

This is my first time testing daily builds - It has worked in previous
releases (I think).
There are some differences in the layout, e.g. the " and @ mappings are
swapped (Shift+2 for " in the UK, and Shift+2 for @ in the US).
I agree it's a low urgency/low importance bug, but it should be easy to fix
(it guesses my location correctly on the "Where are you?" screen)

On Wed, 27 Oct 2021 at 17:44, Sebastien Bacher <1948...@bugs.launchpad.net>
wrote:

> Thank you for your bug report, unsure how much difference there is
> between those layouts. Did it work in past cycles?
>
> ** Changed in: ubiquity (Ubuntu)
>Importance: Undecided => Low
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1948716
>
> Title:
>   Proposed Keyboard is Incorrect
>
> Status in ubiquity package in Ubuntu:
>   New
>
> Bug description:
>   The jammy daily testcase states:
>
>   "The proposed keyboard corresponds with your keyboard"
>
>   The proposed keyboard was English (US) and my keyboard is English (UK)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
>   Uname: Linux 5.13.0-19-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu70
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Oct 25 20:59:03 2021
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>   InstallationDate: Installed on 2021-10-25 (0 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
> (20211024)
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948716/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=ubiquity;
> component=main; status=New; importance=Low; assignee=None;
> Launchpad-Bug-Tags: amd64 apport-bug iso-testing jammy ubiquity-21.10.10
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: juglugs1974 seb128 ubuntuqa
> Launchpad-Bug-Reporter: Mark Smith (juglugs1974)
> Launchpad-Bug-Modifier: Sebastien Bacher (seb128)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: juglugs1974
>
>

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

Title:
  Proposed Keyboard is Incorrect

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

The '@' character also does not work in any position of the string.

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

Note: Booting into recovery and setting the password from the command
line allows the # character, so it's only in Ubiquity at install that
there is a bug.

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

I've narrowed it down to a specific special character at any location in
the string, and after changing all of my passwords that included it, I
can reveal it to be the '#' character. So either pass#word or password#
fails.

I am now checking other special characters ('*' works).

Is there a faster way of me doing this than spinning up new VMs and
going through the installation each time?

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

OK, so it appears that the bug is if you have a special character in the
original password. I don't really want to say which special character
and where in the password it appears in this public area, but if you
contact me, I'll let you know.

Also, please excuse my ignorance on all of this. I am a complete Noob to
Ubuntu testing, but very eager to learn from more experienced people.

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948716] Re: Proposed Keyboard is Incorrect

[Mark Smith]

Clicking the 'Detect Keyboard Layout' button works fine, but not the
initial guess when going through the installation menus

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

Title:
  Proposed Keyboard is Incorrect

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

New data point: Using build 20211028 and an alpha-character ONLY
password works. I'll now test the 21.10 build with that alpha password

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948714] Re: After reboot, the password set at install time doesn't work.

[Mark Smith]

Hi Leo,

Interesting. I ran the Ubuntu 21.20 iso through the same VM (used fresh
VDI) and I get the same fault. On my actual Ubuntu machine 21.10 was
installed with no problems.

So maybe it's a VirtualBox issue? 
I don't understand (I mean I really am lacking the knowledge) why the keyboard 
layout bug https://bugs.launchpad.net/bugs/1948716 would affect this?

I have attached the VB configuration for reference.

** Attachment added: "VB Configuration for Daily Build testing"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948714/+attachment/5536761/+files/Screenshot%20from%202021-10-28%2013-58-12.png

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

Title:
  After reboot, the password set at install time doesn't work.

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


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

[Bug 1948716] Re: Proposed Keyboard is Incorrect

[Mark Smith]

This is my first time testing daily builds - It has worked in previous releases 
(I think).
There are some differences in the layout, e.g. the " and @ mappings are swapped 
(Shift+2 for " in the UK, and Shift+2 for @ in the US).
I agree it's a low urgency/low importance bug, but it should be easy to fix (it 
guesses my location correctly on the "Where are you?" screen)

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

Title:
  Proposed Keyboard is Incorrect

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


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

[Bug 1868371] Re: incorrect name of 'Preparing to install Xubuntu' screen

[Mark Smith]

Also exists in Jammy builds scripts for steps 3 & 4

3. Select your keyboard layout and click on continue
The 'Preparing to install Ubuntu' screen is displayed
4. On the screen Preparing to install Ubuntu, note the availability of the 
following components.

Should be 'Updates and other software' screen

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

** No longer affects: ubuntu

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

Title:
  incorrect name of 'Preparing to install Xubuntu' screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1868371/+subscriptions


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

[Bug 1948716] Re: Proposed Keyboard is Incorrect

[Mark Smith]

Also exists in 20211027 build

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

Title:
  Proposed Keyboard is Incorrect

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


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

[Bug 1948716] [NEW] Proposed Keyboard is Incorrect

[Mark Smith]

Public bug reported:

The jammy daily testcase states:

"The proposed keyboard corresponds with your keyboard"

The proposed keyboard was English (US) and my keyboard is English (UK)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 20:59:03 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2021-10-25 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211024)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy ubiquity-21.10.10

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

Title:
  Proposed Keyboard is Incorrect

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


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

[Bug 1881712] Re: gnome-software says connection is metered while is not

[Mark Smith]

Same issue on 21.04

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

Title:
  gnome-software says connection is metered while is not

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

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

[Bug 1920812] [NEW] Unity Launcher hidden behind open applications

[Mark Smith]

Public bug reported:

To reproduce:

1. Start any application, e.g. Nautilus or Terminal
2. Click 9-dot grid in bottom corner fo screen.
3. The launcher (and it's app shortcuts) are hidden behind the application 
windows that were opened in step 1.

Those open applications are tiled as if I had pressed the SUPER key
(WinKey).

Unable to select the app shortcuts hidden behind the open applications,
but I am able to scroll the launcher window down to see the other app
shortcuts.

Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04

(Apologies, I don't know if I'm referencing the correct Unity below as
it says that they are not installed?)

unity:
  Installed: (none)
  Candidate: 7.5.0+20.04.20200312-0ubuntu1
  Version table:
 7.5.0+20.04.20200312-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages
unity:
  Installed: (none)
  Candidate: 7.5.0+20.04.20200312-0ubuntu1
  Version table:
 7.5.0+20.04.20200312-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: unity (not installed)
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 22 19:40:04 2021
InstallationDate: Installed on 2021-03-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute launcher unity wayland-session

** Attachment added: "Screenshot of Bug"
   
https://bugs.launchpad.net/bugs/1920812/+attachment/5479263/+files/2021-03-22_19-48.png

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

Title:
  Unity Launcher hidden behind open applications

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

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

[Bug 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error

[Mark Smith]

Adding some cross-linking to help people who encounter this in the
future, and perhaps also help the devs:

This is discussed in the Ask Ubuntu post:
https://askubuntu.com/questions/1128164/no-suitable-destination-host-
found-by-cups-browsed

The solution there (which worked for me) is to `apt remove cups-browsed`
and add the printer manually.

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

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+subscriptions

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Mark Smith]

ID = #3026

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3026
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

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

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

[Bug 1887313] [NEW] Filename prefixed with "Disc 1"

[Mark Smith]

Public bug reported:

Ubuntu 18.04
Sound Juicer 3.24.0-2

Operation:
Rip a single-disc album, with the "File name" preference set to "Number - 
Title".

Expectation:
The filename should be something like "01 - My Song.mp3"

What actually happens:
The filename generated will be something like "Disc 1 - 01 - My Song.mp3".

The "Disc 1" part it not necessary (or sensible) in single-disc albums
(i.e. most of them).  It would be better to either have it only included
on multi-disc albums, or have a different filename formats which include
and exclude the "Disc n" part.

(Looks like this was introduced intentionally for
https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/212846)

** Affects: sound-juicer (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/1887313

Title:
  Filename prefixed with "Disc 1"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/1887313/+subscriptions

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

[Bug 1872026] [NEW] Activity Bar icon aspect ratio broken

[Mark Smith]

Public bug reported:

The aspect ratio of the icon on the top left of the screen (Activites
bar?) is broken so it looks taller and thinner than normal.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
Uname: Linux 5.4.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 10 09:10:09 2020
InstallationDate: Installed on 2020-01-24 (76 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2020-04-10 09:03:51.154471
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2020-04-03T20:22:43.358127

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade focal

** Attachment added: "Screenshot of distorted icon"
   
https://bugs.launchpad.net/bugs/1872026/+attachment/5351098/+files/Screenshot%20from%202020-04-10%2009-04-23.png

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

Title:
  Activity Bar icon aspect ratio broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1872026/+subscriptions

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

[Bug 1870748] Re: Authentication Window Stays Open

[Mark Smith]

Sorry, I should add that the pop-up window remained on top of all the others, 
so it wasn't hidden behind anything else before I went to bed. 
And although it was at the top, when I entered my password and the field went 
grey, the window remained visible, but if I clicked anywhere in the window, I 
actually clicked whatever was behind it.

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

Title:
  Authentication Window Stays Open

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

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

[Bug 1870748] Re: Authentication Window Stays Open

[Mark Smith]

Not at that time - I had just gone to bed. I had changed them earlier that day, 
and the error triggered. So I rebooted. This time the error came about without 
me touching it.
Journal output attached.
The bug doesn't appear to be triggered by any steps in Software-Updater


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+attachment/5347706/+files/journal.txt

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

Title:
  Authentication Window Stays Open

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

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

[Bug 1870748] Re: Authentication Window Stays Open

[Mark Smith]

I attempted to make a change to a repository by launching Software &
Updates and editing an unselected package from eoan to fossa - the
authentication window persisted at the top left of my screen throughout
- even after entering my credentials in the central authentication
window that popped up (and went as normal)

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

Title:
  Authentication Window Stays Open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870748/+subscriptions

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

[Bug 1870748] [NEW] Authentication Window Stays Open

[Mark Smith]

Public bug reported:

I left the Beta of Focal Fossa running overnight and when I logged in
this morning, I found an open Authentication window with the message "To
change software repository settings, you need to authenticate" (see
attached screenshot).

I enter my password and the password field grey out.

The window stays persistent but is "invisible" to the mouse - i.e. if I click 
anywhere in it, it actually clicks the thing behind it. 
The Cancel button does nothing.

I had this same issue yesterday when actually running Software &
Updates.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.7
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 09:55:33 2020
InstallationDate: Installed on 2020-01-24 (70 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot of persistent Software & Updates 
authentication window"
   
https://bugs.launchpad.net/bugs/1870748/+attachment/5346150/+files/Screenshot%20from%202020-04-04%2009-58-06.png

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

Title:
  Authentication Window Stays Open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870748/+subscriptions

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

[Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

[Mark smith]

Two network & volume indicators also on XFCE panel.
No change even after resetting the panel (xfce4-panel -r).
I guess two is better than none. ;-)

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

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

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

[Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Mark smith]

I *might* have a possible clue for the gdebi gui crash in Bionic.

If I right click on a .deb file and tell it to install with gdebi the gui will 
crash.
If I open a terminal in the same directory as the file and launch gdebi-gtk 
*.deb the gui will install and uninstall the .deb file without crashing.

I hope this offers a potential clue for a fix, I love the gdebi
installer and I thank ALL of you programmers for your diligence and hard
work!!

Mark

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

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

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

[Bug 1686084] [NEW] x11vnc on zesty terminates with **stack smashing detected** error

[Mark Smith]

Public bug reported:

x11vnc will terminate abnormally on zesty with a **stack smashing
detected** error. Reverting to an x11vnc from an earlier Ubuntu version
appears to resolve this error. The error is generated by user activity,
it seems to be triggered by certain user input, such as a mouse click.

** Affects: x11vnc (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/1686084

Title:
  x11vnc on zesty terminates with **stack smashing detected** error

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

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

[Bug 1672562] Re: No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to detect card

[Mark Smith]

This turned out to be a problem with the user not being in the audio and
pulse-access groups. Also  the back panel speaker out only has one
channel working, however the front panel headphone connector works fine.
So I just use the front panel headphone jack.

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837337/+files/AlsaInfo.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837339/+files/Dependencies.txt

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

Title:
  No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line
  Out, Rear] Pulseaudio fails to detect card

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

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

[Bug 1672562] Re: No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to detect card

[Mark Smith]

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837338/+files/CurrentDmesg.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837340/+files/JournalErrors.txt

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

Title:
  No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line
  Out, Rear] Pulseaudio fails to detect card

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

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

[Bug 1672562] Re: No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to detect card

[Mark Smith]

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837341/+files/PulseList.txt

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

Title:
  No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line
  Out, Rear] Pulseaudio fails to detect card

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

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

[Bug 1672562] [NEW] No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to detect card

[Mark Smith]

Public bug reported:

I have no audio output with the following configuration:

  *-multimedia
  description: Audio device
  product: MCP61 High Definition Audio
  vendor: NVIDIA Corporation
  physical id: 5
  bus info: pci@:00:05.0
  version: a2
  width: 32 bits
  clock: 66MHz
  capabilities: bus_master cap_list
  configuration: driver=snd_hda_intel latency=0 maxlatency=5 mingnt=2
  resources: irq:21 memory:fbff8000-fbffbfff

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: XFCE
Date: Mon Mar 13 18:56:40 2017
InstallationDate: Installed on 2017-02-07 (34 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA NVidia
Symptom_Jack: Green Line Out, Rear
Title: [p6714y, Realtek Generic, Green Line Out, Rear] Pulseaudio fails to 
detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.01
dmi.board.name: 2A6C
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 5.00
dmi.chassis.asset.tag: 3CR0510YC1
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.01:bd09/29/2010:svnHewlett-Packard:pnp6714y:pvr:rvnPEGATRONCORPORATION:rn2A6C:rvr5.00:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: p6714y
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

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

Title:
  No audio output on MCP61 Nvidia. [p6714y, Realtek Generic, Green Line
  Out, Rear] Pulseaudio fails to detect card

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

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

[Bug 1555147] Re: package linux-image-extra-4.4.0-11-generic 4.4.0-11.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Mark Smith]

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package linux-image-extra-4.4.0-11-generic 4.4.0-11.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

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

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

It looks like sudo 1.8.12 made it into 15.10 finally. Excellent. Apple
went the other route and locked the clock back down.
(https://support.apple.com/en-us/HT205031)

The CVE associated with this bug seems to be about the TZ (seen on
RedHat's security site:
https://access.redhat.com/security/cve/CVE-2014-9680). Apple's CVE is
about restricting access to the time settings (http://www.cve.mitre.org
/cgi-bin/cvename.cgi?name=CVE-2015-3757). I don't think either one
really reflects this bug.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-3757

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1453162] Re: Complete plasma crash at every login

[Mark Smith]

This appears to be a package dependancy problem because installing kio,
plasma-desktop and plasma-desktop-data fixed this

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

Title:
  Complete plasma crash at every login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1453162/+subscriptions

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

[Bug 1453162] Re: Complete plasma crash at every login

[Mark Smith]

** Description changed:

+ This is on Ubuntu 15.04.
+ 
  This bug results in KDE crashing on login. This results in KDE being
  completely nonfunctional, we are left with a blank screen. Any help is
  appreciated.
  
  With every login to Plasma, we get a plasma crash. Then KDE session does
  not continue, we are left with an empty screen.  Thus KDE is completely
  non-functional and broken. Any help is appreciated.
  
  Application: Plasma (plasmashell), signal: Aborted
  Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
  [Current thread is 1 (Thread 0xb1f57980 (LWP 21925))]
  
  Thread 6 (Thread 0xb1b55b40 (LWP 21941)):
  #0  0xb7731be0 in __kernel_vsyscall ()
  #1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
  #2  0xb69093a8 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
  #3  0xb690b394 in xcb_wait_for_event () from 
/usr/lib/i386-linux-gnu/libxcb.so.1
  #4  0xb1ca97d3 in ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
  #5  0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #6  0xb4b431aa in start_thread (arg=0xb1b55b40) at pthread_create.c:333
  #7  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 5 (Thread 0xafc66b40 (LWP 21947)):
  #0  0xb7731be0 in __kernel_vsyscall ()
  #1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
  #2  0xb446a120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb445b014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb445b439 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb09d12f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  #6  0xb448240a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #7  0xb4b431aa in start_thread (arg=0xafc66b40) at pthread_create.c:333
  #8  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 4 (Thread 0xaf2ffb40 (LWP 21948)):
  #0  0xb7731be0 in __kernel_vsyscall ()
  #1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
  #2  0xb446a120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb445b014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb445b1b0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #6  0xb448240a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #7  0xb4b431aa in start_thread (arg=0xaf2ffb40) at pthread_create.c:333
  #8  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 3 (Thread 0xad994b40 (LWP 21956)):
  #0  0xb513345e in QElapsedTimer::isMonotonic() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #1  0xb53177c6 in QTimerInfoList::repairTimersIfNeeded() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #2  0xb5317842 in QTimerInfoList::timerWait(timespec) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #3  0xb5318db9 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #4  0xb445a41b in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb445af24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #6  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #7  0xb53199fc in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #8  0xb52bad93 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #9  0xb52bb1fa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #10 0xb508d40d in QThread::exec() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #11 0xb671f50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
  #12 0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #13 0xb4b431aa in start_thread (arg=0xad994b40) at pthread_create.c:333
  #14 0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 2 (Thread 0xaeafeb40 (LWP 21988)):
  #0  0xb445a2a4 in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #1  0xb445af24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #2  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb53199fc in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #4  0xb52bad93 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #5  0xb52bb1fa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #6  0xb508d40d in QThread::exec() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #7  0xb671f50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
  #8  0xb50927eb in ?? () from 

[Bug 1453162] [NEW] Complete plasma crash at every login

[Mark Smith]

Public bug reported:

This bug results in KDE crashing on login. This results in KDE being
completely nonfunctional, we are left with a blank screen. Any help is
appreciated.

Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb1f57980 (LWP 21925))]

Thread 6 (Thread 0xb1b55b40 (LWP 21941)):
#0  0xb7731be0 in __kernel_vsyscall ()
#1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb69093a8 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3  0xb690b394 in xcb_wait_for_event () from /usr/lib/i386-linux-gnu/libxcb.so.1
#4  0xb1ca97d3 in ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
#5  0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb4b431aa in start_thread (arg=0xb1b55b40) at pthread_create.c:333
#7  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 5 (Thread 0xafc66b40 (LWP 21947)):
#0  0xb7731be0 in __kernel_vsyscall ()
#1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb446a120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb445b014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb445b439 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb09d12f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb448240a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb4b431aa in start_thread (arg=0xafc66b40) at pthread_create.c:333
#8  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 4 (Thread 0xaf2ffb40 (LWP 21948)):
#0  0xb7731be0 in __kernel_vsyscall ()
#1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb446a120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb445b014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb445b1b0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb448240a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb4b431aa in start_thread (arg=0xaf2ffb40) at pthread_create.c:333
#8  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 3 (Thread 0xad994b40 (LWP 21956)):
#0  0xb513345e in QElapsedTimer::isMonotonic() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#1  0xb53177c6 in QTimerInfoList::repairTimersIfNeeded() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#2  0xb5317842 in QTimerInfoList::timerWait(timespec) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#3  0xb5318db9 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#4  0xb445a41b in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb445af24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb53199fc in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#8  0xb52bad93 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#9  0xb52bb1fa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#10 0xb508d40d in QThread::exec() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#11 0xb671f50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#12 0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#13 0xb4b431aa in start_thread (arg=0xad994b40) at pthread_create.c:333
#14 0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 2 (Thread 0xaeafeb40 (LWP 21988)):
#0  0xb445a2a4 in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb445af24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb53199fc in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#4  0xb52bad93 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5  0xb52bb1fa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb508d40d in QThread::exec() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb671f50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#8  0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#9  0xb4b431aa in start_thread (arg=0xaeafeb40) at pthread_create.c:333
#10 0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
With every login to Plasma, we get a plasma crash. Then KDE session does not 
continue, we are left with an empty screen.  Thus KDE is completely 
non-functional and broken. Any help is appreciated.

Application: 

[Bug 1453162] Re: Complete plasma crash at every login

[Mark Smith]

** Description changed:

  This bug results in KDE crashing on login. This results in KDE being
  completely nonfunctional, we are left with a blank screen. Any help is
  appreciated.
+ 
+ With every login to Plasma, we get a plasma crash. Then KDE session does
+ not continue, we are left with an empty screen.  Thus KDE is completely
+ non-functional and broken. Any help is appreciated.
  
  Application: Plasma (plasmashell), signal: Aborted
  Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
  [Current thread is 1 (Thread 0xb1f57980 (LWP 21925))]
  
  Thread 6 (Thread 0xb1b55b40 (LWP 21941)):
  #0  0xb7731be0 in __kernel_vsyscall ()
  #1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
  #2  0xb69093a8 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
  #3  0xb690b394 in xcb_wait_for_event () from 
/usr/lib/i386-linux-gnu/libxcb.so.1
  #4  0xb1ca97d3 in ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
  #5  0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #6  0xb4b431aa in start_thread (arg=0xb1b55b40) at pthread_create.c:333
  #7  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 5 (Thread 0xafc66b40 (LWP 21947)):
  #0  0xb7731be0 in __kernel_vsyscall ()
  #1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
  #2  0xb446a120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb445b014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb445b439 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb09d12f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  #6  0xb448240a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #7  0xb4b431aa in start_thread (arg=0xafc66b40) at pthread_create.c:333
  #8  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 4 (Thread 0xaf2ffb40 (LWP 21948)):
  #0  0xb7731be0 in __kernel_vsyscall ()
  #1  0xb4e373db in poll () at ../sysdeps/unix/syscall-template.S:81
  #2  0xb446a120 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb445b014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb445b1b0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #6  0xb448240a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #7  0xb4b431aa in start_thread (arg=0xaf2ffb40) at pthread_create.c:333
  #8  0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 3 (Thread 0xad994b40 (LWP 21956)):
  #0  0xb513345e in QElapsedTimer::isMonotonic() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #1  0xb53177c6 in QTimerInfoList::repairTimersIfNeeded() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #2  0xb5317842 in QTimerInfoList::timerWait(timespec) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #3  0xb5318db9 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #4  0xb445a41b in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb445af24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #6  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #7  0xb53199fc in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #8  0xb52bad93 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #9  0xb52bb1fa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #10 0xb508d40d in QThread::exec() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #11 0xb671f50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
  #12 0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #13 0xb4b431aa in start_thread (arg=0xad994b40) at pthread_create.c:333
  #14 0xb4e41fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122
  
  Thread 2 (Thread 0xaeafeb40 (LWP 21988)):
  #0  0xb445a2a4 in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #1  0xb445af24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #2  0xb445b156 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb53199fc in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #4  0xb52bad93 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #5  0xb52bb1fa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #6  0xb508d40d in QThread::exec() () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #7  0xb671f50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
  #8  0xb50927eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
  #9  0xb4b431aa 

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

 You can set the time with:

 timedatectl set-time 2000-01-01 10:00:00

Wow. Yeah, that'll make exploiting this *much* easier on desktop.

Fortunately Ubuntu Server doesn't allow this without authenticating.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Notice that only the SID changed though.  That gives me a 1 in 32k
chance, and I can generate them basically at will with setsid. In my
testing so far, the inode of the TTY file for /dev/pts/0 has stayed 3
across several reboots. If it doesn't change, then it is moot from a
security standpoint.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

To clarify: I reboot, log in, open gnome-terminal.  The tty is always
/dev/pts/0, and ls -i /dev/pts/0 shows an inode of 3. This occurs even
if I shut down and power back on, though admittedly in a VM.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Yup, I think so. while true; do setsid something to run sudo; done; or
the like. In my tests rolling through then all took about 5 minutes, and
that was in a crappy VM with 1 core and 30% CPU being used by compiz. I
haven't gotten it to pop an escalated shell yet, but I'll poke at it
more tonight after work.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Oh, nevermind! You're talking about outside of the sudo instance. In the
case of Cron, etc: just let *the user* decide whether they want to be
asked after the first time. Make it an option to unlock the clock,
disabled by default but still available.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Kay, the update to sudo (1.8.10) actually solves this by using the
monotonic clock. All that needs to happen is for Ubuntu to udpate to it.
:)

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

 Without rebooting, the tty, inode, sid should change for every
terminal you open.

When I tried this on 15.04, the tty and inode didnt: only the SID
changed. Closing a gnome-terminal and reopening it got the same tty and
SID. For *additional* terminals, they got new ttys and inodes, but if
you close the one on /dev/pty/0 the file will dissapear. The next gnome-
terminal you launch will be on /dev/pty/0 with the same inode as the old
one you closed. Can you confirm?

Apologies for any typos, I'm on my phone.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Indeed. Trojaning those requires waiting for the user. Why lay a trap
and wait when you can just break down the door? If I can use dogtail or
similar to automate the clock and suddenly we're in drive-by territory.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Tyler,
it's great that this bug will be fixed. However, I have some concerns about the 
mitigations factors.

1) Timestamp: Easily found in the auth.log, and easily bypassed due to
an unlocked clock.

2) TTY: The tty of the first gnome-terminal running is (as far as I can
tell) /dev/pts/0. That's predictable, so if the auth.log contains a sudo
session on /dev/pty/0, it's trivial to re-create the tty.

3) inode: Does this mean Session ID? If so, I'm worried. If not, we have
a bigger problem. Here's why:


hexdump -d /var/lib/sudo/mscs/0 
000   00013   0   0   0   34816   0   0   0
010   3   0   0   0   01000   0   5   0
020   31291   0   0   0
028

hexdump -d /var/lib/sudo/mscs/0 
000   00013   0   0   0   34816   0   0   0
010   3   0   0   0   01000   0   5   0
020   01464   0   0   0
028


See 31291, and 01464 in the second column near the bottom? It turns out that 
they correspond to SID.
I checked using python:

import os
pid = os.getpid()
sid = os.getsid(pid)
print pid, sid

1775 1464

I tested this several times. Since the setsid can generate a new sid,
and there are only 32768 possible SIDs as configured out of the box, how
hard would it be to brute force the sid, simply running sudo -n -s? If
SID isn't == to Inode, where's inode in that file? The ls -i command
reports no difference in the inode of the file itself (545179 both
times, even if the gnome-terminal is closed and re-opened.)

I've poked at the sid option already, and have indeed had good success
with getting sessions matching the sid using this brute force method.
It's now a question of how I get that session lined up with the pty
(which is predictable) and see if sudo -s works without a password at
the last escalation time. Perhaps there is some other security feature
that will block me, but right now I don't see it.

Thoughts?

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Congratulations, Ubuntu team. You have now fallen behind *Debian's
Stable Release* in a security update to sudo, despite several releases
in between. They even released their newest (24 month development cycle)
in the same month as you. This has been fixed, *fully fixed*, for over a
year now. Epic fail.

mscs@water:~$ sudo -V
Sudo version 1.8.10p3
Sudoers policy plugin version 1.8.10p3
Sudoers file grammar version 43
Sudoers I/O plugin version 1.8.10p3
mscs@water:~$ 


https://packages.debian.org/search?keywords=sudo
https://launchpad.net/ubuntu/+source/sudo

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

 Debian hasn't fixed this in squeeze or wheezy yet, it's fixed in
jessie because they have a recent enough version of sudo.

They haven't fixed it because they were never vulnerable: they don't
allow you to change the clock without a password.

 We do plan on backporting monolithic timer support, we just have not
had time yet.

Was a year and two releases not enough time?

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions

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

[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

[Mark Smith]

Really? If the terminal I last ran sudo in is open still on the machine,
and it's unlocked, I couldn't simply change the time back to the
previous sudo command an escalate?

Even if it's a remote chance, it's still an easy exploit.

/var/log/auth.log is certainly readable by a program that uses a
different exploit to gain access to that admin user (say, a browser
exploit) and contains the PTY and timestamp. It doesn't even have to be
exact: It just has to be ~ 15 minutes after the last sudo, right?

This is a simple upgrade that even your parent distribution has adopted
for their stable. Why ignore it for over a year? Can you please show me
the information about the inode? My impression was that it was based on
the SID, rather than inode, but perhaps that has changed.

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions

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

[Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure

[Mark smith]

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

But a Dell Inspiron 15R isn't an Dell Inspiron 1525.  ;-)
Glad that script cures it, that script worked well until I installed the kernel 
3.13.0-35.62 on our Dell Inspiron 1525.

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

Title:
  [Dell Inspiron 1525] suspend/resume failure

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

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

[Bug 1331654] Re: [Dell Inspiron 1525] Cannot resume from suspend

[Mark smith]

It looks like linux-image-3.13.0-35-generic (3.13.0-35.62) contains the
fixes for this bug.

Yes it does, I deleted the band-aid fix script in my /etc/pm/sleep.d/
folder and upgraded from  the recommended 3.13.0-24-generic kernel to
3.13.0-35 via the update manager in Mint 17 and our Inspiron 1525 laptop
has since been resuming from sleep without hanging.

My thanks to everyone responsible for finding  fixing this bug!
Mark

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

Title:
  [Dell Inspiron 1525] Cannot resume from suspend

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

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

[Bug 1291075] Re: printer icon does not disappear

[Mark smith]

Same here with two different network printers on Linux Mint 17 Qiana XFCE 
desktop.
The xfce4-panel -r command in a terminal window removes it OK though.

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

Title:
  printer icon does not disappear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1291075/+subscriptions

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

[Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure

[Mark smith]

So I'm assuming that all the scripts in the sleep.d directory get
executed on a suspend/resume event?

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

Title:
  [Dell Inspiron 1525] suspend/resume failure

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

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

[Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure

[Mark smith]

I have 3 files in that directory (sleep.d),

10_grub-common
10_unattended-upgrades-hibernate
novatel_3g_suspend

what would this script be called or is it appended to one of these files?
Thanks!

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

Title:
  [Dell Inspiron 1525] suspend/resume failure

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

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

[Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure

[Mark smith]

I'm running the 3.13.0-30-55 kernel on a 1525 laptop and unfortunately this 
problem still exists.
Suspend always works, resume works maybe 80% of the time. It's the wife's 
laptop so it's high visibility. ;-)
I can give more info if given specific instructions, thanks.

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

Title:
  [Dell Inspiron 1525] suspend/resume failure

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

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

[Bug 418826] Re: [Inspiron 1525] hibernate/resume failure

[Mark smith]

I loaded the 3.14.5-031405-generic kernel  my Inspiron 1525 laptop will still 
not resume from standby about 80% of the time.
Total lockup, must power off.  (kernel 3.13.0-24 acted the same way)  :-(
I'm running the XFCE desktop in Mint 17.

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

Title:
  [Inspiron 1525] hibernate/resume failure

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

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

[Bug 1328313] Card0.Codecs.codec.0.txt

[Mark Smith]

apport information

** Attachment added: Card0.Codecs.codec.0.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129129/+files/Card0.Codecs.codec.0.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] AlsaDevices.txt

[Mark Smith]

apport information

** Attachment added: AlsaDevices.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129125/+files/AlsaDevices.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] Card0.Amixer.values.txt

[Mark Smith]

apport information

** Attachment added: Card0.Amixer.values.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129128/+files/Card0.Amixer.values.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] Re: Alps Touchpad acts erratically when multi-touch is vertical, not horizontal

[Mark Smith]

apport information

** Tags added: apport-collected

** Description changed:

  I'm on a Dell Latitude E7240 running 12.04 LTS and my touch pad acts 
erratically. It happens because my middle and ring fingers accidentally touch 
the top edge of the pad while my pointer finger is moving the cursor. I can 
reproduce this on purpose by running xinput --test [device number] and 
watching the events while I do the following:
  - Touch the pad near the middle or bottom. The cursor moves slightly as my 
finger wiggles around.
  - Without removing the first finger, touch the pad again with a second finger 
above the first finger. The cursor shoots up to a[1]=0 (which is the y 
position).
  - Without removing the first finger, remove the second (top) finger. The 
cursor shoots back down to a[1]=some large number Sometimes it takes it all 
the way to the bottom of the screen, sometimes it goes back to where it was, or 
somewhere else. I haven't been able to figure out how it decides what to go 
back to.
  
  With this, while I touching with my pointer finger and my middle or ring
  finger accidentally touch the pad at the top, the cursor shoots where I
  don't want it. Then when my middle/ring finger leaves the pad (usually
  because I started cursing (get it?) at my cursor), it shoots back down
  again somewhere completely arbitrary.
  
  Similarly:
  - Touch the bad near the top.
  - Without removing the top finger, touch somewhere near the bottom. The 
cursor doesn't (yet) move.
  - Lift the top finger. The cursor shoots to the bottom.
  - Put down the top finger again, without lifting the bottom. The cursor 
shoots back up again.
  
  You can make the cursor shoot up and down just by keeping your bottom
  finger down and tapping the top finger. The cursor follows the top
  finger no matter what you do.
  
  Interestingly, this does NOT happen from side-to-side. Two touches side-
  by-side trigger the multi-touch gestures and don't move the cursor.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53~precise1
  ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Jun  9 16:59:49 2014
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-29-generic.
+ ApportVersion: 2.0.1-0ubuntu17.6
+ Architecture: amd64
+ ArecordDevices:
+   List of CAPTURE Hardware Devices 
+  card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
+Subdevices: 1/1
+Subdevice #0: subdevice #0
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  mrksmith   2576 F pulseaudio
+  /dev/snd/controlC0:  mrksmith   2576 F pulseaudio
+ CRDA: Error: [Errno 2] No such file or directory
+ Card0.Amixer.info:
+  Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7e34000 irq 64'
+Mixer name : 'Intel Haswell HDMI'
+Components : 'HDA:80862807,80860101,0010'
+Controls  : 21
+Simple ctrls  : 3
+ Card1.Amixer.info:
+  Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 65'
+Mixer name : 'Realtek ALC292'
+Components : 'HDA:10ec0292,102805ca,0011'
+Controls  : 28
+Simple ctrls  : 13
+ DistroRelease: Ubuntu 12.04
+ HibernationDevice: RESUME=UUID=303359b5-1c66-468d-935e-a6d9bc56e4e9
+ MachineType: Dell Inc. Latitude E7240
+ MarkForUpload: True
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic 
root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-29.53~precise1-generic 3.13.11.2
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-29-generic N/A
+  linux-backports-modules-3.13.0-29-generic  N/A
+  linux-firmware 1.79.14
+ Tags:  precise running-unity
+ Uname: Linux 3.13.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo
+ dmi.bios.date: 02/18/2014
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A08
+ dmi.board.asset.tag: 1201037379
+ dmi.board.name: 0531FD
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.asset.tag: 1201037379
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Latitude E7240
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.

** Attachment added: AcpiTables.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129124/+files/AcpiTables.txt

-- 
You received this bug 

[Bug 1328313] Card1.Codecs.codec.0.txt

[Mark Smith]

apport information

** Attachment added: Card1.Codecs.codec.0.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129131/+files/Card1.Codecs.codec.0.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] AplayDevices.txt

[Mark Smith]

apport information

** Attachment added: AplayDevices.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129126/+files/AplayDevices.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] BootDmesg.txt

[Mark Smith]

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129127/+files/BootDmesg.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] Lspci.txt

[Mark Smith]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1328313/+attachment/4129134/+files/Lspci.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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

[Bug 1328313] ProcInterrupts.txt

[Mark Smith]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1328313/+attachment/4129138/+files/ProcInterrupts.txt

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

Title:
  Alps Touchpad acts erratically when multi-touch is vertical, not
  horizontal

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

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