[Bug 2047711] Re: console error after upgrade to ubuntu 22.04
Hi Sebastien, sorry missed your info request. I actually saw this warning today: ``` Jun 18 16:34:55 cerberus thunderbird.desktop[9414]: console.error: " tried to scroll to a row that doesn't exist: 4294967295" ``` I don't see user visible consequences though. ** Changed in: thunderbird (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047711 Title: console error after upgrade to ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2047711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists
Just saw this on some field units that are iOT type devices and sometimes get shutdown non-cleanly. We run apt-update on startup and we noticed one machine would not update and had no knowledge of any packages in one of the repos in the sources.list. We noticed the Packages file has 0 size, and no amount of apt update or apt-cache clean could fix it besides deleting/removing the corrupt file. Deleting it resolved the issue: ``` $ ls -lat /var/lib/apt/lists/ total 71252 drwx-- 2 _apt root 4096 Apr 23 16:18 partial drwxr-xr-x 5 root root 4096 Apr 23 15:40 .. drwxr-xr-x 4 root root 4096 Apr 22 21:13 . -rw-r--r-- 1 root root 4342 Apr 22 20:12 [redacted-package-server]-experimental_dists_focal_InRelease -rw-r--r-- 1 root root0 Apr 22 20:12 [redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages -rw-r--r-- 1 root root 4362 Jan 27 2023 [redacted-package-server]-ubuntu-experimental_dists_focal_InRelease ``` Note the 0 file size on the `[redacted-package- server]-experimental_dists_focal_main_binary-amd64_Packages` file. During this time, it would not Get any new information from the package server. Even with updates pushed to the package server. After removing the file, it does a `Get` and now can see all the packages again: $ sudo mv /var/lib/apt/lists/[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages $ sudo apt update Hit:1 [redacted-server]-experimental focal InRelease Hit:2 [redacted-server]-ubuntu-experimental focal InRelease Get:3 [redacted-server]-experimental focal/main amd64 Packages [3524 kB] Fetched 3524 kB in 6s (571 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 27 packages can be upgraded. Run 'apt list --upgradable' to see them. ``` Server software is aptly. apt version is `apt 2.0.6 (amd64)` Happy to track this down and submit a patch for checking the file size of 0, or the algorithm as suggested above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809174 Title: apt doesn't detect file corruption in /var/lib/apt/lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1809174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967037] [NEW] gnome-calculator crash during session login (misclassified?)
Public bug reported: Hi maintainers, It is likely this report is misclassified, but I haven't been able to trace it back to the real source. When I log into a gnome session, I see the following warning in the system log: Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.ControlCenter.SearchProvider' requeste> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Nautilus' requested by ':1.37' (uid=10> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Calculator.SearchProvider' requested b> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Calendar' requested by ':1.37' (uid=10> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Characters.BackgroundService' requeste> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.seahorse.Application' requested by ':1> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-ter> Mar 29 21:54:01 thinkpad3 systemd[1465]: Created slice apps.slice. Mar 29 21:54:01 thinkpad3 systemd[1465]: Created slice apps-org.gnome.Terminal.slice. Mar 29 21:54:01 thinkpad3 systemd[1465]: Starting GNOME Terminal Server... Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.seahorse.Application' Mar 29 21:54:01 thinkpad3 dbus-daemon[776]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.t> Mar 29 21:54:01 thinkpad3 systemd[1]: Starting Time & Date Service... Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Characters.BackgroundService' Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Terminal' Mar 29 21:54:01 thinkpad3 systemd[1465]: Started GNOME Terminal Server. Mar 29 21:54:01 thinkpad3 dbus-daemon[776]: [system] Successfully activated service 'org.freedesktop.timedate1' Mar 29 21:54:01 thinkpad3 systemd[1]: Started Time & Date Service. Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Calendar' Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Calculator.SearchProvider' Mar 29 21:54:01 thinkpad3 gnome-calculato[2141]: search-provider.vala:140: Failed to spawn Calculator: Child process killed by signal 9 I'm having trouble tracing what is going on here, other than there appears to be a segfault related to gnome-calculator. The following appears relevant: /usr/share/gnome-shell/search-providers/org.gnome.Calculator-search-provider.ini This may be related to https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1795399 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calculator 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 21:57:31 2022 InstallationDate: Installed on 2018-12-01 (1214 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: Upgraded to focal on 2021-12-14 (105 days ago) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967037 Title: gnome-calculator crash during session login (misclassified?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1967037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
Got hit by this, flooded with cron emails, thanks. For others affected who land here, I've found that the proper fix for the issue is: ``` apt purge snapd apt-mark hold snapd ``` Good riddance. Dear, Canonical, no one wants snapd, and it is pushing a large majority of your userbase away. Would love to keep using Ubuntu, but your decisions around snapd (such as discovering security updates aren't being applied at all to Firefox, thanks again for that) are making the Ubuntu ecosystem unusable, particularly for long time users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958022] Re: fish integration broken in focal
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 Got hit by this, flooded with cron emails, thanks. For others affected who land here, I've found that the proper fix for the issue is: ``` apt purge snapd apt-mark hold snapd ``` Good riddance. Dear, Canonical, no one wants snapd, and it is pushing a large majority of your userbase away. Would love to keep using Ubuntu, but your decisions around snapd (such as discovering security updates aren't being applied at all to Firefox, thanks again for that) are making the Ubuntu ecosystem unusable, particularly for long time users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958022 Title: fish integration broken in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] Re: firefox crashes often
I do still get pretty regular crashes. I will have to check with extensions disabled. Disabling adblocking is pretty painful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940900] Re: Grub failed boot detection - invalid enviroment block
Same issue here. Was a machine that I had not touched for several months. Booted it and after updating, got this error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940900 Title: Grub failed boot detection - invalid enviroment block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956977] [NEW] ubuntu dock causes gnome-shell keysym warnings
Public bug reported: Hi devs, I was disabling gnome-shell extensions to try to narrow down a different problem and discovered this one. The log snippet below appears from time to time in my logs, but I've never known where it comes from. I had disabled Ubuntu Dock and most other extensions. I didn't like it off and turned it back on while following the log and saw another instance of this. I verified that on my system, activating Dock causes gnome-shell to print these warnings: Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). It may be a gnome-shell bug, but this seems like the starting place to report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 11:16:41 2022 InstallationDate: Installed on 2020-05-29 (590 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-11-04 (432 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-06-21T20:18:54.448530 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956977 Title: ubuntu dock causes gnome-shell keysym warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1956977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956714] [NEW] gui took long time to return from blank screen
Public bug reported: I ignored my system for a while, long enough for the screensaver to blank the screen. When I tried to get it to awake ( I don't need to log back in), it seemed to be semihung, showing pretty black screen, but a mouse cursor visible. It did not respond to hitting keys. I tried switching back and forth between VT1 and VT2 to get it to come back to life. Eventually it came back on its own, but it took too long. Here's a chunk of log from the time this happened. There are on the order of 2000 of the "maximum number of pending replies" messages that you see at the end of this log snippet. Jan 06 23:52:41 cerberus gsd-power[2252]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: Error 02ff: PTP I/O Error Jan 06 23:52:51 cerberus gnome-shell[2987]: [System monitor] applet enabling done Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gsd-power[3176]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > ... Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus gnome-shell[2987]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: The maximum> Jan 06 23:52:52 cerberus gnome-shell[2987]: Error checking authorization for action id org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.DBus.Error.Limit> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 00:00:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (587 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
[Bug 1955500] Re: firefox crashes often
2 more crashes today -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] [NEW] firefox crashes often
Public bug reported: Recently (since ~2021-12-15) firefox has been crashing a lot, often daily. There's no obvious pattern that I can see. Most recent crash logs: Dec 21 12:37:51 cerberus firefox.desktop[755990]: Sandbox: Unexpected EOF, op 0 flags 0200 path /proc/755990/cgroup Dec 21 12:37:51 cerberus firefox.desktop[756121]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755809]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755990]: Exiting due to channel error. ... Dec 21 12:37:51 cerberus firefox.desktop[745228]: [GFX1-]: Receive IPC close with reason=AbnormalShutdown Dec 21 12:37:51 cerberus firefox.desktop[744870]: Exiting due to channel error. ... Previous crash: Dec 20 12:56:53 cerberus kernel: traps: GeckoMain[613052] trap int3 ip:7fa351cc1295 sp:7fff6ba7eea0 error:0 in libglib-2.> Dec 20 12:56:53 cerberus gnome-shell[722119]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[722386]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[615970]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[717612]: Exiting due to channel error. ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 95.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jlquinn2641 F pulseaudio /dev/snd/controlC0: jlquinn2641 F pulseaudio /dev/snd/controlC2: jlquinn2641 F pulseaudio /dev/snd/controlC1: jlquinn2641 F pulseaudio BuildID: 20211215221728 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 13:17:24 2021 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:363 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 2020-05-29 (570 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.10 metric 100 MostRecentCrashID: bp-6d5c31fc-1b33-459b-bfab-9d3b20211216 ProcEnviron: TERM=xterm-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 Profile1Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=54.0/20170612122310 (Out of date) Profile0 (Default) - LastVersion=95.0.1/20211215221728 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-11-04 (412 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 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.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro mtime.conffile..etc.apport.crashdb.conf: 2021-06-21T20:18:54.448530 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] Re: firefox crashes often
I have as extensions: Feedbro GNOME Shell Integration (courtesy of ubuntu) Stylus uBlock Origin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803856] Re: Access to Samsung fails in file manager
Ubuntu 20.04 fails to access an older Samsung phone properly for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803856 Title: Access to Samsung fails in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1803856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901829] Re: thunderbird fails to open, xml parse error
I see this issue in 20.04 but it interfere with starting thunderbird. I'm using en-US. jlquinn@cerberus:~/Videos/summits$ lsb_release -a; uname -a; apt-cache policy thunderbird No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Linux cerberus 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux thunderbird: Installed: 1:78.11.0+build1-0ubuntu0.20.04.2 Candidate: 1:78.11.0+build1-0ubuntu0.20.04.2 Version table: *** 1:78.11.0+build1-0ubuntu0.20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:68.7.0+build1-0ubuntu2 500 500 http://us.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/1901829 Title: thunderbird fails to open, xml parse error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] Re: Braswell video locks up under gnome-shell
Hi, there's a crash report mentioned on this page: https://errors.ubuntu.com/user/241a8d330b8560e5d29b49b2d8df1a9340834364d1e9930a70caae16e29bf446d33032781384b132361e219d11002feddb39eb224ef4a8725b7f4651d988de57 but I don't have permission to follow the link to the actual crash report. I originally tried using this box with X11, but I could lock up the screen regularly. So I tried running under wayland, which seems to be more stable for this machine. The above crash report is from kodi- wayland. When I look at what's running, I see Xwayland, which I assume is wayland running with the x layer on top? When I log in after a restart (too many of them), I have gnome on wayland chosen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: Braswell video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] Re: Braswell video locks up under gnome-shell
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+attachment/5511461/+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/1935901 Title: Braswell video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] Re: video locks up under gnome-shell
It seems to happen intermittently but when it does, I typically can't get back control at the console. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] [NEW] video locks up under gnome-shell
Public bug reported: I get a blank screen with a mouse cursor. Cursor doesn't respond to mouse inputs. System doesn't respond to keyboard inputs. I can still ssh in from another machine. I see the following in the journal: Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-442ms> Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer event3 debounce short: scheduled expiry is in the past (> Jul 13 01:57:07 jenks gnome-shell[1403]: Failed to post KMS update: drmModePageFlip on CRTC 93 failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 13 02:06:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-29 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935760] Re: video locks up under kodi
Video lockup is reproducible. This may not be a kernel issue. Switching to wayland display server doesn't lock up this way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935760 Title: video locks up under kodi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1935760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935760] [NEW] video locks up under kodi
Public bug reported: jlquinn@jenks:~/bug$ lsb_release -d Description:Ubuntu 20.04.2 LTS jlquinn@jenks:~/bug$ apt-cache policy linux-image-5.8.0-59-generic linux-image-5.8.0-59-generic: Installed: 5.8.0-59.66~20.04.1 Candidate: 5.8.0-59.66~20.04.1 Version table: *** 5.8.0-59.66~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status I have an Intel NUC 5PPYB hooked up to an AOC 4K monitor. I tried to run kodi for the first time, added a video, and tried to play it. The console locked up hard. Mouse doesn't move and I cannot get to a virtual terminal either. I can still ssh into the system. Eventually I see a kworker task blocked for a long time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 10 22:14:20 2021 InstallationDate: Installed on 2021-06-29 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "journalctl log" https://bugs.launchpad.net/bugs/1935760/+attachment/5510331/+files/jlog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935760 Title: video locks up under kodi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1935760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932979] Re: blank screen with cursor after login
Neither step 1 nor step 2 gave me anything unfortunately. I've commented out the the problem types field, so perhaps I'll get more useful data eventually. This is a rare occurrence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932979 Title: blank screen with cursor after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1932979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
The last comment of this bug report appears to describe what's happening: https://bugzilla.redhat.com/show_bug.cgi?id=1641541 There are 2 Xorg processes running for some reason. One I'm logged into, and the other is on another VT. The one I'm logged into has my user id. The other one has uid gdm. The Xorg with uid gdm has a child gsd-color process with the pid that matches the errant log message. There is also a gsd-color process with my uid that is a child of systemd --user. I assume this happens when I logged in. So this seems to be a bad byproduct of there being 2 Xorgs and gdms running. Why does this happen anyway? ** Bug watch added: Red Hat Bugzilla #1641541 https://bugzilla.redhat.com/show_bug.cgi?id=1641541 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932979] [NEW] blank screen with cursor after login
Public bug reported: Ubuntu 20.04 on amd64. I came back to the machine after it was idle long enough for the screen to go blank. I can see the cursor move with the mouse, but nothing else. This is VT2. VT1 shows a login screen. I can get to console VTs as well and did so to file the report. I see the following in the system log that may be related: Jun 18 18:29:54 cerberus gnome-shell[4694]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568871 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568998 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3569045 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: [System monitor] applet disable Jun 18 18:29:54 cerberus gnome-shell[4694]: g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 18 19:33:55 2021 DistUpgraded: 2020-11-04 10:03:47,100 DEBUG running doUpdate() (showErrors=True) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2020-05-29 (385 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Supermicro X10DAi ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=linux XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=/dev/mapper/ubuntu--vg-root ro amdgpu.dc=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-04 (226 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 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.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932979 Title: blank screen with cursor after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1932979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928358] [NEW] gnome-shell spamming the log
Public bug reported:
I don't know what happened, but I just sat down at my machine to find it
sluggish. Digging further, I find that gnome-shell is spamming the
system log with these messages:
May 13 12:06:42 cerberus gnome-shell[3120]: JS ERROR: TypeError: null has no
properties
_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
actionMoveWorkspace@resource:///org/gnome/shell/ui/windowManager.js:2170:23
_showWorkspaceSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2144:18
Restarting the shell with:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting…")'
restored it to sanity.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 13 12:07:00 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-29 (348 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-11-04 (190 days ago)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928358
Title:
gnome-shell spamming the log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928358/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913662] [NEW] gnome-shell dock dvd icons remain after hard eject
Public bug reported: jlquinn@cerberus:~/Videos$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 jlquinn@cerberus:~/Videos$ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages I put in a video DVD and use it. After finishing, I eject by pressing the physical drive button. The DVD icon in the gnome-shell dock remains. I cannot then make the icon go away by right-clicking and using the eject menu entry. If I instead rightclick the DVD icon to eject while the disc is still in the drive, the icon disappears as expected. I've tried reinserting the DVD and then using the icon menu eject option, but that doesn't remove the icon either. So far, restarting the whole gui is the only way to clean up these disconnected icons that I've found. ** Affects: gnome-shell (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/1913662 Title: gnome-shell dock dvd icons remain after hard eject To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879414] Re: Cannot log into a server I logged into previously with error "Your home directory path contains non-ASCII characters. Aborting session startup."
This issue was helpful. I also had a full /tmp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879414 Title: Cannot log into a server I logged into previously with error "Your home directory path contains non-ASCII characters. Aborting session startup." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x2goclient/+bug/1879414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911242] [NEW] session.py syntax warning
Public bug reported: I just installed pyhoca-gui, which installed python3-x2go. During the install, I see the following warning: Setting up python3-x2go (0.6.1.3-2) ... /usr/lib/python3/dist-packages/x2go/session.py:2020: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self._SUPPORTED_SOUND and self.terminal_session.params.snd_system is not 'none': Setting up pyhoca-gui (0.6.1.1-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-x2go 0.6.1.3-2 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 15:15:00 2021 InstallationDate: Installed on 2020-05-29 (227 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-x2go UpgradeStatus: Upgraded to focal on 2020-11-04 (69 days ago) ** Affects: python-x2go (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911242 Title: session.py syntax warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-x2go/+bug/1911242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911206] [NEW] Update info on reloading sysctl with systemd
Public bug reported: /etc/sysctl.d/README says that after making changes, you should run "service procps start" to activate the changes. Since systemd is now the default init system, please update the README files to also say you can activate changes with: systemctl restart systemd-sysctl ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: procps 2:3.3.16-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 09:23:57 2021 InstallationDate: Installed on 2020-05-29 (227 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: procps UpgradeStatus: Upgraded to focal on 2020-11-04 (68 days ago) modified.conffile..etc.sysctl.d.10-link-restrictions.conf: [deleted] ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911206 Title: Update info on reloading sysctl with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1911206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909955] [NEW] missing helper program pylzma not available
Public bug reported: After indexing, I see the following at the end of the log: :3:index/fsindexer.cpp:247::FsIndexer::index missing helper program(s): python3:pylzma (application/x-7z-compressed) However, pylzma does not seem to be available in Ubuntu. I don't know if this counts as a bug against recoll or not, but it would be good to include info on how to address this missing helper program. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: recoll 1.26.3-1build1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 22:42:29 2021 InstallationDate: Installed on 2020-05-29 (219 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: recoll UpgradeStatus: Upgraded to focal on 2020-11-04 (60 days ago) ** Affects: recoll (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909955 Title: missing helper program pylzma not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/recoll/+bug/1909955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909407] [NEW] Mistake in Alt-Tab operation
Public bug reported: I've uncovered what I think is a bug in the way that gnome-shell implements Alt-Tab support. First, my understanding is that the current version of Alt-Tab is only supposed to select between windows in the current virtual desktop. I accidentally uncovered this as follows. I moved a Firefox window (I have many open) from virtual desktop 2 to virtual desktop 1 using C-S-A-Up. Then, when I use Alt-Tab, I see 3 firefox windows as part of the 7 choices displayed. If I click on one of the other 2 firefox windows, it takes me down to virtual desktop 2. The window list for Alt-Tab in virtual desktop 2 doesn't include the firefox window in virtual desktop 1, so immediately doing Alt-Tab after the mistake doesn't reverse things. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 27 11:33:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (211 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-11-04 (53 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909407 Title: Mistake in Alt-Tab operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908435] Re: Ubuntu Installation Failure With Formatted Disk
I was able to get ubuntu installed successfully using ZFS by doing an offline minimal installation both `Download Updates` and `Third Party Software` disabled. The installation was successful and Ubuntu booted ok. I have now switched my production desktop over to the new installation. I suspect the majority of the failures were due to `Third Party Software` option (https://bugs.launchpad.net/ubuntu- cdimage/+bug/1871268). As its possible that I got a false positive on the bug, I suggest that you close this ticket until I get time to do some playing around to see if drive formatting is actually an issue with current builds of ubiquity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908435 Title: Ubuntu Installation Failure With Formatted Disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1908435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908435] Re: Ubuntu Installation Failure With Formatted Disk
Update, my last 'successful' install failed because it looks like gparted did not completely nuke the drive and the installation did not boot up after it completed. At boot, I got the Busybox screen with no clear errors. When I pulled up the drive in Ubuntu live cd, the partitions were very odd sda1, sda2, sda5, sda6, sda7 and no sda3, or sda4. I used 'disks' utility to wipe all partitions and used `df` to verify that there were no partitions left on the disk and am now trying 20.04.1 install again... This is another failure mode of Ubuntu installer not really wiping the drive before before starting install; a 'successful' installation that does not boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908435 Title: Ubuntu Installation Failure With Formatted Disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908435] [NEW] Ubuntu Installation Failure With Formatted Disk
Public bug reported: Ubuntu Installer fails when trying to install on a Drive that is previously formatted by Ubuntu installer. I know this issue has been around for a long time but is there a way that the installer can detect a formatted drive automatically and if the usecase is to wipe the drive anyway, automatically format the drive before running any code that may fail due to the existing drive formatting? I can imagine this issue can be a real roadblock for newbies as when it fails as there are virtually no hints of why it is failing. Background: Today, I was installing Ubuntu 20.04 on an new computer I used a DVD I burned back in May of this year. The installer failed and it appears to have already formatted the drive at that point. I had assumed that the DVD may have been damaged so I downloaded 20.04.1 and burned a new DVD. When I installed, it failed again before I got to the final "install" button. I did let the system send the bug report up to the server at the time (about 13:00 EST). I have seen this issue before and it was related to the drive formatting causing the installer to bail so I used Ubuntu Live and gparted to delete any data on the drive. When I re-installed, it installed successfully. During all the above installations, I used the `Wipe drive and use ZFS` option. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: drive format installer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908435 Title: Ubuntu Installation Failure With Formatted Disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877668] Re: KDESVN Context Menu issue
This issue was resolved by installing `kde-plasma-desktop` which put in all the necessary libraries to get KDE apps working much better. This installation also fixed KFind and other KDE apps that I use. Note `kde-plasma-desktop` is huge and after installing and before restarting the computer run `sudo apt update`. If you don't run this update, may brick gnome on reboot making it a very tricky to get back up and running. I made this mistake the first time I installed 20.04 by rebooting without an `apt update`. My Gnome was pooched and I had to do a revert to a ZVN snapshot, which is never ideal as the revert will not fix files under your home which were modified by kde library installation leaving gnome working but in a sad place. If this happens, you would need to hand revert files in home that were modified during kde libs install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877668 Title: KDESVN Context Menu issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesvn/+bug/1877668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819543] Re: Does not exit correctly, have to "kill -9
It affects me in 20.04 LTS. I didn't have it in 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819543 Title: Does not exit correctly, have to "kill -9 To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1819543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Hi, I have just tested kernel 5.4.0-53-generic (Ubuntu kernel) on the same hardware and the bug is still present. When will the fix be pushed out to the current ubuntu kernels? Quinn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903081] [NEW] Unable to update colorhug firmware
Public bug reported: I have a colorhug version 1 device with firmware 1.2.1. From reading, it appears that fwupd supports the colorhug firmware: jlquinn@cerberus:~$ fwupdmgr get-devices X10DAi │ ├─ColorHug: │ Device ID: 9bacaf023cb4913d27ee9dea10752fde615b2f1f │ Summary: An open source display colorimeter │ Current version: 0.2 │ Vendor: Hughski Ltd. (USB:0x273F) │ Install Duration:8 seconds │ GUIDs: 40338ceb-b966-4eae-adae-9c32edfcc484 │ afdcc391-6c33-5914-b4d2-b4dd71fe9c5a │ 4841a9e4-e5c8-5107-a83e-d6c6d9c21248 │ 6bc5ff27-d631-5660-9991-6d24954c6f90 │ Device Flags:• Updatable │ • Supported on remote server │ • Device can recover flash failures I've read that there is a firmware 1.2.6 that I need for this device. I ran fwupdmgr refresh, then downloaded and examined the xml file by hand. There appears to be an entry for 1.2.6 (and versions back to 1.2.2): com.hughski.ColorHug.firmware ColorHug Device Update Firmware for the Hughski ColorHug Colorimeter Updating the firmware on your ColorHug device improves performance and adds new features. 40338ceb-b966-4eae-adae-9c32edfcc484 http://www.hughski.com/ CC0-1.0 GPL-2.0+ Hughski Limited X-Device triplet com.hughski.colorhug https://fwupd.org/downloads/aa1b94b36c91929fbf75551b8a376d7292f8c51c-hughski-colorhug-1.2.6.cab 570a4259af0c7670f3883e84d2f4e6ff7de572c2 257aadbaa3a7af6ae62607b8709626487118a7ca5f5a1f535a0dea78e166a7d8 111784ffadfd5dd43f05655b266b5142230195b6 fce1847b0599bb19cd913d02268f15107691a79221ce16822b4c931cd1bda2c5 This release fixes prevents the firmware returning an error when the remote SHA1 hash was never sent. https://github.com/hughski/colorhug1-firmware/releases/tag/1.2.6 16384 10687 However, when I try to update, I get the following: root@cerberus:~# fwupdmgr update • ColorHug has the latest available firmware version so for some reason, fwupdmgr believes that this firmware doesn't apply. On the surface this seems like a bug, based on other things I've read around the net. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fwupd 1.3.11-1~focal1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 11:23:01 2020 InstallationDate: Installed on 2020-05-29 (159 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fwupd UpgradeStatus: Upgraded to focal on 2020-11-04 (1 days ago) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903081 Title: Unable to update colorhug firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1903081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 996916] Re: postgresql packages in the removal blacklist making it hard to upgrade
Or, if you're committed to posting here, post your logs, please. On Wed, Sep 30, 2020 at 10:10 AM Quinn Balazs wrote: > I'm trying to say that if you're still experiencing this issue and you > have updated past Oneiric (11.10) this is NOT the same bug. postgres was in > the removal blacklist due to Bug 871893. Fix released for 871893 in Oneiric > Updates. Therefore if it is in the removal blacklist again, it is a > different issue altogether, Do not keep adding reports to an invalid bug > from 2015 that was due to something now marked Fix Released. Please for the > love of dog, report a new bug, with new logs. > > On Wed, Sep 30, 2020 at 10:04 AM Flaburgan <996...@bugs.launchpad.net> > wrote: > >> No need to remove all postgres packages, removing postgis should be >> enough. >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1246020). >> https://bugs.launchpad.net/bugs/996916 >> >> Title: >> postgresql packages in the removal blacklist making it hard to upgrade >> >> Status in update-manager package in Ubuntu: >> Invalid >> >> Bug description: >> I have got this pop-up error message while updating from Ubuntu >> version 11.04 to 11.10: >> >> Could not calculate the upgrade >> >> An unresolvable problem occurred while calculating the upgrade: >> The package 'postgresql-plperl-8.4' is marked for removal but it is in >> the removal blacklist. >> >>This can be caused by: >>* Upgrading to a pre-release version of Ubuntu >>* Running the current pre-release version of Ubuntu >>* Unofficial software packages not provided by Ubuntu >> >> If none of this applies, then please report this bug using the command >> 'ubuntu-bug update-manager' in a terminal. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 11.04 >> Package: update-manager 1:0.150.5.2 >> ProcVersionSignature: Ubuntu 2.6.38-15.59-generic 2.6.38.8 >> Uname: Linux 2.6.38-15-generic x86_64 >> NonfreeKernelModules: nvidia >> Architecture: amd64 >> Date: Wed May 9 15:17:02 2012 >> GConfNonDefault: >>/apps/update-manager/check_new_release_ignore=oneiric >>/apps/update-manager/first_run=false >>/apps/update-manager/window_size=(600,600) >> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 >> (20101007) >> PackageArchitecture: all >> ProcEnviron: >>LANGUAGE=en_US:en >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> SourcePackage: update-manager >> UpgradeStatus: Upgraded to natty on 2012-05-09 (0 days ago) >> VarLogDistupgradeApttermlog: >> >> VarLogDistupgradeHistorylog: >> >> VarLogDistupgradeSystemstatetargz: >> >> VarLogDistupgradeTermlog: >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/996916/+subscriptions >> > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996916 Title: postgresql packages in the removal blacklist making it hard to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/996916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996916] Re: postgresql packages in the removal blacklist making it hard to upgrade
Fix released in Oneiric. This particular bug has been resolved. Future issues are not due to bug #871893, thus should be reported separately n -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996916 Title: postgresql packages in the removal blacklist making it hard to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/996916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 996916] Re: postgresql packages in the removal blacklist making it hard to upgrade
I'm trying to say that if you're still experiencing this issue and you have updated past Oneiric (11.10) this is NOT the same bug. postgres was in the removal blacklist due to Bug 871893. Fix released for 871893 in Oneiric Updates. Therefore if it is in the removal blacklist again, it is a different issue altogether, Do not keep adding reports to an invalid bug from 2015 that was due to something now marked Fix Released. Please for the love of dog, report a new bug, with new logs. On Wed, Sep 30, 2020 at 10:04 AM Flaburgan <996...@bugs.launchpad.net> wrote: > No need to remove all postgres packages, removing postgis should be > enough. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1246020). > https://bugs.launchpad.net/bugs/996916 > > Title: > postgresql packages in the removal blacklist making it hard to upgrade > > Status in update-manager package in Ubuntu: > Invalid > > Bug description: > I have got this pop-up error message while updating from Ubuntu > version 11.04 to 11.10: > > Could not calculate the upgrade > > An unresolvable problem occurred while calculating the upgrade: > The package 'postgresql-plperl-8.4' is marked for removal but it is in > the removal blacklist. > >This can be caused by: >* Upgrading to a pre-release version of Ubuntu >* Running the current pre-release version of Ubuntu >* Unofficial software packages not provided by Ubuntu > > If none of this applies, then please report this bug using the command > 'ubuntu-bug update-manager' in a terminal. > > ProblemType: Bug > DistroRelease: Ubuntu 11.04 > Package: update-manager 1:0.150.5.2 > ProcVersionSignature: Ubuntu 2.6.38-15.59-generic 2.6.38.8 > Uname: Linux 2.6.38-15-generic x86_64 > NonfreeKernelModules: nvidia > Architecture: amd64 > Date: Wed May 9 15:17:02 2012 > GConfNonDefault: >/apps/update-manager/check_new_release_ignore=oneiric >/apps/update-manager/first_run=false >/apps/update-manager/window_size=(600,600) > InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 > (20101007) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=en_US:en >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: update-manager > UpgradeStatus: Upgraded to natty on 2012-05-09 (0 days ago) > VarLogDistupgradeApttermlog: > > VarLogDistupgradeHistorylog: > > VarLogDistupgradeSystemstatetargz: > > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/996916/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996916 Title: postgresql packages in the removal blacklist making it hard to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/996916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897399] Re: ubuntu 20.4 keeps on bugging for me
Please attach system logs to this bug report. ** Package changed: ubiquity (Ubuntu) => grub-installer (Ubuntu) ** Changed in: grub-installer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897399 Title: ubuntu 20.4 keeps on bugging for me To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1897399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Ok, I finally got commit b292b50b0efcc7095d8bf15505fba6909bb35dce to build successfully. Result is also success! Normal reboot works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Hi, Since I wasn't able to build this commit, I used the deb's provided in Comment #36 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/comments/36) Result is success! Soft rebooting works normally with this build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Can't seem to compile this commit. Here are the commands I used: sudo apt-get -y install libncurses-dev flex bison openssl libssl-dev dkms libelf-dev libudev-dev libpci-dev libiberty-dev autoconf sudo apt-get -y build-dep linux git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git checkout -f b292b50b0efcc7095d8bf15505fba6909bb35dce cp /boot/config-$(uname -r) .config yes '' | make oldconfig make -j 17 deb-pkg LOCALVERSION=-custom Build fails with the following messages: --- dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1) dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i.git -b . subprocess returned exit status 1 make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 1 make: *** [Makefile:1495: deb-pkg] Error 2 --- Build environment: Ubuntu 20.04, 48GB RAM, 16 CPU's. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Finally got 5.8-rc4 compiled with patch applied. Posting dmesg results. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+attachment/5401384/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
I haven't been able to compile 5.8-rc4 for some reason but have had success with 5.4.0-44 - I applied the patch to 5.4.0-44 and attached the dmesg file here. Hope this helps. ** Attachment added: "kernel messages from serial patched kernel 5.4.0-44" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+attachment/5401335/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891211] [NEW] segfault when closing connection
Public bug reported: I log into a machine then reboot the machine when I'm logged in. While the machine is no longer accessible, I then press the Terminate button for the session, and the x2goclient dies with a segfault. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x2goclient 4.1.1.1-2ubuntu0.18.04.1 Uname: Linux 5.7.6-050706-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 12:04:19 2020 InstallationDate: Installed on 2020-05-29 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: x2goclient UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: x2goclient (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891211 Title: segfault when closing connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x2goclient/+bug/1891211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890156] [NEW] package cbindgen (not installed) failed to install/upgrade: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1
Public bug reported: Attempting to install cbindgen ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cbindgen (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: cbindgen:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 3 09:22:48 2020 DpkgTerminalLog: Preparing to unpack .../cbindgen_0.12.1-1build1_amd64.deb ... Unpacking cbindgen (0.12.1-1build1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/cbindgen_0.12.1-1build1_amd64.deb (--unpack): trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 ErrorMessage: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 InstallationDate: Installed on 2020-05-28 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/local/bin/python3.8, Python 3.8.3, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: rust-cbindgen Title: package cbindgen (not installed) failed to install/upgrade: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rust-cbindgen (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890156 Title: package cbindgen (not installed) failed to install/upgrade: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-cbindgen/+bug/1890156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Currently on vacation - will be back in 3 weeks. Is the patch is for 5.8-rc4 or for 4.15.0-99? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
I have now installed, booted, and tested the reboot with kernel 5.8-rc4 - no change - bug still persists. I have attached dmesg log for this kernel. ** Attachment added: "dmesg-5.8-rc4.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+attachment/5390979/+files/dmesg-5.8-rc4.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390944/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390945/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390949/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390948/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390941/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390947/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390942/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390946/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390943/+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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
apport information ** Tags added: apport-collected ** Description changed: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 9 09:55 seq + crw-rw 1 root audio 116, 33 Jul 9 09:55 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=/dev/mapper/system-swap + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard + Bus 001 Device 002: ID 8087:07e6 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: To be filled by O.E.M. To be filled by O.E.M. + Package: linux (not installed) + PciMultimedia: + + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" + ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-99-generic N/A + linux-backports-modules-4.15.0-99-generic N/A + linux-firmware 1.173.18 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-99-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip disk plugdev sudo + _MarkForUpload: True + dmi.bios.date: 05/05/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5.6.5 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Aptio CRB + dmi.board.vendor: AMI Corporation + dmi.board.version: To be filled by O.E.M. + 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.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.: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.version: To be filled by O.E.M. + dmi.sys.vendor: To be filled by O.E.M. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1886827/+attachment/5390940/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+attachment/5390939/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Seeing as the console reports systemd-shutdown, I decided to debugging that. So far: systemctl reboot -ff has no effect - the system still hangs with the affected kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
I have now tried all combinations of "reboot=" as advised by: https://wiki.ubuntu.com/BIOSandUbuntu with no effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
SysRq-b is unaffected by this kernel bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
Kernel bisection was done following the procedures listed here: https://wiki.ubuntu.com/Kernel/KernelBisection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "git-bisect.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390798/+files/git-bisect.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] [NEW] Machine hangs when doing a normal reboot
Public bug reported: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn ** Affects: 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/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "console.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390794/+files/console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "dmidecode.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390797/+files/dmidecode.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390792/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "console.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390793/+files/console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390791/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "cpuinfo.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390796/+files/cpuinfo.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "git-bisect-log.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390799/+files/git-bisect-log.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886827] Re: Machine hangs when doing a normal reboot
** Attachment added: "policy.log" https://bugs.launchpad.net/ubuntu/+bug/1886827/+attachment/5390795/+files/policy.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885583] [NEW] denyhosts blocks localhost
Public bug reported: I got onto my machine this morning and found networking broken. I traced it to the fact that denyhosts added 127.0.0.1 to the deny list. I couldn't find any events in the log that look like ssh attempts coming from localhost, but it still got added. I would consider this an important bug because networking failed in a non-obvious way, which could cause data loss for network connections. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: denyhosts 2.10-2 Uname: Linux 5.7.1-050701-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 10:56:03 2020 InstallationDate: Installed on 2020-05-29 (30 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: denyhosts UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.denyhosts.conf: [inaccessible: [Errno 13] Permission denied: '/etc/denyhosts.conf'] ** Affects: denyhosts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885583 Title: denyhosts blocks localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/denyhosts/+bug/1885583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870014] Re: task blocked too long
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881423] Re: error channel closing too late to send/recv
I wasn't able to match the messages to an associated behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1881423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881390] Re: amdgpu.dc=0 required for gui display
apport information ** Tags added: apport-collected ** Description changed: I have Ubuntu 18.04 on my system. When I boot, I get a black screen once mode switching happens. Rescue mode (aka nomodeswitch) would bring me to a gui screen correctly. I tried backing off to X.org from Wayland, but that didn't help. I eventually found an obscure post suggesting adding amdgpu.dc=0 to the command line. With this added, I have the GUI I expect. Originally the system worked as expected, but something changed which required this setting. The graphics card is an AMD RX480. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04 5.3.0.53.110 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 30 02:26:41 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-05-29 (11 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: bionic + Uname: Linux 5.7.1-050701-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881390/+attachment/5382645/+files/ProcCpuinfoMinimal.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881390 Title: amdgpu.dc=0 required for gui display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881390] Re: amdgpu.dc=0 required for gui display
I followed the instructions to change to confirmed. But the kernel from proposed, as well as the mainline one I have up at the moment, work correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881390 Title: amdgpu.dc=0 required for gui display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870014] Re: task blocked too long
** Attachment added: "Log showing kernel failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+attachment/5382115/+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/1870014 Title: task blocked too long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870014] Re: task blocked too long
** Attachment added: "Taken after I plug in the device" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+attachment/5382114/+files/lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870014] Re: task blocked too long
I tested with the latest kernel image I saw, which appears to be 5.7.1: ii linux-image-unsigned-5.7.1-050701-generi 5.7.1-050701.202006071230 amd64 Linux kernel image for version 5.7.1 on 64 bit x86 SMP jlquinn@cerberus:~$ uname -a Linux cerberus 5.7.1-050701-generic #202006071230 SMP Sun Jun 7 12:32:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux When I first plug in the device, /dev/video0 appears as expected. I then start vlc and attempt to input from capture device /dev/video0 and audio hw3,0. After several seconds, I get kernel warnings and /dev/video0 disappears. I've attached the segment of kernel log from the time I plug in the capture device to the time things blow up. I've also attached lsusb -v taken after I plug in the device and before I attempt to use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881390] Re: amdgpu.dc=0 required for gui display
Yes, I have my gui back without amdgpu.dc=0. Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881390 Title: amdgpu.dc=0 required for gui display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882490] [NEW] gsd-media-keys unable to get default source or sink
Public bug reported: jlquinn@cerberus:~$ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 jlquinn@cerberus:~$ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.28.1-0ubuntu1.3 Candidate: 3.28.1-0ubuntu1.3 Version table: *** 3.28.1-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages In my log, I see the following messages: Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default sink Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default source This seems like something is amiss. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 01:03:33 2020 InstallationDate: Installed on 2020-05-29 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882490 Title: gsd-media-keys unable to get default source or sink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1882490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882487] Re: USB headset stops working
This is the log from when I plug the device from the working port into the misbehaving port: Jun 08 00:27:24 cerberus kernel: debugfs: Directory '26' with parent 'devices' already present! Jun 08 00:27:24 cerberus kernel: usb 3-11.3: new full-speed USB device number 65 using xhci_hcd Jun 08 00:27:24 cerberus sshd[47656]: Failed password for root from 139.199.115.133 port 38408 ssh2 Jun 08 00:27:25 cerberus sshd[47656]: Received disconnect from 139.199.115.133 port 38408:11: Bye Bye [preauth] Jun 08 00:27:25 cerberus sshd[47656]: Disconnected from authenticating user root 139.199.115.133 port 38408 [preauth] Jun 08 00:27:25 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:25 cerberus kernel: debugfs: Directory '05' with parent 'devices' already present! Jun 08 00:27:25 cerberus kernel: usb 3-11.3: device descriptor read/all, error -32 Jun 08 00:27:25 cerberus kernel: debugfs: Directory '16' with parent 'devices' already present! Jun 08 00:27:25 cerberus kernel: usb 3-11.3: new full-speed USB device number 66 using xhci_hcd Jun 08 00:27:25 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:25 cerberus kernel: debugfs: Directory '29' with parent 'devices' already present! Jun 08 00:27:25 cerberus sshd[47658]: Failed password for root from 213.183.101.89 port 40696 ssh2 Jun 08 00:27:26 cerberus sshd[47658]: Received disconnect from 213.183.101.89 port 40696:11: Bye Bye [preauth] Jun 08 00:27:26 cerberus sshd[47658]: Disconnected from authenticating user root 213.183.101.89 port 40696 [preauth] Jun 08 00:27:26 cerberus kernel: usb 3-11.3: device descriptor read/all, error -32 Jun 08 00:27:26 cerberus kernel: usb 3-11-port3: attempt power cycle Jun 08 00:27:26 cerberus kernel: debugfs: Directory '22' with parent 'devices' already present! Jun 08 00:27:26 cerberus kernel: usb 3-11.3: new full-speed USB device number 67 using xhci_hcd Jun 08 00:27:26 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:26 cerberus kernel: debugfs: Directory '02' with parent 'devices' already present! Jun 08 00:27:26 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: debugfs: Directory '08' with parent 'devices' already present! Jun 08 00:27:27 cerberus kernel: usb 3-11.3: new full-speed USB device number 68 using xhci_hcd Jun 08 00:27:27 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:27 cerberus kernel: debugfs: Directory '15' with parent 'devices' already present! Jun 08 00:27:27 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: usb 3-11-port3: unable to enumerate USB device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882487 Title: USB headset stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1882487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882487] [NEW] USB headset stops working
Public bug reported: root@cerberus:/var/log# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 jlquinn@cerberus:~$ apt-cache policy linux-generic-hwe-18.04 linux-generic-hwe-18.04: Installed: 5.3.0.53.110 Candidate: 5.3.0.53.110 I have a Logitech usb headset that stopped working for unknown reasons. It had been working fine, then seems deactivated. There is a light on the volume control that is no longer lit up. Surprisingly, if I did lsusb, the light briefly lights up, and shuts off. It is plugged into a usb hub on my monitor which had been working fine for a couple months. I plugged it into a different usb on the computer itself, and the headset starts working as expected. Plugging it back into the monitor hub, I see the light on the device flash a couple times, then shut off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.3.0.53.110 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 00:16:57 2020 InstallationDate: Installed on 2020-05-29 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882487 Title: USB headset stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1882487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882487] Re: USB headset stops working
Here's what seems like the relevant portion of the kernel log where the device log appears ok, and where it starts to go bad. Jun 6 17:44:12 cerberus kernel: [620023.619292] hid-generic 0003:046D:0A8F.0045: input,hidraw7: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-:00:14. 0-11.3/input3 Jun 6 19:24:43 cerberus kernel: [626054.614288] usb 3-11: USB disconnect, device number 126 Jun 6 19:24:43 cerberus kernel: [626054.614292] usb 3-11.3: USB disconnect, device number 127 Jun 6 19:24:45 cerberus kernel: [626056.528798] usb 4-4: Disable of device-initiated U1 failed. Jun 6 19:24:45 cerberus kernel: [626056.532295] usb 4-4: Disable of device-initiated U2 failed. Jun 6 19:24:45 cerberus kernel: [626056.657614] usb 4-4: reset SuperSpeed Gen 1 USB device number 15 using xhci_hcd Jun 6 19:24:45 cerberus kernel: [626057.041278] usb 3-11: new high-speed USB device number 5 using xhci_hcd Jun 6 19:24:45 cerberus kernel: [626057.063343] usb 3-11: New USB device found, idVendor=2109, idProduct=2811, bcdDevice=90.90 Jun 6 19:24:45 cerberus kernel: [626057.063348] usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 6 19:24:45 cerberus kernel: [626057.063350] usb 3-11: Product: USB2.0 Hub Jun 6 19:24:45 cerberus kernel: [626057.063352] usb 3-11: Manufacturer: VIA Labs, Inc. Jun 6 19:24:45 cerberus kernel: [626057.064033] hub 3-11:1.0: USB hub found Jun 6 19:24:45 cerberus kernel: [626057.064165] hub 3-11:1.0: 4 ports detected Jun 6 19:24:46 cerberus kernel: [626057.369269] usb 3-11.3: new full-speed USB device number 7 using xhci_hcd Jun 6 19:24:47 cerberus kernel: [626058.789112] usb 3-11.3: New USB device found, idVendor=046d, idProduct=0a8f, bcdDevice= 0.12 Jun 6 19:24:47 cerberus kernel: [626058.789116] usb 3-11.3: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Jun 6 19:24:47 cerberus kernel: [626058.789119] usb 3-11.3: Product: Logitech USB Headset Jun 6 19:24:47 cerberus kernel: [626058.789121] usb 3-11.3: Manufacturer: Logitech USB Headset Jun 6 19:24:48 cerberus kernel: [626059.379000] input: Logitech USB Headset Logitech USB Headset as /devices/pci:00/:00:14.0/usb3/3-11/3-11.3/3-11.3:1.3/0003:046D:0A8F.004 6/input/input94 Jun 6 19:24:48 cerberus kernel: [626059.437566] hid-generic 0003:046D:0A8F.0046: input,hidraw7: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-:00:14. 0-11.3/input3 Jun 6 19:38:00 cerberus kernel: [626852.308189] usb 3-11: USB disconnect, device number 5 Jun 6 19:38:00 cerberus kernel: [626852.308193] usb 3-11.3: USB disconnect, device number 7 Jun 6 19:38:04 cerberus kernel: [626855.724635] usb 4-4: Disable of device-initiated U1 failed. Jun 6 19:38:04 cerberus kernel: [626855.728132] usb 4-4: Disable of device-initiated U2 failed. Jun 6 19:38:04 cerberus kernel: [626855.853383] usb 4-4: reset SuperSpeed Gen 1 USB device number 15 using xhci_hcd Jun 6 19:38:04 cerberus kernel: [626856.241122] usb 3-11: new high-speed USB device number 8 using xhci_hcd Jun 6 19:38:04 cerberus kernel: [626856.263123] usb 3-11: New USB device found, idVendor=2109, idProduct=2811, bcdDevice=90.90 Jun 6 19:38:04 cerberus kernel: [626856.263126] usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 6 19:38:04 cerberus kernel: [626856.263129] usb 3-11: Product: USB2.0 Hub Jun 6 19:38:04 cerberus kernel: [626856.263131] usb 3-11: Manufacturer: VIA Labs, Inc. Jun 6 19:38:04 cerberus kernel: [626856.263786] hub 3-11:1.0: USB hub found Jun 6 19:38:04 cerberus kernel: [626856.263916] hub 3-11:1.0: 4 ports detected Jun 6 19:38:05 cerberus kernel: [626856.569115] usb 3-11.3: new full-speed USB device number 10 using xhci_hcd Jun 6 19:38:06 cerberus kernel: [626857.981374] usb 3-11.3: New USB device found, idVendor=046d, idProduct=0a8f, bcdDevice= 0.12 Jun 6 19:38:06 cerberus kernel: [626857.981378] usb 3-11.3: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Jun 6 19:38:06 cerberus kernel: [626857.981381] usb 3-11.3: Product: Logitech USB Headset Jun 6 19:38:06 cerberus kernel: [626857.981383] usb 3-11.3: Manufacturer: Logitech USB Headset Jun 6 19:38:07 cerberus kernel: [626858.567678] input: Logitech USB Headset Logitech USB Headset as /devices/pci:00/:00:14.0/usb3/3-11/3-11.3/3-11.3:1.3/0003:046D:0A8F.0047/input/input95 Jun 6 19:38:06 cerberus kernel: [626857.981383] usb 3-11.3: Manufacturer: Logitech USB Headset Jun 6 19:38:07 cerberus kernel: [626858.567678] input: Logitech USB Headset Logitech USB Headset as /devices/pci:00/:00:14.0/usb3/3-11/3-11.3/3-11.3:1.3/0003:046D:0A8F.004 7/input/input95 Jun 6 19:38:07 cerberus kernel: [626858.625328] hid-generic 0003:046D:0A8F.0047: input,hidraw7: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-:00:14. 0-11.3/input3 Jun 6 19:38:08 cerberus kernel: [626859.692643] usb 3-11: USB
[Bug 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881669 Title: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1881669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
Hi Sebastien. It seems to be reproducible, but I don't know how to do it. I see several events in my log today. One clue I see is that there is a gnome-software message as well as the gnome-shell traces. I then ran gnome-software. I see that it last checked at 6:16. And in the log, there's one of these traces at 6:16. Unfortunately, starting gnome-software and asking it to refresh didn't create another stack trace. Jun 3 18:16:35 cerberus gnome-shell[3318]: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2cf3450), has been already finalized. Impossible to set any property to it. Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: == Stack trace for context 0x5582a28894b0 == Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #0 0x7ffc718e6f10 I resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f70f00b5de0 @ 87) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #1 0x5582a2c5ae38 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93 (0x7f6ee00c2340 @ 58) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #2 0x7ffc718e7af0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #3 0x7ffc718e7bb0 b self-hosted:916 (0x7f70f00f12b8 @ 367) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #4 0x7ffc718e7ca0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5adb0 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190 (0x7f6ee00adf78 @ 22) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #6 0x7ffc718e88f0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #7 0x5582a2c5ad08 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:219 (0x7f6ee00ad5e8 @ 225) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #8 0x7ffc718e94d0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #9 0x5582a2c5ac90 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/extension.js:61 (0x7f6ee0084780 @ 37) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #10 0x5582a2c5abd0 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7f70b40592b8 @ 441) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #11 0x5582a2c5ab50 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7f70b4059d58 @ 13) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #12 0x7ffc718ea1d0 b self-hosted:251 (0x7f70f00c4ab0 @ 223) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #13 0x5582a2c5aad0 i resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7f70b4059cd0 @ 64) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #14 0x5582a2c5aa50 i resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7f70b4059de0 @ 87) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #15 0x7ffc718eb6d0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #16 0x7ffc718ebee0 b resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7f709c0704d8 @ 254) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #17 0x7ffc718ecbc0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #18 0x5582a2c5a910 i resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7f709c0702b8 @ 40) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #19 0x7ffc718ed7a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus gnome-shell[3318]: Object .Gjs_AppIndicatorIconActor__1 (0x5582a47a7040), has been already finalized. Impossible to set any property to it. Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #20 0x5582a2c5a868 i resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7f709c053a28 @ 188) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #21 0x7ffc718ee380 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #22 0x5582a2c5a7e0 i resource:///org/gnome/shell/ui/screenShield.js:902 (0x7f709c051b38 @ 18) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #23 0x7ffc718eef60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #24 0x7ffc718ef700 b self-hosted:916 (0x7f70f00f12b8 @ 367) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #25 0x7ffc718ef7f0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386) Jun 3 18:16:35 cerberus org.gnome.Shell.desktop[3318]: #26 0x5582a2c5a760 i resource:///org/gnome/shell/ui/lightbox.js:186
[Bug 1881344] Re: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
apport information ** Tags added: apport-collected bionic ** Description changed: May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 786]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 - It seems the pomodoro extension package is either out of date or too new - for the version of gnome-shell in Ubuntu 18.04. + It seems the pomodoro extension package is either out of date or too new for the version of gnome-shell in Ubuntu 18.04. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-05-29 (3 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + Package: gnome-shell-pomodoro 0.13.4-2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 + Tags: bionic + Uname: Linux 5.3.0-53-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1881344/+attachment/5379777/+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/1881344 Title: JS WARNING: [/usr/share/gnome- shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-pomodoro/+bug/1881344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881344] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881344/+attachment/5379778/+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/1881344 Title: JS WARNING: [/usr/share/gnome- shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-pomodoro/+bug/1881344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881669] [NEW] Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
Public bug reported: jlquinn@cerberus:~$ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 jlquinn@cerberus:~/Videos$ apt-cache policy gnome-shell-extension-appindicator gnome-shell-extension-appindicator: Installed: 18.04.1 Candidate: 18.04.1 Version table: *** 18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status This may be related to bug 1879016, but my stack trace is smaller and different. I enabled the appindicator extension, and see the following my logs: Jun 01 17:24:15 cerberus gnome-shell[3318]: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it. Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: == Stack trace for context 0x5582a28894b0 == Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #0 0x7ffc718eda00 b resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f70f00b5de0 @ 87) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #1 0x5582a2c5a930 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93 (0x7f6ee00 Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #2 0x7ffc718ee5e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #3 0x7ffc718eed80 b self-hosted:916 (0x7f70f00f12b8 @ 367) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #4 0x7ffc718eee70 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5a8a8 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190 (0x7f6ee00adf78 Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #6 0x7ffc718efac0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #7 0x5582a2c5a800 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:176 (0x7f6e Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #8 0x7ffc718f06a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #9 0x5582a2c5a760 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:170 (0x7f6e Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #10 0x7ffc718f1290 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #11 0x7ffc718f1a50 b self-hosted:918 (0x7f70f00f12b8 @ 394) Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While reading menu layout: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1. Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy is null DBusClient<._beginRequestProperties@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:247:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-appindicator 18.04.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 17:41:57 2020 Dependencies: InstallationDate: Installed on 2020-05-29 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881669 Title: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1881669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822416] Re: resolve: do not hit CNAME or DNAME entry in NODATA cache
I have the same problem in 237-3ubuntu10.41 amd64 May 30 12:55:59 cerberus systemd-resolved[1595]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822416 Title: resolve: do not hit CNAME or DNAME entry in NODATA cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1822416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881423] [NEW] error channel closing too late to send/recv
Public bug reported: I saw the following in my logs on a fresh install of 18.04.4: May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 12:57:41 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881390] Re: amdgpu.dc=0 required for gui display
amdgpu.dc=0 gets me a gui with X.org. With Xwayland, I still get a blank screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881390 Title: amdgpu.dc=0 required for gui display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1881390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881390] [NEW] amdgpu.dc=0 required for gui display
Public bug reported: I have Ubuntu 18.04 on my system. When I boot, I get a black screen once mode switching happens. Rescue mode (aka nomodeswitch) would bring me to a gui screen correctly. I tried backing off to X.org from Wayland, but that didn't help. I eventually found an obscure post suggesting adding amdgpu.dc=0 to the command line. With this added, I have the GUI I expect. Originally the system worked as expected, but something changed which required this setting. The graphics card is an AMD RX480. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04 5.3.0.53.110 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 30 02:26:41 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881390 Title: amdgpu.dc=0 required for gui display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1881390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881344] [NEW] JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
Public bug reported: May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 786]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 It seems the pomodoro extension package is either out of date or too new for the version of gnome-shell in Ubuntu 18.04. ** 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/1881344 Title: JS WARNING: [/usr/share/gnome- shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855968] Re: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1090]: unreachable code after return statement
For Ubuntu 18.04, it's at line 1028, but is the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855968 Title: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu- d...@ubuntu.com/appIcons.js 1090]: unreachable code after return statement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1855968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881330] [NEW] gnome-terminal fails to start
Public bug reported: My system has something strange going on. I'm unable to start gnome- terminal. In journalctl, I see the following cryptic message: May 29 13:08:38 cerberus org.gnome.Shell.desktop[3960]: # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Could not connect: Connection refused If I then try to start it from an existing terminal, I get: jlquinn@cerberus:~/work/lt-language-pairs$ gnome-terminal # Error constructing proxy for :1.89:/org/gnome/Terminal/Factory0: Could not connect: Connection refused # Failed to use specified server: Could not connect: Connection refused # Falling back to default server. # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Could not connect: Connection refused This is a somewhat important issue because it will force me to reboot my machine (or at least GUI) due to the inability to create new terminals. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 29 13:03:43 2020 InstallationDate: Installed on 2016-05-30 (1459 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-09-17 (620 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1881330 Title: gnome-terminal fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1881330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
