[Bug 2067318] [NEW] Hitting Ctrl-C in the dpkg config conflict interactive sub-shell aborts the upgrade

[Kai Groner]

Public bug reported:

During an upgrade from 23.10 to 24.04, while investigating a config
conflict in an interactive sub shell I used ^C to discard the current
command in that shell. Instead of the shell receiving the interrupt
signal and responding in the way it normally did, some other process in
the upgrade process received it and aborted the upgrade.

Using ^C to discard the current command in a shell is normal use and
shouldn't result in catastrophic failure of the upgrade.

Some of the upgrade is still running, but nothing is responding to
keyboard input.

Here is the output of the process after I hit ^C:
-
   Could not install the upgrades

  The 
upgrade has aborted. Your system could be in an unusable state. A
 recovery will run now (dpkg --configure -a).

  dpkg: error: dpkg database lock 
was locked by another process with pid 1275670

Note: removing the lock file is 
always wrong, can damage the locked area
 and the entire system. See 
.

 dp

   Upgrade complete

 The upgrade has completed but there were errors during the upgrade
process.


 To continue please press [ENTER]
-


Here is the process tree that remained after the upgrade process aborted:
-
USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1218552  0.0  0.0  17396  7680 pts/3S+   12:50   0:01 sudo 
do-release-upgrade
root 1218553  0.0  0.0  17396  2628 pts/2Ss   12:50   0:00  \_ sudo 
do-release-upgrade
root 1218554  0.7  0.7 558320 245452 pts/2   Sl+  12:50   0:50  \_ 
/usr/bin/python3 -s /tmp/ubuntu-release-upgrader-xq5m8ra9/noble --mode=server 
--frontend=DistUpgradeViewText
root 1224613  0.0  0.0  0 0 pts/2Z+   12:58   0:00  \_ 
[sh] 
root 1224643  0.1  0.5 560428 172244 pts/2   S+   12:58   0:12  \_ 
/usr/bin/python3 -s /tmp/ubuntu-release-upgrader-xq5m8ra9/noble --mode=server 
--frontend=DistUpgradeViewText
root 1275670  0.0  0.0  21320 16700 pts/0Ss   13:12   0:02  
\_ /usr/bin/dpkg --force-overwrite --status-fd 112 --configure --pending
root 1320513  0.0  0.0   8592  5376 pts/0S+   14:27   0:00  
\_ /bin/bash -i --
-

It appears there are several pseudoterminals in use.

I thought screen used to be used for this, but it doesn't seem to be in
this case. Maybe that's not relevant here, I don't know.

Whatever code is doing this needs to put the outer layer in raw mode to
be able to handle normal interactive use.

** Affects: ubuntu-release-upgrader (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/2067318

Title:
  Hitting Ctrl-C in the dpkg config conflict interactive sub-shell
  aborts the upgrade

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


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

[Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

[Kai Groner]

I've been running the ubuntu generic kernel (5.13.0-28-generic) for the
last 33 days without the issue reoccurring, so I think this can be
closed.

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

Title:
  WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

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


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

[Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows

[Kai Groner]

https://bugzilla.mozilla.org/show_bug.cgi?id=1756170

** Bug watch added: Mozilla Bugzilla #1756170
   https://bugzilla.mozilla.org/show_bug.cgi?id=1756170

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

Title:
  CSD do not distinguish focused and unfocused FF windows

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


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

[Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows

[Kai Groner]

At the moment it's "Yaru-dark / Yaru" and the issue remains.

I was using a third party theme when I first encountered this. I
switched back to Yaru before filing this bug, but about:support was
still showing the third party theme. After resetting the theme it's
showing "Yaru-dark / Yaru".

I did some more testing with a separate login I use for steam and a new
FF profile. It seems to only happen when a a FF colorways theme is used.
If the default theme is used I am able to see a difference in the
titlebar shade (it's too subtle IMO, but I can see it).

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

Title:
  CSD do not distinguish focused and unfocused FF windows

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


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

[Bug 1957944] [NEW] CSD do not distinguish focused and unfocused FF windows

[Kai Groner]

Public bug reported:

After the FF 96 upgrade I can't distinguish focused and unfocused FF
windows from their client side decorations.

Previously the distinction was subtle, but not impossible.

The attached image shows two windows, the one on the left has focus.
The only way you can tell this is that the scrollbar is faded in the
unfocused window.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: firefox 96.0+build2-0ubuntu0.21.10.1
Uname: Linux 5.14.0-051400-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BuildID: 20220106144528
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 14 13:15:27 2022
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-06-18 (941 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profile2Extensions: extensions.sqlite corrupt or missing
Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile2Locales: extensions.sqlite corrupt or missing
Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
Profile2PrefSources: prefs.js
Profile2Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=96.0/20220106144528 (In use)
 Profile0 (Default) - LastVersion=96.0/20220106144528 (In use)
 Profile2 - LastVersion=71.0/20191205203726 (Out of date)
RebootRequiredPkgs: Error: path contained symlinks.
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.90
dmi.board.name: B450M Steel Legend
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

** Attachment added: "ff-csd-focus-bug.png"
   
https://bugs.launchpad.net/bugs/1957944/+attachment/5554362/+files/ff-csd-focus-bug.png

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

Title:
  CSD do not distinguish focused and unfocused FF windows

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


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

[Bug 1956771] Re: zfs dataset mountpoints moved to /var/lib/snapd/hostfs

[Kai Groner]

I initially thought this was a snapd issue (hey, snapd stole my zfs
mounts!), but I think those are supposed to be bind mounts.

I also looked at the zfsutils-linux changelog and recent patches but
didn't see anything that seemed suspicious to me.

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

Title:
  zfs dataset mountpoints moved to /var/lib/snapd/hostfs

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


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

[Bug 1956771] Re: zfs dataset mountpoints moved to /var/lib/snapd/hostfs

[Kai Groner]

Here are the mountpoints, after I moved them out of
/var/lib/snapd/hostfs.

: kai@cakepile kai; zfs mount -l
square/postgresql   /var/lib/postgresql-square
square/docker   /var/lib/docker-square
square/avahi-captures   /mnt/avahi-captures
square/mn   /mn
square/mn/elasticsearch-staging  /mn/elasticsearch-staging
square/mn/etcd-foo  /mn/etcd-foo
square/mn/minio /mn/minio
square/mn/pg-staging/mn/pg-staging
square/mn/postgres-a/mn/postgres-a
square/mn/postgres-b/mn/postgres-b
square/mn/redis-staging /mn/redis-staging
square/mn/rels.sqlite   /mn/rels.sqlite
square/mn/wal-g-test/mn/wal-g-test

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

Title:
  zfs dataset mountpoints moved to /var/lib/snapd/hostfs

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


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

[Bug 1956771] [NEW] zfs dataset mountpoints moved to /var/lib/snapd/hostfs

[Kai Groner]

Public bug reported:

After a reboot, my zfs datasets all mounted under /var/lib/snapd/hostfs,
exclusively.

This is on a 20.04 machine. It has received package updates, but no
reboots for 4.5 months.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: focal

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

Title:
  zfs dataset mountpoints moved to /var/lib/snapd/hostfs

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


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

[Bug 1952468] [NEW] gnome-settings-daemon resetting time zone after network-manager sets it

[Kai Groner]

Public bug reported:

I am currently traveling and have observed the time zone being set
correctly when I connect to a network and then reset to my home time
zone a short while later.

Automatic Time Zone is enabled in settings.

Logs indicate the reset is coming from /usr/libexec/gsd-datetime.  I
guess it's not informed of the configuration coming from network-
manager?

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-settings-daemon 40.0.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 26 10:35:29 2021
InstallationDate: Installed on 2019-03-17 (984 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to impish on 2021-10-17 (39 days ago)

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


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

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

Title:
  gnome-settings-daemon resetting time zone after network-manager sets
  it

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


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

[Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

[Kai Groner]

This issue in evolution-data-server seems to describe the problem.

https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276


** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #276
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

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


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

[Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

[Kai Groner]

This is still happening after upgrading to 21.10. The calendar reminder
I saw today and last night was canceled several weeks ago. When I looked
in the topbar calendar dropdown, the event did not appear there.

It's unclear to me if this is a gnome-shell issue or a gnome-calendar
issue or maybe something like evolution-data-server?

** Tags removed: hirsute
** Tags added: impish

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

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


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

[Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

[Kai Groner]

After 20 days with the mainline 5.14.0 kernel, I have not seen a
reoccurrence this behavior.

There was one "WARNING: ... decide_linksettings [amdgpu]" kernel
message, but the inability to bring the display port monitors back up
did not occur.

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

Title:
  WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

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


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

[Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

[Kai Groner]

I have booted and installed the mainline kernel. I don't have a recipe
to reproduce the problem, and sometimes weeks go by between occurrences.
I will follow up here when it happens again or check back in a few weeks
if it does not.

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

Title:
  WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

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


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

[Bug 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

[Kai Groner]

This happened again today. I have discovered that recovery by
suspend/resume is possible.

** Summary changed:

- WARNING: CPU: 11 PID: 3608 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529 
decide_link_settings+0x1ab/0x1d0 [amdgpu]
+ WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

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

Title:
  WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]

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


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

[Bug 1942619] Re: WARNING: CPU: 11 PID: 3608 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529 decide_link_settings+0x1ab/0x1d0 [amdgpu]

[Kai Groner]

** Attachment added: "journalctl -t kernel -g 
'drm.*ERROR|WARNING.*amdgpu|Linux.version|PM: suspend.exit'"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942619/+attachment/5522834/+files/amdgpu-stability-hilites.txt

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

Title:
  WARNING: CPU: 11 PID: 3608 at
  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529
  decide_link_settings+0x1ab/0x1d0 [amdgpu]

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


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

[Bug 1942619] [NEW] WARNING: CPU: 11 PID: 3608 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529 decide_link_settings+0x1ab/0x1d0 [amdgpu]

[Kai Groner]

Public bug reported:

This has hit me twice in the last 24 hours.

Displays come in and out of power saving, without actually displaying
anything. The console doesn't become usable. It seems to be
unrecoverable, shutdown gets stuck somewhere and I end up having to hit
the reset button.

This is a desktop machine, which suspends frequently, usually without issue.
Radeon RX 570, dual monitor, display link

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-generic 5.11.0.31.33
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  3 10:11:35 2021
InstallationDate: Installed on 2019-06-18 (808 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic 
root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-31-generic N/A
 linux-backports-modules-5.11.0-31-generic  N/A
 linux-firmware 1.197.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-05-09 (116 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.90
dmi.board.name: B450M Steel Legend
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

Title:
  WARNING: CPU: 11 PID: 3608 at
  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:2529
  decide_link_settings+0x1ab/0x1d0 [amdgpu]

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


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

[Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

[Kai Groner]

This is still happening in 21.04, most recently with a repeating
calendar event instance that was canceled over a week ago. The desktop
has been rebooted in the interim.

** Tags added: hirsute

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

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

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

[Bug 1923893] [NEW] After rescheduling an event, calendar alerts appear for the old time

[Kai Groner]

Public bug reported:

I use google calendar.  Events are created and updated via the browser.
The calendar feed is configured through settings/online accounts. I can
see upcoming events in the calendar drop down. The calendar and desktop
are configured for the same timezone, and alerts normally appear
simultaneously on my phone and desktop.

I know sometimes stale calendar entries can be a factor, but I don't
*think* that's an issue at this time (the change was made almost 24
hours ago, I don't see the API limit errors I used to see in logs).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 14 15:02:11 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (666 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs:
 linux-image-5.8.0-49-generic
 linux-base
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago)

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


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

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

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

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

[Bug 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Kai Groner]

I've also had this problem with the flameshot icon disappearing after
upgrading to 20.04.

Reverting to gnome-shell-extension-appindicator 33-1 has fixed it for
now, but having broken dependencies isn't good (even if things seem to
be working).


Comments on https://github.com/flameshot-org/flameshot/issues/1206 also suggest 
this problem doesn't occur with the flameshot snap.  Testing the deb package 
specifically may be a good idea.

** Bug watch added: github.com/flameshot-org/flameshot/issues #1206
   https://github.com/flameshot-org/flameshot/issues/1206

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

Title:
  flameshot: The icon does not appear in the GNOME bar

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

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

[Bug 1850744] Re: amdgpu_device_ip_resume_phase2 errors

[Kai Groner]

I haven't experienced this hang since 2020-01-12 (as far back as my logs
go), so I think the upstream fix probably made it into the 19.10 and
20.04 kernels.

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

Title:
  amdgpu_device_ip_resume_phase2 errors

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

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

[Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Kai Groner]

I am running the 5.4.0-32-generic kernel from focal-proposed, and rtkit-
daemon seems to be working normally now.

: kai@dipper kai; uname -r
5.4.0-32-generic
: kai@dipper kai; journalctl -b0 -u rtkit-daemon
-- Logs begin at Fri 2020-01-03 16:35:36 EST, end at Tue 2020-05-19 11:02:23 
EDT. --
May 19 10:59:19 dipper systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
May 19 10:59:19 dipper systemd[1]: Started RealtimeKit Scheduling Policy 
Service.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully called chroot.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully dropped privileges.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully limited resources.
May 19 10:59:19 dipper rtkit-daemon[2535]: Running.
May 19 10:59:19 dipper rtkit-daemon[2535]: Canary thread running.
May 19 10:59:19 dipper rtkit-daemon[2535]: Watchdog thread running.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully made thread 2444 of 
process 2444 owned by '123' high priority at nice level -11.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 1 threads of 1 processes 
of 1 users.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 1 threads of 1 processes 
of 1 users.
May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully made thread 2682 of 
process 2444 owned by '123' RT at priority 5.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 2 threads of 1 processes 
of 1 users.
May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 2 threads of 1 processes 
of 1 users.
⋮

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

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

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

[Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Kai Groner]

In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled.  It was
only disabled for the lowlatency kernel.

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

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

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

[Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Kai Groner]

Enabling, but not configuring CONFIG_RT_GROUP_SCHED seems likely to be the 
cause of this:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next=9b039fc517876d312e7fa0955571101a299c91f5

Some discussion of this WRT lowlatency kernel is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

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

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

[Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages

[Kai Groner]

The full log is the best I can offer unless I figure out how to
reproduce this (it hasn't even re-occurred randomly).  If you skip the
first 50 lines and ignore the libinput errors, it's entirely errors
produced during or immediately after a freeze.

gnome-shell-extension-prefs shows the following enabled:
- Desktop Icons
- Ubuntu AppIndicators
- Ubuntu Dock

I don't know how to reproduce this problem, so I can't meaningfully test
disabling the Ubuntu AppIndicators extension.


** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367364/+files/lspcik.txt

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

Title:
  gnome-shell freezing with "Attempting to run a JS callback during
  garbage collection." messages

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

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

[Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages

[Kai Groner]

>From top, just now (gnome-shell has not been freezing during this
session):

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND  


   
   3885 kai   20   0 8342772 602120 331580 R  12.9   1.8 101:26.43 
gnome-shell 



When I enter and leave the activities screen, CPU time spikes to about
30%.  At idle it runs between 3% and 13%.

Cumulative CPU time is over 8-10h.

I don't have any record of the resource usage when it was freezing, but
I will try to grab that if it happens again.  This probably wasn't a low
memory situation as the machine had just booted and I had wasn't able to
run anything more than a terminal before I gave up and rebooted.

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

Title:
  gnome-shell freezing with "Attempting to run a JS callback during
  garbage collection." messages

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

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

[Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages

[Kai Groner]

In logs I have going back 6 months the errors "Attempting to run a JS
callback during garbage collection." and "The offending callback was
..." only appear on one other date.

There is a similar message "Attempting to call back into JSAPI during
the sweeping phase of GC." that appears more frequently.

I think it will be hard to get good timing data when the console is
freezing and unresponsive and I'm not sure when the issue might re-
occur.

I'm attaching the log from this session, as well as the log from my
current session for comparison.


** Attachment added: "GnomeShellFreezeLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367200/+files/GnomeShellFreezeLog.txt

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

Title:
  gnome-shell freezing with "Attempting to run a JS callback during
  garbage collection." messages

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

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

[Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages

[Kai Groner]

** Attachment added: "GnomeShellNormalLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367201/+files/GnomeShellNormalLog.txt

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

Title:
  gnome-shell freezing with "Attempting to run a JS callback during
  garbage collection." messages

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

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

[Bug 1876946] [NEW] gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages

[Kai Groner]

Public bug reported:

This happened soon after logging in.  The entire desktop (mouse cursor
included) would freeze for maybe 30 seconds at a time.  The activities
screen seemed to trigger it.  The dock appeared empty.

After a few minutes of this I rebooted and things seem to be alright
now.

Relevant log messages start on May 5 at 11:10 AM US/Eastern time.

Similar messages appear on March 31st.  I don't recall whether I
experienced similar freezing behavior at that time.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May  5 11:22:41 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (322 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago)

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


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

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

Title:
  gnome-shell freezing with "Attempting to run a JS callback during
  garbage collection." messages

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

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

[Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Kai Groner]

At this point it's just these log messages.

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

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

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

[Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Kai Groner]

In a virtual machine I can reproduce this by installing pulseaudio and
docker.io.

I'm attaching a Vagrantfile that reproduces the issue for me.

:; vagrant up
:; vagrant ssh -t -- journalctl -u rtkit-daemon

** Attachment added: "vagrantfile to reproduce issue"
   
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+attachment/5364696/+files/Vagrantfile

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

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

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

[Bug 1875665] [NEW] rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Kai Groner]

Public bug reported:

These errors started right after upgrading to 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rtkit 0.12-4
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 10:31:43 2020
InstallationDate: Installed on 2019-06-18 (315 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: rtkit
UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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


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

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

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

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

[Bug 1855198] Re: Gnome shell crash, maybe related to wireless mouse battery running out

[Kai Groner]

I'm unable to resubmit the retraced crash report using the linked
instructions.  A message in the journal says "Crash already reported."
I can try submitting a new report if the problem reoccurs.

Below is the content of StacktraceSource.  I'm attaching the more
detailed ThreadStacktrace.

#0  __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
  [Error: raise.c was not found in source tree]
#1  0x5573ecb6a52a in dump_gjs_stack_on_signal_handler ()
#2  
#3  0x in ?? ()
#4  0x7f073d599a37 in meta_selection_source_wayland_deactivated 
(source=0x5573fc425b50) at ../src/wayland/meta-selection-source-wayland.c:121
  [Error: meta-selection-source-wayland.c was not found in source tree]
#5  0x7f073e191936 in _g_closure_invoke_va () from 
/tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1
#6  0x7f073e1ae36c in g_signal_emit_valist () from 
/tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1
#7  0x7f073e1aefa9 in g_signal_emit_by_name () from 
/tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1
#8  0x7f073d55fd99 in meta_selection_set_owner (selection=0x5573edfeb8c0, 
selection_type=META_SELECTION_DND, owner=0x5573f439a290) at 
../src/core/meta-selection.c:100
  [Error: meta-selection.c was not found in source tree]
#9  0x7f073d586437 in source_new_cb (object=, res=, user_data=user_data@entry=0x5573fdafb8a0) at 
../src/x11/meta-x11-selection.c:257
  [Error: meta-x11-selection.c was not found in source tree]
#10 0x7f073e28c029 in g_task_return_now (task=0x7f072c003a50) at 
../../../gio/gtask.c:1212
  [Error: gtask.c was not found in source tree]
#11 0x7f073e28cbfd in g_task_return (task=0x7f072c003a50, type=) at ../../../gio/gtask.c:1281
  [Error: gtask.c was not found in source tree]
#12 0x7f073d5819b2 in read_mimetypes_cb (stream=, 
res=, task=task@entry=0x7f072c003a50) at 
../src/x11/meta-selection-source-x11.c:199
  [Error: meta-selection-source-x11.c was not found in source tree]
#13 0x7f073e28c029 in g_task_return_now (task=0x5573efdee8e0) at 
../../../gio/gtask.c:1212
  [Error: gtask.c was not found in source tree]
#14 0x7f073e28cbfd in g_task_return (task=0x5573efdee8e0, type=) at ../../../gio/gtask.c:1281
  [Error: gtask.c was not found in source tree]
#15 0x7f073e256826 in read_bytes_callback (stream=0x5573f3cb0380, 
result=0x5573fdae4e40, user_data=0x5573efdee8e0) at 
../../../gio/ginputstream.c:874
  [Error: ginputstream.c was not found in source tree]
#16 0x7f073e257d2b in async_ready_callback_wrapper 
(source_object=0x5573f3cb0380, res=0x5573fdae4e40, user_data=0x5573efdee8e0) at 
../../../gio/ginputstream.c:532
  [Error: ginputstream.c was not found in source tree]
#17 0x7f073e28c029 in g_task_return_now (task=0x5573fdae4e40) at 
../../../gio/gtask.c:1212
  [Error: gtask.c was not found in source tree]
#18 0x7f073e28c06d in complete_in_idle_cb (task=0x5573fdae4e40) at 
../../../gio/gtask.c:1226
  [Error: gtask.c was not found in source tree]
#19 0x7f073e0a671e in g_main_context_dispatch () from 
/tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#20 0x7f073e0a6ad0 in g_main_context_iterate.isra () from 
/tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#21 0x7f073e0a6dc3 in g_main_loop_run () from 
/tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#22 0x7f073d55c280 in meta_run () at ../src/core/main.c:676
#23 0x5573ecb69d85 in main ()


** Attachment added: "ThreadStacktrace"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+attachment/5309904/+files/ThreadStacktrace

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

Title:
  Gnome shell crash, maybe related to wireless mouse battery running out

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

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

[Bug 1855198] Re: Gnome shell crash, maybe related to wireless mouse battery running out

[Kai Groner]

Adding StacktraceSource as an attachment since it got folded in my
previous comment.

** Attachment added: "StacktraceSource"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+attachment/5309905/+files/StacktraceSource

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

Title:
  Gnome shell crash, maybe related to wireless mouse battery running out

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

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

[Bug 1855198] Re: Gnome shell crash, maybe related to wireless mouse battery running out

[Kai Groner]

Sorry, I'm not very familiar with apport or what the ubuntu error
collection system does with crash files.

I've been able to get an actual stack trace using apport-retrace here.
Is that useful if I resubmit with that?

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

Title:
  Gnome shell crash, maybe related to wireless mouse battery running out

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

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

[Bug 1855198] [NEW] Gnome shell crash, maybe related to wireless mouse battery running out

[Kai Groner]

Public bug reported:

This crash happened as I was changing the batteries for my wireless
mouse.  Needing to change the batteries in the middle of a session is
routine and has not lead to this failure previously.

There is a crash report, with the following oops id:

8ad61c2c-16e5-11ea-b0eb-fa163e983629

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  4 17:44:39 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (169 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago)

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


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

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

Title:
  Gnome shell crash, maybe related to wireless mouse battery running out

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

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

[Bug 1851564] [NEW] Daily Limit Exceeded messages for google calendars

[Kai Groner]

Public bug reported:

This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have
logs going back to mid august.  The message is repeated for each
calendar at various times.

Nov 06 13:49:13 dipper gnome-calendar[8681]:
source_credentials_required_cb: Failed to authenticate 'Kai Groner':
Daily Limit Exceeded. The quota will be reset at midnight Pacific Time
(PT). You may monitor your quota usage and adjust limits in the API
Console:
https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-calendar 3.34.2-1
ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  6 15:07:56 2019
InstallationDate: Installed on 2019-06-18 (141 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)

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


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

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

Title:
  Daily Limit Exceeded messages for google calendars

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

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

[Bug 1850744] Re: amdgpu_device_ip_resume_phase2 errors

[Kai Groner]

Reported upstream

https://bugs.freedesktop.org/show_bug.cgi?id=112221

** Bug watch added: freedesktop.org Bugzilla #112221
   https://bugs.freedesktop.org/show_bug.cgi?id=112221

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

Title:
  amdgpu_device_ip_resume_phase2 errors

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

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

[Bug 1850744] [NEW] amdgpu_device_ip_resume_phase2 errors

[Kai Groner]

Public bug reported:

I am using a Radeon RX 580.  This setup was stable with Ubuntu 19.04.
Since upgrading to 19.10 it's failed to resume from S3 sleep 3 times out
of 15.  The console will be unresponsive, but the machine is still
accessible over the network.

Here are some of the errors from dmesg (the second block happened on two
boots).  Complete kernel logs from all three boots are attached.

--
amdgpu :07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 
test failed (-110)
[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block 
 failed -110
[drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed 
(-110).
PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -110
PM: Device :07:00.0 failed to resume async: error -110
--
amdgpu :07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx 
test failed (-110)
[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block 
 failed -110
[drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed 
(-110).
PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -110
PM: Device :07:00.0 failed to resume async: error -110

--
The kernel is based on the Ubuntu-5.3.0-20.21 tag of the eoan kernel repo with 
the below listed patches applied.
 [v2,1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 70h
 [v2,2/2] hwmon/k10temp: Add support for AMD family 17h, model 70h CPUs 
https://patchwork.kernel.org/patch/11053205/

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-19-generic (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  kai3355 F pulseaudio
 /dev/snd/controlC1:  kai3355 F pulseaudio
 /dev/snd/controlC2:  kai3355 F pulseaudio
 /dev/snd/controlC0:  kai3355 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 30 23:21:52 2019
InstallationDate: Installed on 2019-06-18 (135 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
 lono wireless extensions.
 
 enp5s0no wireless extensions.
 
 lxdbr0no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-generic N/A
 linux-backports-modules-5.3.0-19-generic  N/A
 linux-firmware1.183.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-23 (8 days ago)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.60
dmi.board.name: B450M Steel Legend
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

** Attachment added: "kernel logs with amdgpu resume errors"
   
https://bugs.launchpad.net/bugs/1850744/+attachment/5301638/+files/amdgpu-resume-errors-dmesg.gz

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

Title:
  amdgpu_device_ip_resume_phase2 errors

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

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

[Bug 1850173] Re: HDMI output selected when it isn't plugged in

[Kai Groner]

** Description changed:

  Pulseaudio has started preferring the "HDMI / Displayport" sink instead
  of the USB audio device I have speakers connected to.  I'm pretty sure
  this behavior change coincided with upgrading from Ubuntu 19.04 to
  19.10.
  
  I've tried using set-default-sink in default.pa, but it doesn't seem to
  have any effect.
  
  The "Set as fallback" buttons in pavucontrol seem to fix it, but I have
- to repeat this after suspend/resume.
+ to repeat this sometimes.  I'm not sure what the pattern is.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 11:15:07 2019
  InstallationDate: Installed on 2019-06-18 (132 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
-  TERM=tmux-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=tmux-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833

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

Title:
  HDMI output selected when it isn't plugged in

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

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

[Bug 1850173] [NEW] HDMI output selected when it isn't plugged in

[Kai Groner]

Public bug reported:

Pulseaudio has started preferring the "HDMI / Displayport" sink instead
of the USB audio device I have speakers connected to.  I'm pretty sure
this behavior change coincided with upgrading from Ubuntu 19.04 to
19.10.

I've tried using set-default-sink in default.pa, but it doesn't seem to
have any effect.

The "Set as fallback" buttons in pavucontrol seem to fix it, but I have
to repeat this after suspend/resume.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 28 11:15:07 2019
InstallationDate: Installed on 2019-06-18 (132 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.60
dmi.board.name: B450M Steel Legend
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833

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


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

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

Title:
  HDMI output selected when it isn't plugged in

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

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

[Bug 1849415] [NEW] Magnifier stuck on wayland

[Kai Groner]

Public bug reported:

I tried to use the gnome magnifier after updating to 19.10 today.  After
enabling zoom from the control panel, I could no longer send mouse input
anywhere other than the desktop.  This made it impossible to turn zoom
off using the mouse and it doesn't seem to be possible to turn off using
keyboard navigation either.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 00:20:13 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (127 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)

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


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

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

Title:
  Magnifier stuck on wayland

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

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

[Bug 1827428] Re: Mouse cursor left frozen copy of itself

[Kai Groner]

I am experiencing this after upgrading to 19.10 and enabling fractional
scaling on wayland.  The extra cursor appears at 125%/150% scaling and
disappears at 100% scaling.

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

Title:
  Mouse cursor left frozen copy of itself

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

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

[Bug 972852] Re: X server hangs when connecting or disconnecting external monitor and input devices

[Kai Groner]

I've been keeping a log of what order I connect and disconnect devices
to this laptop and whether it causes the server to hang.

Disconnecting the video, then the inputs, quickly seems to cause the
server to hang.  When I pause before disconnecting the inputs or if I
disconnect the inputs first the X server did not hang.

I haven't done this many times, so it could still be a coincidence.

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

Title:
  X server hangs when connecting or disconnecting external monitor and
  input devices

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

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

[Bug 972852] [NEW] X server hangs when connecting or disconnecting external monitor and input devices

[Kai Groner]

Public bug reported:

The logs from this report are from a disconnect, but a similar symptom
occurs when connecting sometimes.  I will try to confirm this next time
it happens.

Keyboard hangs, but magic sysrq works.

I'm pretty sure this started when I upgraded to the 12.04 beta.

Possibly the same as #970049.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
Date: Tue Apr  3 16:42:00 2012
DistUpgraded: 2012-03-02 12:20:20,666 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
MachineType: ASUSTeK Computer Inc. UL30A
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic 
root=UUID=e997edc0-622f-4e23-8d7c-59e71847af11 ro acpi_backlight=vendor 
acpi_osi=\!Windows 2009\ crashkernel=384M-2G:64M,2G-:128M quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to precise on 2012-03-02 (32 days ago)
dmi.bios.date: 12/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL30A
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.:bvr212:bd12/28/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL30A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.7.2-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug precise regression ubuntu

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

Title:
  X server hangs when connecting or disconnecting external monitor and
  input devices

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

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

[Bug 972852] Re: X server hangs when connecting or disconnecting external monitor and input devices

[Kai Groner]

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

Title:
  X server hangs when connecting or disconnecting external monitor and
  input devices

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

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

[Bug 959803] [NEW] Desktop switcher does not hide when keybindings are changed from Ctrl+Alt+Arrow to Meta+[hjkl]

[Kai Groner]

Public bug reported:

Background:
These key bindings worked fine in 12.04beta1 from March 2nd until I updated on 
March 13th.  Before March 2nd I was using gnome-shell, without compiz.

Steps:
1. Run unity --reset --replace
2. In keyboard control panel (or in the CCSM Desktop Wall page), change 
bindings for move to desktop {left,right,up,down} from 
Ctrl+Alt+{Left,Right,Up,Down} to Meta+{h,l,k,j}.
3. After switching desktops using the new keybindings, observe that the 
switcher stays open until I press Escape or I press and release Ctrl+Alt.

Other thoughts:
- I didn't have this problem last time I used Gnome 2 with compiz (about a year 
ago).
- Meta+{Left,Right,Up,Down} have other bindings so I avoided testing these, I 
just tested Meta+Up and had the same problem.


: kai@cactron log; ack-grep 'status installed compiz-plugins-main-default' dpkg*
dpkg.log.1
25574:2012-03-02 11:50:33 status installed compiz-plugins-main-default 
1:0.9.7.0~bzr19-0ubuntu5
49619:2012-03-13 10:14:35 status installed compiz-plugins-main-default 
1:0.9.7.0~bzr19-0ubuntu6

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: compiz-plugins-main-default 1:0.9.7.0~bzr19-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 19 15:58:03 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: compiz-plugins-main
UpgradeStatus: Upgraded to precise on 2012-03-02 (17 days ago)

** Affects: compiz-plugins-main (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

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

Title:
  Desktop switcher does not hide when keybindings are changed from
  Ctrl+Alt+Arrow to Meta+[hjkl]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/959803/+subscriptions

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

[Bug 959803] Re: Desktop switcher does not hide when keybindings are changed from Ctrl+Alt+Arrow to Meta+[hjkl]

[Kai Groner]

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

Title:
  Desktop switcher does not hide when keybindings are changed from
  Ctrl+Alt+Arrow to Meta+[hjkl]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/959803/+subscriptions

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

[Bug 947591] [NEW] init ran out of file descriptors, spinning while trying to start a broken service

[Kai Groner]

Public bug reported:

After updating to 12.04 beta1, mysql service was broken.

I noticed my fan turn on a while after running sudo service mysql status
(never completed).

:; sudo strace -f -p 1
Process 1 attached - interrupt to quit
pipe([1022, 1023])  = 0
open(/dev/ptmx, O_RDWR|O_NOCTTY)  = -1 EMFILE (Too many open files)
close(1022) = 0
close(1023) = 0
pipe([1022, 1023])  = 0
open(/dev/ptmx, O_RDWR|O_NOCTTY)  = -1 EMFILE (Too many open files)
close(1022) = 0
close(1023) = 0
pipe([1022, 1023])  = 0
.
.
.
^C

:; sudo ls -lv /proc/1/fd | grep -c /var/log/upstart/mysql.log
1005

I guess this is probably the same as #940290

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: upstart 1.4-0ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Mon Mar  5 17:59:16 2012
EcryptfsInUse: Yes
ExecutablePath: /sbin/init
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: upstart
UpgradeStatus: Upgraded to precise on 2012-03-02 (3 days ago)

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


** Tags: amd64 apport-bug precise

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

Title:
  init ran out of file descriptors, spinning while trying to start a
  broken service

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

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

[Bug 947591] Re: init ran out of file descriptors, spinning while trying to start a broken service

[Kai Groner]

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

Title:
  init ran out of file descriptors, spinning while trying to start a
  broken service

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

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

[Bug 890343] Re: Cheese crashes on start (BadDrawable)

[Kai Groner]

Thanks for the hint, D.  Since filing this bug, I have rebooted my
machine and cheese is no longer crashing.

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

Title:
  Cheese crashes on start (BadDrawable)

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

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

[Bug 890343] [NEW] Cheese crashes on start (BadDrawable)

[Kai Groner]

Public bug reported:

I'm including a backtrace.   I didn't find a -dbg package for cheese
itself, so I don't know if this will be useful.


1) If the problem is reproducible?
Yes

  - If so, what specific steps should we take to recreate this bug? Be as 
detailed as possible.
# Run cheese
:; cheese

2) What you expected to happen?
Cheese would start and  wait for user input

3) What happened instead?
Cheese window appears, past images appear in a strip on the right edge of the 
window.  Then cheese window disappears, cheese reports baddrawable error and 
exits.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cheese 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Nov 14 12:16:56 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
MachineType: ASUSTeK Computer Inc. UL30A
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 cheese3.2.0-0ubuntu2
 cheese-common 3.2.0-0ubuntu2
SourcePackage: cheese
UpgradeStatus: Upgraded to oneiric on 2011-10-06 (39 days ago)
dmi.bios.date: 12/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL30A
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr212:bd12/28/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL30A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-bug oneiric

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

Title:
  Cheese crashes on start (BadDrawable)

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

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

[Bug 890343] Re: Cheese crashes on start (BadDrawable)

[Kai Groner]

** Attachment added: gdb-cheese.txt
   
https://bugs.launchpad.net/bugs/890343/+attachment/2596764/+files/gdb-cheese.txt

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

Title:
  Cheese crashes on start (BadDrawable)

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

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

[Bug 640018] Re: empathy throws untrusted certificate warning on google chat services using google apps (non-google domains)

[Kai Groner]

I have this problem as well.  This is with a jabber account configured
to use the server talk.google.com.

-- 
empathy throws untrusted certificate warning on google chat services using 
google apps (non-google domains)
https://bugs.launchpad.net/bugs/640018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 522438] [NEW] makedumpfile won't dump 2.6.31 kernels

[Kai Groner]

Public bug reported:

Binary package hint: makedumpfile

Description:Ubuntu 9.10
Release:9.10

makedumpfile:
  Installed: 1.3.3-0ubuntu4
  Candidate: 1.3.3-0ubuntu4
  Version table:
 *** 1.3.3-0ubuntu4 0
500 http://us.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status

linux-image-generic:
  Installed: 2.6.31.19.32
  Candidate: 2.6.31.19.32
  Version table:
 *** 2.6.31.19.32 0
500 http://us.archive.ubuntu.com karmic-updates/main Packages
500 http://security.ubuntu.com karmic-security/main Packages
100 /var/lib/dpkg/status
 2.6.31.14.27 0
500 http://us.archive.ubuntu.com karmic/main Packages

: k...@cactron makedumpfile-1.3.3; uname -a
Linux cactron 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 2010 
x86_64 GNU/Linux

What I expected to happen:
makedumpfile complete without error

What happened instead:
makedumpfile ends early with the error The kernel version is not supported

It appears that the patch debian/patches/02-Add_x86_64_linux-2.6.31.patch
does not update the #define LATEST_VERSION in makedumpfile.h which still refers 
to 2.6.29.  

Changing this allows makedumpfile to complete without error.

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

-- 
makedumpfile won't dump 2.6.31 kernels
https://bugs.launchpad.net/bugs/522438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 522438] Re: makedumpfile won't dump 2.6.31 kernels

[Kai Groner]

** Patch added: Update LATEST_VERSION #define in makedumpfile.h
   http://launchpadlibrarian.net/39251750/makedumpfile-LATEST_VERSION.patch

-- 
makedumpfile won't dump 2.6.31 kernels
https://bugs.launchpad.net/bugs/522438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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