[Bug 2071463] [NEW] Duplicate unread message notifications between dash and dock

[Jake Hoban]

Public bug reported:

When there are unread messages in a messaging app (e.g. Mattermost,
Telegram, Proton Mail, whatsapp-for-linux - some of these are installed
from deb and some from snap) the unread count appears in the dash, but
stays after I've read the messages unless I also dismiss it from the
Gnome dock notification centre. The only way to stop that behaviour
seems to be to set "do not disturb" in Gnome dock but that's not what i
want. I want notifications for unread messages, which disappear
automatically when I've read them.

Screenshot attached - Mattermost icon in dash shows 3 unread messages,
although they have all been read.  At the top you see the notification
centre where I have to click away the messages to make the count on the
icon go down.

Ubuntu 24.04, gnome-shell 46.0-0ubuntu5.1

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
Uname: Linux 6.8.0-36-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 28 13:20:03 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-05-12 (47 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-05-13 (46 days ago)

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


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

** Attachment added: "Screenshot from 2024-06-28 13-26-53.png"
   
https://bugs.launchpad.net/bugs/2071463/+attachment/5793084/+files/Screenshot%20from%202024-06-28%2013-26-53.png

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

Title:
  Duplicate unread message notifications between dash and dock

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


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

[Bug 2069206] Re: Sticky keys being enabled prevents login to GNOME

[Jake]

Looks like Settings > Accessibility > Typing > Enable by Keyboard must
be off as well to log in (gsettings set org.gnome.desktop.a11y.keyboard
enable false).

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

Title:
  Sticky keys being enabled prevents login to GNOME

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


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

[Bug 2069206] Re: Sticky keys being enabled prevents login to GNOME

[Jake]

** Description changed:

  When Sticky Keys is enabled for a user in GNOME Settings > Accessibility
  > Typing in Ubuntu 23.10, after typing the user's password to log in, a
  black screen appears momentarily and then the login screen returns, with
  journalctl showing:
  
  snapd-desktop-i[20093]: Failed to do gtk init. Waiting for a new session with 
desktop capabilities.
  snapd-desktop-i[20093]: Checking session 
/org/freedesktop/login1/session/_324...
  snapd-desktop-i[20093]: Is a desktop session! Forcing a reload.
  snapd-desktop-i[20093]: Checking session /org/freedesktop/login1/session/c8...
  snapd-desktop-i[20093]: Checking session 
/org/freedesktop/login1/session/_318...
  snapd-desktop-i[20093]: Loop exited. Forcing reload.
  systemd[13871]: org.gnome.Shell@wayland.service: Main process exited, 
code=dumped, status=11/SEGV
  systemd[13871]: org.gnome.Shell@wayland.service: Failed with result 
'core-dump'.
  systemd[13871]: Failed to start org.gnome.Shell@wayland.service - GNOME Shell 
on Wayland.
  
  This happens on a different, newer user account too, as well as while
  moving all hidden files in $HOME to a backup folder and only enabling
  Sticky Keys via gsettings before logging in.
  
  Performing "gsettings set org.gnome.desktop.a11y.keyboard stickykeys-
  enable false" in a different tty first allows logging in.
  
+ --
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-41.41-generic 6.5.13
  Uname: Linux 6.5.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Wed Jun 12 13:35:30 2024
  InstallationDate: Installed on 2023-03-23 (447 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to mantic on 2024-05-30 (13 days ago)

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

Title:
  Sticky keys being enabled prevents login to GNOME

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


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

[Bug 2069206] [NEW] Sticky keys being enabled prevents login to GNOME

[Jake]

Public bug reported:

When Sticky Keys is enabled for a user in GNOME Settings > Accessibility
> Typing in Ubuntu 23.10, after typing the user's password to log in, a
black screen appears momentarily and then the login screen returns, with
journalctl showing:

snapd-desktop-i[20093]: Failed to do gtk init. Waiting for a new session with 
desktop capabilities.
snapd-desktop-i[20093]: Checking session /org/freedesktop/login1/session/_324...
snapd-desktop-i[20093]: Is a desktop session! Forcing a reload.
snapd-desktop-i[20093]: Checking session /org/freedesktop/login1/session/c8...
snapd-desktop-i[20093]: Checking session /org/freedesktop/login1/session/_318...
snapd-desktop-i[20093]: Loop exited. Forcing reload.
systemd[13871]: org.gnome.Shell@wayland.service: Main process exited, 
code=dumped, status=11/SEGV
systemd[13871]: org.gnome.Shell@wayland.service: Failed with result 'core-dump'.
systemd[13871]: Failed to start org.gnome.Shell@wayland.service - GNOME Shell 
on Wayland.

This happens on a different, newer user account too, as well as while
moving all hidden files in $HOME to a backup folder and only enabling
Sticky Keys via gsettings before logging in.

Performing "gsettings set org.gnome.desktop.a11y.keyboard stickykeys-
enable false" in a different tty first allows logging in.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 6.5.0-41.41-generic 6.5.13
Uname: Linux 6.5.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed Jun 12 13:35:30 2024
InstallationDate: Installed on 2023-03-23 (447 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: meta-gnome3
UpgradeStatus: Upgraded to mantic on 2024-05-30 (13 days ago)

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


** Tags: amd64 apport-bug mantic 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/2069206

Title:
  Sticky keys being enabled prevents login to GNOME

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


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

[Bug 2065838] Re: System crash on resume from sleep

[Jake]

I am having the exact same issue.


OS: Ubuntu 24.04 LTS
Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC
CPU: 12th Gen Intel(R) Core(TM) i7-12700H
-
jake@CodeBox:~/temp$ cat lshw.txt 
H/W path   Device   Class  Description
==
system 21DCCTO1WW 
(LENOVO_MT_21DC_BU_Think_FM_ThinkPad P1 Gen 5)
/0  bus21DCCTO1WW
/0/1memory 64GiB System Memory
/0/1/0  memory 32GiB SODIMM Synchronous 
4800 MHz (0.2 ns)
/0/1/1  memory 32GiB SODIMM Synchronous 
4800 MHz (0.2 ns)
/0/cmemory 288KiB L1 cache
/0/dmemory 192KiB L1 cache
/0/ememory 7680KiB L2 cache
/0/fmemory 24MiB L3 cache
/0/10   memory 256KiB L1 cache
/0/11   memory 512KiB L1 cache
/0/12   memory 4MiB L2 cache
/0/13   memory 24MiB L3 cache
/0/14   processor  12th Gen Intel(R) 
Core(TM) i7-12700H
/0/15   memory 128KiB BIOS
/0/100  bridge 12th Gen Core Processor 
Host Bridge/DRAM Registers
/0/100/1bridge 12th Gen Core Processor 
PCI Express x16 Controller #1
/0/100/1/0 /dev/fb0 displayGA107GLM [RTX A1000 
Laptop GPU]
/0/100/1/0.1   card0multimedia NVIDIA Corporation
/0/100/1/0.1/0 input13  input  HDA NVidia HDMI/DP,pcm=3
/0/100/1/0.1/1 input14  input  HDA NVidia HDMI/DP,pcm=7
/0/100/1/0.1/2 input15  input  HDA NVidia HDMI/DP,pcm=8
/0/100/1/0.1/3 input16  input  HDA NVidia HDMI/DP,pcm=9
/0/100/2   /dev/fb0 displayAlder Lake-P GT2 [Iris 
Xe Graphics]
/0/100/4genericAlder Lake Innovation 
Platform Framework Processor Participant
/0/100/6bridge 12th Gen Core Processor 
PCI Express x4 Controller #0
/0/100/6/0 /dev/nvme0   storageWD PC SN810 
SDCQNRY-1T00-1001
/0/100/6/0/0   hwmon3   disk   NVMe disk
/0/100/6/0/2   /dev/ng0n1   disk   NVMe disk
/0/100/6/0/1   /dev/nvme0n1 disk   1024GB NVMe disk
/0/100/6/0/1/1 /dev/nvme0n1p1   volume 99MiB Windows FAT volume
/0/100/6/0/1/2 /dev/nvme0n1p2   volume 15MiB reserved partition
/0/100/6/0/1/3 /dev/nvme0n1p3   volume 464GiB Windows NTFS 
volume
/0/100/6/0/1/4 /dev/nvme0n1p4   volume 624MiB Windows NTFS 
volume
/0/100/6/0/1/5 /dev/nvme0n1p5   volume 488GiB EXT4 volume
/0/100/8generic12th Gen Core Processor 
Gaussian & Neural Accelerator
/0/100/agenericPlatform Monitoring 
Technology
/0/100/14   busAlder Lake PCH USB 3.2 
xHCI Host Controller
/0/100/14/0usb1 busxHCI Host Controller
/0/100/14/0/1   busUSB2.0 Hub
/0/100/14/0/1/4 busUSB2.0 Hub
/0/100/14/0/1/4/2   busUSB 2.0 Hub [MTT]
/0/100/14/0/1/4/2/1 genericUSB-Serial Bridge
/0/100/14/0/1/4/4   busUSB 2.0 Hub
/0/100/14/0/1/4/4/1 input  USB Receiver
/0/100/14/0/1/4/4/1/0  input43  input  Logitech Wireless 
Keyboard PID:4023
/0/100/14/0/1/4/4/1/1  input44  input  Logitech Wireless Mouse
/0/100/14/0/1/4/4/2card3multimedia DeSheng Electronics Inc. 
XIBERIA
/0/100/14/0/1/4/4/4input31  input  SINOWEALTH 2.4G Wireless 
Receiver Keyboard
/0/100/14/0/6   genericGeneric USB device
/0/100/14/0/8   multimedia Integrated Camera
/0/100/14/0/a   communication  AX211 Bluetooth
/0/100/14/1usb2 busxHCI Host Controller
/0/100/14.2 memory RAM memory
/0/100/14.3wlp0s20f3networkAlder Lake-P PCH CNVi 
WiFi
/0/100/15   busAlder Lake PCH Serial IO 
I2C Controller #0
/0/100/16   communication  A

[Bug 1461834] Re: 1024-bit signing keys should be deprecated

[Jake Lepere]

Enabling FIPS on Ubuntu Pro 22.04+ machines [1] drops rsa1024 as an
available encryption key because rsa1024 isn't FIPS compliant.
Therefore, adding rsa1024 signed apt keys here isn't possible.


Does anyone have suggestions to work around this? I've asked if maintainers 
could resign apt keys for relevant repos but haven't heard back. Additionally, 
adding apt keys before enabling FIPS works, but future apt updates 
unfortunately fail afterwards.

[1] https://ubuntu.com/security/certifications/docs/fips-enablement

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

Title:
  1024-bit signing keys should be deprecated

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


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

[Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"

[Jake Commons]

https://bugzilla.kernel.org/show_bug.cgi?id=218654

** Bug watch added: Linux Kernel Bug Tracker #218654
   https://bugzilla.kernel.org/show_bug.cgi?id=218654

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

Title:
  System unstable, kernel ring buffer flooded with "BUG: Bad page state
  in process swapper/0"

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


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

[Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"

[Jake Commons]

All of my VMs running 6.8 under Xen with XCP-ng are impacted. Also
affects non-Ubuntu distros with vanilla 6.8.1 kernels. 6.7.9 runs fine.

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

Title:
  System unstable, kernel ring buffer flooded with "BUG: Bad page state
  in process swapper/0"

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


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

Can the python3 package be updated

[Jake Kaphingst]

3.10.5 was released the other day.
I am using an app that relies on system python and is suffering from a bug that 
was patched in 3.10.5

Sent from Nine
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

[Bug 1974076] Re: /home/xubuntu/Desktop/xfce4-session-xubuntu:0

[jake]

xfce4-session for ubuntu is missing an important file required for
xfce4-session to run properly without crashing the required file must be
patched by creating a file in the directory for the missing file
xfce4-session for ubuntu is missing an important file required for
xfce4-session to run properly without crashing the required file must be
patched by creating a file in the directory for the missing file in
/home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0

when you do a fresh install of any ubuntu 18.04.5 LTS
do these commands then update/upgrade your system
for all the patches to take place.

run the commands to fix it yourself

nano /home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0

** Changed in: xfce4-session (Ubuntu)
   Status: New => Confirmed

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

Title:
  /home/xubuntu/Desktop/xfce4-session-xubuntu:0

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


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

[Bug 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

[jake]

libreoffice for ubuntu is missing an important symlink required for
libreoffice to run properly without crashing the required file must be
patched by creating a symlink in the directory for the missing symlink
in /root/.config/libreoffice/4/user/config/

when you do a fresh install of any ubuntu 18.04.5 LTS
do these commands then update/upgrade your system
for all the patches to take place.

run the commands to fix it yourself

ln -s /home/xubuntu/Desktop/libreoffice/javasettings_Linux_X86_64.xml
/home/xubuntu/Desktop/libreoffice/javasettings_Linux_*.xml

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

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


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

[Bug 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

[jake]

** Attachment added: "javasettings_Linux_*.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590981/+files/javasettings_Linux_%2A.xml

** Patch removed: "javasettings_Linux_X86_64.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590980/+files/javasettings_Linux_X86_64.xml

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => jake (adam21232323)

** Changed in: libreoffice (Ubuntu)
   Status: New => Confirmed

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

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


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

[Bug 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

[jake]

** Attachment removed: 
"/root/.config/libreoffice/4/user/config/javasettings_Linux_*.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590973/+files/ProcCpuinfoMinimal.txt

** Attachment added: "javasettings_Linux_X86_64.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590980/+files/javasettings_Linux_X86_64.xml

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

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


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

[Bug 1974076] Re: (xfce4-session:1675): xfce4-session-WARNING **: 17:47:35.298: xfsm_manager_load_session: Something wrong with /home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0, Does it exist? Pe

[jake]

** Patch removed: "/home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0"
   
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1974076/+attachment/5590975/+files/ProcCpuinfoMinimal.txt

** Attachment added: "xfce4-session-xubuntu:0"
   
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1974076/+attachment/5590979/+files/xfce4-session-xubuntu%3A0

** Summary changed:

- (xfce4-session:1675): xfce4-session-WARNING **: 17:47:35.298: 
xfsm_manager_load_session: Something wrong with 
/home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0, Does it exist? 
Permissions issue?
+ /home/xubuntu/Desktop/xfce4-session-xubuntu:0

** Description changed:

- (xfce4-session:1675): xfce4-session-WARNING **: 17:47:35.298:
- xfsm_manager_load_session: Something wrong with
- /home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0, Does it exist?
- Permissions issue?
+ /home/xubuntu/Desktop/xfce4-session-xubuntu:0 is missing

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

Title:
  /home/xubuntu/Desktop/xfce4-session-xubuntu:0

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


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

[Bug 1974074] Re: libreoffice crashes because of a missing symlink

[jake]

** Tags removed: amd64 bionic

** Description changed:

- libreoffice crashes if you dont add a symlink in
- /root/.config/libreoffice/4/user/config/ named  javasettings_Linux_*.xml
- by creating a symlink with ln -s javasettings_Linux_X86_64.xml
- javasettings_Linux_*.xml that fixes the problem please add a bug fix by
- automatically creating this symlink to prevent libreoffice from crashing
- in a future update or upgrade.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: libreoffice (installed)
- ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
- Uname: Linux 5.4.0-42-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.16
- Architecture: amd64
- CasperVersion: 1.394.3
- CurrentDesktop: XFCE
- Date: Wed May 18 18:04:17 2022
- LiveMediaBuild: Xubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
- SourcePackage: libreoffice
- UpgradeStatus: No upgrade log present (probably fresh install)
+ missing symlink in
+ /root/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

** Description changed:

- missing symlink in
- /root/.config/libreoffice/4/user/config/javasettings_Linux_*.xml
+ missing symlink in /root/.config/libreoffice/4/user/config/
+ 
+ javasettings_Linux_*.xml

** Attachment added: "Screenshot_2022-05-18_18-40-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590976/+files/Screenshot_2022-05-18_18-40-29.png

** Information type changed from Private Security to Public

** Summary changed:

- libreoffice crashes because of a missing symlink
+ missing symlink in /root/.config/libreoffice/4/user/config/

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

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


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

[Bug 1974076] Re: (xfce4-session:1675): xfce4-session-WARNING **: 17:47:35.298: xfsm_manager_load_session: Something wrong with /home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0, Does it exist? Pe

[jake]

** Information type changed from Private Security to Public

** Description changed:

  (xfce4-session:1675): xfce4-session-WARNING **: 17:47:35.298:
  xfsm_manager_load_session: Something wrong with
  /home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0, Does it exist?
  Permissions issue?
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: xfce4-session 4.12.1-3ubuntu3
- ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
- Uname: Linux 5.4.0-42-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.16
- Architecture: amd64
- CasperVersion: 1.394.3
- CurrentDesktop: XFCE
- Date: Wed May 18 18:30:03 2022
- LiveMediaBuild: Xubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
- SourcePackage: xfce4-session
- 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/1974076

Title:
  (xfce4-session:1675): xfce4-session-WARNING **: 17:47:35.298:
  xfsm_manager_load_session: Something wrong with
  /home/xubuntu/.cache/sessions/xfce4-session-xubuntu:0, Does it exist?
  Permissions issue?

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


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

[Bug 1971203] [NEW] Trying to upgrade from 20.04 lts to 22.04 lts but kept getting error messages in terminal

[Jake Doed]

Public bug reported:

Below is the command(s) I used in terminal to attempt the upgrade and
all the outputs it gave me.

$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]

   
Get:2 Upgrade tool [1,261 kB]   

   
Fetched 1,262 kB in 0s (0 B/s)  

   
authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' 
extracting 'jammy.tar.gz'

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]   

   
Hit http://archive.ubuntu.com/ubuntu focal InRelease

   
Hit http://us.archive.ubuntu.com/ubuntu focal InRelease 

   
Hit http://us.archive.ubuntu.com/ubuntu focal-updates InRelease 

   
Hit http://us.archive.ubuntu.com/ubuntu focal-backports InRelease   

   
Fetched 114 kB in 0s (0 B/s)

   
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Connection to Snap Store failed

Your system does not have a connection to the Snap Store. For the 
best upgrade experience make sure that your system can connect to 
api.snapcraft.io. 
Do you still want to continue with the upgrade? 

Continue [yN] y

Updating repository information

Third party sources disabled

Some third party entries in your sources.list were disabled. You can 
re-enable them after the upgrade with the 'software-properties' tool 
or your package manager. 

To continue please press [ENTER]

Fetched 0 B in 0s (0 B/s)

Checking package manager
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Invalid package information

After updating your package information, the essential package 
'ubuntu-minimal' could not be located. This may be because you have 
no official mirrors listed in your software sources, or because of 
excessive load on the mirror you are using. See /etc/apt/sources.list 
for the current list of configured software sources. 
In the case of an overloaded mirror, you may want to try the upgrade 
again later. 


Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree  
Reading state information... Done

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.38
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
Date: Mon May  2 16:20:25 2022
InstallationDate: Installed on 2022-05-02 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2022-05-02 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2022-05-02 16:19:43.993098
 Log time: 2022-05-02 16:19:46.324357
 Log time: 2022-05-02 16:20:25.186042
 Log time: 2022-05-02 16:20:26.734146

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


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

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

Title:
  Trying to upgrade from 20.04 lts to 22.04 lts but kept getting error
  messages in terminal

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


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

[Bug 1971064] [NEW] installer crashed on attempt to install root boot ZFS with encryption on Secureboot enabled Lenovo Thinkpad P1, UEFI

[Jake Carroll]

Public bug reported:

Laptop is configured for secureboot.

Will safely and correctly install with EXT4 + Encrypted boot but not
ZFS.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.470
CurrentDesktop: ubuntu:GNOME
Date: Sun May  1 13:47:18 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANGUAGE=en_AU.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  installer crashed on attempt to install root boot ZFS with encryption
  on Secureboot enabled Lenovo Thinkpad P1, UEFI

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


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

[Bug 1968412] [NEW] When trying to open the program it says that i need to be in a special group to use it

[Jake]

Public bug reported:

Version: 0.99.22
Kubuntu version 22.04
I expected it to open up the software properties without any errors.
It said that i need to be in a special group (wheel) to use it.
It says the password is incorrect even though i use this password to log in.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-qt 0.99.22
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sat Apr  9 11:59:59 2022
InstallationDate: Installed on 2022-04-09 (0 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  When trying to open the program it says that i need to be in a special
  group to use it

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


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

[Bug 1955642] [NEW] package liborocos-kdl-dev:arm64 1.4.0-7ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Jake Costi]

Public bug reported:

This error occurred after running sudo apt upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: liborocos-kdl-dev:arm64 1.4.0-7ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-1047.52-raspi 5.4.151
Uname: Linux 5.4.0-1047-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: arm64
CasperMD5CheckResult: skip
Date: Thu Dec 23 11:52:05 2021
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
ImageMediaBuild: 20210819.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: orocos-kdl
Title: package liborocos-kdl-dev:arm64 1.4.0-7ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: orocos-kdl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 arm64-image focal raspi-image uec-images

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

Title:
  package liborocos-kdl-dev:arm64 1.4.0-7ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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


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

[Bug 1952352] [NEW] Server group creation fails on Xena

[Jake Hill]

Public bug reported:

Due to nova API changes in Xena.

ubuntu@temp:~$ openstack stack event list --follow 
3d6f356c-d938-45e8-9f47-659c5fa17a86
2021-11-25 17:54:17Z [test-cluster-ct5rkxe453yi]: CREATE_IN_PROGRESS  Stack 
CREATE started
2021-11-25 17:54:19Z [test-cluster-ct5rkxe453yi.worker_nodes_server_group]: 
CREATE_IN_PROGRESS  state changed
2021-11-25 17:54:19Z [test-cluster-ct5rkxe453yi.worker_nodes_server_group]: 
CREATE_FAILED  TypeError: resources.worker_nodes_server_group: create() got an 
unexpected keyword argument 'policies'
2021-11-25 17:54:19Z [test-cluster-ct5rkxe453yi]: CREATE_FAILED  Resource 
CREATE failed: TypeError: resources.worker_nodes_server_group: create() got an 
unexpected keyword argument 'policies'

This with heat-engine 1:17.0.0-0ubuntu1~cloud0

I think a fix for this is committed upstream?

  https://review.opendev.org/c/openstack/heat/+/814353

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

** Description changed:

  Due to nova API changes in Xena.
  
  ubuntu@temp:~$ openstack stack event list --follow 
3d6f356c-d938-45e8-9f47-659c5fa17a86
  2021-11-25 17:54:17Z [test-cluster-ct5rkxe453yi]: CREATE_IN_PROGRESS  Stack 
CREATE started
  2021-11-25 17:54:19Z [test-cluster-ct5rkxe453yi.worker_nodes_server_group]: 
CREATE_IN_PROGRESS  state changed
  2021-11-25 17:54:19Z [test-cluster-ct5rkxe453yi.worker_nodes_server_group]: 
CREATE_FAILED  TypeError: resources.worker_nodes_server_group: create() got an 
unexpected keyword argument 'policies'
  2021-11-25 17:54:19Z [test-cluster-ct5rkxe453yi]: CREATE_FAILED  Resource 
CREATE failed: TypeError: resources.worker_nodes_server_group: create() got an 
unexpected keyword argument 'policies'
  
+ This with heat-engine 1:17.0.0-0ubuntu1~cloud0
+ 
  I think a fix for this is committed upstream?
  
-   https://review.opendev.org/c/openstack/heat/+/814353
+   https://review.opendev.org/c/openstack/heat/+/814353

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

Title:
  Server group creation fails on Xena

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


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

[Bug 1929591] Re: MD RAID 6 Periodic Kernel Panic Stack Overflow Double-Fault

[Jake Staehle]

Another one today on 5.8.0-55:

[  OK  ] Started Hostname Service.
[  OK  ] Started User Login Management.
[  OK  ] Started Docker Application Container Engine.

Ubuntu 20.10 babylon ttyS0

babylon login: [   43.284962] cloud-init[6278]: Cloud-init v. 
21.2-3-g899bfaa9-0ubuntu2~20.10.1 running 'modules:config' at Thu, 17 Jun 2021 
04:50:23 +. Up 43.23 seconds.
[   43.555449] cloud-init[6294]: Cloud-init v. 
21.2-3-g899bfaa9-0ubuntu2~20.10.1 running 'modules:final' at Thu, 17 Jun 2021 
04:50:23 +. Up 43.48 seconds.
[   43.59] cloud-init[6294]: Cloud-init v. 
21.2-3-g899bfaa9-0ubuntu2~20.10.1 finished at Thu, 17 Jun 2021 04:50:23 +. 
Datasource DataSourceNone.  Up 43.55 seconds
[   43.98] cloud-init[6294]: 2021-06-17 04:50:23,906 - 
cc_final_message.py[WARNING]: Used fallback datasource
[470667.791418] BUG: stack guard page was hit at 6cd7c52c (stack is 
b38fb7cf..d2b542d2)
[470667.791418] kernel stack overflow (double-fault):  [#1] SMP NOPTI
[470667.791418] CPU: 15 PID: 514 Comm: md0_raid6 Tainted: P   OE 
5.8.0-55-generic #62-Ubuntu
[470667.791419] Hardware name: Gigabyte Technology Co., Ltd. B550M AORUS 
PRO/B550M AORUS PRO, BIOS F13h 04/23/2021
[470667.791419] RIP: 0010:slab_free_freelist_hook+0x35/0x120
[470667.791419] Code: 89 d5 41 54 49 89 f4 53 48 89 fb 48 83 ec 08 48 8b 02 4c 
8b 36 48 c7 06 00 00 00 00 48 c7 02 00 00 00 00 48 85 c0 49 0f 44 c6 <48> 89 45 
d0 eb 06 4c 3b 7d d0 74 5d 8b 53 20 4d 89 f7 49 8d 34 16
[470667.791419] RSP: 0018:9b13808b3ff8 EFLAGS: 00010246
[470667.791420] RAX: 8c43bd86d9c0 RBX: 8c459b407800 RCX: 
0001
[470667.791420] RDX: 9b13808b4040 RSI: 9b13808b4038 RDI: 
8c459b407800
[470667.791420] RBP: 9b13808b4028 R08: 0001 R09: 
ae641900
[470667.791421] R10: 8c43bd86d1e0 R11: 0001 R12: 
9b13808b4038
[470667.791421] R13: 9b13808b4040 R14: 8c43bd86d9c0 R15: 
8c4585ea1070
[470667.791421] FS:  () GS:8c459edc() 
knlGS:
[470667.791421] CS:  0010 DS:  ES:  CR0: 80050033
[470667.791422] CR2: 9b13808b3fe8 CR3: 0007948a8000 CR4: 
00340ee0
[470667.791422] Call Trace:
[470667.791422]  ? mempool_kfree+0xe/0x10
[470667.791422]  ? kfree+0xb8/0x220
[470667.791422]  ? mempool_kfree+0xe/0x10
[470667.791422]  ? mempool_free+0x2f/0x80
[470667.791422]  ? md_end_io+0x4b/0x70
[470667.791423]  ? bio_endio+0xe6/0x150
[470667.791423]  ? bio_chain_endio+0x2d/0x40
[470667.791423]  ? md_end_io+0x5d/0x70
[470667.791423]  ? bio_endio+0xe6/0x150
[470667.791423]  ? bio_chain_endio+0x2d/0x40
[470667.791423]  ? md_end_io+0x5d/0x70
[470667.791423]  ? bio_endio+0xe6/0x150
[470667.791424]  ? bio_chain_endio+0x2d/0x40
[470667.791424]  ? md_end_io+0x5d/0x70
[470667.791424]  ? bio_endio+0xe6/0x150
[470667.791424]  ? bio_chain_endio+0x2d/0x40
[470667.791424]  ? md_end_io+0x5d/0x70
[470667.791424]  ? bio_endio+0xe6/0x150
[470667.791424]  ? bio_chain_endio+0x2d/0x40
[470667.791424]  ? md_end_io+0x5d/0x70
[470667.791425]  ? bio_endio+0xe6/0x150
[470667.791425]  ? bio_chain_endio+0x2d/0x40
[470667.791425]  ? md_end_io+0x5d/0x70
[470667.791425]  ? bio_endio+0xe6/0x150
[470667.791425]  ? bio_chain_endio+0x2d/0x40
[470667.791425]  ? md_end_io+0x5d/0x70
[470667.791425]  ? bio_endio+0xe6/0x150
[470667.791425]  ? bio_chain_endio+0x2d/0x40
[470667.791426]  ? md_end_io+0x5d/0x70
[470667.791426]  ? bio_endio+0xe6/0x150
[470667.791426]  ? bio_chain_endio+0x2d/0x40
[470667.791426]  ? md_end_io+0x5d/0x70
[470667.791426]  ? bio_endio+0xe6/0x150
[470667.791426]  ? bio_chain_endio+0x2d/0x40
[470667.791426]  ? md_end_io+0x5d/0x70
[470667.791427]  ? bio_endio+0xe6/0x150
[470667.791427]  ? bio_chain_endio+0x2d/0x40
[470667.791427]  ? md_end_io+0x5d/0x70
[470667.791427]  ? bio_endio+0xe6/0x150
[470667.791427]  ? bio_chain_endio+0x2d/0x40
[470667.791427]  ? md_end_io+0x5d/0x70
[470667.791427]  ? bio_endio+0xe6/0x150
[470667.791427]  ? bio_chain_endio+0x2d/0x40
[470667.791428]  ? md_end_io+0x5d/0x70
[470667.791428]  ? bio_endio+0xe6/0x150
[470667.791428]  ? bio_chain_endio+0x2d/0x40
[470667.791428]  ? md_end_io+0x5d/0x70
[470667.791428]  ? bio_endio+0xe6/0x150
[470667.791428]  ? bio_chain_endio+0x2d/0x40
[470667.791428]  ? md_end_io+0x5d/0x70
[470667.791429]  ? bio_endio+0xe6/0x150
[470667.791429]  ? bio_chain_endio+0x2d/0x40
[470667.791429]  ? md_end_io+0x5d/0x70
[470667.791429]  ? bio_endio+0xe6/0x150
[470667.791429]  ? bio_chain_endio+0x2d/0x40
[470667.791429]  ? md_end_io+0x5d/0x70
[470667.791429]  ? bio_endio+0xe6/0x150
[470667.791429]  ? bio_chain_endio+0x2d/0x40
[470667.791430]  ? md_end_io+0x5d/0x70
[470667.791430]  ? bio_endio+0xe6/0x150
[470667.791430]  ? bio_chain_endio+0x2d/0x40
[470667.791430]  ? md_end_io+0x5d/0x70
[470667.791430]  ? bio_endio+0xe6/0x150
[470667.791430]  ? bio_chain_endio+0x2d/0x40
[470667.791430]  ? md_end_io+0x5d/0x70
[470667.791430]  ? bio_endio+0xe6/0x150
[470667.791431]  ? 

[Bug 1929591] Re: MD RAID 6 Periodic Kernel Panic Stack Overflow Double-Fault

[Jake Staehle]

Hey so this is totally still happening on kernel 5.8.0-53. Just got this
serial console capture:


babylon login: [1457468.880947] BUG: stack guard page was hit at 
7aef1a4a (stack is af9c61cd..7ccda653)
[1457468.880948] kernel stack overflow (double-fault):  [#1] SMP NOPTI
[1457468.880948] CPU: 3 PID: 512 Comm: md0_raid6 Tainted: P   OE 
5.8.0-53-generic #60-Ubuntu
[1457468.880949] Hardware name: Gigabyte Technology Co., Ltd. B550M AORUS 
PRO/B550M AORUS PRO, BIOS F13h 04/23/2021
[1457468.880949] RIP: 0010:slab_free_freelist_hook+0x35/0x120
[1457468.880950] Code: 89 d5 41 54 49 89 f4 53 48 89 fb 48 83 ec 08 48 8b 02 4c 
8b 36 48 c7 06 00 00 00 00 48 c7 02 00 00 00 00 48 85 c0 49 0f 44 c6 <48> 89 45 
d0 eb 06 4c 3b 7d d0 74 5d 8b 53 20 4d 89 f7 49 8d 34 16
[1457468.880951] RSP: 0018:bcda805efff8 EFLAGS: 00010246
[1457468.880952] RAX: 9bfb8ccc42a0 RBX: 9bfcdb407800 RCX: 
0001
[1457468.880952] RDX: bcda805f0040 RSI: bcda805f0038 RDI: 
9bfcdb407800
[1457468.880953] RBP: bcda805f0028 R08: 0001 R09: 
90841600
[1457468.880953] R10: 9bfb8ccc4f40 R11: 0001 R12: 
bcda805f0038
[1457468.880953] R13: bcda805f0040 R14: 9bfb8ccc42a0 R15: 
9bf766967940
[1457468.880954] FS:  () GS:9bfcdeac() 
knlGS:
[1457468.880954] CS:  0010 DS:  ES:  CR0: 80050033
[1457468.880955] CR2: bcda805effe8 CR3: 0003a65ee000 CR4: 
00340ee0
[1457468.880955] Call Trace:
[1457468.880955]  ? mempool_kfree+0xe/0x10
[1457468.880956]  ? kfree+0xb8/0x220
[1457468.880956]  ? mempool_kfree+0xe/0x10
[1457468.880956]  ? mempool_free+0x2f/0x80
[1457468.880956]  ? md_end_io+0x4b/0x70
[1457468.880957]  ? bio_endio+0xe6/0x150
[1457468.880957]  ? bio_chain_endio+0x2d/0x40
[1457468.880957]  ? md_end_io+0x5d/0x70
[1457468.880958]  ? bio_endio+0xe6/0x150
[1457468.880958]  ? bio_chain_endio+0x2d/0x40
[1457468.880958]  ? md_end_io+0x5d/0x70
[1457468.880959]  ? bio_endio+0xe6/0x150
[1457468.880959]  ? bio_chain_endio+0x2d/0x40
[1457468.880959]  ? md_end_io+0x5d/0x70
[1457468.880959]  ? bio_endio+0xe6/0x150
[1457468.880960]  ? bio_chain_endio+0x2d/0x40
[1457468.880960]  ? md_end_io+0x5d/0x70
[1457468.880960]  ? bio_endio+0xe6/0x150
[1457468.880960]  ? bio_chain_endio+0x2d/0x40
[1457468.880961]  ? md_end_io+0x5d/0x70
[1457468.880961]  ? bio_endio+0xe6/0x150
[1457468.880961]  ? bio_chain_endio+0x2d/0x40
[1457468.880962]  ? md_end_io+0x5d/0x70
[1457468.880962]  ? bio_endio+0xe6/0x150
[1457468.880962]  ? bio_chain_endio+0x2d/0x40
[1457468.880962]  ? md_end_io+0x5d/0x70
[1457468.880963]  ? bio_endio+0xe6/0x150
[1457468.880963]  ? bio_chain_endio+0x2d/0x40
[1457468.880963]  ? md_end_io+0x5d/0x70
[1457468.880963]  ? bio_endio+0xe6/0x150
[1457468.880964]  ? bio_chain_endio+0x2d/0x40
[1457468.880964]  ? md_end_io+0x5d/0x70
[1457468.880964]  ? bio_endio+0xe6/0x150
[1457468.880965]  ? bio_chain_endio+0x2d/0x40
[1457468.880965]  ? md_end_io+0x5d/0x70
[1457468.880965]  ? bio_endio+0xe6/0x150
[1457468.880965]  ? bio_chain_endio+0x2d/0x40
[1457468.880966]  ? md_end_io+0x5d/0x70
[1457468.880966]  ? bio_endio+0xe6/0x150
[1457468.880966]  ? bio_chain_endio+0x2d/0x40
[1457468.880966]  ? md_end_io+0x5d/0x70
[1457468.880967]  ? bio_endio+0xe6/0x150
[1457468.880967]  ? bio_chain_endio+0x2d/0x40
[1457468.880967]  ? md_end_io+0x5d/0x70
[1457468.880968]  ? bio_endio+0xe6/0x150
[1457468.880968]  ? bio_chain_endio+0x2d/0x40
[1457468.880968]  ? md_end_io+0x5d/0x70
[1457468.880968]  ? bio_endio+0xe6/0x150
[1457468.880969]  ? bio_chain_endio+0x2d/0x40
[1457468.880969]  ? md_end_io+0x5d/0x70
[1457468.880969]  ? bio_endio+0xe6/0x150
[1457468.880969]  ? bio_chain_endio+0x2d/0x40
[1457468.880970]  ? md_end_io+0x5d/0x70
[1457468.880970]  ? bio_endio+0xe6/0x150
[1457468.880970]  ? bio_chain_endio+0x2d/0x40
[1457468.880971]  ? md_end_io+0x5d/0x70
[1457468.880971]  ? bio_endio+0xe6/0x150
[1457468.880971]  ? bio_chain_endio+0x2d/0x40
[1457468.880971]  ? md_end_io+0x5d/0x70
[1457468.880972]  ? bio_endio+0xe6/0x150
[1457468.880972]  ? bio_chain_endio+0x2d/0x40
[1457468.880972]  ? md_end_io+0x5d/0x70
[1457468.880972]  ? bio_endio+0xe6/0x150
[1457468.880973]  ? bio_chain_endio+0x2d/0x40
[1457468.880973]  ? md_end_io+0x5d/0x70
[1457468.880973]  ? bio_endio+0xe6/0x150
[1457468.880973]  ? bio_chain_endio+0x2d/0x40
[1457468.880974]  ? md_end_io+0x5d/0x70
[1457468.880974]  ? bio_endio+0xe6/0x150
[1457468.880974]  ? bio_chain_endio+0x2d/0x40
[1457468.880975]  ? md_end_io+0x5d/0x70
[1457468.880975]  ? bio_endio+0xe6/0x150
[1457468.880975]  ? bio_chain_endio+0x2d/0x40
[1457468.880975]  ? md_end_io+0x5d/0x70
[1457468.880976]  ? bio_endio+0xe6/0x150
[1457468.880976]  ? bio_chain_endio+0x2d/0x40
[1457468.880976]  ? md_end_io+0x5d/0x70
[1457468.880976]  ? bio_endio+0xe6/0x150
[1457468.880977]  ? bio_chain_endio+0x2d/0x40
[1457468.880977]  ? md_end_io+0x5d/0x70
[1457468.880977]  ? bio_endio+0xe6/0x150

[Bug 1929591] [NEW] MD RAID 6 Periodic Kernel Panic Stack Overflow Double-Fault

[Jake Staehle]

Public bug reported:

Hello:
Every few days I get a kernel panic on my Ubuntu Server 20.10 box, which was 
recently upgraded to a Ryzen 3700X. I have 7 WD Red Pro HDDs in a RAID 6 array 
with Linux MD, and they're all attached to a LSI 9211-8ik PCIe card. 
Motherboard is currently a Gigabyte B550M Aorus Pro. My Ubuntu install is 
running the latest 5.8.0-53 kernel.

This is the 2nd hardware configuration with the exact same kernel panic text. 
Previously I had these HDDs directly connected to the SATA controller of a 
ASRock X570 Pro4 ATX mobo with the same 3700X. I was also previously using 
Ubuntu Server 20.04 LTS -- I had upgraded to 20.10 in hopes that the newer 
kernel would fix it, which it did not.
 
I had posted a whole story on StackOverflow about this journey if you're 
interested: 
https://superuser.com/questions/1615400/md-raid-6-periodic-kernel-panic-possible-kernel-bug
 

However, I am now convinced this is a Linux kernel bug in the MD driver.

Example 1 kernel panic:

[406005.583315] BUG: stack guard page was hit at 7cbff150 (stack is 
3b7072a2..dac5ed08)
[406005.583315] kernel stack overflow (double-fault):  [#1] SMP NOPTI
[406005.583315] CPU: 15 PID: 514 Comm: md0_raid6 Tainted: P   OE 
5.8.0-36-generic #40-Ubuntu
[406005.583316] Hardware name: Gigabyte Technology Co., Ltd. B550M AORUS 
PRO/B550M AORUS PRO, BIOS F1 05/19/2020
[406005.583316] RIP: 0010:slab_free_freelist_hook+0x35/0x120
[406005.583316] Code: 89 d5 41 54 49 89 f4 53 48 89 fb 48 83 ec 08 48 8b 02 4c 
8b 36 48 c7 06 00 00 00 00 48 c7 02 00 00 00 00 48 85 c0 49 0f 44 c6 <48> 89 45 
d0 eb 06 4c 3b 7d d0 74 5d 8b 53 20 4d 89 f7 49 8d 34 16
[406005.583316] RSP: 0018:a620c06e3ff8 EFLAGS: 00010246
[406005.583317] RAX: 9aaf36f54720 RBX: 9ab34b407800 RCX: 
0001
[406005.583317] RDX: a620c06e4040 RSI: a620c06e4038 RDI: 
9ab34b407800
[406005.583317] RBP: a620c06e4028 R08: 0001 R09: 
b9c54500
[406005.583318] R10: 9aaf36f54fe0 R11: 0001 R12: 
a620c06e4038
[406005.583318] R13: a620c06e4040 R14: 9aaf36f54720 R15: 
9ab2925cbd10
[406005.583318] FS:  () GS:9ab34edc() 
knlGS:
[406005.583318] CS:  0010 DS:  ES:  CR0: 80050033
[406005.583318] CR2: a620c06e3fe8 CR3: 0005d52ac000 CR4: 
00340ee0
[406005.583319] Call Trace:
[406005.583319]  ? mempool_kfree+0xe/0x10
[406005.583319]  ? kfree+0xb8/0x220
[406005.583319]  ? mempool_kfree+0xe/0x10
[406005.583319]  ? mempool_free+0x2f/0x80
[406005.583319]  ? md_end_io+0x4b/0x70
[406005.583319]  ? bio_endio+0xe6/0x150


Example 2 kernel panic with old mobo:

[161342.301305] BUG: stack guard page was hit at fc60f228 (stack is 
875efe77..3f38a379)
[161342.301306] kernel stack overflow (double-fault):  [#1] SMP NOPTI
[161342.301306] CPU: 10 PID: 465 Comm: md0_raid6 Tainted: P   OE 
5.8.0-33-generic #36-Ubuntu
[161342.301307] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./X570 Pro4, BIOS P3.60 12/01/2020
[161342.301307] RIP: 0010:slab_free_freelist_hook+0x35/0x120
[161342.301308] Code: 89 d5 41 54 49 89 f4 53 48 89 fb 48 83 ec 08 48 8b 02 4c 
8b 36 48 c7 06 00 00 00 00 48 c7 02 00 00 00 00 48 85 c0 49 0f 44 c6 <48> 89 45 
d0 eb 06 4c 3b 7d d0 74 5d 8b 53 20 4d 89 f7 49 8d 34 16
[161342.301308] RSP: 0018:a86b00c6fff8 EFLAGS: 00010246
[161342.301309] RAX: 98edc21cac40 RBX: 98ef0b407800 RCX: 
0001
[161342.301310] RDX: a86b00c70040 RSI: a86b00c70038 RDI: 
98ef0b407800
[161342.301310] RBP: a86b00c70028 R08: 0001 R09: 
85854500
[161342.301311] R10: 98edc21ca100 R11: 0001 R12: 
a86b00c70038
[161342.301311] R13: a86b00c70040 R14: 98edc21cac40 R15: 
98e9b53d74d8
[161342.301311] FS:  () GS:98ef0ec8() 
knlGS:
[161342.301312] CS:  0010 DS:  ES:  CR0: 80050033
[161342.301312] CR2: a86b00c6ffe8 CR3: 0007fa766000 CR4: 
00340ee0
[161342.301312] Call Trace:
[161342.301313]  ? mempool_kfree+0xe/0x10
[161342.301313]  ? kfree+0xb8/0x220
[161342.301313]  ? mempool_kfree+0xe/0x10
[161342.301313]  ? mempool_free+0x2f/0x80
[161342.301314]  ? md_end_io+0x4b/0x70
[161342.301314]  ? bio_endio+0xe6/0x150
[161342.301314]  ? bio_chain_endio+0x2d/0x40
[161342.301315]  ? md_end_io+0x5d/0x70
[161342.301315]  ? bio_endio+0xe6/0x150
[161342.301315]  ? bio_chain_endio+0x2d/0x40
[161342.301315]  ? md_end_io+0x5d/0x70
[161342.301316]  ? bio_endio+0xe6/0x150
[161342.301316]  ? bio_chain_endio+0x2d/0x40
[161342.301316]  ? md_end_io+0x5d/0x70
[161342.301316]  ? bio_endio+0xe6/0x150
[161342.301317]  ? bio_chain_endio+0x2d/0x40
[161342.301317]  ? md_end_io+0x5d/0x70
[161342.301317]  ? bio_endio+0xe6/0x150
[161342.301317]  ? bio_chain_endio+0x2d/0x40
...
[161342.301379]  ? md_end_io+0x5d/0x70
[161342.301379]  ? 

[Bug 1906995] [NEW] Gnome suddently crahses after update

[jake]

Public bug reported:

After Ubuntu enter sleep mode, Gnome crashes

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  6 16:25:49 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-11-21 (15 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-11-30 (6 days ago)

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


** Tags: amd64 apport-bug groovy 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/1906995

Title:
  Gnome suddently crahses after update

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

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

[Bug 1904745] Re: File permissions in /var/lib/nova/.ssh broken in upgrade

[Jake Hill]

FWIW and perhaps expectedly, the subsequent do-release-upgrade step also
mangles the permissions.

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

Title:
  File permissions in /var/lib/nova/.ssh broken in upgrade

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

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

[Bug 1904745] [NEW] File permissions in /var/lib/nova/.ssh broken in upgrade

[Jake Hill]

Public bug reported:

I am doing series upgrade on charmed openstack following the normal
procedure. The upgrade is cloud:bionic-ussuri to focal distro.

On compute units I notice that running apt full-upgrade prior to doing
do-release-upgrade results in incorrect file permissions on
/var/lib/nova/.ssh/. This in turn breaks migrations at least.

I did not catch if it was nova-common or nova-compute that did this
during the upgrade, but something wrote 644 on everything.

(osc) routergod@juju:~$ juju ssh 40 -- sudo ls -l /var/lib/nova/.ssh
total 44
-rw-r- 1 nova nova 10615 Nov 10 17:34 authorized_keys
-rw--- 1 nova nova  1675 Apr  9  2020 id_rsa
-rw-r- 1 nova nova   393 Apr  9  2020 id_rsa.pub
-rw-r- 1 nova nova 21216 Nov 10 17:34 known_hosts
(osc) routergod@juju:~$ juju upgrade-series 40 prepare focal
WARNING: This command will mark machine "40" as being upgraded to series 
"focal".
This operation cannot be reverted or canceled once started.
Units running on the machine will also be upgraded. These units include:
  nova-compute/11
  ntp/151
  neutron-openvswitch/67
  nova-compute-syslog/0
[...]
(osc) routergod@juju:~$ juju ssh 40 -- sudo apt update
[...]
(osc) routergod@juju:~$ juju ssh 40 -- sudo apt full-upgrade
[...]
(osc) routergod@juju:~$ juju ssh 40 -- sudo ls -l /var/lib/nova/.ssh
total 44
-rw-r--r-- 1 nova nova 10615 Nov 10 17:34 authorized_keys
-rw-r--r-- 1 nova nova  1675 Apr  9  2020 id_rsa
-rw-r--r-- 1 nova nova   393 Apr  9  2020 id_rsa.pub
-rw-r--r-- 1 nova nova 21216 Nov 10 17:34 known_hosts

** Affects: nova (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/1904745

Title:
  File permissions in /var/lib/nova/.ssh broken in upgrade

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

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

[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once

[Jake Cobb]

Confirmed, thanks for your work on this.

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

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1893584] Re: ayatana-indicator-datetime-service crashed with signal 5 in g_object_new_valist()

[Jake McGregor]

I'll also add this same thing happens on armhf on Raspberry Pi 4 4GB as
well. It doesn't seem to negatively affect the rest of the system, but
I'll note I've changed some of the indicators that appear on the top
bar, so I'm likely not using the one that's crashing.

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

Title:
  ayatana-indicator-datetime-service crashed with signal 5 in
  g_object_new_valist()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-datetime/+bug/1893584/+subscriptions

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

[Bug 137917] Re: vim c syntax does not support ansi anonymous array

[Jake Mercer]

Still seeing this issue in Ubuntu 20.

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

Title:
  vim c syntax does not support ansi anonymous array

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

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

[Bug 1889967] [NEW] virtualbox-dkms 6.1.12-dfsg-8: virtualbox kernel module failed to build

[Jake McGregor]

Public bug reported:

My system had recently rebooted after a kernel update when this
appeared. VirtualBox was not in use before or after the reboot. This bug
appears similar to #1081307, but given it was posted 6 years ago, I'm
reluctant to mark it as the same bug. The error message and the fact I'm
using Nvidia graphics seems interesting, so I have to wonder if it's the
same issue appearing again or somewhere else.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: virtualbox-dkms 6.1.12-dfsg-8
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu43
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.8.0-12-generic
Date: Sat Aug  1 03:08:06 2020
InstallationDate: Installed on 2020-03-30 (124 days ago)
InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageVersion: 6.1.12-dfsg-8
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.20.5ubuntu1
 apt  2.1.7
SourcePackage: virtualbox
Title: virtualbox-dkms 6.1.12-dfsg-8: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy

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

Title:
  virtualbox-dkms 6.1.12-dfsg-8: virtualbox kernel module failed to
  build

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

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

[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once

[Jake Cobb]

Both problems persist on 20200522.0.0, here is the kernel panic and
reboot:

[0.883971] VFS: Cannot open root device "PARTUUID=43931bda-01" or 
unknown-block(0,0): error -6
[0.885744] Please append a correct "root=" boot option; here are the 
available partitions:
[0.887371] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[0.888956] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-31-generic 
#35-Ubuntu
[0.890427] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
[0.891863] Call Trace:
[0.892322]  dump_stack+0x6d/0x9a
[0.892865]  panic+0x101/0x2e3
[0.893466]  mount_block_root+0x23f/0x2e8
[0.894322]  mount_root+0x38/0x3a
[0.894984]  prepare_namespace+0x13f/0x194
[0.895776]  kernel_init_freeable+0x231/0x255
[0.896743]  ? rest_init+0xb0/0xb0
[0.897499]  kernel_init+0xe/0x100
[0.898283]  ret_from_fork+0x35/0x40
[0.899058] Kernel Offset: 0x3240 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[0.900974] ACPI MEMORY or I/O RESET_REG.
[0.00] Linux version 5.4.0-31-generic (buildd@lgw01-amd64-059) (gcc 
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #35-Ubuntu SMP Thu May 7 20:20:34 UTC 
2020 (Ubuntu 5.4.0-31.35-generic 5.4.34)

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

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Yes, there is some lag.  Although the image is named 0522, it was not
available until the 25th of May, note the created message from your
link:

"v20200522.0.0 currently released version
This version was created about 24 hours ago."

I did test the 0518 focal image and it was not fixed, 0522 is the first
that works.

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Confirmed, it is available now and fixes the issue.

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

New images do not appear to be available quite yet, still getting the
May 18 image.

$ vagrant box update
==> default: Checking for updates to 'ubuntu/focal64'
default: Latest installed version: 20200518.0.0
default: Version constraints: 
default: Provider: virtualbox
==> default: Box 'ubuntu/focal64' (v20200518.0.0) is running the latest version.

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Bug 1874453] ProcCpuinfoMinimal.txt

[Jake Cobb]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367917/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] ProcCpuinfo.txt

[Jake Cobb]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367916/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] UdevDb.txt

[Jake Cobb]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1874453/+attachment/5367920/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] Lspci-vt.txt

[Jake Cobb]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367914/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] PciMultimedia.txt

[Jake Cobb]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367915/+files/PciMultimedia.txt

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

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] ProcModules.txt

[Jake Cobb]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367919/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] WifiSyslog.txt

[Jake Cobb]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367921/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] ProcInterrupts.txt

[Jake Cobb]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1874453/+attachment/5367918/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] Lspci.txt

[Jake Cobb]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1874453/+attachment/5367913/+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/1874453

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once

[Jake Cobb]

apport information

** Tags added: apport-collected uec-images

** Description changed:

  Using `ubuntu/focal64` version `20200423.0.0`, the boot process is
  extremely slow and the box always reboots once before completing a
  successful boot.  With default settings, this causes a timeout in
  Vagrant waiting for SSH to be available.  Setting a long enough timeout
  it does eventually boot successfully.  For comparison, `ubuntu/bionic64`
  boots successfully in roughly 10 seconds on my machine.
  
  This appears to be the big hang-up:
  
  Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] 
enabled
  Apr 23 14:00:12 ubuntu-focal kernel: [   76.448371] printk: console [ttyS0] 
enabled
  
  I have a hard time telling where exactly it reboots because my
  /var/log/syslog only ends up with the second boot.  I can watch it in
  Virtualbox though and it suddenly reboots, then the second boot process
  runs to completion.  The long delay shown above happens both times
  making the total time to a successful boot very long.  Here is the head
  of my /var/log/syslog:
  
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel 
File Systems.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File 
System...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild 
Hardware Database being skipped.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform 
Persistent Storage Archival being skipped.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users...
  Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting 
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
  Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting 
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File 
System.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent 
Storage.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables.
  Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group 
systemd-coredump with gid 999.
  Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete 
Device Initialization...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes 
in /dev...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes 
in /dev.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device 
Manager...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager.
  Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 
5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 
9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (
  Ubuntu 5.4.0-26.30-generic 5.4.30)
  Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro 
console=tty1 console=ttyS0
  
  
  Subsequent boots are also slow but don't seem to have the extra reboot.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 May  7 16:02 seq
+  crw-rw 1 root audio 116, 33 May  7 16:02 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 vboxvideodrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 

[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once

[Jake Cobb]

Same behavior on eoan, both the one-off kernel panic and slow boot
without overriding the console settings.

** Tags added: eoan

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

Title:
  ubuntu/focal64 very slow to boot and reboots once

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions

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

[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Ok, I tested 5.3.0-52-generic on eoan, the modules are present, the
system boots and runs normally.

vagrant@ubuntu-eoan:~$ ls -1 
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/*
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/vboxguest.ko
/lib/modules/5.3.0-52-generic/kernel/virtualbox-guest/vboxsf.ko

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Not sure how to test this as requested by the bot.  I don't think just
enabling proposed on an existing published image is sufficient.  Are
there proposed cloud image builds posted somewhere?

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Bug 1822467] Re: OpeonConnect fails with generic TLS Fatal Alert Error

[Jake Palmer]

Any solution to this that doesn't involve building from source?  I have
this problem in Ubuntu 19.10. Openconnect works fine in 18.04, but I get
a TLS error in anything newer.

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

Title:
  OpeonConnect fails with generic TLS Fatal Alert Error

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

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

[Bug 1229738] Re: grub doesn't boot with efi and md raid root

[Jake Hemmerle]

I am experiencing these same symptoms while trying to install Ubuntu
18.04 in UEFI mode with a 4-disk RAID10 as root on my R410. ESP gets
mounted at /boot/efi, kernel/ramdisk get installed to /boot, and the
ESP's grub.cfg points to another grub.cfg that is only accessable after
the array is assembled. The result on boot is Grub CLI that isn't able
to identify any partitions (ie 'ls (hd0)' results in an unknown
filesystem error). Will try above soon and report back.

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

Title:
  grub doesn't boot with efi and md raid root

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

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

[Bug 1860564] [NEW] 2 ports for 2 monitors, usb c port works, hdmi gives "NO SIGNAL" on monitor

[Jake Zegil]

Public bug reported:

>From what I have read, this appears to be a lightdm bug. It will
occasionally resolve when switching managers and rebooting, but it's
inconsistent.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 09:41:13 2020
InstallationDate: Installed on 2019-01-07 (379 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  2 ports for 2 monitors, usb c port works, hdmi gives "NO SIGNAL" on
  monitor

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

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

[Bug 1859276] Re: package samba-common-bin 2:4.11.1+dfsg-3ubuntu2 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1

[Jake McGregor]

Thanks for the input. I've been meaning to fix my Samba config, and this
only made it more obvious. For quite a while it's been 'If it ain't
broke, don't fix it.'. Well, obviously it was broken I just never
noticed. Even with the errors, my machines were still able to connect to
it fine, though I did notice version 1 support was dropped, which
affected a few old network printers. I've since fixed that issue. I have
updates installed via a Bash script on Pulseway, so I don't usually see
the output unless there's a problem with Apt that caused it to fail.

As for Webmin, I suspect it relies on Python 2, which I hear is steadily
being removed from Focal. Since it's still being maintained, this will
probably be fixed soon. While this has nothing to do with Samba, it was
the tool I was using to manage it. I saw it was removed a few days after
this was posted to fix a dependency issue.

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

Title:
  package samba-common-bin 2:4.11.1+dfsg-3ubuntu2 failed to
  install/upgrade: installed samba-common-bin package post-installation
  script subprocess returned error exit status 1

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

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

[Bug 1859276] [NEW] package samba-common-bin 2:4.11.1+dfsg-3ubuntu2 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1

[Jake McGregor]

Public bug reported:

I attempted to upgrade a system to focal for beta testing. Everything
except Samba upgraded fine and the system rebooted without issue. I
think this error was caused by my aging Samba config, which is probably
pushing 10 years old now and likely has parameters no longer supported
and was designed in my early high school days. Up until this upgrade, it
worked fine without issue.

What I found a little strange is how my outdated config was preventing
it from being properly installed. I was able to get the upgrade
completed by removing Samba, deleting my config file and replacing it
with a blank one, and applying the remaining upgrades. Once that was
done, Samba was installed again. I was able to generate a new Samba
config with Webmin and my systems can access the share just fine.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: samba-common-bin 2:4.11.1+dfsg-3ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Sat Jan 11 02:07:53 2020
ErrorMessage: installed samba-common-bin package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2019-01-10 (366 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
NmbdLog:
 
OtherFailedConnect: Yes
Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.5
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: samba
TestparmExitCode: 1
Title: package samba-common-bin 2:4.11.1+dfsg-3ubuntu2 failed to 
install/upgrade: installed samba-common-bin package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package samba-common-bin 2:4.11.1+dfsg-3ubuntu2 failed to
  install/upgrade: installed samba-common-bin package post-installation
  script subprocess returned error exit status 1

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

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

[Bug 1854205] [NEW] nameservers update differently with openconnect and openconnect-gnome in ubuntu 18.04

[Jake Cross]

Public bug reported:

[What I expected to happen]
openconnect (command line) and network-manager-openconnect-gnome behave in the 
same way when it comes to resolving hosts through the vpn

[What happened]
openconnect from the command line sets up the system in a way that can resolve 
hosts through the vpn. network-manager-openconnect-gnome does not set up the 
system in a way that can resolve hosts through the vpn. 

[Steps to reproduce]

This seems to be a new issue with network-manager-openconect-gnome in
Ubuntu 18.04+

I install sudo apt install network-manager-openconnect-gnome to get
gnome integration with opeconnect and Cisco AnyConnect Compatible VPN
(openconnect)

As an aside (which may actually be relevant) I do this to get *.local
addresses to resolve:

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf as per 
systemd docs
Move dns before mdns4_minimal in /etc/nsswitch.conf

If I connect to the VPN with openconnect through the gnome network
manager, VPN addresses (sites for work) do not resolve. Regular sites
continue to work as expected.

If I connect to the VPN with openconnect on the command line with sudo
openconnect vpn.mycompany.com, VPN addresses (sites for work) do
resolve. Regular sites continue to work as expected.

I thought I would check to see if there were any differences between
/etc/resolv.conf with each of these VPN connection methods and sure
enough, there is one:

openconnect on the command line (working):

#@VPNC_GENERATED@ -- this file is generated by vpnc
# and will be overwritten by vpnc
# as long as the above mark is intact
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 10.10.10.10
nameserver 10.10.10.11
search broadband mycompany.com

openconnect gnome integration (not working):

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 192.168.1.1
nameserver 10.10.10.10
nameserver 10.10.10.11
search broadband mycompany.com

If I remove (or comment out) the nameserver 192.168.1.1, which is the
difference in content between the working and not working files...
everything works as expected. I can resolve addresses within the company
and regular sites work as expected.

This does not happen with Fedora. Everything works out of the box. I'm
not sure why the network-manager-openconnect-gnome package works
differently or if there's a way I can make it work without either

Editing the file by hand.
Using the openconnect tool from the command line and keeping a terminal 
open running that command.


[System details]

lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

apt-cache policy network-manager-openconnect-gnome
network-manager-openconnect-gnome:
  Installed: 1.2.4-1ubuntu1
  Candidate: 1.2.4-1ubuntu1
  Version table:
 *** 1.2.4-1ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 1.2.4-1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

** Affects: network-manager-openconnect (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/1854205

Title:
  nameservers update differently with openconnect and openconnect-gnome
  in ubuntu 18.04

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

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

[Bug 1840909] Re: ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 instances from stopping normally

[Jake Withecombe]

Can confirm this issue & that commenting out the line fixes it on AWS at
least.

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

Title:
  ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 instances from
  stopping normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1840909/+subscriptions

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

[Bug 1304067] Re: Mouse cursor changes size in some GTK2 applications

[Jake Vincent]

Also experiencing this odd bug on a Dell XPS 13 9350 with an external
monitor. My built-in display is 1920x1080, but my external monitor is a
4K 27" display (3840x2160). When I am experiencing the issue, the mouse
pointer is just abnormally huge on both screens, *unless* the pointer is
in a particular app, like Firefox.

The solution for me is not to power on the computer with the external
display connected. If I power on the computer, get to the log in screen,
and attach the external display at this point, then when I log in,
everything is normal--I have a pointer that is an acceptable size, and
it stays the same size no matter which monitor it's on or which app it's
in. I haven't figured out what happens yet if I attach the external
display after logging in.

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

Title:
  Mouse cursor changes size in some GTK2 applications

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

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

[Bug 1820604] Re: curtin fails to find itself in subiquity snap, when running on serial-subiquity@.service

[Jake Billo]

I also receive the same "Unable to find helpers or 'curtin' exe to add
to path" error as Jim K reported in
https://bugs.launchpad.net/curtin/+bug/1820604/comments/18, after
defining a partition layout in the installer. I am installing on a
Lanner FW-8758 using a Rufus-generated USB stick and have tried both
"ubuntu-18.04.2-live-server-amd64.iso" and "ubuntu-18.04.2-server-
amd64.iso".

I activated the serial console output using similar instructions to
https://github.com/ynkjm/ubuntu-serial-install - mainly adding
"console=tty0 console=ttyS0,115200n8" where necessary.

Unfortunately dropping to shell after the failure occurs won't let me
log in to investigate further, or at least I don't know the appropriate
credentials (root and ubuntu users with a blank password, or the same
username/password result in an authentication failure.)

When installing using VGA mode and without the grub parameters, this
error didn't occur on the same hardware and without having adjusted the
partitions on the SSD.

It'd be great to get an updated install ISO, or at least a workaround
that I could use to pre-prepare a USB stick in case I have to drop back
to using the console port.

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

Title:
  curtin fails to find itself in subiquity snap, when running on serial-
  subiquity@.service

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

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

[Bug 1806543] Re: Plasma Desktop on multimonitor setup asks to reconfigure desktop layout on every login

[Jake Magee]

Same issue here... I have the layout pop-up on every login and it never
remembers my multi-monitor arrangement.

My hardware: Intel Core i5-3570K, Nvidia GeForce GTX 670 (with nouveau
driver)

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

Title:
  Plasma Desktop on multimonitor setup asks to reconfigure desktop
  layout on every login

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

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

[Bug 1795292] Re: ELAN469D touch pad not working

[Jake Jensen]

Does anyone have the technical sheet on this touchpad? 
I've seen reference to it's clock being 133mhz, but can't confirm it as I don't 
own an oscilloscope. 

If it's a different clock, it should be a simple patch to get it
functioning normally again.

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

Title:
  ELAN469D touch pad not working

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

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

[Bug 1795292] Re: ELAN469D touch pad not working

[Jake Jensen]

Someone's probably working on it. I personally am. But have nothing to
show yet. Most likely the same with whoever else is working on it
currently

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

Title:
  ELAN469D touch pad not working

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

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

[Bug 1795292] Re: ELAN469D touch pad not working

[Jake Jensen]

That's pretty much all you can do unless you're capable of writing
drivers or reading ACPI tables yourself.

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

Title:
  ELAN469D touch pad not working

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

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

[Bug 1795292] Re: ELAN469D touch pad not working

[Jake Jensen]

acpidump:
5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4  9_HIDTCPD...
5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50  .SYNA3255TCP
5B30: 44 0A 03 A4 0D 41 4C 50 53 31 32 31 45 00 A4 0D  DALPS121E...
5B40: 45 4C 41 4E 34 36 39 44 00 08 45 49 43 30 11 21  ELAN469D..EIC0.!
5B50: 0A 1E 8E 19 00 01 00 01 02 00 00 01 06 00 80 1A  
5B60: 06 00 15 00 5C 5F 53 42 2E 49 32 43 44 00 79 00  \_SB.I2CD.y.
5B70: 08 53 49 43 30 11 21 0A 1E 8E 19 00 01 00 01 02  .SIC0.!.

Upon installing libinput, and uninstalling synaptics, all mention of
ELAN has disappeared from dmesg, and /dev/input shows nothing related to
mouse/ touchpad.

Hardware debugging told me nothing useful, other than the device is
physically there and receiving power.

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

Title:
  ELAN469D touch pad not working

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

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

[Bug 1795292] Re: ELAN469D touch pad not working

[Jake Jensen]

Kernel 4.19.0-rc7
Laptop is a Lenovo IdeaPad 330S-15ARR. Same issue as everyone else. 

Attempting to install various ALPS drivers doesn't work, nor does the
i8042.reset workaround.

Patching elan_i2c_core to add the 469D entry also failed.

Notes: noapic is required for the laptop to load into Ubuntu.

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

Title:
  ELAN469D touch pad not working

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

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

[Bug 1717807] Re: When the menu contains too elements, the bottom ones does not appear

[Jake Douglas]

We also experience this in our application.

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

Title:
  When the menu contains too elements, the bottom ones does not appear

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

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

[Bug 1745496] [NEW] lubuntu install crashes after erase everything install type selected

[Jake]

Public bug reported:

lubuntu install crashes after erase everything install type selected
tried to install with full disk encryption, failed due to swap
ran swapoff --all
tried to install with full disk encryption, failed due to lvm problems
erased all partitions, made new partition table, rebooted
tried to install with full disk encryption, failed due to swap
ran swapoff --all
tried to install normally, failed due to installer crash

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.387
Date: Thu Jan 25 22:23:39 2018
LiveMediaBuild: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
ProcEnviron:
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  lubuntu install crashes after erase everything install type selected

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

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

[Bug 1744834] [NEW] cant upgrade

[jake]

Public bug reported:

upgrade

** Affects: update-manager (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/1744834

Title:
  cant upgrade

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

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

[Bug 1744831] [NEW] unable to prerequisities

[jake]

Public bug reported:

cant update

** Affects: update-manager (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/1744831

Title:
  unable to prerequisities

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

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

[Bug 1736696] Re: "openstack image list" fails when any images lack names

[Jake Yip]

** Package changed: python-openstackclient (Ubuntu) => python-
openstackclient

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

Title:
  "openstack image list" fails when any images lack names

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-openstackclient/+bug/1736696/+subscriptions

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

[Bug 1511557] Re: Notes with lots of text grow too big, they don't have a scrollbar

[Jake]

I would also like to see this feature very much, currently xpad has this
feature however they also have a fatal bug for 16.04, please add!!

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

** No longer affects: ubuntu

** 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/1511557

Title:
  Notes with lots of text grow too big, they don't have a scrollbar

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-stickynotes/+bug/1511557/+subscriptions

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

[Bug 477] Re: Config of pure-ftpd need to be simplified.

[Jake Magee]

Obviously, this package has been updated since the original bug /
feature ticket was placed.  Is it possible that the ability to use a
single conf file (with options as documented in the upstream package)
was added and the ticket just hasn't been updated?

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

Title:
  Config of pure-ftpd need to be simplified.

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

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

[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Jake Billo]

With the sysctl settings provided by Pete (vm.min_free_kbytes = 100
and vm.zone_reclaim_mode = 1), we've been running the linux-aws
4.4.0-1028.37 kernel successfully without an OOM killer invocation for
about four days now. Previously we would have seen three or more
occurrences of this per day, so it's a positive indication.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

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

[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Jake Billo]

Apologies - the file was inadvertently split by logrotate. I have
concatenated the entire contents of kern.log and kern.log.1 into the
attached file; these are the only kern.log files in /var/log on the
system.

I do have to redact the hostname in question, but it is a simple
substitution of 'localhost' for the FQDN of the system.

** Attachment added: "full kern.log contents"
   
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1655842/+attachment/4933724/+files/full_kern_20170816.log

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

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

[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Jake Billo]

We are also experiencing this issue running linux-aws 4.4.0-1028.37,
which tracks Ubuntu kernel 4.4.0-89.112. Our use case is very similar to
comment #86
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/comments/86).
In our case ElasticSearch 2.4.5 is running under Java 1.8.0_131 with a
~29GB heap; we downsized from 31GB as a troubleshooting effort with no
change to the frequency of OOM. The issue also occurs regardless of
vm.overcommit_memory being set to 0, 1 or 2.

The relevant data from kern.log (with redacted hostname) is attached;
I'm happy to provide additional logs or test different kernels, but
since our use case is i3-class instances in AWS, we need the nvme
enhancements and enhanced network I/O provided by the linux-aws package.

** Attachment added: "kern.log from affected system"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4933628/+files/kern_20170816.log

** Also affects: linux-aws (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/1655842

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

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

[Bug 1676114] [NEW] kubuntu 16.10 installer crashed at "prepare"

[Jake]

Public bug reported:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 655, in 
main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 639, in main
install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 274, in install
ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 512, in run
if self.backup or self.dbfilter_handle_status():
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 857, in 
dbfilter_handle_status
QtWidgets.QMessageBox.Close)
TypeError: warning(QWidget, str, str, buttons: 
Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = 
QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = 
QMessageBox.NoButton): too many arguments

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.14
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CasperVersion: 1.379
CurrentDesktop: KDE
Date: Sun Mar 26 04:27:53 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed 
boot=casper maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-16.10.14 yakkety

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

Title:
  kubuntu 16.10 installer crashed at "prepare"

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

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

[Bug 1675269] [NEW] wont startup, grub wont load. cant install OS

[jake]

Public bug reported:

have had ubuntu installed before, i formatted the HD and tried
reinstalling the OS but it keeps crashing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
Date: Thu Mar 23 16:43:39 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcEnviron:
 LANGUAGE=en_AU.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63.3 ubuntu xenial

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

Title:
  wont startup, grub wont load. cant install OS

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

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

[Bug 1670037] [NEW] missing symlink breaks haskeline

[Jake Fennick]

Public bug reported:

See https://github.com/commercialhaskell/intero/issues/372
and https://bugs.archlinux.org/task/53157

There is a missing symlink which causes a compile error when trying to
install haskeline.  This affects both 16.04 and 16.10.

sudo ln -s /lib/x86_64-linux-gnu/libtinfo.so.5 /lib/x86_64-linux-
gnu/libtinfo.so

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libtinfo5 6.0+20160625-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar  4 08:49:49 2017
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu2
 libgcc1 1:6.2.0-5ubuntu12
InstallationDate: Installed on 2016-07-07 (240 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ncurses
UpgradeStatus: Upgraded to yakkety on 2017-02-25 (7 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  missing symlink breaks haskeline

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

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

[Bug 1617468] Re: Package contains files in /usr/@DATADIRNAME@/locale

[Jake Li]

When will this bug be fixed? Could I delete the directory?

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

Title:
  Package contains files in /usr/@DATADIRNAME@/locale

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

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

[Bug 1642356] Re: Ubuntu 16.10 no longer connects to Panasonic projector through vga

[Jake Li]

Today official kernel updated to 4.8.0.28.37, and it is able to connect
inFocus projector! Thanks!

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

Title:
  Ubuntu 16.10 no longer connects to Panasonic projector through vga

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

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

[Bug 1642356] Re: Ubuntu 16.10 no longer connects to Panasonic projector through vga

[Jake Li]

Any updates on this bug?

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

Title:
  Ubuntu 16.10 no longer connects to Panasonic projector through vga

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

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

[Bug 1642356] Re: Ubuntu 16.10 no longer connects to Panasonic projector through vga

[Jake Li]

I met the problem too, and finally back to kernel linux-
image-4.6.3-040603-generic, then it worked again and was able to connect
to office InFocus projector just like before.

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

Title:
  Ubuntu 16.10 no longer connects to Panasonic projector through vga

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

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

[Bug 1627612] [NEW] systemctl restart xxx* does not restart inactive services

[Jake Yip]

Public bug reported:

Man pages of systemctl indicates that the start, restart, status takes
in [PATTERN], which accepts wildcard.

However, for an inactive service, it does not work UNLESS --all is
provided, which does not make sense for a command like restart. If one
wants to restart only if service is active, there is the try-restart
command.

To replicate

1. Stop a service. `systemctl stop sysstat.service`
2. Restart with wildcard. `systemctl restart sysstat*`
3. Check service status. It should still be inactive.
4. Restart with --all wildcard. `systemctl restart --all sysstat*`
5. Check again, service should have been started.

More logs below

root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2016-09-26 16:22:02 AEST; 48min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 3607 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 3809 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)
Tasks: 0
   Memory: 0B
  CPU: 0

Sep 26 16:22:02 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 16:22:02 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.
root@notifications-m:~# systemctl stop sysstat.service 
root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-09-26 17:10:16 AEST; 1s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 8228 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 3809 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)

Sep 26 16:22:02 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 16:22:02 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.
Sep 26 17:10:16 notifications-m systemd[1]: Stopping LSB: Start/stop sysstat's 
sadc...
Sep 26 17:10:16 notifications-m systemd[1]: Stopped LSB: Start/stop sysstat's 
sadc.
(reverse-i-search)`restar': systemctl ^Cstart --all 
ceilometer-agent-notification*
root@notifications-m:~# systemctl restart sysstat*
root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-09-26 17:10:16 AEST; 16s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 8228 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 3809 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)

Sep 26 16:22:02 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 16:22:02 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.
Sep 26 17:10:16 notifications-m systemd[1]: Stopping LSB: Start/stop sysstat's 
sadc...
Sep 26 17:10:16 notifications-m systemd[1]: Stopped LSB: Start/stop sysstat's 
sadc.
root@notifications-m:~# systemctl restart --all sysstat*
root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2016-09-26 17:10:39 AEST; 1s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 8228 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 8250 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)

Sep 26 17:10:39 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 17:10:39 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.

** Affects: systemd (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/1627612

Title:
  systemctl restart xxx* does not restart inactive services

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

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

[Bug 1609061] [NEW] package ecryptfs-utils 108-0ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Jake]

Public bug reported:

software update keeps crashing

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: ecryptfs-utils 108-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Aug  2 08:38:25 2016
DpkgHistoryLog:
 
DpkgTerminalLog:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2016-04-12 (112 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu3
SourcePackage: ecryptfs-utils
Title: package ecryptfs-utils 108-0ubuntu1.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ecryptfs-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package ecryptfs-utils 108-0ubuntu1.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

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

[Bug 1598187] [NEW] mlsd/mlst fails on some clients

[Jake Hill]

Public bug reported:

Description:Ubuntu 16.04 LTS
Release:16.04

proftpd-basic:
  Installed: 1.3.5a-1build1
  Candidate: 1.3.5a-1build1
  Version table:
 *** 1.3.5a-1build1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

Bug reported: http://bugs.proftpd.org/show_bug.cgi?id=4202

Fixed in version 1.3.5b.

** Affects: proftpd-dfsg (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/1598187

Title:
  mlsd/mlst fails on some clients

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

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

[Bug 1558737] Re: fsmonitor missing

[Jake Teton-Landis]

This issue is forcing me to create my own package - the `-repeat watch`
functionality is essential! And unison-fsmonitor is already compiled
successfully by the package build script - we just don't package it.

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

Title:
  fsmonitor missing

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

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

[Bug 1559306] [NEW] package bind9 1:9.10.3.dfsg.P4-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/sbin/named-checkzone', que está también en el paquete bind9utils 1:9.10.3.dfsg.P4-

[Jake McGregor]

Public bug reported:

This was probably caused by updates being installed in the background
via Webmin. Nothing else seems wrong, and system appears to be running
fine.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bind9 1:9.10.3.dfsg.P4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Fri Mar 18 15:41:32 2016
ErrorMessage: intentando sobreescribir `/usr/sbin/named-checkzone', que está 
también en el paquete bind9utils 1:9.10.3.dfsg.P4-1ubuntu1
InstallationDate: Installed on 2016-02-02 (45 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_os_name=Linux acpi_osi= quiet splash
RelatedPackageVersions:
 bind9utils 1:9.10.3.dfsg.P4-1ubuntu2
 apparmor   2.10-3ubuntu2
SourcePackage: bind9
Title: package bind9 1:9.10.3.dfsg.P4-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir `/usr/sbin/named-checkzone', que está también en el 
paquete bind9utils 1:9.10.3.dfsg.P4-1ubuntu1
UpgradeStatus: Upgraded to xenial on 2016-02-02 (45 days ago)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1559306

Title:
  package bind9 1:9.10.3.dfsg.P4-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/sbin/named-checkzone', que está también
  en el paquete bind9utils 1:9.10.3.dfsg.P4-1ubuntu1

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1559306] [NEW] package bind9 1:9.10.3.dfsg.P4-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/sbin/named-checkzone', que está también en el paquete bind9utils 1:9.10.3.dfsg.P4-

[Jake McGregor]

Public bug reported:

This was probably caused by updates being installed in the background
via Webmin. Nothing else seems wrong, and system appears to be running
fine.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bind9 1:9.10.3.dfsg.P4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Fri Mar 18 15:41:32 2016
ErrorMessage: intentando sobreescribir `/usr/sbin/named-checkzone', que está 
también en el paquete bind9utils 1:9.10.3.dfsg.P4-1ubuntu1
InstallationDate: Installed on 2016-02-02 (45 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_os_name=Linux acpi_osi= quiet splash
RelatedPackageVersions:
 bind9utils 1:9.10.3.dfsg.P4-1ubuntu2
 apparmor   2.10-3ubuntu2
SourcePackage: bind9
Title: package bind9 1:9.10.3.dfsg.P4-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir `/usr/sbin/named-checkzone', que está también en el 
paquete bind9utils 1:9.10.3.dfsg.P4-1ubuntu1
UpgradeStatus: Upgraded to xenial on 2016-02-02 (45 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package bind9 1:9.10.3.dfsg.P4-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/sbin/named-checkzone', que está también
  en el paquete bind9utils 1:9.10.3.dfsg.P4-1ubuntu1

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

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

[Bug 1554003] Re: xenial kernel crash on HP BL460c G7 (qla24xx problem?)

[Jake Anderson]

Just confirming this on an IBM HS21 with the nightly from 14-Mar-2016 07:01 @ 
http://cdimage.ubuntu.com/ubuntu-server/daily/current/xenial-server-amd64.iso 
IBM Part Number   26R0892

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

Title:
  xenial kernel crash on HP BL460c G7 (qla24xx problem?)

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

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

[Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Jake McGregor]

The only thing I can add here (and hopefully I'm not repeating anyone
here) is /boot claims to be about 75% full, and I have also seen it 100%
on another system of mine. It appears the problem is during the
transition between kernel 4.3 and 4.4. I use an encrypted partition on
both systems, one of which is a Surface Pro 3 using secure boot (if that
matters to anyone). I have only had one case where the system was unable
to boot because of this. Lucky for me I have a cloud backup. The others
I caught it in time. I was able to keep the system stable by fixing what
appeared to be a dependency error. Then again not rebooting might have
also helped. My guess is the Ubuntu installer didn't leave much space on
/boot, though normally all that is stored there is a few kernels and
related files. Everything appears fine now.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

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

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

[Bug 1542765] Re: package icedtea-netx:amd64 1.6.2-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2

[Jake McGregor]

I haven't noticed anything out of the ordinary when this appeared. It
almost appears as if this affects fresh installs, which mine is. I had
to reinstall due to kernel 4.4 not installing correctly. It also seems
interesting that I too have Spanish set as the main language, if that
even matters...

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

Title:
  package icedtea-netx:amd64 1.6.2-1ubuntu1 failed to install/upgrade:
  el subproceso instalado el script post-installation devolvió el código
  de salida de error 2

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

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

[Bug 1536790] [NEW] package brltty 5.3.1-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Jake McGregor]

Public bug reported:

This bug might be similar to #1533040, but I should note that this is
Ubuntu Mate running on a Raspberry Pi 2 (Arm v7), so I don't know if the
other bug is on the same CPU architecture or not. Feel free to mark it
as a duplicate if true. I was attempting to upgrade to Ubuntu 16.04, and
it appears as if I ran into some dependency errors. I'll see if I can
get them sorted out with aptitude in the mean time. System is still
stable and boots up fine, but I would imagine this will affect new
installs until the dependency error is resolved.

Here is the error output;

sudo aptitude upgrade
The following partially installed packages will be configured:
  brltty brltty-x11 
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up brltty (5.3.1-1ubuntu3) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults

That is where it stops. So far not even aptitude can fix this...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: brltty 5.3.1-1ubuntu3
Uname: Linux 4.1.13-v7+ armv7l
ApportVersion: 2.19.3-0ubuntu3
Architecture: armhf
Date: Thu Jan 21 13:41:50 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.1.10
SourcePackage: brltty
Title: package brltty 5.3.1-1ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package armhf need-duplicate-check xenial

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

Title:
  package brltty 5.3.1-1ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

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

[Bug 1533453] Re: fonts-tlwg-*-ttf packages fail to upgrade from 1:0.6.2-1

[Jake McGregor]

I see this bug already has a released fix, but I wanted to make sure
this is the same error and not something different. This was an easy fix
by resolving dependancy errors. Everything appears find now.

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

Title:
  fonts-tlwg-*-ttf packages fail to upgrade from 1:0.6.2-1

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

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

[Bug 702452]

[Jake-phy]

Is there any news on this?  The missing StartupWMClass=program.exe in
the desktop files, is causing issues in my Mint Linux applet.
https://github.com/jake-phy/WindowIconList/issues/105

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

Title:
  [launcher] Wine applications are wrongly matched

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

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

[Bug 1103833]

[Jake-phy]

Is there any news on this?  The missing StartupWMClass=program.exe in
the desktop files, is causing issues in my Mint Linux applet.
https://github.com/jake-phy/WindowIconList/issues/105

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

Title:
  Wine's icon and description appears for all Windows applications

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

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

[Bug 1386005] Re: Password not accepted graphical boot for encrypted root system

[Jake Catayoc]

Before I forget, I'm also using Ubuntu 15.10

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

Title:
  Password not accepted graphical boot for encrypted root system

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

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

[Bug 1386005] Re: Password not accepted graphical boot for encrypted root system

[Jake Catayoc]

I also experienced the same problem, after installing the proprietary
Nvidia drivers and following the instructions at
http://www.webupd8.org/2010/03/how-to-get-plymouth-working-with-
nvidia.html to re-enable plymouth on my proprietary Nvidia driver.

Right now, I'm undoing the graphical plymouth fix so I can boot by
entering my encrypted password, but all I get is a text-mode plymouth.

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

Title:
  Password not accepted graphical boot for encrypted root system

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

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

[Bug 1503850] Re: I'm at a loss.

[Jake]

Okay, what do I do with all this?

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

Title:
  I'm at a loss.

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

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

[Bug 1503850] [NEW] I'm at a loss.

[Jake]

Public bug reported:

I don't know what the problem is, but at times I can't even bring up
shutdown menu. This thing keeps darkening and freezing, I know xfinity
sucks but part of it is this machine.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-66.107-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct  7 12:49:05 2015
DistUpgraded: 2015-05-07 09:04:05,014 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0520]
InstallationDate: Installed on 2015-05-07 (153 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Lsusb:
 Bus 002 Device 002: ID 04fc:2801 Sunplus Technology Co., Ltd 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer Aspire 5253
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=59ffd65c-0160-476d-8d4e-b170407d1056 ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2015-05-07 (153 days ago)
dmi.bios.date: 02/09/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.06
dmi.board.name: Aspire 5253
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAcer:bvrV1.06:bd02/09/2011:svnAcer:pnAspire5253:pvrV1.06:rvnAcer:rnAspire5253:rvrV1.06:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 5253
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Oct  7 11:10:17 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  I'm at a loss.

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

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

[Bug 1503812] [NEW] Issues with Intel Graphics

[Jake Wells]

Public bug reported:

Multiple intel graphics related errors on startup

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct  7 14:22:42 2015
InstallationDate: Installed on 2015-09-26 (11 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  Issues with Intel Graphics

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

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

[Bug 1486195] [NEW] login loop and can't load terminal

[Jake Waller]

Public bug reported:

Every time i would try to login, the screen went black for a second then
it went back to the login screen, i tried to open the terminal with ctrl
+ alt + f1-f6, byt the screen just went black, but ctrl + alt +f7 worked
fine.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 3.19.0-26-generic
Date: Tue Aug 18 16:53:47 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e283]
InstallationDate: Installed on 2015-05-30 (79 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 2:15.200-0ubuntu4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=fcd5406e-d3d6-4f2b-a369-8a0ac4fc72b5 ro quiet splash vt.handoff=7 
init=/sbin/upstart
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.asset.tag: D05099590F12
dmi.board.name: 980DE3/U3S3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd05/06/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Aug 18 19:51:01 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8
 inputLogitech USB Keyboard KEYBOARD, id 9
 inputLogitech USB Keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: fglrx

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 ubuntu vivid

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

Title:
  login loop and can't load terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1486195/+subscriptions

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