[Bug 1975597] [NEW] Python files are still packaged for Python 3.8
Public bug reported: The Python files in the indicator-keyboard package are being installed in /usr/lib/python3.8 instead of /usr/lib/python3.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: indicator-keyboard 0.0.0+19.10.20190716-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 24 10:08:37 2022 InstallationDate: Installed on 2019-08-16 (1011 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to jammy on 2021-11-09 (196 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975597 Title: Python files are still packaged for Python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1975597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer
Yes, the print job in question works when I print it to the driverless printer. I would not say that it is therefore reasonable to declare that this issue is resolved, but *shrug* whatever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968722 Title: File fails to print when rendered with CUPS, prints fine when fed directly to printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969280] [NEW] gnome-terminal not obeying light vs. dark theme
Public bug reported: In a brand new account created just to test this issue, gnome-terminal has a dark background and light fonts even when the GNOME them is set to light. I am not sure if this is a new issue in Jammy, but it sure is frustrating that when I switch to light mode every app switches to a white background except gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 14:44:00 2022 InstallationDate: Installed on 2019-08-16 (973 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2021-11-09 (158 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969280 Title: gnome-terminal not obeying light vs. dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1969280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer
>Do you have cups-filter 1.28.15 installed Yes, and I rebooted after installing it just to make sure. Problem persists. >Or did you try the option "pdftops-renderer=gs" as described there and which you confirmed as fixing that bug? I _also_ have this setting in my printers.conf. So clearly this bug is different from that one. > Generally, driverless printing is more reliable than PostScript printing. PostScript interpreters in printers often have bugs. These two statements seem to be contradictory. If driverless printing is more reliable, that would seem to imply that files sent directly to the printer print more reliably than files sent through the CUPS filters, which would seem to imply that it is the filters, not the printer, that have bugs. ** Changed in: cups (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/1968722 Title: File fails to print when rendered with CUPS, prints fine when fed directly to printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer
Here's my printers.conf, since it doesn't look like ubuntu-bug attached it, and there's no sensitive information in it. ** Attachment added: "printers.conf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+attachment/5579950/+files/printers.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968722 Title: File fails to print when rendered with CUPS, prints fine when fed directly to printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968722] [NEW] File fails to print when rendered with CUPS, prints fine when fed directly to printer
Public bug reported:
I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI socket://m551dn.kamens.brookline.ma.us:9100"
in printers.conf) and the same physical printer configured driverless in
CUPS with a different name ("MakeModel HP LaserJet 500 color M551,
driverless, cups-filters 1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.
The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when sent
through the CUPS Postscript renderer, i.e., the former printer. In
particular, the file stops printing after four pages and then the
printer spits out this error page:
ERROR:
typecheck
OFFENDING-COMMAND:
known
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
device for HP_LaserJet_500_color_M551_1637DA:
implicitclass://HP_LaserJet_500_color_M551_1637DA/
device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd',
'/etc/cups/ppd/duplex.ppd',
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2:
grep: /etc/cups/ppd/simplex.ppd: Permission denied
grep: /etc/cups/ppd/duplex.ppd: Permission denied
grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Attachment added: "comics.pdf"
https://bugs.launchpad.net/bugs/1968722/+attachment/5579931/+files/comics.pdf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968722
Title:
File fails to print when rendered with CUPS, prints fine when fed
directly to printer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
The file prints with pdftops-renderer=gs. I can fix this for me personally, but is there any way to adjust the default CUPS configuration for the type of printer that I have to make this setting the default for others with the same printer, so they don't also run into this issue? ** Changed in: cups (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/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1967816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967816] [NEW] PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
Public bug reported: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "/var/log/cups/error_log excerpt" https://bugs.launchpad.net/bugs/1967816/+attachment/5577050/+files/error_log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1967816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason
I just installed another round of new Jammy updates on the laptop where gnome-extensions-app was crashing, and it's not crashing anymore. I don't know if it's the installing of the updates that fixed this or if it's an intermittent issue and just not happening at the moment. Hard to tell since no crash report was generated. :shrug: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967637 Title: gnome-extensions-app crashing on startup, not producing reportable crash for some reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963755] Re: extensions get turned off spontaneously when I log out and log back in
I can no longer reproduce this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963755 Title: extensions get turned off spontaneously when I log out and log back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1963755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason
I have two machines with Jammy on them and this is happening reliably on one but not the other. On the one where it's happening, it happens even immediately after I've updated all out-of-date packages and rebooted the machine. I don't know why it's not generating a crash report. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967637 Title: gnome-extensions-app crashing on startup, not producing reportable crash for some reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967637] [NEW] gnome-extensions-app crashing on startup, not producing reportable crash for some reason
Public bug reported: $ /usr/bin/gnome-extensions-app Segmentation fault (core dumped) There's nothing in /var/crash. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:01:32 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (960 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-09 (144 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967637 Title: gnome-extensions-app crashing on startup, not producing reportable crash for some reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966614] Re: I am getting calendar notification pop-ups even though I've turned them off
Yes they are Reminders from the Calendar app. For a Google account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966614 Title: I am getting calendar notification pop-ups even though I've turned them off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1966614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966614] [NEW] I am getting calendar notification pop-ups even though I've turned them off
Public bug reported: I keep getting calendar notification pop-ups -- at the top middle of my screen -- even though in the calendar settings in Notifications I have "Notification Popups" turned off. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.2-3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 20:20:15 2022 InstallationDate: Installed on 2019-08-16 (954 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to jammy on 2021-11-09 (138 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966614 Title: I am getting calendar notification pop-ups even though I've turned them off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1966614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964976] [NEW] gnome-remote-desktop is not listening on port 5900, no sign of why
Public bug reported: With all current packages from jammy, gnome-remote-desktop is not listening on port 5900. Lsof doesn't show it listening on that port, attempting to connect to that port yields connection refused), with no indication of why. There are no errors matching the pattern "gnome- remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome- remote-desktop" doesn't show any errors, "systemctl status --user gnome- remote-desktop" shows that it is running, my settings show that screen sharing is enabled, this used to work, and I haven't changed anything since it did. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42~rc-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 10:49:08 2022 InstallationDate: Installed on 2019-01-02 (1167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-remote-desktop UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964976 Title: gnome-remote-desktop is not listening on port 5900, no sign of why To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
Works for me as well. (Does Ubuntu have some sort of karma system similar to Fedora's, i.e., is there another web site somewhere we should be going to to indicate that the fix works for us?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963756] Re: Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on
*** This bug is a duplicate of bug 1963755 *** https://bugs.launchpad.net/bugs/1963755 I don't think these two issues are duplicates, which is why I filed them separately. This issue occurs even when the other one, which is intermittent, does not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963756 Title: Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1963756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963766] Re: Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8
All of these problems seem to go away when I download GnuCash 4.9 from gnucash.org, build it from source after `apt-get build-dep gnucash` with an install prefix of /opt/gnucash, install it in /opt/gnucash, and run it from there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963766 Title: Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1963766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963766] [NEW] Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8
Public bug reported: After installing the recent upgrade from gnucash 4.4 to 4.8 and opening gnucash, it doesn't start with my previously opened gnucash file opened as it usually does, but that's the only start of the problems. When I open the file explicitly, it only shows two account tabs even though there were previously a lot more tabs than that open, it doesn't show the main Accounts tab, and there appears to be no way to get it to open the main Accounts tab. My previously configured preferences are all gone. Changing preferences does not seem to have any effect, and when I change preferences and then close and reopen the preferences window my changes are gone. Removing ~/.config/gnucash has no effect on any of this. Removing ~/.cache/gnucash has no effect on any of this. Removing ~/.gnucash has no effect on any of this. Removing ~/.local/share/gnucash at least brings back the Accounts tab but all the other problems enumerated above remain. Basically, things are completely screwed up and I can't find any way to fix it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnucash 1:4.8-1build2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 5 15:05:29 2022 InstallationDate: Installed on 2019-01-02 (1158 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnucash UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago) ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1963766 Title: Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1963766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963755] [NEW] extensions get turned off spontaneously when I log out and log back in
Public bug reported: 1. Have some GNOME shell extensions installed (I have Allow Locked Remote Desktop, Mpris Indicator Button, Removable Drive Menu, User Themes, plus built-ins Desktop Icons NG, Ubuntu AppIndicators, Ubuntu Dock). 2. Open the Extensions app. 3. Confirm that the switch at the top controlling all extensions is on. 4. Log out. 5. Log back in. 6. Observe that your extensions are not running. 7. Open the Extensions app. 8. Observe that the switch at the top is now off, even though you never turned it off. This is reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 5 13:02:55 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1158 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1963755 Title: extensions get turned off spontaneously when I log out and log back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963756] [NEW] Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on
Public bug reported: 1. Observe icons from Desktop Icons NG on desktop. 2. Log out. 3. Log back in. 4. Observe that desktop icons are gone. 5. Open Extensions app. 6. Observe that the Desktop Icons NG extension is enabled. 7. Turn it off and turn it back on. 8. Observe that the missing desktop icons now appear. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-desktop-icons-ng 39-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 5 13:06:10 2022 InstallationDate: Installed on 2019-01-02 (1158 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1963756 Title: Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1963756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957010] [NEW] After upgrade to FlameShot 11, complains about bad config file and system tray icon is missing
Public bug reported: After upgrade from Flameshot 0.10 to Flameshot 11, upon login I get a pop-up notification telling me that there's an error in the Flameshot configuration file and it's reverting to the default settings, but then there's no Flameshot icon in the system tray and seemingly no way to bring up the Flameshot UI -- opening the Flameshot app doesn't do anything. Note however that there's a flameshot process running in the background. I had to trash ~/.config/flameshot and then kill and restart Flameshot to get it back. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flameshot 11.0~rc1+ds1-2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 16:26:23 2022 InstallationDate: Installed on 2019-08-16 (878 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: flameshot UpgradeStatus: Upgraded to jammy on 2021-11-09 (62 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: flameshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957010 Title: After upgrade to FlameShot 11, complains about bad config file and system tray icon is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1957010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956850] [NEW] Please upgrade to GNU mailutils 3.14 to fix incorrect time zones in Date headers of sent messages
Public bug reported: I just ran into this bug: https://savannah.gnu.org/bugs/?61239 . In particular, apticron used the mailutils version of /usr/bin/mail to send me an email message, and the Date header in the email message had a completely bogus UTC offset in it. This bug is fixed in mailutils 3.14. Please upgrades mailutils to 3.14 or at least pull the patch for this bug: http://git.savannah.gnu.org/cgit/mailutils.git/commit/libmailutils/datetime/utcoff.c?id=305b124c78459fe1d89a6ed4ebf30a955d530a4c ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mailutils 1:3.13-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 8 22:40:41 2022 InstallationDate: Installed on 2019-08-16 (876 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mailutils UpgradeStatus: Upgraded to jammy on 2021-11-09 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: mailutils Importance: Unknown Status: Unknown ** Affects: mailutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy upgrade-software-version ** Bug watch added: GNU Savannah Bug Tracker #61239 http://savannah.gnu.org/bugs/?61239 ** Also affects: mailutils via http://savannah.gnu.org/bugs/?61239 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956850 Title: Please upgrade to GNU mailutils 3.14 to fix incorrect time zones in Date headers of sent messages To manage notifications about this bug go to: https://bugs.launchpad.net/mailutils/+bug/1956850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
No longer reproducible 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/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953209] [NEW] ICS imported into GNOME calendar (Google Calendar) with UTC start and end times breaks if you edit it
Public bug reported: 1. Your local computer should be in a time zone other than UTC. 2. Save the attached sample.ics to your Desktop. 3. Double-click on it to import it into GNOME Calendar. 4. Save the imported event. Observe that it is saved at the correct time in your calendar. 5. In GNOME calendar, click on the event and click edit. 6. Expand the start and end time sections and observe that the times next to "Starts" and "Ends" are the UTC times for the event, while the times in the time pickers are the correct time in the local time zone. 7. Click the "Done" button without actually changing anything and observe that the event moves to the incorrect time, interpreting the original UTC times of the event as local times. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.1-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 3 21:28:09 2021 InstallationDate: Installed on 2019-08-16 (840 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to jammy on 2021-11-09 (24 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-calendar Importance: Unknown Status: Unknown ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "sample ICS file to demonstrate bug" https://bugs.launchpad.net/bugs/1953209/+attachment/5545308/+files/sample.ics ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #755 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/755 ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/755 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953209 Title: ICS imported into GNOME calendar (Google Calendar) with UTC start and end times breaks if you edit it To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1953209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
1) ~/.local/share/gnome-shell/extensions is empty 2) I reproduced this issue with Chromium and there is no Chromium crash in /var/crash, nor is there an error report for Chromium tied to my whoopsie ID. Since the chromium snap is provided by Canonical and this issue is reproducible with Chromium does that mean it's no longer an "Invalid" issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 It's hard to see why the retracing service marked this as a duplicate of 1751508. I'm fairly certain it is not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952619 Title: Xwayland crashed with SIGABRT in __libc_start_call_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1952619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
(Though why _Wayland_ is crashing when I'm trying to log into an _Xorg_ session and the options menu on the login screen says that I have Xorg selected remains a mystery.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
Problem still occurs with mprisindicatorbutton, batime, and allowlockedremotedesktop completely uninstalled. Can't uninstall multi- volume because neither Extensions app nor extensions.gnome.org say it's installed. Probably relevant crash: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1952619 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
I removed 'mprisindicatorbut...@jasonlg1979.github.io', 'bat...@martin.zurowietz.de', and 'allowlockedremotedesk...@kamens.us', but GNOME doesn't seem to think I have 'multi-volume@tigersoldier' installed, so I'm not sure where you got that from or what to do with it. See attached screenshot of Extensions app. I also looked on extensions.gnome.org and it also doesn't list it as an installed extension. With the other three extensions removed completely the problem still occurs even after two logout / login cycles after removing the extensions to ensure they're completely purged. Regarding the crash instructions you sent, there is in fact a Chrome crash in /var/crash that looks relevant but of course I can't report it with ubuntu-bug because Chrome is not an Ubuntu package. There are no crashes on errors.ubuntu.com for my Whoopsie ID, and I've already got the workaround from bug 994921. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
** Attachment added: "screenshot showing no multi-volume@tigersoldier" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+attachment/5544070/+files/extensions%20app.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] [NEW] Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
Public bug reported: In Jammy when I have Chrome running and I log out of a Wayland session and then log back in and restart Chrome it says it wasn't shut down correctly. I'm pretty sure in earlier releases Chrome was given the opportunity to shut down cleanly when I logged out, but :shrug: I could be remembering this incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:17:25 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 40.5-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] Re: Flameshot can't take screenshots, 22.04, wayland
Screenshots work in Xorg session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] [NEW] Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
Public bug reported: On Jammy, I log out of a Wayland session, click my name on the login screen, go down to the options menu and select Ubuntu on Xorg, enter my password, get "Oh no! Something has gone wrong. A probleme has occurred and the system can't recover. Please log out and try again. [Log Out]" I click the log out button and log in again, and I'm logged into a Wayland session. Why was I logged into a Wayland session when I selected Xorg the last time I tried to log in? This issue is intermittent I had been able to log into an Xorg session just a few minutes prior. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:10:10 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 40.5-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
I logged out immediately after logging in again as described above, then went to log in again and checked the options menu, and it correctly had "Ubuntu on Xorg" selected as my session type, but when I finished logging in I was in a Wayland session, not an Xorg session. So for some reason my selection of Xorg as my desired session is being ignored? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] [NEW] Flameshot can't take screenshots, 22.04, wayland
Public bug reported: With all current packages from Jammy, Flameshot does nothing when I click on the top bar icon and select "Take screenshot". If, after doing that, I click on the icon again and select "Quit", *then* as Flameshot is exiting it pops up a notification that says "Unable to capture screen". There's some discussion that seems relevant at https://github.com/flameshot-org/flameshot/issues/1910, but that discussion claims screenshots work in Flameshot 10.2, and that appears to be the version currently in Jammy, so I'm not sure why it's not working. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flameshot 0.10.2+ds1-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:02:58 2021 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: flameshot UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: flameshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796758] Re: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups
This is still a problem but I'm not convinced it's enough of a problem to warrant reopening the ticket. I run into this because my `systemd --user` process persists between logins because I have persistent service units running under it. For most people `systemd --user` will exit when they log out, so for most people, logging out and logging back in will indeed reset their groups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796758 Title: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215882]
The other reason this is a critical bug is because if the user does not have Thunderbird configured to save messages in Sent Mail -- which the user *shouldn't*, e.g., if the user is using Gmail, since Gmail saves outbound messages automatically, then this bug causes DATA LOSS by closing the window without saving the message ANYWHERE. Can believe this bug is still not fixed after nearly a decade. Glad to see it's about to be fixed, but as someone else pointed out in a recent comment, if this is just a matter of changing the status codes that cause Thunderbird to leave the compose window open, then maybe we should make that fix in TB78 rather than waiting until the next major release for it to be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215882 Title: Emails are silently discarded on 554 reply to STARTTLS To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1215882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule
This appears to no longer be an issue with the current versions of
systemd and udev in 21.04.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: systemd (Ubuntu Groovy)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916418
Title:
Custom properties set with ENV{WHATEVER} in parent no longer imported
with IMPORT{parent} in udev rule
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule
Please tell me specifically how to enable debug and afterward capture
the logs that you want to see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916418
Title:
Custom properties set with ENV{WHATEVER} in parent no longer imported
with IMPORT{parent} in udev rule
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917178] Re: As of today in hirsute no longer possible to use open-fprintd
>Could you give some details on your reader? It could be possible to enable it using https://gitlab.freedesktop.org/3v1n0/libfprint-tod- vfs0090 Could you give some details on (a) how I can "give some details on [my] reader" and (b) how I can "enable it using..."? >I think the issue the original poster was stating is a new dependency that does not allow us to have just the package we need for open- fprintd. Yes. Although I would love if the fprintd provided by Ubuntu supported my reader, this particular bug was about the fact that there shouldn't be dependencies in the OS packages that prevent people from being able to use open-fprintd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917178 Title: As of today in hirsute no longer possible to use open-fprintd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1917178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924915] Re: Typo in anacron log message ("ststus" should be "status")
** Bug watch added: Debian Bug tracker #987153
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987153
** Also affects: anacron (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987153
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924915
Title:
Typo in anacron log message ("ststus" should be "status")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1924915/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924915] [NEW] Typo in anacron log message ("ststus" should be "status")
Public bug reported:
Log message from anacron:
Apr 17 15:20:23 jik5 anacron[425521]: Tried to mail output of job
`cron.daily', but mailer process (/usr/sbin/sendmail) exited with ststus
75
Note "ststus".
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: anacron 2.3-30ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 09:44:49 2021
InstallationDate: Installed on 2019-08-16 (610 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: anacron
UpgradeStatus: Upgraded to hirsute on 2021-02-20 (56 days ago)
** Affects: anacron (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924915
Title:
Typo in anacron log message ("ststus" should be "status")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1924915/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917787] Re: evdi-dkms fails to build on hirsute with the latest 5.11 kernel
If you've landed here looking for how to use EVDI or DisplayLink with Hirsute, please see my blog posting about this: https://blog.kamens.us/2021/03/19/update-on-using-displaylink-with- ubuntu-21-04-hirsute-hippo/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917787 Title: evdi-dkms fails to build on hirsute with the latest 5.11 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1917787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Can you please read what other people have said before commenting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921006] Re: When NOTIFY_HOLDS=0, apticron should ignore new packages depended on by held ones
** Bug watch added: Debian Bug tracker #985795 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985795 ** Also affects: apticron (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985795 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921006 Title: When NOTIFY_HOLDS=0, apticron should ignore new packages depended on by held ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1921006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921006] [NEW] When NOTIFY_HOLDS=0, apticron should ignore new packages depended on by held ones
Public bug reported: When NOTIFY_HOLDS=0, apticron shouldn't notify about a new package that is an install candidate only because it is a dependency of the new version of a package currently being held. For example, if linux-headers-generic is held and NOTIFY_HOLDS=0, then apticron shouldn't notify about a kernel-specific headers package, i.e., linux-headers-#-generic, that the new version of linux-headers-generic depends on. Patch attached. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apticron 1.2.3+nmu1 [modified: usr/sbin/apticron] ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 23 16:36:42 2021 InstallationDate: Installed on 2019-01-02 (811 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: apticron UpgradeStatus: Upgraded to hirsute on 2021-02-21 (30 days ago) ** Affects: apticron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Patch added: "0002-When-NOTIFY_HOLDS-0-ignore-new-packages-depended-on-.patch" https://bugs.launchpad.net/bugs/1921006/+attachment/5480317/+files/0002-When-NOTIFY_HOLDS-0-ignore-new-packages-depended-on-.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921006 Title: When NOTIFY_HOLDS=0, apticron should ignore new packages depended on by held ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1921006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921000] Re: with multiarch, apticron sometimes lists packages it shouldn't when NOTIFY_HOLDS=0
** Bug watch added: Debian Bug tracker #985794 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985794 ** Also affects: apticron (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985794 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921000 Title: with multiarch, apticron sometimes lists packages it shouldn't when NOTIFY_HOLDS=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1921000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921000] [NEW] with multiarch, apticron sometimes lists packages it shouldn't when NOTIFY_HOLDS=0
Public bug reported: When using multiarch, `dpkg --get-selections` appends the system's default architecture to package names in some cases, but `apt-get -q -y -s dist-upgrade` doesn't, so the code in apticron to filter out held packages doesn't work. Here's a fix: --- /usr/sbin/apticron 2020-12-20 09:03:57.183515992 -0500 +++ apticron2021-03-23 15:40:58.054450596 -0400 @@ -129,7 +129,7 @@ # workaround to handle apt-get installing packages hold by aptitude. See #137771. APTITUDE_HOLDS=`grep "^State: 2" -B 3 /var/lib/aptitude/pkgstates 2>/dev/null |grep "^Package: .*$" |cut -d" " -f 2` -DSELECT_HOLDS=`dpkg --get-selections |grep "hold$" |cut -f1` +DSELECT_HOLDS=`dpkg --get-selections |grep "hold$" |cut -f1 |sed -e "s/:$(dpkg --print-architecture)$//"` if [ "$NOTIFY_HOLDS" = "0" ]; then # packages hold by aptitude don't go to the upgrading candidates list ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apticron 1.2.3+nmu1 [modified: usr/sbin/apticron] ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 23 15:52:39 2021 InstallationDate: Installed on 2019-01-02 (811 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: apticron UpgradeStatus: Upgraded to hirsute on 2021-02-21 (30 days ago) ** Affects: apticron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921000 Title: with multiarch, apticron sometimes lists packages it shouldn't when NOTIFY_HOLDS=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1921000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920059] Re: evdi module not building with current (5.11) Hirsute kernel
For those of you who landed here looking for how to use DisplayLink in Hirsute, I wrote up a workaround here: https://blog.kamens.us/2021/03/19 /update-on-using-displaylink-with-ubuntu-21-04-hirsute-hippo/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920059 Title: evdi module not building with current (5.11) Hirsute kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
For those of you who landed here looking for how to use DisplayLink in Hirsute, I wrote up a workaround here: https://blog.kamens.us/2021/03/19 /update-on-using-displaylink-with-ubuntu-21-04-hirsute-hippo/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is
lol PEBKAC issue. I had an sshfs session running on another computer and whenever I rebooted it was reconnecting. Sorry to trouble you. That's for telling me how to figure it out. ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920061 Title: when I go to restart it claims there is someone logged in remotely when no one is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is
It says "No inhibitors", and yet there is still no one else logged in remotely and it is still claiming that there is when I try to restart. ** Changed in: gnome-shell (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/1920061 Title: when I go to restart it claims there is someone logged in remotely when no one is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
I performed the splash -> nosplash test described above; it made no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
** Also affects: mesa (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/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
I debugged this further and discovered that one of the following updates caused evdi with kernel 5.10 to start failing as described above: 2021-03-18 21:55:45 upgrade libegl-mesa0:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:45 upgrade libgbm1:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:45 upgrade libgl1-mesa-dri:i386 20.3.4-1 21.0.0-1 2021-03-18 21:55:46 upgrade libgl1-mesa-dri:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:47 upgrade libglx-mesa0:i386 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglx-mesa0:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglapi-mesa:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglapi-mesa:i386 20.3.4-1 21.0.0-1 When I downgraded all of the listed debs to the old version indicated (20.3.4-1) and rebooted, evdi with kernel 5.10 started working again. So I guess this is a mesa bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] [NEW] Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
Public bug reported: As I indicated in a bug report I filed earlier today, https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms can no longer compile the evdi kernel module with the 5.11 kernel. So, to work around this, I need to keep using the 5.10 kernel instead. But I can't, because when I boot with the 5.10 kernel this is what shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login screen (note: I have an NVIDIA graphics card, which is why (I believe) Wayland isn't being used here): [ 857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy [ 857.957] (EE) Fatal server error: [ 857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 [ 857.957] (EE) [ 857.957] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 857.957] (EE) [ 858.144] (EE) Server terminated with error (1). Closing log file. This is probably not what you will see in the Xorg.0.log (if any) attached automatically to this bug because I've completely wiped the evdi kernel module from my system since that was the only way I could get a display manager up so I could use ubuntu-bug to submit this bug. Here's what I updated today: 2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1 2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2 2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1 2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6 2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:41 install linux-headers-5.11.0-11:all 5.11.0-11.12 2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12 2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0 2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 2:21.0.99.902-0ubuntu1 2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3 At first glance I don't understand how any of these could be causing this behavior. Potentially relevant: I had to recompile and reinstall the evdi kernel module while booted into 5.10 because when I install the 5.11 kernel dkms removed the module from 5.10 and then failed to rebuild it because the 5.11 build failed (or something I don't really understand why dkms does what it does *sigh*). I don't see how that should matter because the recompiled version of the module should have been identical, but *shrug*. As noted above, when I remove the evdi kernel modules from /lib/modules and reboot with 5.10 the problem goes away, so this does appear to be an evdi issue. In short: despite the fact that it's not clear how upgrading any of the modules listed above would cause evdi that used to work to suddenly stop working, that appears to be the case. Any advice would be appreciated because now I can't use the displays connected to my DisplayLink hub with either 5.10 or 5.11 kernels, despite the fact that they worked with the 5.10 kernel before today. Please let me know if there's any other info you need here. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.141 Mon Dec 28 16:21:32 UTC 2020
[Bug 1920059] Re: evdi module not building with current (5.11) Hirsute kernel
I tried compiling the evdi module code from https://github.com/sickcodes/evdi in branch rockorequin-sickcodes- microhobby-patch-1.7.x (see https://github.com/DisplayLink/evdi/issues/249), and it builds, but it has the same problem with 5.11 that the Ubuntu version of evdi has with 5.10, that I just described at https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1920067. Ugh, what a mess. ** Bug watch added: github.com/DisplayLink/evdi/issues #249 https://github.com/DisplayLink/evdi/issues/249 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920059 Title: evdi module not building with current (5.11) Hirsute kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920061] [NEW] when I go to restart it claims there is someone logged in remotely when no one is
Public bug reported: With all current Hirsute updates as of today, when I reboot my machine and then immediately after logging in select Power Off/Log Out and then Restart... the warning that pops up claims that I am logged in remotely (see attached screenshot) when I am not. As I said, I just rebooted and no one else is logged in. `who` also doesn't think anyone else is logged in: jik@jik5:~$ who jik :0 2021-03-18 15:24 (:0) jik@jik5:~$ ubuntu-bug gnome-shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 15:28:47 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (806 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-21 (25 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute regression-release ** Attachment added: "screen shot of restart pop-up claiming I am logged in remotely" https://bugs.launchpad.net/bugs/1920061/+attachment/5477970/+files/2021-03-18_15-28.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920061 Title: when I go to restart it claims there is someone logged in remotely when no one is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920059] Re: evdi module not building with current (5.11) Hirsute kernel
** Attachment added: "dkms make.log" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+attachment/5477968/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920059 Title: evdi module not building with current (5.11) Hirsute kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920059] Re: evdi module not building with current (5.11) Hirsute kernel
** Attachment added: "evdi-dkms.0.crash" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+attachment/5477967/+files/evdi-dkms.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920059 Title: evdi module not building with current (5.11) Hirsute kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920059] [NEW] evdi module not building with current (5.11) Hirsute kernel
Public bug reported: After the recent kernel update released to Hirsuite: jik@jik5:~$ uname -r 5.11.0-11-generic jik@jik5:~$ find /lib/modules -iname '*evdi*' /lib/modules/5.10.0-14-generic/updates/dkms/evdi.ko /lib/modules/5.8.0-43-generic/updates/dkms/evdi.ko jik@jik5:~$ Attempting to dpkg-reconfigure evdi-dkms yields: Building for 5.11.0-11-generic Building initial module for 5.11.0-11-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/evdi-dkms.0.crash' Error! Bad return status for module build on kernel: 5.11.0-11-generic (x86_64) Consult /var/lib/dkms/evdi/1.7.0+dfsg/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evdi-dkms 1.7.0+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 15:09:39 2021 InstallationDate: Installed on 2019-01-02 (806 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: evdi UpgradeStatus: Upgraded to hirsute on 2021-02-21 (25 days ago) ** Affects: evdi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920059 Title: evdi module not building with current (5.11) Hirsute kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
I want to thank you from the bottom of my heart for taking time out of what I'm sure is a very busy schedule to educate poor little me, who is so ignorant that I've only been working on open source and commercial software for over 30 years and using Linux since the early days of Slackware and at one point had submitted more Linux bug reports to Red Hat than literally any other account in bugzilla, about what a "show- stopper" bug is. Truly, I am enlightened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Claiming that Ubuntu could simply have stuck with the previous version of GNOME when shipping the LTS release is failing to see the forest for the trees. Many factors go into the decision of what version of a critical package like GNOME to put in a release. Ubuntu looked at all of those factors and made the decision they did. Unless you were involved in that discussion or have done an analysis similar to theirs, you are in no position to second-guess their decision; you simply are not considering even a small fraction of the information they considered when making it. Desktop Icons NG was around when 20.04 shipped, though it probably wasn't complete, tested, or stable enough to ship with an LTS release. There have been significant changes since 20.04 shipped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Three notes: 1. Ubuntu has addressed this in 21.04 by shipping gnome-shell-extension- desktop-icons-ng by default. 2. Note that you can fix this yourself in any earlier version of Ubuntu by installing that extension directly from extensions.gnome.org ( https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ ) and disabling the older version shipped with Ubuntu. 3. This is GNOME's fault, not Ubuntu's fault, so bitching at Ubuntu about it is not helpful or useful. It's not practical for Ubuntu to keep using obsolete versions of GNOME when the GNOME developers introduce regressions like this, and it's not feasible for Ubuntu to fix all of the regressions that the GNOME developers introduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917175] Re: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything
I don't understand why you are asking me for a crash report. You don't need a crash report to know what is going on here. I described to you exactly what is going on and exactly how to reproduce the issue: gdm fails in the way I described if libpam-fprintd isn't installed, and the web of dependencies of packages in Hirsute allowed an upgrade to uninstall fprintd-clients but did not require libpam-fprintd to be installed in its place. It appears that perhaps a dependency to libpam-fprintd was added to the gdm3 package after I filed this issue, because I see that it has such a dependency now, and I don't see how I could have done the update before with that dependency in place without libpam-fprintd being installed during the update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917175 Title: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917515] [NEW] System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates
Public bug reported: Note: I'm guessing that lvm2 is the most likely culprit for this issue, but I don't know for certain. After today's Hirsute upgrades, my system won't boot. The boot gets to the point where it asks me for the passphrase for my encrypted root disk, and I enter it, and then it says that it was unlocked successfully, and then it spins for a while, and then I get the message shown in the attached photo. When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I have installed the system boots successfully, but I don't think this is a kernel issue per se since I didn't upgrade the kernel today and my system has rebooted successfully before with the Hirsute kernel I currently have installed. Note: the two kernel messages shown at the beginning of the photo are not relevant; they occur even when I fall back to the old kernel and boot successfully. Attached: photo of console from failed boot, list of packages that were upgraded today. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lvm2 2.03.11-2ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 14:22:26 2021 InstallationDate: Installed on 2019-01-02 (790 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: lvm2 UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute regression-release ** Attachment added: "photo of console after failed boot" https://bugs.launchpad.net/bugs/1917515/+attachment/5471982/+files/PXL_20210302_191525480.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917515 Title: System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917515] Re: System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates
** Attachment added: "list of packages upgraded today from dpkg.log" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+attachment/5471986/+files/upgraded.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917515 Title: System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917175] Re: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything
I figured out the problem. When I upgraded packages today, it uninstalled fprintd-clients but did not install libpam-fprintd. /etc/pam.d/gdm-fingerprint says that gdm is supposed to open pam_fprintd.so, but it couldn't because it wasn't available any longer. I have no understanding of the intricacies of all the package dependencies that caused this broken situation to be allowed to occur. I will, however, mention that previous to today's package upgrade, I had open-fprintd installed, _not_ fprintd, because the fprintd that ships with Ubuntu is incompatible with my fingerprint reader (Lenovo Thinkpad X1 Carbon 6th gen). I don't know whether this is relevant to the problem that occurred here. To fix this, I had to uninstall open-fprintd (which means I can no longer use my fingerprint reader) and install libpam-fprintd, which pulled in the fprintd package along with it even though that's useless to me since that fprintd doesn't work with my reader. I am now unable to use open-fprintd because it conflicts with the fprintd package but I can't uninstall fprintd because that will cause libpam-fprintd to be uninstalled as well. But I'm going to open a separate ticket about that, since that's a different issue from the fact that today's upgrade made my system unusable as described above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917175 Title: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917178] [NEW] As of today in hirsute no longer possible to use open-fprintd
Public bug reported: It appears that fprintd-clients was replaced with libpam-fprintd, and libpam-fprintd can't be installed without fprintd. I can't use fprintd because it's incompatible with my fingerprint reader (Lenovo Thinkpad X1 Carbon 6th gen). Prior to today I was successfully using open-fprintd. Now, however, I had to uninstall open-fprintd and install libpam-fprintd to be able to log in (see bug 1917175), and I am unable to put open- fprintd back because that will force fprintd to uninstall, which will force libpam-fprintd to uninstall, which will make me unable to log in because pam_fprintd.so will disappear. This isn't great. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: fprintd 1.90.9-1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 27 17:16:27 2021 InstallationDate: Installed on 2019-08-16 (561 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: fprintd UpgradeStatus: Upgraded to hirsute on 2021-02-20 (6 days ago) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute regression-release wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917178 Title: As of today in hirsute no longer possible to use open-fprintd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1917178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917175] [NEW] gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything
Public bug reported: After today's update to all of the current Hirsute packages, I can't login in. When I click on my username on the gdm3 login screen, it immediately displays with shaking the error "Sorry, that didn't work. Please try again." It does this three times, and then sends me back to the main login screen. It does this EVEN THOUGH I'M NOT TYPING ANYTHING. Please see the attached video. I tried downgrading a bunch of packages but wasn't able to find a downgrade that made the problem go away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.1-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Feb 27 16:20:47 2021 InstallationDate: Installed on 2019-08-16 (561 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-02-20 (6 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute regression-release ** Attachment added: "video of my being unable to log in" https://bugs.launchpad.net/bugs/1917175/+attachment/5469795/+files/login_failure.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917175 Title: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916418] [NEW] Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule
Public bug reported:
DisplayLink uses these udev rules to start the displaylink service when
a displaylink device is plugged in:
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTR{idVendor}=="17e9",
IMPORT{builtin}="usb_id", ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
$env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
$env{DISPLAYLINK_DEVNAME}"
The important thing to note here is that the first rule is for the
device that is the parent of the device triggers the second rule, and
the first rule sets ENV{DISPLAYLINK_DEVNAME} and
ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import them
with IMPORT{parent} and then use them.
This worked fine in 20.04.
It does not work in 21.04.
When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
DISPLAYLINK_DEVNAME are not set.
I have confirmed via udevadm monitor that the variables are getting set
on the parent.
I have confirmed via udevadm info --attribute-walk that the device
triggering the second rule is the child of the device triggering the
first one.
I have tried to import the variables explicitly instead of using a glob
pattern and that doesn't work either.
When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
ID_SERIAL directly, that works. The problem appears to be that these
custom properties we are setting in the parent can't be imported in the
child.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: udev 247.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules
70-snap.chromium.rules 99-displaylink.rules
Date: Sun Feb 21 19:21:20 2021
InstallationDate: Installed on 2019-01-02 (781 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Acer Predator G6-710
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute regression-release 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/1916418
Title:
Custom properties set with ENV{WHATEVER} in parent no longer imported
with IMPORT{parent} in udev rule
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696885] Re: Implement remote desktop support for GNOME on Wayland
GNOME now supports remote desktop sharing in Wayland, but it isn't enabled in Ubuntu. Apparently one of the prerequisites for being able to enable it in Ubuntu was recompiling mutter with support for it, and that has now been done in Hirsute. What else needs to be done in Hirsute to make this work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696885 Title: Implement remote desktop support for GNOME on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730612] Re: Enable Remote desktop feature during build
Even with that version of mutter installed I still don't see screen sharing as an option under sharing in the settings app when logged in under Wayland. Are there other packages that need to be updated before screen sharing will be available in Wayland sessions, and are there open bug tickets for those? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901772] Re: apticron uses deprecated tempfile command
** Bug watch added: Debian Bug tracker #962921 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962921 ** Also affects: apticron (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962921 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901772 Title: apticron uses deprecated tempfile command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1901772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902766] Re: Automatic suspend when idle not working in 20.10
Darn it, I tested this like three times before reporting it, but I can no longer reproduce the issue. Sorry to bother you. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902766 Title: Automatic suspend when idle not working in 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902766] [NEW] Automatic suspend when idle not working in 20.10
Public bug reported: I have my laptop configured to suspend automatically after 20 minutes of idle time when on battery power. See screenshot attached showing these settings. This worked fine in 20.04. It is not working in 20.10: the laptop is not suspending even after far more than 20 minutes of idle time. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 3 13:18:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (444 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-26 (8 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-04-19T16:14:35.801558 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "screenshot of automatic suspend configuration" https://bugs.launchpad.net/bugs/1902766/+attachment/5430756/+files/2020-11-03_13-20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902766 Title: Automatic suspend when idle not working in 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901772] [NEW] apticron uses deprecated tempfile command
Public bug reported: The output of my apticron cron job emailed to me says, "WARNING: tempfile is deprecated; consider using mktemp instead." A quick search yields two usages of the tempfile command in /usr/sbin/apticron. Please fix so that people don't have to get emails from apticron consisting of nothing but this warning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apticron 1.2.3+nmu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 16:47:52 2020 InstallationDate: Installed on 2019-08-16 (438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: apticron UpgradeStatus: Upgraded to groovy on 2020-10-26 (1 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-04-19T16:14:35.801558 ** Affects: apticron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901772 Title: apticron uses deprecated tempfile command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1901772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901631] [NEW] flameshot, yubico authenticator app indicator icons missing on login
Public bug reported: This problem seems to come and go. It was gone in Ubuntu 20.04 and it's back in Ubuntu 20.10. I have both Flameshot and Yubico Authenticator configured to launch on login. They are supposed to put app indicator icons in the top bar. The icons are not there even though both apps are running. To get the icons I have to kill the apps and run them again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-appindicator 34-1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 19:32:07 2020 InstallationDate: Installed on 2019-01-02 (663 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to groovy on 2020-10-25 (1 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-04-17T14:48:03.262066 ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy regression-release regression-update ** Tags added: regression-release regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901631 Title: flameshot, yubico authenticator app indicator icons missing on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1901631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901625] [NEW] CIFS server / filesystem that worked fine in Ubuntu 20.04 breaks in Ubuntu 20.10
Public bug reported: After upgrading from 20.04 to 20.10 yesterday, my backup overnight failed. rclone reported these errors trying to read from the CIFS filesystem being backed up: 2020/10/26 18:45:00 ERROR : 2006/0713: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:45:00 ERROR : 2019/0417: error reading source directory: directory not found 2020/10/26 18:45:01 ERROR : 2018/0518: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:45:02 ERROR : 2018/1112: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:45:03 ERROR : [private path one elided]/2017-08-29: error reading source directory: failed to read directory entry: readdirent: interrupted system call 2020/10/26 18:45:04 ERROR : [private path one elided]/2018-07-22: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:45:04 ERROR : [private path one elided]/Hangouts/[private path two elided]: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:45:11 ERROR : Encrypted drive 'B2-encrypted:pictures': not deleting files as there were IO errors 2020/10/26 18:45:11 ERROR : Encrypted drive 'B2-encrypted:pictures': not deleting directories as there were IO errors 2020/10/26 18:45:11 ERROR : Attempt 1/3 failed with 8 errors and: march failed with 7 error(s): first error: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:46:20 ERROR : 2016/1229: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:46:21 ERROR : [private path one elided]/2017-12-31 - 2018-01-01: error reading source directory: failed to read directory entry: readdirent: interrupted system call 2020/10/26 18:46:22 ERROR : [private path one elided]/2018-03-19: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:46:22 ERROR : [private path one elided]/2018-07-19: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:46:27 ERROR : [private path one elided]/backup/Screenshots: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:46:27 ERROR : Encrypted drive 'B2-encrypted:pictures': not deleting files as there were IO errors 2020/10/26 18:46:27 ERROR : Encrypted drive 'B2-encrypted:pictures': not deleting directories as there were IO errors 2020/10/26 18:46:27 ERROR : Attempt 2/3 failed with 6 errors and: march failed with 5 error(s): first error: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:47:32 ERROR : [private path one elided]: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:47:33 ERROR : 2014/0606: error reading source directory: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:47:36 ERROR : Encrypted drive 'B2-encrypted:pictures': not deleting files as there were IO errors 2020/10/26 18:47:36 ERROR : Encrypted drive 'B2-encrypted:pictures': not deleting directories as there were IO errors 2020/10/26 18:47:36 ERROR : Attempt 3/3 failed with 3 errors and: march failed with 2 error(s): first error: failed to read directory entry: readdirent: no such file or directory 2020/10/26 18:47:36 Failed to sync with 3 errors: last error was: march failed with 2 error(s): first error: failed to read directory entry: readdirent: no such file or directory In addition I see the following in dmesg: [ 371.203517] CIFS: VFS: \\[private LAN host name elided]\photo Close interrupted close [ 373.131953] CIFS: VFS: \\[private LAN host name elided]\photo Close interrupted close [ 374.421419] CIFS: VFS: \\[private LAN host name elided]\photo Close interrupted close I want to emphasize that this worked fine in 20.04 basically forever, and then stopped working immediately after upgrading to 20.10. I tried rebooting, didn't help. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 18:51:48 2020 InstallationDate: Installed on 2019-01-02 (663 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions:
[Bug 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key
I can't test because I've followed the instructions in https://gitlab.gnome.org/GNOME/nautilus/issues/158#alternative-solution to switch to Nemo to address both this issue and https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/+bug/1813441, which still hasn't been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844808 Title: Can't delete file from desktop by clicking it and hitting delete key To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867796] Re: GnuCash icon in dock is blank
Important: The icon comes back if I set the dock icon size lower than 34 or higher than 44. It is only blank if the icon size is between 34 and 44. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867796 Title: GnuCash icon in dock is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1867796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867796] Re: GnuCash icon in dock is blank
Yup, that's the problem. When I repair that file the icon is no longer
invisible regardless of the size I set for the dock icons:
diff /usr/share/icons/hicolor/scalable/apps/gnucash-icon.svg{.bad,}
10c10
xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867796
Title:
GnuCash icon in dock is blank
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1867796/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867796] Re: GnuCash icon in dock is blank
The issue may be that /usr/share/icons/hicolor/scalable/apps/gnucash- icon.svg is corrupt. Here is what I see when I try to open it: XML parse error: error code=99 (3) in (null):10:72: xmlns:sodipodi: 'http://inkscape.sourceforge.net/DTD/s odipodi-0.dtd' is not a valid URI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867796 Title: GnuCash icon in dock is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1867796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867796] Re: GnuCash icon in dock is blank
There is nothing that looks relevant in journalctl output: jik@jik5:~$ journalctl -f -- Logs begin at Fri 2020-03-27 09:00:00 EDT. -- May 04 13:00:24 jik5.kamens.us systemd[1]: Stopping User Runtime Directory /run/user/1001... May 04 13:00:24 jik5.kamens.us systemd[1]: run-user-1001.mount: Succeeded. May 04 13:00:24 jik5.kamens.us systemd[1]: user-runtime-dir@1001.service: Succeeded. May 04 13:00:24 jik5.kamens.us systemd[1]: Stopped User Runtime Directory /run/user/1001. May 04 13:00:24 jik5.kamens.us systemd[2630]: run-user-1001.mount: Succeeded. May 04 13:00:24 jik5.kamens.us systemd[1]: Removed slice User Slice of UID 1001. May 04 13:00:27 jik5.kamens.us gnome-shell[3465]: Usage of indicator.indicators is deprecated for Indicator get indicators@resource:///org/gnome/shell/ui/panelMenu.js:213:25 getBattery@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:41:5 update@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:23:3 May 04 13:00:27 jik5.kamens.us gnome-shell[3465]: Usage of indicator.indicators is deprecated for Indicator get indicators@resource:///org/gnome/shell/ui/panelMenu.js:213:25 getBattery@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:41:5 show@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:10:3 update/<@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:27:7 getBattery@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:41:5 update@/home/jik/.local/share/gnome-shell/extensions/autohide-batt...@sitnik.ru/extension.js:23:3 There is nothing useful in the output of gnucash or gsettings: jik@jik5:~$ gnucash Found Finance::Quote version 1.49. jik@jik5:~$ gsettings get org.gnome.shell favorite-apps ['org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'google-chrome.desktop', 'org.gnome.Terminal.desktop', 'emacs.desktop', 'thunderbird.desktop', 'slack.desktop', 'vinagre.desktop', 'chrome-https___keep.google.com_u_0_.desktop', 'virtualbox.desktop', 'gnucash.desktop'] I am using US English. ** Changed in: gnucash (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/1867796 Title: GnuCash icon in dock is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1867796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
I understand that, but in this particular case we're talking about a transition from a deb to a snap, not a snap update. Apparently there's special logic in update-manager to handle this, and perhaps in do- release-upgrade as well, but I don't think either apt nor snap auto- updates will handle this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
I think Naël is correct that this problem goes away when gnome-software is replaced by snap-store. Or, at least, it appears to have gone away for me when I did that. I'm a bit concerned about that, though, because the reason why I didn't get that update is because I pretty much exclusively use apt to do my updates, and apparently that's no longer sufficient to get all the updates needed on an Ubuntu system. I don't want to have to run the graphical update-manager to do updates. I know this is mostly off-topic here, but I don't suppose anyone knows whether there is a way to do the equivalent of what update-manager does, but from the command line? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
>With the replacement of gnome-software by snap-store in 20.04, this bug is no longer apparent. Only users who manually (re-)install gnome- software will see it. I am not sure what you mean. There is no "snap-store" deb on my 20.04 system, nor does "apt search snap-store" yield any results. Furthermore, this bug was initially reported about the output of apticron showing up in cron job emails; as far as I know, apticron is independent of gnome-software. Please clarify your meaning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864223] Re: shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
If "you don't get downgraded to [the working versions] if you caught the broken one," then can someone explain to me how my laptop suddenly successfully upgraded two different firmware files after it failed to do so for weeks presumably because of this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864223 Title: shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864223] Re: shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
I think this has been fixed in focal? Within the last few days (I believe) my laptop successfully installed the firmware updates that had been failing to install because of this issue. Which is weird because the bug says it's in shim, but my dpkg log says the last time the shim package was updated was in February? Maybe it wasn't actually a shim bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864223 Title: shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869431] [NEW] TypeError: '>' not supported between instances of 'Version' and 'Version'
Public bug reported: Please see further discussion at https://github.com/pypa/pip/issues/7909, where we concluded that virtualenv on Ubuntu 20.04 is somehow installing pip wrong. Repro: $ virtualenv venv created virtual environment CPython3.8.2.final.0-64 in 158ms creator CPython3Posix(dest=/tmp/venv, clear=False, global=False) seeder FromAppData(download=False, html5lib=latest, pyparsing=latest, distlib=latest, wheel=latest, chardet=latest, colorama=latest, webencodings=latest, contextlib2=latest, requests=latest, six=latest, msgpack=latest, pip=latest, urllib3=latest, lockfile=latest, retrying=latest, pkg_resources=latest, appdirs=latest, progress=latest, idna=latest, setuptools=latest, pep517=latest, CacheControl=latest, pytoml=latest, distro=latest, certifi=latest, packaging=latest, via=copy, app_data_dir=/home/jik/.local/share/virtualenv/seed-app-data/v1.0.1) activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator $ . ./venv/bin/activate (venv) $ pip list --outdated ERROR: Exception: Traceback (most recent call last): File "/tmp/venv/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 186, in _main status = self.run(options, args) File "/tmp/venv/lib/python3.8/site-packages/pip/_internal/commands/list.py", line 158, in run packages = self.get_outdated(packages, options) File "/tmp/venv/lib/python3.8/site-packages/pip/_internal/commands/list.py", line 165, in get_outdated return [ File "/tmp/venv/lib/python3.8/site-packages/pip/_internal/commands/list.py", line 167, in if dist.latest_version > dist.parsed_version TypeError: '>' not supported between instances of 'Version' and 'Version' (venv) $ Fixing it by reinstalling pip: (venv) $ pip uninstall pip Found existing installation: pip 20.0.2 Uninstalling pip-20.0.2: Would remove: /tmp/venv/bin/pip /tmp/venv/bin/pip-3.8 /tmp/venv/bin/pip3 /tmp/venv/bin/pip3.8 /tmp/venv/lib/python3.8/site-packages/pip-20.0.2.dist-info/* /tmp/venv/lib/python3.8/site-packages/pip-20.0.2.virtualenv /tmp/venv/lib/python3.8/site-packages/pip/* Proceed (y/n)? y Successfully uninstalled pip-20.0.2 (venv) $ curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 1764k 100 1764k0 0 10.0M 0 --:--:-- --:--:-- --:--:-- 10.0M (venv) $ python get-pip.py Collecting pip Using cached pip-20.0.2-py2.py3-none-any.whl (1.4 MB) Installing collected packages: pip Successfully installed pip-20.0.2 (venv) $ pip list --outdated Package Version Latest Type --- --- --- - contextlib2 0.6.0 0.6.0.post1 wheel idna2.8 2.9 wheel msgpack 0.6.2 1.0.0 wheel packaging 20.120.3wheel pep517 0.7.0 0.8.1 wheel requests2.22.0 2.23.0 wheel setuptools 45.2.0 46.1.3 wheel (venv) $ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualenv 20.0.13-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 16:46:29 2020 InstallationDate: Installed on 2019-01-02 (450 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: python-virtualenv UpgradeStatus: Upgraded to focal on 2020-02-25 (31 days ago) ** Affects: python-virtualenv (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/1869431 Title: TypeError: '>' not supported between instances of 'Version' and 'Version' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1869431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
Yes, both microphone and speakers are now working for me after updating from proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860697 Title: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867796] Re: GnuCash icon in dock is blank
Don't have time to test with a clean ISO. Testing with a clean ISO kind of misses the point. I'm not imagining it; it's broken for me. So maybe let's try to figure out why. If you have any advice for what I can do to collect more data to troubleshoot on my system, I'm all ears. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867796 Title: GnuCash icon in dock is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1867796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867796] [NEW] GnuCash icon in dock is blank
Public bug reported: The dock icon for GnuCash recently became blank. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnucash 1:3.8b-1build3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 11:32:01 2020 InstallationDate: Installed on 2019-01-02 (440 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnucash UpgradeStatus: Upgraded to focal on 2020-02-25 (21 days ago) ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screen capture of a bit of my dock" https://bugs.launchpad.net/bugs/1867796/+attachment/5338017/+files/dock.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867796 Title: GnuCash icon in dock is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1867796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
Any hope of this being fixed any time soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860697 Title: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861837] Re: machine doesn't come up after suspend and re-opening the lid
Yup, sleep and wake work now, but I still don't have sound on my Thinkpad X1 Carbon 7th Gen. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801757] Re: all app indicators disappear
If I restart gnome shell, most of the app indicators remain, but the Google Chrome and Hangouts appindicators disappear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726402] Re: No Google Chrome icons in top bar
I still see it in current Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726402 Title: No Google Chrome icons in top bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1726402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726402] Re: No Google Chrome icons in top bar
Well, more accurately, I _sometimes_ see it in Focal. The icons in the top bar come and go seemingly at random i.e. I can't currently identify what makes them disappear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726402 Title: No Google Chrome icons in top bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1726402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866460] [NEW] UEFI Device Firmware update failing
Public bug reported: The Updates tab on Software Center is currently telling me that I have a Lenofo ThinkPad X1 Carbon 7th / X1 Yoga 4th Embedded Controller Firmware Version 1.5 updae to install. It claims it will upgrade my UEFI Device Firmware from 0.1.14 to 0.1.15. I click the Update button. The update goes away briefly and a pop-up appears telling me I need to reboot. Then the update reappears. I reboot, and nothing happens during the reboot, i.e., I don't see an update being installed during the reboot, and when I open Software Center again after the reboot the update is still listed there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 09:01:19 2020 InstallationDate: Installed on 2019-09-12 (176 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866460 Title: UEFI Device Firmware update failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1866460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
