[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

I tested systemd 245.4-4ubuntu3.12 just now. It worked immediately on
three boots!

raek@mizar:~$ apt-cache policy systemd
systemd:
  Installed: 245.4-4ubuntu3.12
  Candidate: 245.4-4ubuntu3.12
  Version table:
 *** 245.4-4ubuntu3.12 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3.11 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
 245.4-4ubuntu3 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

Dan: I just added the PPA, upgraded the packages and did 3 reboots. In
all cases "systemctl" showed "starting" when I logged in and then
"started" some seconds later. So it seems like the problem is solved!

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

My problem looks similar to the on reported in the Home Assistant bug
tracker.


raek@mizar:~$ systemctl status systemd-time-wait-sync   

  
... *SNIP* ...
 └─508 /lib/systemd/systemd-time-wait-sync  

  


raek@mizar:~$ sudo lsof -nPp 508
COMMAND   PID USER   FD  TYPE DEVICE SIZE/OFFNODE NAME
... *SNIP* ...
systemd-t 508 root0r  CHR1,3  0t0   6 /dev/null
systemd-t 508 root1u unix 0x99d964ad0c00  0t0   16894 
type=STREAM
systemd-t 508 root2u unix 0x99d964ad0c00  0t0   16894 
type=STREAM
systemd-t 508 root3u  a_inode   0,140   11428 
[eventpoll]
systemd-t 508 root4u  a_inode   0,140   11428 [signalfd]
systemd-t 508 root5r  a_inode   0,140   11428 inotify
systemd-t 508 root6u  a_inode   0,140   11428 [timerfd]


raek@mizar:~$ sudo strace -ttTp 508
strace: Process 508 attached
22:59:52.923972 gettid()= 508 <0.23>
22:59:52.925523 epoll_wait(3, 


raek@mizar:~$ sudo cat /proc/508/fdinfo/5
pos:0
flags:  02004000
mnt_id: 15
inotify wd:1 ino:17b sdev:18 mask:100 ignored_mask:0 fhandle-bytes:8 
fhandle-type:1 f_handle:ac95aa8d7b01


raek@mizar:~$ sudo cat /proc/508/mountinfo  | grep :15
39 34 0:33 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:15 - 
cgroup cgroup rw,memory


The mountinfo lines look different for me than for tmm1 (see previously
linked home assistant ticket).

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

One more boot. This time I checked the timestamp of the
/run/systemd/timesync/synchronized file (and did not run any timedatectl
commands):

raek@mizar:~$ ls -la /run/systemd/timesync
total 0
drwxr-xr-x  2 systemd-timesync systemd-timesync  60 Jul 26 22:51 .
drwxr-xr-x 24 root root 540 Jul 26 22:52 ..
-rw-r--r--  1 systemd-timesync systemd-timesync   0 Jul 26 22:53 synchronized


** Attachment added: "redacted_journal2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+attachment/5513863/+files/redacted_journal2.txt

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

I found these two bug tickets that could be relevant:

https://github.com/home-assistant/operating-system/issues/896

https://github.com/systemd/systemd/issues/8683

I should also add that this seems to happen on the majority of boots for
me, but not every boot. So there is some amount of non-determinism
involved.

I'm not familiar with what service / tool / part of kernel does what in
the boot of an Ubuntu 20.04 system, but I might read up on what systemd-
time-wait-sync.service waits for to see if I can figure out why that
does not happen.

Anyway, thanks for helping me debug this issue!

** Bug watch added: github.com/home-assistant/operating-system/issues #896
   https://github.com/home-assistant/operating-system/issues/896

** Bug watch added: github.com/systemd/systemd/issues #8683
   https://github.com/systemd/systemd/issues/8683

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

Here is the output from the journal from a boot where time-wait-
sync.service "stuck". (I removed some line relating to syncthing and to
a private IRC bot I run.) After boot I logged in, checked "journalctl"
and saw that time-wait-sync.service was "activating" and then ran
"timedatectl status" and "timedatectl timesync-status". The outputs said
that time was synced. Now that I look in the journal, I see these
interesting lines:

Jul 26 22:19:41 mizar dbus-daemon[835]: [system] Activating via systemd: 
service name='org.freedesktop.timedate1' 
unit='dbus-org.freedesktop.timedate1.service' requested by ':1.29' (uid=1000 
pid=1406 comm="timedatectl status " label="unconfined")
Jul 26 22:19:41 mizar systemd[1]: Starting Time & Date Service...
Jul 26 22:19:41 mizar dbus-daemon[835]: [system] Successfully activated service 
'org.freedesktop.timedate1'
Jul 26 22:19:41 mizar systemd[1]: Started Time & Date Service.

Maybe that means that some service started because I tried to check the
status? Just a thought.

** Attachment added: "redacted_journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+attachment/5513859/+files/redacted_journal.txt

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

This is my contents of /etc/systemd/timesyncd.conf

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.

[Time]
NTP=ntp.se se.pool.ntp.org
FallbackNTP=ntp.ubuntu.com
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048


And this is the outputs of some timedatectl status commands:

raek@mizar:~$ timedatectl status
   Local time: Sun 2021-07-25 20:13:01 CEST  
   Universal time: Sun 2021-07-25 18:13:01 UTC   
 RTC time: Sun 2021-07-25 18:13:01   
Time zone: Europe/Stockholm (CEST, +0200)
System clock synchronized: yes   
  NTP service: active
  RTC in local TZ: no
raek@mizar:~$ timedatectl timesync-status 
   Server: 2a01:3f7::1 (ntp.se) 
Poll interval: 34min 8s (min: 32s; max 34min 8s)
 Leap: normal   
  Version: 4
  Stratum: 1
Reference: PPS  
Precision: 1us (-25)
Root distance: 30us (max: 5s)   
   Offset: -104us   
Delay: 11.063ms 
   Jitter: 5.968ms  
 Packet count: 147  
Frequency: +4.989ppm

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.

raek@mizar:~/code/raek-totp-token/firmware$ apt-cache policy systemd-timesyncd
systemd-timesyncd:
  Installed: 245.4-4ubuntu3.11
  Candidate: 245.4-4ubuntu3.11
  Version table:
 *** 245.4-4ubuntu3.11 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
raek@mizar:~/code/raek-totp-token/firmware$ systemctl status 
systemd-timesyncd.service 
● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Thu 2021-07-22 11:06:53 CEST; 3 days ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 792 (systemd-timesyn)
 Status: "Initial synchronization to time server [2a01:3f7::1]:123 
(ntp.se)."
  Tasks: 2 (limit: 9415)
 Memory: 3.2M
 CGroup: /system.slice/systemd-timesyncd.service
 └─792 /lib/systemd/systemd-timesyncd

Jul 22 11:06:53 mizar systemd[1]: Starting Network Time Synchronization...
Jul 22 11:06:53 mizar systemd[1]: Started Network Time Synchronization.
Jul 22 11:06:59 mizar systemd-timesyncd[792]: Network configuration changed, 
trying to establish connection.
Jul 22 11:07:01 mizar systemd-timesyncd[792]: Network configuration changed, 
trying to establish connection.
Jul 22 11:07:02 mizar systemd-timesyncd[792]: Network configuration changed, 
trying to establish connection.
Jul 22 11:07:02 mizar systemd-timesyncd[792]: Network configuration changed, 
trying to establish connection.
Jul 22 11:07:04 mizar systemd-timesyncd[792]: Network configuration changed, 
trying to establish connection.
Jul 22 11:07:04 mizar systemd-timesyncd[792]: Initial synchronization to time 
server [2a01:3f7::1]:123 (ntp.se).


I have done some NTP-related configuration (added an NTP server more close by(. 
I'll try to find all deviations from the default I have made and come back.

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

This started happen to me in January of February. This is easy for me to
reproduce since it happens at every boot. I would be happy to provide
more information or run more tests if needed.

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1937238] [NEW] systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Rasmus Bondesson]

Public bug reported:

When I start my server running Ubuntu 20.04 the systemd-time-wait-
sync.service is stuck in "activating" state. I noticed this because none
of the systemd timer units triggered, because all the timers depend on
systemd-time-wait-sync.service. Running "systemctl restart systemd-time-
wait-sync.service" manually works around the problem.

Some logs and command outputs:


raek@mizar:~$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04


raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service
  systemd-time-wait-sync.service
   loaded activating start start Wait Until Kernel Time 
Synchronized  


raek@mizar:~$ systemctl status systemd-time-wait-sync.service
● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
 Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; 
enabled; vendor preset: enabled)
 Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago
   Docs: man:systemd-time-wait-sync.service(8)
   Main PID: 514 (systemd-time-wa)
  Tasks: 1 (limit: 9415)
 Memory: 972.0K
 CGroup: /system.slice/systemd-time-wait-sync.service
 └─514 /lib/systemd/systemd-time-wait-sync

Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 
time Thu 2021-07-22 09:06:52.216338 UTC
Warning: journal has been rotated since unit was started, output may be 
incomplete.


raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service
-- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 
CEST. --
Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 
time Thu 2021-07-22 09:06:52.216338 UTC


raek@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service
systemd: /lib/systemd/system/systemd-time-wait-sync.service


raek@mizar:~$ apt-cache policy systemd
systemd:
  Installed: 245.4-4ubuntu3.11
  Candidate: 245.4-4ubuntu3.11
  Version table:
 *** 245.4-4ubuntu3.11 500
500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3.10 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 245.4-4ubuntu3.8 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
 245.4-4ubuntu3 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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


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

[Bug 1876570] Re: Could not resume from hibernation when swap is specified as device

[Rasmus Bonnedal]

I have now tested initramfs-tools 0.130ubuntu3.12 on bionic and it fixes
the issue for me.

Same test as above.

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

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

Title:
  Could not resume from hibernation when swap is specified as device

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

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

[Bug 1876570] Re: Could not resume from hibernation when swap is specified as device

[Rasmus Bonnedal]

I have now tested initramfs-tools 0.136ubuntu6.5 on focal and it fixes
the issue for me.

Same test as above.

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

Title:
  Could not resume from hibernation when swap is specified as device

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

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

[Bug 1876570] Re: Could not resume from hibernation when swap is specified as device

[Rasmus Bonnedal]

I have tested initramfs-tools 0.137ubuntu12.1 on groovy and it fixes the
issue for me.

I performed the following test:
1. Setup swap on /dev/sda3
2. Add resume=/dev/sda3 to GRUB_CMDLINE_LINUX_DEFAULT
3. Run update-grub
4. Run pm-hibernate

The system resumes from hibernation.

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

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

Title:
  Could not resume from hibernation when swap is specified as device

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

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

[Bug 1899224] Re: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?

[Rasmus Eneman]

>The crashes you mention are probably bug 1916716.

I tried your mentioned workaround and rebooted but Chrome still crashes.
ctrl+shift+alt+r work now tough.

When Chrome crashes I get this in the terminal:
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared 
object file: No such file or directory
zsh: segmentation fault  google-chrome

Current stable chrome is 88 and according to this post
https://jgrulich.cz/2020/12/18/webrtc-chromium-updates-in-2020/ 89 is
the version that will probably receive 0.3 support so 88 would
absolutely need libpipewire0.2 (and possible something else if it isn't
libpipewire0.2 that provides libspa-support.so).

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

Title:
  Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?

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

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

[Bug 1899224] Re: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?

[Rasmus Eneman]

Screensharing with Firefox and Chrome unstable works now in 21.04 but
Chrome stable crashes. While chrome stable will probably start working
before 21.04 is released (both 89 and 90 coming up), electron apps like
Slack and Teams are usually not as fast to update and libpipewire0.2
would be great to have for supporting them.

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

Title:
  Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?

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

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

[Bug 1802533] Re: [MIR] pipewire

[Rasmus Eneman]

As Ubuntu 21.04 won't have Gnome 40, can this be enabled for the current
version (in 21.04 ofc.)?

It's explicitly disabled for Ubuntu here https://salsa.debian.org/gnome-
team/mutter/-/blob/debian/master/debian/rules#L41-48

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

Title:
  [MIR] pipewire

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

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

[Bug 1802533] Re: [MIR] pipewire

[Rasmus Eneman]

Thank you Christian, that sounds great!

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

Title:
  [MIR] pipewire

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

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

[Bug 1802533] Re: [MIR] pipewire

[Rasmus Eneman]

Hello, what is the status of this MIR? Getting screen sharing to work in
Wayland would be a huge improvement in times like these and I'm weary of
the "Unassigned, importance low" status that this currently have.

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

Title:
  [MIR] pipewire

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

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

[Bug 1802533] Re: [MIR] pipewire

[Rasmus Eneman]

Thank you Liz! I'll see if I have the energy to do that, but with my
company pushing bad remote meeting solutions I might have to :/ Now I at
least know where things stand and what to do.

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

Title:
  [MIR] pipewire

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

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

[Bug 1802533] Re: [MIR] pipewire

[Rasmus Eneman]

@Liz Fong-Jones

What did you do to get xdg-desktop-portal working in Ubuntu?
I installed pipewire (0.3.10-4 avalible in groovy) and tried to pull 
xdg-desktop-portal, mutter and mutter-common form Debian but that causes mutter 
to immediately crash. After restoring mutter and mutter-common I have a usable 
system again but screen sharing still does not work.

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

Title:
  [MIR] pipewire

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

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

[Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Rasmus Underbjerg Pinnerup]

Yep, works like a charm with 3.38.0-1ubuntu1.1 from groovy-proposed here
as well.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

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

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

[Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

[Rasmus Underbjerg Pinnerup]

Thanks for the speedy work! I'm afraid I'm registering problems with the
update, however.

I just got gir1.2-gtk-3.0 through -proposed, and whereas it works as
intended in so far as I can now choose Ubuntu Mono in Gnome Terminal and
get the regular font face, it seemingly introduces a bug where gnome-
terminal crashes, when I try to select certain typefaces.

For instance, when I open up Preferences of go to the font selection
box, as soon as I click on e.g. "DejaVu Sans Mono", gnome-terminal just
closes. When I open it again, it's still using the previously set font.
The problem also occurs with "Inconsolata", but seemingly not with any
other fonts I have installed, whether fonts that ship with Ubuntu or
fonts I've installed on my own.

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions

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

[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

@Sebastien: No, I've not noticed the bug for a long while. It must have
been fixed in later Ubuntu versions somehow.

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

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

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

[Bug 1876570] [NEW] Could not resume from hibernation when swap is specified as device

[Rasmus Bonnedal]

Public bug reported:

I originally experienced this on Pop!_OS but I have reproduced it on a
freshly installed Ubuntu.

1. Ubuntu 20.04 LTS
2. initramfs-tools-core 0.136ubuntu6
3. I expect the system to resume from hibernation when running pm_hibernate
4. The system starts up anew when I try to resume

I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable
hibernate I added the kernel parameter "resume=/dev/vda2" to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub.

>From debugging initramfs it tries to follow a symbolic link

DEV=$(readlink "$resume")
(see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35)

which works well when swap is specified with uuid. When swap is
specified as a device directly the readlink returns an empty string and
the system does not resume from hibernation.

To verify this I added the parameter -f to readlink and run "update-
initramfs -u". The system now hibernates successfully.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May  3 13:26:02 2020
InstallationDate: Installed on 2020-05-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Patch added: "resume.patch"
   
https://bugs.launchpad.net/bugs/1876570/+attachment/5365684/+files/resume.patch

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

Title:
  Could not resume from hibernation when swap is specified as device

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

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

[Bug 1813266] Re: udhcpd: not dying on SIGTERM

[Rasmus Villemoes]

This has been open for over a year, with a fix indicated from the very
beginning. Is there any chance that patch can be applied?

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

Title:
  udhcpd: not dying on SIGTERM

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

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

[Bug 1859483] Re: busybox udhcpd does not honour SIGTERM

[Rasmus Villemoes]

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

** This bug has been marked a duplicate of bug 1813266
   udhcpd: not dying on SIGTERM

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

Title:
  busybox udhcpd does not honour SIGTERM

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

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

[Bug 1859483] [NEW] busybox udhcpd does not honour SIGTERM

[Rasmus Villemoes]

Public bug reported:

busybox 1.27.2, shipped with at least Ubuntu 18.04, has a bug where the
udhcpd daemon does not react properly to SIGTERM.

That bug if fixed in upstream busybox as of 1.29.0, commit
3293bc146985c56790033409facc0ad64a471084 . That patch should be back-
ported to the busybox 1.27.2 - I believe it applies cleanly (it did when
we hit this on our Yocto-based embedded systems).

** Affects: busybox (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/1859483

Title:
  busybox udhcpd does not honour SIGTERM

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

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

Re: [Bug 1737187] Re: Unable to launch AWS M5 instance with newest Ubuntu AMI

[Rasmus Larsen]

No, I believe it's resolved.

On Tue, Jul 30, 2019, 10:31 Po-Hsu Lin  wrote:

> Do you still experiencing this issue?
>
> ** Changed in: linux-aws (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737187
>
> Title:
>   Unable to launch AWS M5 instance with newest Ubuntu AMI
>
> Status in linux-aws package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When booting Ubuntu Linux 16.04 on an M5.large instance, the instance
>   fails to startup and dies, seemingly during initialization of the NVMe
>   interface, here's the most relevant lines (full kernel log attached):
>
>   [8.840439] Btrfs loaded
>   [   61.888098] clocksource: tsc: mask: 0x max_cycles:
> 0x240939f1bb2, max_idle_ns: 440795263295 ns
>   [   64.807909] nvme :00:04.0: I/O 0 QID 0 timeout, disable controller
>   [   64.916220] nvme :00:04.0: Cancelling I/O 0 QID 0
>   [   64.920779] nvme :00:04.0: Identify Controller failed (-4)
>   [   64.925737] nvme :00:04.0: Removing after probe failure
>   [   64.930506] iounmap: bad address c9e5
>   [   64.934951] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted
> 4.4.0-1041-aws #50-Ubuntu
>   [   64.942528] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
>   [   64.947684] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
>   [   64.952688]  0286 fd001be315a343d4 8800bbb4bcd8
> 813f7743
>   [   64.960923]  880036c6d4f0 c9e5 8800bbb4bcf8
> 8106ae7f
>   [   64.969368]  880036c6d4f0 880036c6d658 8800bbb4bd08
> 8106aebc
>   [   64.977878] Call Trace:
>   [   64.981322]  [] dump_stack+0x63/0x90
>   [   64.985878]  [] iounmap.part.1+0x7f/0x90
>   [   64.990583]  [] iounmap+0x2c/0x30
>   [   64.994873]  [] nvme_dev_unmap.isra.35+0x1a/0x30
> [nvme]
>   [   65.71]  [] nvme_remove+0xce/0xe0 [nvme]
>   [   65.005125]  [] pci_device_remove+0x39/0xc0
>   [   65.009912]  [] __device_release_driver+0xa1/0x150
>   [   65.015009]  [] device_release_driver+0x23/0x30
>   [   65.020019]  [] pci_stop_bus_device+0x8a/0xa0
>   [   65.024806]  []
> pci_stop_and_remove_bus_device_locked+0x1a/0x30
>   [   65.032326]  []
> nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme]
>   [   65.037731]  [] process_one_work+0x165/0x480
>   [   65.042482]  [] worker_thread+0x4b/0x4c0
>   [   65.046978]  [] ? process_one_work+0x480/0x480
>   [   65.051905]  [] kthread+0xe5/0x100
>   [   65.056224]  [] ? kthread_create_on_node+0x1e0/0x1e0
>   [   65.061380]  [] ret_from_fork+0x3f/0x70
>   [   65.066103]  [] ? kthread_create_on_node+0x1e0/0x1e0
>   [   65.071235] Trying to free nonexistent resource
> 
>   [  125.080477] random: nonblocking pool is initialized
>   (...End of output...)
>
>   Relevant data:
>   AMI id: ami-8fd760f6 (Should be the latest official release)
>   Instance type: m5.large
>   Region: eu-west-1
>
>   Issue seems completely repeatable.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1737187/+subscriptions
>

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

Title:
  Unable to launch AWS M5 instance with newest Ubuntu AMI

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

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

[Bug 1833680] [NEW] package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned

[Rasmus Eneman]

Public bug reported:

The upgrade manager told me to report this.
I don't really have much extra information so if this isn't helpful, just close 
the issue.

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: libvlc-bin:amd64 3.0.6-1
ProcVersionSignature: Ubuntu 4.18.0-22.23-generic 4.18.20
Uname: Linux 4.18.0-22-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Fri Jun 21 10:33:53 2019
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-01-24 (877 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
SourcePackage: vlc
Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to disco on 2019-06-21 (0 days ago)

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


** Tags: amd64 apport-package disco

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

Title:
  package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

[Rasmus Malver]

I tried installing 4.18, but it persisted. I tried an older kernel, and
then the networking stopped working. I tried re-installing Bionic
Beaver, and when booting from USB everything works. But after install
and update, it's broken again.

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

Title:
  [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer
  freezes after login

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

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

[Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

[Rasmus Malver]

@vanvugt, I installed nvidia-driver-390, and now the second display
doesn't work (again). I have removed it, but the damage persists. I'll
see what I can do re disabling in BIOS.

@kaihengfeng, I'd like to test the mainline kernel, but could you give
me a couple of lines on how? I'm guessing I have to curl some of the
files from here https://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.18-rc6/ and dpkg them.

I have attached a new crash file from a crash when I tried to boot into
an earlier kernel.

** Attachment added: "linux-image-4.15.0-45-generic.259785.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1818899/+attachment/5244339/+files/linux-image-4.15.0-45-generic.259785.crash

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

Title:
  [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer
  freezes after login

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

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

[Bug 1818899] Re: After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

[Rasmus Malver]

I installed an older kernel, and was able to boot and log in. But the
external display (HDMI) still didn't work. In desperation I went to
Settings -> Users -> Automatic Login.

And now everything works. Apart from the fact that my computer can be
used by anyone. So it was a mistake on my part to tag this as a xorg
problem. It's clearly to do with the login of the window manager.

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] Xrandr.txt

[Rasmus Malver]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1818899/+attachment/5244164/+files/Xrandr.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] ProcModules.txt

[Rasmus Malver]

apport information

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] Dependencies.txt

[Rasmus Malver]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244151/+files/Dependencies.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] MonitorsUser.xml.txt

[Rasmus Malver]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244154/+files/MonitorsUser.xml.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] ProcEnviron.txt

[Rasmus Malver]

apport information

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

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] DpkgLog.txt

[Rasmus Malver]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244152/+files/DpkgLog.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] xserver.devices.txt

[Rasmus Malver]

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244166/+files/xserver.devices.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] CurrentDmesg.txt

[Rasmus Malver]

apport information

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

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] ProcCpuinfo.txt

[Rasmus Malver]

apport information

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] ProcInterrupts.txt

[Rasmus Malver]

apport information

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] xdpyinfo.txt

[Rasmus Malver]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244165/+files/xdpyinfo.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] UdevDb.txt

[Rasmus Malver]

apport information

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] XorgLogOld.txt

[Rasmus Malver]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244163/+files/XorgLogOld.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] XorgLog.txt

[Rasmus Malver]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244162/+files/XorgLog.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] UnitySupportTest.txt

[Rasmus Malver]

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244161/+files/UnitySupportTest.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] Lspci.txt

[Rasmus Malver]

apport information

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] ProcCpuinfoMinimal.txt

[Rasmus Malver]

apport information

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] BootLog.txt

[Rasmus Malver]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1818899/+attachment/5244149/+files/BootLog.txt

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

Title:
  After Ubuntu Base update tp 4.15.0-46-generic computer freezes after
  login

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

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

[Bug 1818899] [NEW] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

[Rasmus Malver]

Public bug reported:

I can boot to login, but if I input correct information it freezes. If I
boot in recovery mode and choose to resume boot, I can login. But my
external display doesn't register. If I choose the failsafeX version
there is an error text related to xorg.

I have not had any problems before on this terminal. It came when I let
the system update and reboot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  6 20:26:56 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:119b]
 NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1197]
InstallationDate: Installed on 2018-11-26 (100 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
 Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire A715-71G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charmeleon_KLS
dmi.board.vendor: KBL
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.family: Aspire 7
dmi.product.name: Aspire A715-71G
dmi.product.version: V1.10
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Mar  6 20:16:01 2019
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2
--- 
ProblemType: Bug
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:119b]
 NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1197]
InstallationDate: Installed on 2018-11-26 (100 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
 Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire A715-71G
Package: xorg 1:7.7+19ubuntu7.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset
ProcVersionSignature: Ubuntu 

[Bug 1785600] Re: Natural scrolling is only applied in one direction (vertical)

[Rasmus Malver]

It can be fixed following the instructions in this answer:
https://askubuntu.com/questions/1029128/inverted-horizontal-scrolling-ubuntu-18-04#answer-1031657

I've had the problem before. It seems like a weird why-bother-choice by
the community / Canonical.

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

Title:
  Natural scrolling is only applied in one direction (vertical)

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

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

[Bug 1800750] Re: Error message during upgrade: "Error writing key update: Permission denied"

[Rasmus Wriedt Larsen]

This also happened to me.

> Did the upgrade process fail?

no

> If you run 'sudo apt -f install' is any change suggested there?

no

> Did you modify the allowed Secure Boot certificates in your machine's
firmware?

$ mokutil --sb-state
This system does't support Secure Boot

I could have disabled secure boot altogether to get my dual boot setup
to work, I honestly can't remember all the details. But given that I
haven't even enabled secure boot, this error seems all the more strange
to me.

> What hardware did this error show up on?

MacBookPro 12,1 [Intel Core i7-5557U] (early 2015)

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

Title:
  Error message during upgrade: "Error writing key update: Permission
  denied"

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

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

[Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Rasmus Pedersen]

Installing resolveconf fixed it for me, now DNS resolv works after PPTP
disconnects.

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

Title:
  No dns resolution after closing a vpn/pptp connection

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

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

[Bug 1759960] [NEW] Installation program started in the moment I should type the computers password.

[Rasmus Arild Djuve]

Public bug reported:

The installation program crashed as I should install Ubuntu 16.04.4 x86
on an HP Compaq dx6100 MT desktop. I do not have any idea why.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.6 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CasperVersion: 1.376.2
Date: Thu Mar 29 23:12:43 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 ubiquity-2.21.63.6 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/1759960

Title:
  Installation program started in the moment I should type the computers
  password.

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

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

[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

I filed it here: https://bugzilla.gnome.org/show_bug.cgi?id=793914

** Bug watch added: GNOME Bug Tracker #793914
   https://bugzilla.gnome.org/show_bug.cgi?id=793914

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

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

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

[Bug 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)

[Rasmus Eneman]

The above bug seems to be solved or at least mitigated a bit. With just
having firefox up the CPU usage of gnome-shell is between 2-5%.

Gnome shell is still much less performant than Unity though, by moving
windows, open Activities or dragging the mouse over the dock its CPU
usage quickly jumps to 20%. But that is probably things that should have
their own bugs.

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

Title:
  High CPU usage in gnome-shell just redrawing the screen (Firefox is
  running)

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

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

[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

** Description changed:

  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.
  
  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops working
  for some files.
  
  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for some
  files. Some files I can click and they open in Evince each time, whereas
  other files will never open in Evince. They open fine in other
  applications and under X.
  
  When I try to open the file from the command line, I get the following
  error message:
  
  pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.
  
  If I rename the file (e.g. by adding the number "2" to the file name),
  make a copy or move it to another directory, it opens without problems.
- However, after some uptime the renamed or new file will often fail to
- open with the same error.
+ However, after some time the renamed or new file will fail to open with
+ the same error.

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

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

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

[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

** Description changed:

  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.
  
  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops working
  for some files.
  
  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for some
  files. Some files I can click and they open in Evince each time, whereas
  other files will never open in Evince. They open fine in other
  applications and under X.
  
  When I try to open the file from the command line, I get the following
  error message:
  
  pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.
  
- If I rename the file (e.g. by adding the number "2" to the file name) or
- move it to another directory, it opens without problems.
+ If I rename the file (e.g. by adding the number "2" to the file name),
+ make a copy or move it to another directory, it opens without problems.
+ However, after some uptime the renamed or new file will often fail to
+ open with the same error.

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

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

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

[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

** Description changed:

  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.
  
  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops working
  for some files.
  
  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for some
  files. Some files I can click and they open in Evince each time, whereas
  other files will never open in Evince. They open fine in other
  applications and under X.
  
  When I try to open the file from the command line, I get the following
  error message:
  
- pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf 
+ pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.
  
  If I rename the file (e.g. by adding the number "2" to the file name) or
- move it to another dictionary, it opens without problems.
+ move it to another directory, it opens without problems.

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

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

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

[Bug 1743043] [NEW] Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

Public bug reported:

Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
when I'm logged on using Wayland. There's no problem using X.

The error is very simple. I double click a PDF file in my file manager
and expect it to open in Evince (Document Viewer). And mostly that's
what happens, but after having opened a few files, it just stops working
for some files.

The error seldom occurs with the first PDF file I open after a reboot,
but after I've opened a few files, the error pops up, but only for some
files. Some files I can click and they open in Evince each time, whereas
other files will never open in Evince. They open fine in other
applications and under X.

When I try to open the file from the command line, I get the following
error message:

pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf 
Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

If I rename the file (e.g. by adding the number "2" to the file name) or
move it to another dictionary, it opens without problems.

** Affects: evince (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/1743043

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

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

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

[Bug 1737187] [NEW] Unable to launch AWS M5 instance with newest Ubuntu AMI

[Rasmus Larsen]

Public bug reported:

When booting Ubuntu Linux 16.04 on an M5.large instance, the instance
fails to startup and dies, seemingly during initialization of the NVMe
interface, here's the most relevant lines (full kernel log attached):

[8.840439] Btrfs loaded
[   61.888098] clocksource: tsc: mask: 0x max_cycles: 
0x240939f1bb2, max_idle_ns: 440795263295 ns
[   64.807909] nvme :00:04.0: I/O 0 QID 0 timeout, disable controller
[   64.916220] nvme :00:04.0: Cancelling I/O 0 QID 0
[   64.920779] nvme :00:04.0: Identify Controller failed (-4)
[   64.925737] nvme :00:04.0: Removing after probe failure
[   64.930506] iounmap: bad address c9e5
[   64.934951] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted 4.4.0-1041-aws 
#50-Ubuntu
[   64.942528] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
[   64.947684] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
[   64.952688]  0286 fd001be315a343d4 8800bbb4bcd8 
813f7743
[   64.960923]  880036c6d4f0 c9e5 8800bbb4bcf8 
8106ae7f
[   64.969368]  880036c6d4f0 880036c6d658 8800bbb4bd08 
8106aebc
[   64.977878] Call Trace:
[   64.981322]  [] dump_stack+0x63/0x90
[   64.985878]  [] iounmap.part.1+0x7f/0x90
[   64.990583]  [] iounmap+0x2c/0x30
[   64.994873]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
[   65.71]  [] nvme_remove+0xce/0xe0 [nvme]
[   65.005125]  [] pci_device_remove+0x39/0xc0
[   65.009912]  [] __device_release_driver+0xa1/0x150
[   65.015009]  [] device_release_driver+0x23/0x30
[   65.020019]  [] pci_stop_bus_device+0x8a/0xa0
[   65.024806]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
[   65.032326]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme]
[   65.037731]  [] process_one_work+0x165/0x480
[   65.042482]  [] worker_thread+0x4b/0x4c0
[   65.046978]  [] ? process_one_work+0x480/0x480
[   65.051905]  [] kthread+0xe5/0x100
[   65.056224]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   65.061380]  [] ret_from_fork+0x3f/0x70
[   65.066103]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   65.071235] Trying to free nonexistent resource 

[  125.080477] random: nonblocking pool is initialized
(...End of output...)

Relevant data:
AMI id: ami-8fd760f6 (Should be the latest official release)
Instance type: m5.large
Region: eu-west-1

Issue seems completely repeatable.

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "kernel.log"
   https://bugs.launchpad.net/bugs/1737187/+attachment/5020190/+files/kernel.log

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

Title:
  Unable to launch AWS M5 instance with newest Ubuntu AMI

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

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

Re: [Bug 1726464] Re: Can't easily move the cursor between monitors when the dock is set to auto-hide

[Rasmus Eneman]

In Unity it's still triggered by the mouse when placing it near the edge of
the screen. I don't know how many pixels is used but I have never felt that
it has been hard to trigger it.

On Sun, Nov 12, 2017, 14:00 Michele <1726...@bugs.launchpad.net> wrote:

> @Rasmus: what's "this"? You mean just allowing the user to trigger the
> dock by keyboard shortcut? Or is there some smarter/more optimized mouse
> gesture to trigger the dock in Unity?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1726464
>
> Title:
>   Can't easily move the cursor between monitors when the dock is set to
>   auto-hide
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726464/+subscriptions
>

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

Title:
  Can't easily move the cursor between monitors when the dock is set to
  auto-hide

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

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

[Bug 1726464] Re: Can't easily move the cursor between monitors when the dock is set to auto-hide

[Rasmus Eneman]

This has worked in Unity for many years so it's certenly not impossible.
Now I don't know the code of neither Unity nor Gnome and it may well be
so that Gnome can not support it but the concept itself is very
possible.

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

Title:
  Can't easily move the cursor between monitors when the dock is set to
  auto-hide

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

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

[Bug 1726464] Re: Add option to disable sticky edges

[Rasmus Eneman]

I realized that this is only when I have the dock set to auto hide. With
always visible it's possible to move the cursor to the other screen
without issues.

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

Title:
  Add option to disable sticky edges

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

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

[Bug 1726464] Re: Add option to disable sticky edges

[Rasmus Eneman]

>Is this the sticky edges feature, or generally a cursor barrier
problem?

I don't know if it's the correct name. But the cursor "sticks" on the
edge between the monitors. It should move just like it does when I drag
it on a single monitor.

>Are you dragging a window when the problem happens?

No, just normal mouse movement without any window, file or other thing
"picked up"

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

Title:
  Add option to disable sticky edges

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

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

[Bug 1726464] [NEW] Add option to disable sticky edges

[Rasmus Eneman]

Public bug reported:

The sticky edge thing between monitors is very annoying as the cursor
never ends up where it should when it's moved over to the other screen.
It's annoying to the degree that I feel like I can not use multiple
monitors with standard Ubuntu anymore.

Unity had an option to disable this, please add one to Gnome as well.

** Affects: gnome-shell-extension-ubuntu-dock (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/1726464

Title:
  Add option to disable sticky edges

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

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

[Bug 1603261] Re: Grub freezes for a few seconds on every boot

[Rasmus Eneman]

Same behavior when my USB hub is connected but if I have just the laptop
it works fine

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

Title:
  Grub freezes for a few seconds on every boot

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

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

[Bug 1705592] [NEW] package linux-image-4.10.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Rasmus Arild Djuve]

Public bug reported:

Several packages have failed installing lately. Should be checked better
before they are made public.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-28-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rasmus 1996 F pulseaudio
Date: Fri Jul 21 01:17:26 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6
InstallationDate: Installed on 2016-06-24 (391 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.10.0-28-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to zesty on 2017-05-05 (76 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P15RAN.208.140429.ZW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370R5E-S08SE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 3570R/370R/470R/450R/510R/4450RV
dmi.product.version: P15RAN
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-28-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

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

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

[Bug 1696305] [NEW] High CPU usage in gnome-shell around 70%

[Rasmus Eneman]

Public bug reported:

Even when doing nothing at all, gnome-shell uses around 70% CPU.

```
inxi -t cm
Processes: CPU: % used - top 5 active
   1: cpu: 68.6% command: gnome-shell pid: 1399
   2: cpu: 50.4% command: Xwayland pid: 1405
   3: cpu: 19.7% command: firefox pid: 3684
   4: cpu: 2.4% command: gnome-shell pid: 1859
   5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 
13603
   Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active
   1: mem: 1033.63MB (8.6%) command: firefox pid: 3684
   2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859
   3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058
   4: mem: 111.25MB (0.9%) command: Xorg pid: 1506
   5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055
```

It's also strange that Xwayland is active as I did choose the "normal" gnome 
session upon signin.
```
echo $XDG_SESSION_TYPE
x11
```

While searching I found a recent problem with AMD GPUs, but I'm using an Intel 
GPU
```
glxinfo 
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_SGI_make_current_read, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
Version: 17.1.0
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, 
GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, 
GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, 
GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, 
GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, 
GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, 
GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, 
GL_ARB_blend_func_extended, 

[Bug 1696198] [NEW] gnome-terminal-server crashed with SIGSEGV

[Rasmus Eneman]

Public bug reported:

Crash when I clicked edit on the profile in the preferences window

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun  6 20:04:16 2017
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2017-06-03 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170602)
ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
SegvAnalysis:
 Segfault happened at: 0x56359a467420:  mov0x40(%rdi),%rax
 PC (0x56359a467420) ok
 source "0x40(%rdi)" (0x0040) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 ()
 ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal-server crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-terminal-server crashed with SIGSEGV

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

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

[Bug 1691432] [NEW] package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Rasmus Arild Djuve]

Public bug reported:

I have Ubuntu on two laptops, and both have problems with the Ubuntu
Software update. This one just sopped in the process of updating without
any external reason.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rasmus 1886 F pulseaudio
Date: Wed May 17 10:56:35 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6
InstallationDate: Installed on 2016-06-24 (326 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to zesty on 2017-05-05 (12 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P15RAN.208.140429.ZW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370R5E-S08SE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 3570R/370R/470R/450R/510R/4450RV
dmi.product.version: P15RAN
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

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

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

[Bug 1691387] [NEW] package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Rasmus Arild Djuve]

Public bug reported:

I have had problems in updating my Ubuntu laptop after I upgraded to
17.04. The "Ubuntu Software" is not working well. Today's problem came
after a power- and internet-cut. I could not get it to resume, and upon
restarting the laptop, the above error message came.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rasmus 1750 F pulseaudio
 /dev/snd/controlC1:  rasmus 1750 F pulseaudio
Date: Wed May 17 09:15:56 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=40d249fd-931c-48a4-88e6-19783194ef76
InstallationDate: Installed on 2017-05-02 (14 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK Computer Inc. K52N
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52N.217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52N
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52N.217:bd12/23/2010:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

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

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

[Bug 1676471] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Update stopped working when updating Thunderbird and OS

[Rasmus Arild Djuve]

Public bug reported:

Update stopped. Possibly reason Old Hardware (Asus A52N)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CupsErrorLog:
 
Date: Mon Mar 27 15:11:01 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-08-04 (234 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: ASUSTeK Computer Inc. K52N
Papersize: a4
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52N.217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52N
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52N.217:bd12/23/2010:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-package 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/1676471

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1 Update stopped working
  when updating Thunderbird and OS

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

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

[Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Rasmus Larsen]

I have only been able to reproduce this on our production workloads, and
we've recently downgraded from HWE (4.8.0-X) to GA (4.4.0-66), where we
currently aren't seeing any issues.

If I see the issue reappear, I'll try to verify it with a mainline
kernel, if someone finds a way to reproduce this consistently, I'll
happily help bisect this.

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

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

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

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

[Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Rasmus Larsen]

I can confirm hitting this on 4.8.41 as well.

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

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

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

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

[Bug 1513232] Re: do-release-upgrade no longer works from lucid to precise

[Rasmus Sten]

With the risk of stating the obvious, allowing unauthenticated packages
is not really an acceptable workaround.

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

Title:
  do-release-upgrade no longer works from lucid to precise

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

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

[Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[Rasmus Eneman]

@bitgandtter
Intel added driver support for hardware that is not released yet, so there are 
no available firmware.
The only affect it has on any actual system is these warnings, it's nothing to 
worry about.

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

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

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

[Bug 1633819] Re: Some PyQt4 applications fail to start in Yakkety due to missing PyQt4-WebKit

[Rasmus Underbjerg Pinnerup]

@David: That worked! Thank you very much for your help. I hope the
overarching issue is resolved soon :)

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

Title:
  Some PyQt4 applications fail to start in Yakkety due to missing
  PyQt4-WebKit

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

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

[Bug 1633819] Re: Some PyQt4 applications fail to start in Yakkety due to missing PyQt4-WebKit

[Rasmus Underbjerg Pinnerup]

@David: Thank you; that doesn't seem to work here, tho. When I run apt-get, it 
replies with:
 E: Version ‘4.11.4+dfsg-1build4’ for ‘python-qt4’ was not found
 E: Version ‘4.11.4+dfsg-1build4’ for ‘python-qt4-sql’ was not found
It seems it doesn't have access to earlier versions that the installed one 
("4.11.4+dfsg-2").

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

Title:
  Some PyQt4 applications fail to start in Yakkety due to missing
  PyQt4-WebKit

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

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

[Bug 1633819] Re: Some PyQt4 applications fail to start in Yakkety due to missing QtWebKit

[Rasmus Underbjerg Pinnerup]

Wow, this is an unfortunate surprise after upgrading to 16.10. I cannot
do without Anki. How did you perform the downgrade, David?

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

Title:
  Some PyQt4 applications fail to start in Yakkety due to missing
  QtWebKit

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

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

[Bug 1590777] Re: gnome-shell crashed with signal 5 in _XIOError()

[Rasmus Thomsen]

** This bug is no longer a duplicate of private bug 1505409

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

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

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

[Bug 1518457] Re: kswapd0 100% CPU usage

[Rasmus Larsen]

I had this issue too on AWS.

In my case, it was the udev rule for vm-hotadd and the fix as mentioned
previously basically came down to "touch /etc/udev/rules.d/40-vm-
hotadd.rules" which effectively disables the /lib/udev/rules.d/40-vm-
hotadd.rules file (after a reboot).

The udev rule basically seems to only be active for Xen or Hyper-V and
while it seems the Hyper-V stuff was also present in previous versions,
the Xen stuff seems to be introduced in 15.10 or newer.

So if you're seeing this issue on anything running on Xen, including
AWS, try:

touch /etc/udev/rules.d/40-vm-hotadd.rules
reboot

This is probably a bug in Xen or a bug in the kernel.

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

Title:
  kswapd0 100% CPU usage

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I've verified that the linux-image-4.4.0-23-generic image in xenial-proposed 
boots correctly on a c3.large ec2 instance.
uname -v: #41-Ubuntu SMP Mon May 16 23:04:25 UTC 2016

root@ip-10-33-53-135:~# apt-cache showpkg linux-image-4.4.0-23-generic
Package: linux-image-4.4.0-23-generic
Versions:
4.4.0-23.41 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-proposed_main_binary-amd64_Packages)
 Description Language:
 File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-proposed_main_binary-amd64_Packages
  MD5: 301993998617cbcae03feb3fe5d3aa55
 Description Language: en
 File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-proposed_main_i18n_Translation-en
  MD5: 301993998617cbcae03feb3fe5d3aa55


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

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Well, they're probably waiting for the patch to hit the LTS kernel 4.4
branch, which will probably happen on the 18th May... Or something like
that.

But you can easily run it until then...

Use the 16.04 Beta 2 AMIs, but just disable kernel updates (say, with
"apt-mark hold") and update everything else. That will basically give
you all the final stuff, just without the last few kernel updates,
including the one that broke most EC2 instances.

When a working kernel gets here, just apt-mark unhold and you should be
good.

You might want to temporarily disable automatic security updates until
then if you do it though...

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Here you go, cpuid -1 -r output.

** Attachment added: "cpuid -1 -r output c3.large instances"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657733/+files/cpuid_raw.txt

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

CPUID output posted before was truncated...

** Attachment added: "Full CPUID output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657525/+files/cpuid_full.txt

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Kernel boots correctly on a c3.large with Thomas patch.

I've attached the output of the cpuid command (apt-get install cpuid) on
the instance, in case it has any interest.

** Attachment added: "cpuid command output c3.large"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657524/+files/cpuid.txt

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I can confirm that I can boot with this kernel on a C3.large instance.

If anyone else wants to verify this, the procedure is to boot one of the
failing instances with the Beta 2 AMIs and install the build (and
reboot).

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I get the same issue with the build, which seemed weird so I retested and it 
looks like I must have mislabeled one of my builds, because now when I build 
31c2013e4ea2e594522980acc3d20e88664b19f1, I still get the issue, but if I go 
back to a6ebb4464659d35e0516900a8493f9720dd77d67 it works.
Somehow I must have swapped some builds...

a6ebb4464659d35e0516900a8493f9720dd77d67 Good
31c2013e4ea2e594522980acc3d20e88664b19f1   Bad
8ae10f463b7ae3455e9d0507176349c76580995f   Bad

Really sorry about the detour Joseph.

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Verified it on multiple instances.

31c2013e4ea2e594522980acc3d20e88664b19f1 is the last good commit.
8ae10f463b7ae3455e9d0507176349c76580995f is the first bad commit.

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

According to my bisect this commit is responsible:

commit 8ae10f463b7ae3455e9d0507176349c76580995f
Author: Vikas Shivappa 
Date:   Thu Mar 10 15:32:09 2016 -0800

perf/x86/mbm: Add Intel Memory B/W Monitoring enumeration and init

BugLink: http://bugs.launchpad.net/bugs/1397880

The MBM init patch enumerates the Intel MBM (Memory b/w monitoring)
and initializes the perf events and datastructures for monitoring the
memory b/w.

Its based on original patch series by Tony Luck and Kanaka Juvva.

Memory bandwidth monitoring (MBM) provides OS/VMM a way to monitor
bandwidth from one level of cache to another. The current patches
support L3 external bandwidth monitoring. It supports both 'local
bandwidth' and 'total bandwidth' monitoring for the socket. Local
bandwidth measures the amount of data sent through the memory controller
on the socket and total b/w measures the total system bandwidth.

Extending the cache quality of service monitoring (CQM) we add two
more events to the perf infrastructure:

  intel_cqm_llc/local_bytes - bytes sent through local socket memory 
controller
  intel_cqm_llc/total_bytes - total L3 external bytes sent

The tasks are associated with a Resouce Monitoring ID (RMID) just like
in CQM and OS uses a MSR write to indicate the RMID of the task during
scheduling.

Signed-off-by: Vikas Shivappa 
Signed-off-by: Peter Zijlstra (Intel) 
Reviewed-by: Tony Luck 
Acked-by: Thomas Gleixner 
Cc: Alexander Shishkin 
Cc: Andy Lutomirski 
Cc: Arnaldo Carvalho de Melo 
Cc: Borislav Petkov 
Cc: Brian Gerst 
Cc: David Ahern 
Cc: Denys Vlasenko 
Cc: H. Peter Anvin 
Cc: Jiri Olsa 
Cc: Linus Torvalds 
Cc: Matt Fleming 
Cc: Namhyung Kim 
Cc: Peter Zijlstra 
Cc: Stephane Eranian 
Cc: Vince Weaver 
Cc: fenghua...@intel.com
Cc: h.peter.an...@intel.com
Cc: ravi.v.shan...@intel.com
Cc: vikas.shiva...@intel.com
Link: 
http://lkml.kernel.org/r/1457652732-4499-4-git-send-email-vikas.shiva...@linux.intel.com
Signed-off-by: Ingo Molnar 
(back ported from commit 33c3cc7acfd95968d74247f1a4e1b0727a07ed43)
Signed-off-by: Tim Gardner 

 Conflicts:
arch/x86/kernel/cpu/common.c

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Bisecting...

Current candidate seems to be 31c2013e4ea2e594522980acc3d20e88664b19f1

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I can still reproduce this in 4.6-rc5. See attached boot log.

I might do a bisect on this if I find the time...

** Attachment added: "kernel4.6-rc5.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4650339/+files/kernel4.6-rc5.log

** Tags added: kernel-bug-exists-upstream

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I've tested with some instance types with the ami-3079f543 image (eg.
ubuntu 16.04 final with Ubuntu 4.4.0-21.37-generic 4.4.6)

The following instance types fail to start with a kernel panic:

r3.large
c3.large

The following instance types seem to work:

t2.micro
c4.large
m3.medium

I haven't tested with all sizes, but I suspect all t2, c4 and m3
instances are good.

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Currently also encountering this issue (the same kernel panic) with ami-
3079f543 on eu-west-1 with a c3.large instance.

So this seems to be a general ubuntu 16.04 on AWS issue and not an
upgrade specific issue. I haven't seen this issue with the beta2 AMIs.

Interestingly I seem to be able to start the AMI on t2.micro instances,
so this could well be instance type specific.

** Attachment added: "AWS Kernel panic log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4648152/+files/aws.log

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening

[Rasmus Underbjerg Pinnerup]

>This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

Sounds good, but I wonder when this reaches Ubuntu then. Mine is
currently at 1:3.14.2-0ubuntu13.

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

Title:
  Empty trash from Launcher results in Nautilus window opening

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

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

[Bug 1468039] Re: XFS: Corruption of in-memory data detected

[Rasmus Borup Hansen]

I' having a similar problem with trusty 3.13.0-55:

[601201.817664] 88016e03e000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 
00  
[601201.818224] 88016e03e010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 
00  . ..
[601201.818827] 88016e03e020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00  
[601201.819429] 88016e03e030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00  
[601201.820013] XFS (dm-0): Internal error xfs_attr3_leaf_write_verify at line 
216 of file /build/buildd/linux-3.13.0/fs/xfs/xfs_attr_leaf.c.  Caller 
0xa00996f0
[601201.820910] CPU: 1 PID: 421 Comm: xfsaild/dm-0 Not tainted 
3.13.0-55-generic #92-Ubuntu
[601201.820913] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 
08/17/2011
[601201.820914]  0001 880035cc3bd0 81723294 
8802ac71d800
[601201.820918]  880035cc3be8 a009d6fb a00996f0 
880035cc3c20
[601201.820919]  a009d755 00d800205500 88001aa2a400 
880050acc2b8
[601201.820922] Call Trace:
[601201.820930]  [81723294] dump_stack+0x45/0x56
[601201.820964]  [a009d6fb] xfs_error_report+0x3b/0x40 [xfs]
[601201.820974]  [a00996f0] ? _xfs_buf_ioapply+0x70/0x3a0 [xfs]
[601201.820984]  [a009d755] xfs_corruption_error+0x55/0x80 [xfs]
[601201.820997]  [a00bab50] xfs_attr3_leaf_write_verify+0x100/0x120 
[xfs]
[601201.821007]  [a00996f0] ? _xfs_buf_ioapply+0x70/0x3a0 [xfs]
[601201.821016]  [a009b3d5] ? xfs_bdstrat_cb+0x55/0xb0 [xfs]
[601201.821026]  [a00996f0] _xfs_buf_ioapply+0x70/0x3a0 [xfs]
[601201.821030]  [8109abc0] ? wake_up_state+0x20/0x20
[601201.821040]  [a009b3d5] ? xfs_bdstrat_cb+0x55/0xb0 [xfs]
[601201.821050]  [a009b336] xfs_buf_iorequest+0x46/0x90 [xfs]
[601201.821060]  [a009b3d5] xfs_bdstrat_cb+0x55/0xb0 [xfs]
[601201.821070]  [a009b56b] __xfs_buf_delwri_submit+0x13b/0x210 [xfs]
[601201.821081]  [a009c000] ? xfs_buf_delwri_submit_nowait+0x20/0x30 
[xfs]
[601201.821100]  [a00faaa0] ? xfs_trans_ail_cursor_first+0x90/0x90 
[xfs]
[601201.821110]  [a009c000] xfs_buf_delwri_submit_nowait+0x20/0x30 
[xfs]
[601201.821127]  [a00facd7] xfsaild+0x237/0x5c0 [xfs]
[601201.821145]  [a00faaa0] ? xfs_trans_ail_cursor_first+0x90/0x90 
[xfs]
[601201.821148]  [8108b702] kthread+0xd2/0xf0
[601201.821150]  [8108b630] ? kthread_create_on_node+0x1c0/0x1c0
[601201.821153]  [81733ca8] ret_from_fork+0x58/0x90
[601201.821155]  [8108b630] ? kthread_create_on_node+0x1c0/0x1c0
[601201.821158] XFS (dm-0): Corruption detected. Unmount and run xfs_repair
[601201.821581] XFS (dm-0): xfs_do_force_shutdown(0x8) called from line 1320 of 
file /build/buildd/linux-3.13.0/fs/xfs/xfs_buf.c.  Return address = 
0xa009971c
[601201.832780] XFS (dm-0): Corruption of in-memory data detected.  Shutting 
down filesystem
[601201.833292] XFS (dm-0): Please umount the filesystem and rectify the 
problem(s)
[601201.843375] 880238b0: 58 44 32 42 01 00 0e c0 00 00 00 00 00 00 00 
00  XD2B
[601201.843924] 880238b00010: 00 00 00 20 3d a7 0c 7b 01 2e 8d 9e 01 88 00 
10  ... =..{
[601201.844472] 880238b00020: 00 00 00 19 21 a9 2d 2f 02 2e 2e 9e 01 88 00 
20  !.-/...
[601201.845031] 880238b00030: 00 00 00 07 39 2b 68 20 18 4d 4f 42 31 41 5f 
48  9+h .MOB1A_H
[601201.845585] XFS (dm-0): Internal error xfs_da3_node_read_verify at line 240 
of file /build/buildd/linux-3.13.0/fs/xfs/xfs_da_btree.c.  Caller 
0xa009a885
[601201.858885] CPU: 1 PID: 2806 Comm: kworker/1:1H Not tainted 
3.13.0-55-generic #92-Ubuntu
[601201.858889] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 
08/17/2011
[601201.858938] Workqueue: xfslogd xfs_buf_iodone_work [xfs]
[601201.858941]  0001 8802af9cbd68 81723294 
8802ac71d800
[601201.858944]  8802af9cbd80 a009d6fb a009a885 
8802af9cbdb8
[601201.858945]  a009d755 00f0810a0465 880031b35b00 
880238b0
[601201.858948] Call Trace:
[601201.858958]  [81723294] dump_stack+0x45/0x56
[601201.858969]  [a009d6fb] xfs_error_report+0x3b/0x40 [xfs]
[601201.858979]  [a009a885] ? xfs_buf_iodone_work+0x85/0xf0 [xfs]
[601201.858989]  [a009d755] xfs_corruption_error+0x55/0x80 [xfs]
[601201.859005]  [a00d146c] xfs_da3_node_read_verify+0x8c/0x180 [xfs]
[601201.859014]  [a009a885] ? xfs_buf_iodone_work+0x85/0xf0 [xfs]
[601201.859024]  [a009a885] xfs_buf_iodone_work+0x85/0xf0 [xfs]
[601201.859028]  [81083b22] process_one_work+0x182/0x450
[601201.859030]  [81084911] worker_thread+0x121/0x410
[601201.859032]  [810847f0] ? rescuer_thread+0x430/0x430
[601201.859035]  [8108b702] kthread+0xd2/0xf0
[601201.859037]  [8108b630] ? kthread_create_on_node+0x1c0/0x1c0

[Bug 1373560] Re: /etc/cron.daily/spamassassin calls sa-update with potentially incorrect umask

[Rasmus Borup Hansen]

I ran into this bug as well and checked if it's also present in Debian.
It appears that from spamassassin 3.4.0-2 the relevant code is:

# Update
umask 022
env -i LANG=$LANG PATH=$PATH start-stop-daemon \
--chuid debian-spamd:debian-spamd --start \
--exec /usr/bin/sa-update -- \
--gpghomedir /var/lib/spamassassin/sa-update-keys 21

When using start-stop-daemon to invoke sa-update the umask is not
changed, so updating to this version will fix the bug.

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

Title:
  /etc/cron.daily/spamassassin calls sa-update with potentially
  incorrect umask

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

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

[Bug 1373560] Re: /etc/cron.daily/spamassassin calls sa-update with potentially incorrect umask

[Rasmus Borup Hansen]

I ran into this bug as well and checked if it's also present in Debian.
It appears that from spamassassin 3.4.0-2 the relevant code is:

# Update
umask 022
env -i LANG=$LANG PATH=$PATH start-stop-daemon \
--chuid debian-spamd:debian-spamd --start \
--exec /usr/bin/sa-update -- \
--gpghomedir /var/lib/spamassassin/sa-update-keys 21

When using start-stop-daemon to invoke sa-update the umask is not
changed, so updating to this version will fix the bug.

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

Title:
  /etc/cron.daily/spamassassin calls sa-update with potentially
  incorrect umask

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1373560/+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