[Bug 2065076] Re: nvidia failure to resume from suspend; kernel fallback broken
Failure to resume is happening systematically now. I have tried four times to suspend/resume since I posted my previous message. All four attempts failed. It does seem like this was triggered by the updates I installed the other day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065076] Re: nvidia failure to resume from suspend; kernel fallback broken
I posted back too soon. The problem has just surfaced again. When I tried to resume my system just now, the screen would not turn on again. As pointed out before, the mouse/keyboard appear to be dead when that happens. The CPU fans also run full speed and do not stop until I reboot. Could this "regression" (if that's the proper term...) be caused by the gnome-shell updates I ran today? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065076] Re: nvidia failure to resume from suspend; kernel fallback broken
OK, this looks (for now) fixed. I have gone back to 535 and now resume is working again. What has made the difference, I guess, is that installing 535 has restored /lib/systemd/system-sleep/nvidia. Deleting that file used to be part of the procedure to disable the systemd suspend/resume mechanism in favour of the kernel driver fallback. It looks like this is no longer the case and that the file needs to be left alone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065076] [NEW] nvidia failure to resume from suspend; kernel fallback broken
Public bug reported: I am unable to resume from suspend. The system comes back on but the screen is black. Switching to a virtual console to look for a solution is impossible as the keyboard appears to be dead. The issue is far from new and and goes as far back (for me) as 22.04. Until 23.10, however, it could be worked around by disabling the systemd suspend mechanism (disable nvidia-suspend, nvidia-hibernate and nvidia- resumpe). The system would then use the kernel driver fallback instead, which worked fine. Until now. I have tried nvida drivers 535 and 550. Neither worked. I have enabled the graphics-drivers ppa to test the latest available driver, which is a newer version of the 550 driver included in the repositories. No luck. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:codey 2877 F pipewire /dev/snd/controlC0: codey 2881 F wireplumber /dev/snd/controlC1: codey 2881 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 16:38:34 2024 InstallationDate: Installed on 2022-03-27 (772 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: System manufacturer System Product Name ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=3e125bf2-3409-4f46-8a06-bba9a5fa9032 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6063 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064977] [NEW] new gnome-terminal instances launched from nautilus fail to receive automatic focus
Public bug reported: When a first gnome-terminal instance is launched from nautilus (context menu item "Open in Terminal"), it automatically receives focus for keyboard input. When additional instances are launched in the same way, the mechanism breaks down and focus remains with nautilus. If the user immediately starts typing, their input ends up being processed by the nautilus search bar instead of the terminal. Correcting this course of action requires unnecessary clicks or keyboard strokes. That is potentially confusing and certainly annoying. I remember being affected by the same bug in the early days of either Ubuntu 23.04 or 23.10. I have found a bug report related to gentoo that mentions something very much like what I am describing here: https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f;. It seems to suggest that the bug affects only wayland but I use X11. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 03:06:57 2024 InstallationDate: Installed on 2022-03-27 (771 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: When a first gnome-terminal instance is launched from nautilus (context menu item "Open in Terminal"), it automatically receives focus. When additional instances are launched in the same way, the mechanism breaks down and focus remains with nautilus. If the user immediately starts typing, their input ends up being processed by the nautilus search bar instead of the terminal. Correcting this course of action requires unnecessary clicks or keyboard strokes. That is potentially confusing and certainly annoying. I remember being affected by the same bug in the early days of either Ubuntu 23.04 or 23.10. I have found a bug report on the gentoo forums that looks very much like what I am describing here: https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f;> - g ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 03:06:57 2024 InstallationDate: Installed on 2022-03-27 (771 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When a first gnome-terminal instance is launched from nautilus (context menu item "Open in Terminal"), it automatically receives focus. When additional instances are launched in the same way, the mechanism breaks down and focus remains with nautilus. If the user immediately starts typing, their input ends up being processed by the nautilus search bar instead of the terminal. Correcting this course of action requires unnecessary clicks or keyboard strokes. That is potentially confusing and certainly annoying. I remember being affected by the same bug in the early days of either Ubuntu 23.04 or 23.10. I have found a bug report on the gentoo forums - that looks very much like what I am describing here: https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f;> - g + that looks very much like what I am describing here: + https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f; ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 03:06:57 2024 InstallationDate: Installed on 2022-03-27 (771 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When a first gnome-terminal instance is launched from nautilus (context - menu item "Open in Terminal"), it automatically receives focus. + menu item "Open in Terminal"), it automatically receives focus for + keyboard input. When additional instances are launched in the same way, the
[Bug 2063397] Re: extracting rar archives sometime incomplete
I have tried to create an archive of my own to reproduce the problem. I
think I have succeeded.
Check the included archive, which contains:
- 10 folders containing 10 (empty) text files
- a zip archive containing a single file filled with some data gleaned from
/dev/random
observation:
- trying to inspect the contents with file-roller causes file-roller to crash
- extracting the file extracts only the contents of the zip archive (compare:
extraction from the CLI with rar e)
more observations:
- I had to compress from the command line (with the rar utility) as nautilus
consistently crashes if I try to compress through the context menu ("compress")
- the issue appears to match this report on reddit:
https://www.reddit.com/r/gnome/comments/1btxk69/nautilus_crashing_when_selecting_multiple_files/
** Attachment added: "archive.rar"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+attachment/5770668/+files/archive.rar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063397
Title:
extracting rar archives sometime incomplete
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063397] Re: extracting rar archives sometime incomplete
Sadly, no. The archives in question are copyrighted so I doubt it would be a good idea to post them here in the open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063397 Title: extracting rar archives sometime incomplete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063397] [NEW] nautilus extract option causes date loss from rar archives
Public bug reported:
Extraction of rar files (v5) from the context menu ("Extract")
occasionally results in one or more subfolders silently being skipped.
This behavior is not systematic. Some rar archives extract properly,
other ones do not.
There is not any warning or error message when the problem manifests,
which make it likely that the problem goes overlooked. I have
effectively sustained data loss until I discovered that one of my
extracted folders was much smaller than it should have been.
I have unrar (non-free) and 7z installed.
Applications like file-roller and arqiver appear to function properly.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 05:26:17 2024
InstallationDate: Installed on 2022-03-27 (759 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
eiciel0.10.0-1build2
file-roller 44.1-1
nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
python3-nautilus 4.0-1build4
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble 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/2063397
Title:
nautilus extract option causes date loss from rar archives
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I believe that the evolution mail program and google accounts are to blame. The problem went away for me after I deleted my keyring and switched from evolution to thunderbird. Trying to (re-)add a mail account to evolution immediately brings the problem is back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
But the flatpak version typically fails to generate thumbnails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
I am seeing the same issues. They have to do with apparmor. Preferences do stick when the evince profile is disabled (sudo apparmor_parser -R /etc/apparmor.d/usr.bin.evince). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969709] Re: libreoffice font selection unusably slow
** Description changed: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to - perform individidual scrolling gestures to move through the list. + perform individidual scrolling gestures. The CPU jumps to 100% and the + whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the - LibreOffice project. They all manifest the same behaviour. I have had to - downgrade to 7.2, which appears to be unaffected. + LibreOffice project. They all manifest the same behaviour. The only + thing that works is disabling font previews. I have downgraded to 7.2 + for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969709] [NEW] libreoffice font selection unusably slow
Public bug reported: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures to move through the list. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. I have had to downgrade to 7.2, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - Trying to scroll the font list from the menu bar of writer, I experience - an unacceptable degree of lagging. Just popping up the dropdown list - takes 7-10 seconds and the system takes the same amount of time to - respond to perform single scrolling gestures moving through the list. + Trying to scroll through the font list in the menu bar, I experience an + unacceptable degree of lagging. Just popping up the dropdown list takes + 7-10 seconds and the system takes the same amount of time to respond to + perform individidual scrolling gestures to move through the list. - I have tried deb, snap and even the packages as offered on the site of - the LibreOffice project. The all manifest the same behaviour. I have had - to downgrade to 7.2. + I have tried deb, snap and even the packages offered on the site of the + LibreOffice project. They all manifest the same behaviour. I have had to + downgrade to 7.2, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should - be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is using 2.13. + be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping + 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
The bug appears to be a theming issue. I have not seen it since I replaced the third party theme I was using with the default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
** Description changed: - Every time I want to use my computer after the screen has blanked, I - find that the open applications are frozen. + When I want to use my computer after the screen has blanked, I often + (about half of the time) find that the open applications are frozen. I can bring them back to life by restarting X or by cycling through the windows (ALT + TAB). Not a major bug certainly annoying as it is happening time and again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 09:53:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-27 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969266] [NEW] application windows frozen after screen blanking
Public bug reported: Every time I want to use my computer after the screen has blanked, I find that the open applications are frozen. I can bring them back to life by restarting X or by cycling through the windows (ALT + TAB). Not a major bug certainly annoying as it is happening time and again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 09:53:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-27 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967885] Re: blanking locks screen although screen lock is disabled
Running gsettings with sudo seems to nail it: sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true' But this disables screen locking for every user. That is irrelevant to me but some may care. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967885] Re: blanking locks screen although screen lock is disabled
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967885] Re: blanking locks screen although screen lock is disabled
Possibly related to bug #1968208, which I reported today: frozen gnome- shell after logging in/unlocking. This new bug would indicate that gnome-shell indeed randomly crashes. The behaviour is inconsistent, though. Sometimes it does not crash at all, at other times it does but it does not always cause the desktop to freeze. I can add a photo, as your requested, but I wonder whether that would add anything. The lock screen is simply the log-in screen that traditionally comes up when the system is booted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967885] [NEW] blanking locks screen although screen lock is disabled
Public bug reported: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (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/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955697] [NEW] file-roller fails to extract zip|rar|tar to symlinked directories
Public bug reported: File-roller fails to extract rar, zip, xz and tar archives when 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or 2) open the archive and run "Extract to" from its menu (which is quite cumbersome when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ** Description changed: - File-roller fails to extract rar, zip, xz and tar archives when - 1) the output folder is or is below a symbolic link + File-roller fails to extract rar, zip, xz and tar archives when + 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) - The typical error message is: + The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I - 1) navigate to the actual location of the output folder + 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or 2) open the archive and run "Extract to" from its menu (that may be fine for a single archive but it is frustrating when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: File-roller fails to extract rar, zip, xz and tar archives when 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or - 2) open the archive and run "Extract to" from its menu (that may be fine for a single archive but it is frustrating when there are dozens of archives to process...). + 2) open the archive and run "Extract to" from its menu (which is quite cumbersome when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955697 Title: file-roller fails to extract zip|rar|tar to symlinked directories To manage notifications about this bug go to:
[Bug 1954586] Re: login screen freezes when switching users
Using method 2, I have found one (recent) link that refers to an issue affecting gdm3: https://errors.ubuntu.com/oops/10ce3186-5b3e-11ec-88a3-fa163e983629 I hope that this sort of link is what you were asking for; I do not seem to have permission to access its contents so I cannot tell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954586 Title: login screen freezes when switching users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1954586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954586] [NEW] login screen freezes when switching users
Public bug reported: Switching users causes the login screen to lock up and the mouse and keyboard to become unresponsive. The order is this: 1) I select "switch user..." from the top bar 2) the login screen pops up and displays the list of users 2) I select my user 4) I enter the password 5) the screen turns black for 2-3 seconds (this is much longer than usual) 6) the login screen pops up again, this time with the text "password" in the input box; the gear in the bottom right corner to select the type of session is missing; the mouse and keyboard are unresponsive 7) I need to reboot I have tried disabling Wayland (uncommented WaylandEnable=false in /etc/gdm3/custom.conf) but that does not make any difference. I do not know whether this may be related, but I have had to disabled the nvidia systemd services because my system failed to suspend until I did (nvidia driver 470). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 12 12:11:57 2021 InstallationDate: Installed on 2021-10-12 (61 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ** Description changed: - Switching users cause the login screen to lock up and the mouse and + Switching users causes the login screen to lock up and the mouse and keyboard to become unresponsive. The order is this: - 1) I select "switch user..." from the top bar + 1) I select "switch user..." from the top bar 2) gdm3 pops up and displays the list of users 2) I select my user - 4) I enter the password - 5) the screen turns black for 2-3 seconds (this is much longer than usual) + 4) I enter the password + 5) the screen turns black for 2-3 seconds (this is much longer than usual) 6) the login screen pops up again, this time with the text "password" in the password input box; at this stage, the mouse and keyboard have become unresponsive 7) I need to reboot I have tried disabling Wayland (uncommented WaylandEnable=false in /etc/gdm3/custom.conf) but that does not make any difference. I do not know whether this may be related, but I have had to disabled the nvidia systemd services because my system failed to suspend until I did (nvidia driver 470). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 12 12:11:57 2021 InstallationDate: Installed on 2021-10-12 (61 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Switching users causes the login screen to lock up and the mouse and keyboard to become unresponsive. The order is this: 1) I select "switch user..." from the top bar - 2) gdm3 pops up and displays the list of users + 2) the login screen pops up and displays the list of users 2) I select my user 4) I enter the password 5) the screen turns black for 2-3 seconds (this is much longer than usual) - 6) the login screen pops up again, this time with the text "password" in the password input box; at this stage, the mouse and keyboard have become unresponsive + 6) the login screen pops up again, this time with the text "password" in the input box; the gear in the bottom right corner to select the type of session is missing; the mouse and keyboard are unresponsive 7) I need to reboot I have tried disabling Wayland (uncommented WaylandEnable=false in /etc/gdm3/custom.conf) but that does not make any difference. I do not know whether this may be related, but I have had to disabled the nvidia systemd services because my system failed to suspend until I did (nvidia driver 470). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 12 12:11:57 2021 InstallationDate: Installed on 2021-10-12 (61 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: gdm3 UpgradeStatus: No upgrade log
[Bug 1928352] [NEW] package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: The installer crashed at the very end with a warning that my computer might fail to boot. It booted alright but after logging in I get a pop-up to signal that shim-signed has failed to install. Something to do with my system (EFI) running in insecure mode? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: shim-signed 1.47+15.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: pass Date: Thu May 13 16:54:46 2021 EFITables: mei 13 17:05:50 Selena kernel: efi: EFI v2.10 by American Megatrends mei 13 17:05:50 Selena kernel: efi: ACPI=0xba80b000 ACPI 2.0=0xba80b000 SMBIOS=0xf04c0 MOKvar=0xae8a2000 mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-13 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SecureBoot: 6 0 0 0 0 SourcePackage: shim-signed Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928352 Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1928352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
Well... I just find that mp3 streams work just as fine. Most likely a kernel thing, then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
I think this ticket can be closed, at least for now. Since I replaced all my mp3 format streams with aac streams, I have not experienced as much as a stutter. Then again, for all I know, the actual reason may be a recent be a kernel update... Anyway, thanks for your assistance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
The URI you put up plays fine. Unfortunately, I ran into the same issue when I started a different stream. There were a few short skips at first but the player came back. Then it suddenly gave up completely with the error message mentioned in my opening post. I am including the log file. The issue appears to show up in lines 8492-8493. The lines further down show a recurring pattern so I assume that the player is stuck in a loop that prevents it from resuming. ** Attachment added: "rhythmbox.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+attachment/5385346/+files/rhythmbox.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
** Description changed: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. + UPDATE: this would appear to be happening only when I run my CPU in + powersave mode (reduced speed and 4-6 vCPUs disabled). + release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
** Description changed: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux + also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jurgen 1998 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: - lono wireless extensions. - - enp10s0 no wireless extensions. + lono wireless extensions. + + enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-33-generic N/A - linux-backports-modules-5.4.0-33-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-33-generic N/A + linux-backports-modules-5.4.0-33-generic N/A + linux-firmware1.187 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
I am including the output of the dmesg command as ran immediately after resume from suspend - it shows the stack trace I am referring to in my bug report. ** Attachment added: "dmesg_2020-06-08_04:12.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+attachment/5381446/+files/dmesg_2020-06-08_04%3A12.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] [NEW] nvme driver issue causing massive system lag on resume from suspend
Public bug reported: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881458] [NEW] Playback aborts when a download is started, printing "server does not support seeking"
Public bug reported: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a manager. Something trivial - say, installing a firefox or a gnome-shell plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Description changed: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a - manager. Something trivial like installing a firefox or a gnome-shell - plug-in can be enough to interrupt playback. + manager. Something trivial - say, installing a firefox or a gnome-shell + plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865289] Re: ubuntu 19.10: libvirt hangs host shutdown
The motherboard in question is the MSI x470 Gaming Plus Max. The original BIOS had to be flashed to version 7B79vH4. On a side note, I ran into the very same issue with an ASUS x470 Prime Pro. Same remedy: a BIOS flash (I used version 5406). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865289 Title: ubuntu 19.10: libvirt hangs host shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1865289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865289] Re: ubuntu 19.10: libvirt hangs host shutdown
** Tags added: hw-specific kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865289 Title: ubuntu 19.10: libvirt hangs host shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1865289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865289] Re: ubuntu 19.10: libvirt hangs host shutdown
Thank you for responding. I managed to solved this through a BIOS update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865289 Title: ubuntu 19.10: libvirt hangs host shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1865289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865289] [NEW] ubuntu 19.10: libvirt hangs host shutdown
Public bug reported: Android studio requires qemu-kvm to emulate android images. After installing qemu, libvirt-daemon-system, libvirt-clients and bridge-utils, my system (host) appears to function correctly but it consistently fails during shutdown. I have not actually run any android/qemu images so it is certainly not a guest issue. After removing the qemu related packages, the system is back to shutting down properly. I suspect the problem has a connection with the kernel. Going over the error messages in journalctl, I see that - only with qemu/libvirt installed - the following will appear when booting up: eb 29 14:02:10 Dapple kernel: ccp :2a:00.1: sev command 0x4 timed out, disabling PSP Feb 29 14:02:10 Dapple kernel: ccp :2a:00.1: SEV: failed to get status. Error: 0x0 Feb 29 14:02:10 Dapple kernel: BUG: kernel NULL pointer dereference, address: 0040 Feb 29 14:02:10 Dapple kernel: #PF: supervisor read access in kernel mode Feb 29 14:02:10 Dapple kernel: #PF: error_code(0x) - not-present page I have also noticed that libvirt-* caused apt to block as it was being purged. I had to do a hard reboot to clear the lock. Here is the relevant excerpt from /var/log/apt/history (compare the start-date and the end-date: 9 minutes and not even finished...): Start-Date: 2020-02-29 14:15:30 Commandline: apt purge libvirt-daemon-system libvirt-clients Requested-By: jurgen (1000) Purge: libvirt-clients:amd64 (5.4.0-0ubuntu5), libvirt-daemon-system:amd64 (5.4.0-0ubuntu5) End-Date: 2020-02-29 14:24:35 ** Affects: libvirt (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/1865289 Title: ubuntu 19.10: libvirt hangs host shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1865289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831185] Re: synaptic package manager crashes on search action
It looks like the crash is caused by the Erlang PPA. As long as I keep it disabled, search works perfectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831185 Title: synaptic package manager crashes on search action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1831185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831185] [NEW] synaptic package manager crashes on search action
Public bug reported: Whenever I press the ENTER key in synaptic to launch a package search, the application crashes immmediately. When I start synaptic from the command line, I get this after every crash: Segmentation fault (core dumped) More details can be found from dmesg, which prints the same two lines for each crash: synaptic[15666]: segfault at 7f048e79a4c0 ip 7f00864090f3 sp 7ffd72ad1400 error 4 in libapt-pkg.so.5.0.2[7f00862b+1b3000] [ 1785.886327] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 84 00 00 00 00 00 55 53 48 89 fd 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f ** Affects: synaptic (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/1831185 Title: synaptic package manager crashes on search action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1831185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577093] Re: libreoffice-gtk conflicts with large lo-writer file
1) No, previous versions were fine. 2) My issue got solved through an August update (comment #4 above) so I have not seen any reason to test other versions since. All I can say is that I did try launchpad at the time I was experiencing the bug - no 5.2.x was available yet - and that did not help at all. I will try a later version as soon as I find the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577093 Title: libreoffice-gtk conflicts with large lo-writer file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577093] Re: libreoffice-gtk conflicts with large lo-writer file
Just an update: all the issues that I reported were fixed some time ago after upgrading libreoffic-gtk (currently using 1:5.1.4-0ubuntu1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577093 Title: libreoffice-gtk conflicts with large lo-writer file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] Re: [regression] NFS client: access problems after updating to kernel 4.4.0-31-generic
I confirm that the issue is solved by the kernel in proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: [regression] NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic
Thanks for your helpful instructions. The most recent mainline kernel (= 4.7.0-040700rc7-generic) appears to be unaffected. I can now enter the exported subfilesystems again with the expected permissions. ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.7rc7 ** Tags removed: kernel-fixed-upstream-4.7rc7 ** Tags added: kernel-fixed-upstream-4.7-rc7 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702569/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702572/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic
apport information ** Tags added: apport-collected ** Description changed: I am denied access to the subfilesystems exported by my nfs server (the top level filesystem itself is unaffected). The client is reporting that I do not have the necessary permissions. However, all was fine until the day before yesterday. - When I revert my client to 4.4.0-28, everything is in working order - again. I assume the permission problem is really a bug in kernel - 4.4.0-31. + When I revert my client to 4.4.0-28, everything is in working order again. I assume the permission problem is really a bug in kernel 4.4.0-31. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jurgen 1743 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52 + InstallationDate: Installed on 2016-04-07 (101 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405) + IwConfig: + lono wireless extensions. + + enp4s0no wireless extensions. + MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514 + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash + ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-31-generic N/A + linux-backports-modules-4.4.0-31-generic N/A + linux-firmware1.157.2 + RfKill: + + Tags: xenial + Uname: Linux 4.4.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/28/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: V1.1 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: MS-7514 + dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: + dmi.product.name: MS-7514 + dmi.product.version: 1.0 + dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702564/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702567/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702574/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702568/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702576/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702566/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702565/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702570/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702575/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702571/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1603719/+attachment/4702573/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603719] [NEW] NFS client: access problems after updating to kernel 4.4.0-31-generic
Public bug reported: I am denied access to the subfilesystems exported by my nfs server (the top level filesystem itself is unaffected). The client is reporting that I do not have the necessary permissions. However, all was fine until the day before yesterday. When I revert my client to 4.4.0-28, everything is in working order again. I assume the permission problem is really a bug in kernel 4.4.0-31. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: access nfs xenial ** Description changed: I am denied access to the subfilesystems exported by my nfs server (the top level filesystem itself is unaffected). - The client is reporting that I do not have the necessary permissions but - everything was fine before I updated to kernel 4.4.0-31 . + The client is reporting that I do not have the necessary permissions. + However, all was fine until the day before yesterday. - I have just tried reverting my client to 4.4.0-28 and now everything is - in working order again. + When I revert my client to 4.4.0-28, everything is in working order + again. I assume the permission problem is really a bug in kernel + 4.4.0-31. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603719 Title: NFS client: access problems after updating to kernel 4.4.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1603719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577093] [NEW] libreoffice-gtk conflicts with large lo-writer file
Public bug reported: Using Ubuntu 16.04 LTS installed originally from a weekly beta2 ISO; the image was verified at the time to match its checksum and the install has since consistently been upgraded. >From the start, Libreoffice writer (1:5.1.2-0ubuntu1 - amd64) has struggled with a "large" file I have been working on since Ubuntu 15.04, although it works perfectly for newly created files or existing smaller files, though. I was hoping to continue using my exiting file, however: one that counts about 14,000 paragraphs, 3.5 million characters and some 300 tables as well a large number of bookmarks/internal links). I should have hoped that LO would simply load it and let me get on with my work as it did before. Unfortunately, here is what really happens whenever I try to load it: - when the progress bar completes , Writer greys out and locks up for several minutes on end (anything from a few minutes to a quarter of an hour) - during that time, the interface is clearly distorted (two overlapping status bars - duplicated vertical scrollbars at the right side - the title bar covering up the menu bar as well as part of the upper toolbar - the horizontal ruler shifted to the right, causing the "comments" column to appear on the left rather than the right) - when the file eventually gets loaded and the interface is restored, the menus turns out to be unusable: the drop-downs are narrow blacks slabs without any entries and without any responsiveness - the page count is wildly off: the file is about 1100 pages, yet Writer reports over 1800; at any moment, however, it will update its count to reflect the actual number. - random actions can produce a new prolonged lock-up; in particular copying text, opening up the navigator or doing a search. The only way to open the file in a usable way is to restart Writer several times in a row (which takes LOTS of patience considering the time it takes the file to load...) Apparently, the only way to avoid these problems is to delete the libreoffice-gnome/gtk packages. Unfortunately, that leaves me with an interface that looks like are relic from a previous century I did not much like that, so I have experimented with the debs available directly from the LibreOffice project. Sadly, I am seeing the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-writer 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 1 05:28:07 2016 InstallationDate: Installed on 2016-04-07 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "for testing purposes I am including the text file in question; it is a rather extensive vocabulary list composed in Dutch; please note it contains a small handful of links that reference other files - I guess it wouldbe better to turn off check links when loading the file" https://bugs.launchpad.net/bugs/1577093/+attachment/4652522/+files/wlst.odt ** Description changed: Using Ubuntu 16.04 LTS installed originally from a weekly beta2 ISO; the image was verified at the time to match its checksum and the install has since consistently been upgraded. From the start, Libreoffice writer (1:5.1.2-0ubuntu1 - amd64) has struggled with a "large" file I have been working on since Ubuntu 15.04, although it works perfectly for newly created files or existing smaller - files, though. + files. - I was hoping to continue using my exiting file, however: one that counts + I was hoping to continue using my existing file, however (it counts about 14,000 paragraphs, 3.5 million characters and some 300 tables as well a large number of bookmarks/internal links). I should have hoped that LO would simply load it and let me get on with my work as it did before. Unfortunately, here is what really happens whenever I try to load it: - when the progress bar completes , Writer greys out and locks up for several minutes on end (anything from a few minutes to a quarter of an hour) - during that time, the interface is clearly distorted (two overlapping status bars - duplicated vertical scrollbars at the right side - the title bar covering up the menu bar as well as part of the upper toolbar - the horizontal ruler shifted to the right, causing the "comments" column to appear on the left rather than the right) - - when the file eventually gets loaded and the interface is restored, the menus turns out to be unusable: the drop-downs are narrow blacks slabs without any entries and without any responsiveness + - when the file eventually gets loaded and the
