[Desktop-packages] [Bug 1793124]
(In reply to V Stuart Foote from comment #40) > (In reply to gulpen from comment #39) > > > Please give this issue some love! > > We have. > > Two options for working with wide columns or tall rows. Or with undersized > displays. > > One would be to adjust the sheet scroll from default spreadsheet centric > "scroll by cell edge" to a "scroll by screen pixel" and requiring new > implementation. > > The other option was implemented to expose the content of oversize cells to > edit engine and UI control via an expandable input window on the FormulaBar > (View -> Formula Bar) where you will find a "Expand Formula Bar" and > "Collapse Formula Bar" toggle triangle. > > The collapsed formula bar is one character row in height. The expanded > formula bar input window can be dragged as tall as 25 lines. Default is 6 > lines, but the UI value is recorded into the spreadsheet on save, so it > keeps it handy. For really large cell content (an actual sc formula or text > strings), the input window has a vertical scroll to work with the entire > cell (up to 64,000 characters IANM). > > Pixel level scrolling a sheet would be nice to implement, but you already > are able to work with cells larger than the display or the app window using > the Formula Bar's input window, without having to zoom the sheet out. Where do I go in the github to assist with creating a scroll by pixel implementation? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I sometimes receive Calc documents where the content of an individual cell is split on so many lines that it fills up the whole screen and more. I can easily see the top part of these cells but scrolling to the bottom does not seem to work. Whether I try dragging the scrollbar or moving the screen with my laptop’s touchpad, Calc seems to skip the bottom part of the cell and jump directly to the following cell. See the attached screenshots of a document which has numbers 1 to 50 so that numbers 4 to 40 occupy one single cell (A4). In the first screenshot I see the top part of that cell (4 to 23) and in the next I have scrolled down the screen as little as possible, and now I see cell A5 (number 41) on the top. Everything in between is visually inaccessible whatever I try. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:16:17 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056494] [NEW] Snap profile import fails with EPERM
Public bug reported: A regular noble full-upgrade transitioned my laptop to the thunderbird snap this morning, and I ended up with no profile due to an EPERM reading ~/.thunderbird during the migration. thunderbird.launcher says it needs personal-files, but the thunderbird snap doesn't seem to have that plug. wgrant@vanth:~$ thunderbird du: cannot read directory '/home/wgrant/.thunderbird': Permission denied Importing existing thunderbird profiles from /home/wgrant/.thunderbird cp: cannot stat '/home/wgrant/.thunderbird/*': No such file or directory Usage: /snap/thunderbird/450/patch-default-profile.py /path/to/profiles_dir/profiles.ini Import done in 0.029 s wgrant@vanth:~$ ls -ld /home/wgrant/.thunderbird drwx-- 6 wgrant wgrant 4096 Aug 13 2020 /home/wgrant/.thunderbird wgrant@vanth:~$ dpkg -l thunderbird | tail -n1 ii thunderbird1:115.8.1+build1+snap2 amd64Transitional package - thunderbird -> thunderbird snap wgrant@vanth:~$ snap info thunderbird | tail -n1 installed: 115.8.1-2(450) 145MB - wgrant@vanth:~$ snap connections thunderbird Interface Plug Slot Notes audio-playback thunderbird:audio-playback:audio-playback - avahi-observe thunderbird:avahi-observe - - browser-support thunderbird:browser-sandbox :browser-support - camera thunderbird:camera- - content[gnome-42-2204] thunderbird:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gtk-3-themes] thunderbird:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes]thunderbird:icon-themes gtk-common-themes:icon-themes - content[sound-themes] thunderbird:sound-themes gtk-common-themes:sound-themes - cups-controlthunderbird:cups-control - - dbus- thunderbird:dbus-daemon - desktop thunderbird:desktop :desktop - desktop-legacy thunderbird:desktop-legacy:desktop-legacy - gpg-keysthunderbird:gpg-keys - - gsettings thunderbird:gsettings :gsettings - homethunderbird:home :home - network thunderbird:network :network - network-control thunderbird:network-control - - opengl thunderbird:opengl:opengl - removable-media thunderbird:removable-media - - system-filesthunderbird:etc-thunderbird-policies :system-files - u2f-devices thunderbird:u2f-devices - - wayland thunderbird:wayland :wayland - x11 thunderbird:x11 :x11 - ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056494 Title: Snap profile import fails with EPERM Status in thunderbird package in Ubuntu: New Bug description: A regular noble full-upgrade transitioned my laptop to the thunderbird snap this morning, and I ended up with no profile due to an EPERM reading ~/.thunderbird during the migration. thunderbird.launcher says it needs personal-files, but the thunderbird snap doesn't seem to have that plug. wgrant@vanth:~$ thunderbird du: cannot read directory '/home/wgrant/.thunderbird': Permission denied Importing existing thunderbird profiles from /home/wgrant/.thunderbird cp: cannot stat '/home/wgrant/.thunderbird/*': No such file or directory Usage: /snap/thunderbird/450/patch-default-profile.py /path/to/profiles_dir/profiles.ini Import done in 0.029 s wgrant@vanth:~$ ls -ld /home/wgrant/.thunderbird drwx-- 6 wgrant wgrant 4096 Aug 13 2020 /home/wgrant/.thunderbird wgrant@vanth:~$ dpkg -l thunderbird | tail -n1 ii thunderbird1:115.8.1+build1+snap2 amd64Transitional package - thunderbird -> thunderbird snap wgrant@vanth:~$ snap info thunderbird | tail -n1 installed: 115.8.1-2(450) 145MB - wgrant@vanth:~$ snap connections thunderbird Interface Plug
[Desktop-packages] [Bug 1938724] Re: uses aptdaemon
*** This bug is a duplicate of bug 1673258 *** https://bugs.launchpad.net/bugs/1673258 ** This bug has been marked a duplicate of bug 1673258 Remove aptdaemon and drop or port its reverse-dependencies -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1938724 Title: uses aptdaemon Status in apturl package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in oem-config package in Ubuntu: New Bug description: aptdaemon is not a maintained component, please use PackageKit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apturl/+bug/1938724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
FYI: My temporary workaround is to just have the Dock to auto-hide (for Ubuntu 22.04). This way there are no windows that might get stuck underneath the Dock. This essentially solves the issue in a simple way, but the only downside is that some folks prefer to see their Dock all the time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038892] Re: How To Contact +1(202-960-2084) McAfee Customer Service Number?
** Package changed: cups (Ubuntu) => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2038892 Title: How To Contact +1(202-960-2084) McAfee Customer Service Number? Status in NULL Project: Invalid Bug description: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2038892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
Here's another journal from the boot after the one before, with the same settings as before (I've set MUTTER_DEBUG_TRIPLE_BUFFERING=never but not yet rebooted). My primary display should have multiple hangs in the last couple of minutes here. I unwisely fullscreened a YouTube video in Firefox, and recovered by replugging my docking station. This repeated a few times, with a LUKS unlock prompt sometimes stopping it from hanging until I dismissed the dialog, until I hit Esc to de-fullscreen the video and replugged one last time. I think my secondary display might also have hung at some point during this boot, but I forget. ** Attachment added: "a journal from several single-display hangs in one session" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702630/+files/journal-redacted.txt.zst -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
** Attachment added: "journal from a single-display hang with gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays through an MST hub, with MUTTER_DEBUG=kms MUTTER_DEBUG_KMS_THREAD_TYPE=user" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702590/+files/journal-redacted.txt.zst -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
** Attachment added: "journal from a single-display hang with gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays through an MST hub" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702587/+files/journal-redacted.txt ** Attachment removed: "journal from a single-display hang with gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays through an MST hub, with MUTTER_DEBUG=kms MUTTER_DEBUG_KMS_THREAD_TYPE=user" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702587/+files/journal-redacted.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i
[Desktop-packages] [Bug 2036373] [NEW] package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
Public bug reported: I am attempting to install Zoom onto my laptop. Any assistance would be greatly appreciated. Thank you! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-bsd 2.3.1-9ubuntu1.5 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Date: Sun Sep 17 20:37:58 2023 DpkgHistoryLog: Start-Date: 2023-09-17 20:37:00 Requested-By: ned_land (1000) Install: libgcc1:amd64 (1:10.5.0-1ubuntu1~20.04) Upgrade: libwebp6:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), libcups2:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-server-common:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), libwebpdemux2:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), cups-ppdc:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), firefox-locale-en:amd64 (117.0+build2-0ubuntu0.20.04.1, 117.0.1+build2-0ubuntu0.20.04.1), libflac8:amd64 (1.3.3-1ubuntu0.1, 1.3.3-1ubuntu0.2), cups-daemon:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-client:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5) DuplicateSignature: package:cups-bsd:2.3.1-9ubuntu1.5 Setting up cups (2.3.1-9ubuntu1.5) ... Updating PPD files for cups ... dpkg: error processing package cups-bsd (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-07 (1105 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for HP_OfficeJet_Pro_6970_BE52B8_: implicitclass://HP_OfficeJet_Pro_6970_BE52B8_/ MachineType: LENOVO 80XS Papersize: letter PpdFiles: HP_OfficeJet_Pro_6970_BE52B8_: HP OfficeJet Pro 6970, driverless, cups-filters 1.27.4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=7dbb25c2-5410-4536-83ab-b1e2505c1318 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=7dbb25c2-5410-4536-83ab-b1e2505c1318 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: cups Title: package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN18WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvr5QCN18WW:bd07/13/2017:br1.18:efr1.18:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2036373 Title: package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: New Bug description: I am attempting to install Zoom onto my laptop. Any assistance would be greatly appreciated. Thank you! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-bsd 2.3.1-9ubuntu1.5 ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Date: Sun Sep 17 20:37:58 2023 DpkgHistoryLog: Start-Date: 2023-09-17 20:37:00 Requested-By: ned_land (1000) Install: libgcc1:amd64 (1:10.5.0-1ubuntu1~20.04) Upgrade: libwebp6:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), libcups2:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-server-common:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), libwebpdemux2:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), cups-ppdc:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), firefox-locale-en:amd64 (117.0+build2-0ubuntu0.20.04.1, 117.0.1+build2-0ubuntu0.20.04.1), libflac8:amd64 (1.3.3-1ubuntu0.1,
[Desktop-packages] [Bug 2012738] Re: language support crashes on install missing translations or writing aids
** Tags removed: rls-ll-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2012738 Title: language support crashes on install missing translations or writing aids Status in devscripts package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Bug description: Installing missing "translations or writing aids" crashes the gnome- language-selector app. I have attached a recording (sorry should have had capture cursor on) and relevant stack trace from journalctl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/2012738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@ BloodyIron It looks like the problem you are experiencing is the same issue as I have had. I think the reason that it works after you kill gvfsd-smb-browse is that your FreeNAS server is advertising itself via mDNS, and gvfsd will see that. You don't need SMB1 or WSDD for gvfsd to discover your NAS. But it is also looking for a "Windows Network" (i.e. the Windows "network neighborhood" or workgroup that shows up as a separate subfolder) using SMB1, and that fails if the server does not provide SMB1. Crucially, however, it fails in a way that leaves the gvfsd-smb-browse process in a bad state where it fails to allow browsing of the server even though it has been discovered via mDNS. I encourage you to take a look at my patch, or to use the PPA at https://launchpad.net/~wmaddox3rd/+archive/ubuntu/gvfs-smb-sharelist- patch. It does indeed look like there is a bug here in that attempting discovery via SMB1 somehow breaks browsing of the server discovered via mDNS. See also my remarks here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/307#note_1632096 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011722] [NEW] Move oem-config-setup steps into ubuntu-raspi-settings-desktop
Public bug reported: When building images with livecd-rootfs, there is a hook to set up oem- config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2011722 Title: Move oem-config-setup steps into ubuntu-raspi-settings-desktop Status in ubuntu-settings package in Ubuntu: New Bug description: When building images with livecd-rootfs, there is a hook to set up oem-config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
You select your kernel in the grub boot menu. There is an option for alternative boot configurations. I have a dual boot environment set up so grub comes up every time for me. I think you hit esc to bring it up if it normally boots straight into windows. If you have any trouble it should come up in a search pretty quick. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Booting with linux-image-5.19.0-35-generic appears to be the problem in 22.10. Booting with linux-image-5.19.0-21-generic lists the audio devices again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
This issue is also present in 22.10. After the update broke audio, I reinstalled 22.10 from a live usb which fixed the issue until I updated again and the issue reappeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008999] Re: User-Agent change breaks sniffing on e.g. meet.google.com
As a workaround, install a User-Agent switcher extension (e.g. https://chrome.google.com/webstore/detail/user-agent-switcher- for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg) and set a value closer to the old one, e.g. "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2008999 Title: User-Agent change breaks sniffing on e.g. meet.google.com Status in chromium-browser package in Ubuntu: Confirmed Bug description: Not sure whether this has been already reported: --- Google Drive is rendered in a weird way, see attached file. Google Meet is telling me "Meet doesn't work on your browser" What steps will reproduce the problem? * Update chromium with `snap refresh chromium` from 110.0.5481.100 to 110.0.5481.177 * Open Google Drive/Google Meet What happens instead? * No proposals for files during search in Google Drive * Old-fashioned look & feel (See screenshot) * Google Meet is telling me: "Meet doesn't work on your browser" uname -a Linux frn-xps-15 5.19.0-31-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 20 15:20:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 snap list chromium --all Name Version Rev Tracking Publisher Notes chromium 110.0.5481.100 2333 latest/stable canonical✓ disabled chromium 110.0.5481.177 2356 latest/stable canonical✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009005] Re: snap version 110.0.5481.177 cant open meets and calendar seems broken
*** This bug is a duplicate of bug 2008999 *** https://bugs.launchpad.net/bugs/2008999 ** This bug has been marked a duplicate of bug 2008999 User-Agent change breaks sniffing on e.g. meet.google.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2009005 Title: snap version 110.0.5481.177 cant open meets and calendar seems broken Status in chromium-browser package in Ubuntu: New Bug description: With the latest version of chromium snap 110.0.5481.177 installed yesterday I am no longer able to use google meet or view my google calendar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2009005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008999] Re: User-Agent change breaks sniffing on e.g. meet.google.com
This is because of https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?h=stable=42ed9c6a14ae9631d0a200dff1674e60560a3d28, which inserted "Ubuntu; " inside the "X11; Linux" part of the User-Agent that lots of services sniff. ** Package changed: ubuntu => chromium-browser (Ubuntu) ** Tags added: snap ** Tags added: regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2008999 Title: User-Agent change breaks sniffing on e.g. meet.google.com Status in chromium-browser package in Ubuntu: New Bug description: Not sure whether this has been already reported: --- Google Drive is rendered in a weird way, see attached file. Google Meet is telling me "Meet doesn't work on your browser" What steps will reproduce the problem? * Update chromium with `snap refresh chromium` from 110.0.5481.100 to 110.0.5481.177 * Open Google Drive/Google Meet What happens instead? * No proposals for files during search in Google Drive * Old-fashioned look & feel (See screenshot) * Google Meet is telling me: "Meet doesn't work on your browser" uname -a Linux frn-xps-15 5.19.0-31-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 20 15:20:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 snap list chromium --all Name Version Rev Tracking Publisher Notes chromium 110.0.5481.100 2333 latest/stable canonical✓ disabled chromium 110.0.5481.177 2356 latest/stable canonical✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007052] [NEW] package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned erro
Public bug reported: crash occurred during 18.04 -> 20.04 do-release-upgrade, transition from dpkg/deb to snap install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-137.154~18.04.1-generic 5.4.218 Uname: Linux 5.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 DRM.card0-Virtual-1: enabled: enabled dpms: On status: connected edid-base64: modes: preferred 1152x864 1024x768 800x600 640x480 DRM.card0-Virtual-2: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-3: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-4: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-5: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-6: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-8: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Mon Feb 13 01:03:59 2023 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-11-04 (2657 days ago) InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) InstalledPlugins: Load-Avg-1min: 0.71 Load-Processes-Running-Percent: 0.3% Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-137-generic root=UUID=152d5d4a-70ca-4be1-a626-b450c2b7965b ro Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-02-13 (0 days ago) dmi.bios.date: 06/25/2021 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.18227214.B64.2106252220 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007052 Title: package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: crash occurred during 18.04 -> 20.04 do-release-upgrade, transition from dpkg/deb to snap install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-137.154~18.04.1-generic 5.4.218 Uname: Linux 5.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 DRM.card0-Virtual-1: enabled: enabled dpms: On status: connected edid-base64: modes: preferred 1152x864 1024x768 800x600 640x480 DRM.card0-Virtual-2: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-3: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-4: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-5: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-6: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-8: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Mon Feb 13 01:03:59 2023 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None'
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Inspired by BloodyIron's comments above, I investigated this issue and was able to develop a patch that solves this problem for my use case: browsing NAS devices running TrueNAS and OpenMediaVault. It appears that the gvfsd-smb-browse process is left in a bad state after attempting to mount a workgroup, which occurs either when attempting to open an URL like smb://WORKGROUP/ or during network discovery in gvfsd- network. My patch simply disables workgroup discovery/browsing functionality, leaving *browsing* functionality intact for servers that are *discovered* via DNS-SD (mDNS). This does not address the issue of discovering Windows 10 servers that advertise themselves only via WS- Discovery, but appears to work fine for devices that advertise themselves using mDNS, allowing those devices to be successfully browsed. I note that workgroups are an obsolete concept in a post-NT1 (post-SMB1) world, so the offending code should eventually just be yanked out, along with the addition of support for WS-Discovery in Linux. My patch does not address the root cause, as whatever is going wrong while attempting to mount a workgroup should result in a recoverable error. I traced gvfsbackendsmbbrowse.c:do_mount() up to the point at which smbc_opendir() is called without any surprises, whereupon things went south. I did not investigate any further, but if I were to do so, I'd be inclined to take a look for an unreleased lock. ** Patch added: "Disable broken workgroup discovery/browsing" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107/+attachment/5639041/+files/smb-browse-patch.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Hi, I just wanted to say that I am also having this problem. I'm on Ubuntu 22.04 LTS with all of the available updates applied. In the attached screenshot, you'll see my terminal window as being underneath the Dock, which I didn't have it like that originally. It tends to happen after unlocking the screen. I do not have the Dock set to use the Auto-hide mode and I've tried using the Dock in both panel and non-panel mode. This bug is super annoying as I need to click the "Restore Down" and then "Maximize" in the window controls in each affected application window to get them fixed temporarily. --William ** Attachment added: "Terminal window underneath the Dock now. Ugh." https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961508/+attachment/5626231/+files/Screenshot%20from%202022-10-23%2016-34-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Same issue with a HP envy 15-ew0 Alder Lake-P and Realtek ALC245. I have tried kernels 5.15, 5.19, 6 and 6.1 RC. I have tried Ubuntu 22.10, 22.04, Linux Mint 21, popOS and fedora 36. Speakers do not work on any of them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490
@arutyun-akopov, can you try the workaround detailed in comment #1? ** Changed in: systemd (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1896540 Title: Incorrectly specified Touchpad size for Lenovo T490 Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Bug description: The vertical sensitivity of the touchpad on my laptop Lenovo T490 seemed significantly higher than the horizontal sensitivity. After doing some research I found out that the touchpad size is incorrectly listed by the kernel. Touchpad size listed by the kernel: 77x107mm The real size of the touchpad: 68x100mm Description: Ubuntu 20.04.1 LTS Release: 20.04 Systemd version: 245.4-4ubuntu3.2 Output from the touchpad-edge-detector: miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 /dev/input/event5 Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5 Move one finger around the touchpad to detect the actual edges Kernel says: x [1266..5678], y [1162..4694] Touchpad sends: x [1266..5678], y [1161..4694] -^C Touchpad size as listed by the kernel: 77x107mm User-specified touchpad size: 68x100mm Calculated ranges: 4412/3533 Suggested udev rule: # evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:* EVDEV_ABS_00=1266:5678:65 EVDEV_ABS_01=1161:4694:35 EVDEV_ABS_35=1266:5678:65 EVDEV_ABS_36=1161:4694:35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1896540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
I think the whole concept of numeric security "levels" is wrong. Instead there should be a list of threats: - physical (address by using LUKS, disabling USB ports, locking screen after N minutes inactivity, etc) - bad apps (address by enabling AppArmor or SELinux etc, using Snaps or Flatpaks, using fewer PPAs, doing updates, etc) - OS vulns (address by doing updates) - network attacks (address by enabling firewall on computer, enabling firewall in router, turning off unused services, blockers in browser, etc) - user mistakes (address by not running as root, using immutable OS, etc) And I would lump in some partially-security things too: - data loss due to hardware failure or user error (backups: suggest TimeShift etc) - network security/privacy attacks (suggest VPN) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Huh, interesting. When I hover my cursor over the sound widgit in my top panel bar, it says: Output: 100% 0.00 dB Built-in Audio Analog Stereo And it says this even when I have something playing that ought to be outputting sound. Doesn't 0.00 db mean silence? Reading this now to find out what I can: https://sound.stackexchange.com/questions/25529/what-is-0-db-in-digital- audio -- "So audio meters don't show the dBu, dBV or dBFS level of the signal (some do, but as an extra). Instead they show 0dB as the standard operating level of the system." Oddly fascinating read. I had no idea that decibels were coined in relation to Bell labs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Re:^^^ Oh, and I have the soundcard: Realtek ALC269VB Analog, also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Hi, This sounds similar to my bug. I am pretty sure my physical speakers work, and even that they worked when I first installed Ubuntu Mate 22.04, but very shortly afterwards they stopped working. The headphone jack also doesn't work. I installed a jack-detection repo and now sometimes (not constantly) the headphones will shoot out max volume white noise. Here is my Alsa info: http://alsa- project.org/db/?f=608937f066095ec6710e5f3bafc292815da99414 I've been trying to fix this problem for a couple weeks now. I've followed different blogs on similar topics and read through various solutions to similar problems posted on launchpad or stackoverflow. Any help would be greatly appreciated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769116] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'
I am seeing this after CDROM read errors of audio CDs using rhythmbox on Ubuntu
20.04 with an Nvidia video card.
After that, rhythmbox fails to start, adding this complaint to /var/log/syslog,
and cannot be restarted without logging off or rebooting.
Nearby syslog entries appended.
Mar 13 08:56:29 wedgingt kernel: [121925.744832] ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 13 08:56:29 wedgingt kernel: [121925.744838] ata2.00: cmd
a0/01:00:00:10:f8/00:00:00:00:00/a0 tag 15 dma 63504 in
Mar 13 08:56:29 wedgingt kernel: [121925.744838] Volume set (in), Read
cd be 00 00 05 56 a2 00 00 1b f8 00 00res 40/00:03:00:00:00/00:00:00:00:00/a0
Emask 0x4 (timeout)
Mar 13 08:56:29 wedgingt kernel: [121925.744839] ata2.00: status: { DRDY }
Mar 13 08:56:29 wedgingt kernel: [121925.744841] ata2: hard resetting link
Mar 13 08:56:30 wedgingt kernel: [121926.059355] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Mar 13 08:56:30 wedgingt kernel: [121926.064621] ata2.00: configured for
UDMA/100
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: scsi_read error:
sector=349858 length=27 retry=0
Mar 13 08:56:30 wedgingt kernel: [121926.065866] ata2: EH complete
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: Sense key:
5 ASC: 21 ASCQ: 4
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: Transport
error: Illegal SCSI request (rejected by target)
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: System
error: Invalid argument
Mar 13 08:57:20 wedgingt kernel: [121976.939509] ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 13 08:57:20 wedgingt kernel: [121976.939515] ata2.00: cmd
a0/01:00:00:70:77/00:00:00:00:00/a0 tag 19 dma 30576 in
Mar 13 08:57:20 wedgingt kernel: [121976.939515] Volume set (in), Read
cd be 00 00 05 56 a2 00 00 0d f8 00 00res 40/00:03:00:00:00/00:00:00:00:00/a0
Emask 0x4 (timeout)
Mar 13 08:57:20 wedgingt kernel: [121976.939516] ata2.00: status: { DRDY }
Mar 13 08:57:20 wedgingt kernel: [121976.939518] ata2: hard resetting link
Mar 13 08:57:21 wedgingt kernel: [121977.253940] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Mar 13 08:57:21 wedgingt kernel: [121977.259226] ata2.00: configured for
UDMA/100
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: scsi_read error:
sector=349858 length=13 retry=1
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: Sense key:
5 ASC: 21 ASCQ: 4
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: Transport
error: Illegal SCSI request (rejected by target)
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: System
error: Invalid argument
Mar 13 08:57:21 wedgingt kernel: [121977.260496] ata2: EH complete
Mar 13 08:57:29 wedgingt gnome-shell[3230]: Some code accessed the property
'discreteGpuAvailable' on the module 'appDisplay'. That property was defined
with 'let' or 'const' inside the module. This was previously supported, but is
not correct according to the ES6 standard. Any symbols to be exported from a
module must be defined with 'var'. The property access will work as previously
for the time being, but please fix your code anyway.
Mar 13 08:57:29 wedgingt gnome-shell[3230]:
../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation()
function can only be called from within the implementation of the
ClutterActor::allocate() virtual function.
Mar 13 08:57:30 wedgingt systemd[2994]: Started Application launched by
gnome-shell.
Mar 13 08:57:30 wedgingt gnome-shell[1803751]: gio: cdda://sr0/: mount
doesn�~@~Yt implement �~@~\eject�~@~] or �~@~\eject_with_operation�~@~]
Mar 13 08:57:30 wedgingt systemd[2994]: gnome-launched-gio-1803751.scope:
Succeeded.
Mar 13 08:58:12 wedgingt kernel: [122028.146104] ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 13 08:58:12 wedgingt kernel: [122028.146110] ata2.00: cmd
a0/01:00:00:20:37/00:00:00:00:00/a0 tag 16 dma 14112 in
Mar 13 08:58:12 wedgingt kernel: [122028.146110] Volume set (in), Read
cd be 00 00 05 56 a2 00 00 06 f8 00 00res 40/00:03:00:00:00/00:00:00:00:00/a0
Emask 0x4 (timeout)
Mar 13 08:58:12 wedgingt kernel: [122028.146111] ata2.00: status: { DRDY }
Mar 13 08:58:12 wedgingt kernel: [122028.146113] ata2: hard resetting link
Mar 13 08:58:12 wedgingt kernel: [122028.460550] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Mar 13 08:58:12 wedgingt kernel: [122028.465458] ata2.00: configured for
UDMA/100
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: scsi_read error:
sector=349858 length=6 retry=2
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: Sense key:
5 ASC: 21 ASCQ: 4
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: Transport
error: Illegal SCSI request (rejected by target)
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: System
error: Invalid argument
Mar 13 08:58:12 wedgingt kernel:
[Desktop-packages] [Bug 1960458] [NEW] patch git_socket_dir.patch causing FTBFS in gspell
Public bug reported: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: New Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
Test Case 3 verification ubuntu@focalvm:~$ apt-cache policy ghostscript ghostscript: Installed: 9.50~dfsg-5ubuntu4.4 Candidate: 9.50~dfsg-5ubuntu4.4 Version table: *** 9.50~dfsg-5ubuntu4.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 9.50~dfsg-5ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 9.50~dfsg-5ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@focalvm:~$ gs waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 4000 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4308816 2840291 2772400 1477426 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3041706 2792600 1499350 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 28 18 282 764 %%HiResBoundingBox: 28.547999 18.251999 281.375991 763.055977 >>showpage, press to continue<< GS>quit ubuntu@focalvm:~$ echo $? 0 ubuntu@focalvm:~$ gs -r300x300 -sPAPERSIZE=letter -sOUTPUTFILE=waterfal.jpg -dNOPAUSE -dBATCH waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 300 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4329016 2846189 1581112 279688 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3044172 1601312 301839 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 22 18 282 763 %%HiResBoundingBox: 22.080001 18.240001 281.520011 762.960029 ubuntu@focalvm:~$ echo $? 0 ubuntu@focalvm:~$ gs -r300x300 -sPAPERSIZE=letter -sOUTPUTFILE=waterfal.jpg -dNOPAUSE -dBATCH -- waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 300 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4329016 2848173 1581112 279944 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3046156 1601312 302095 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 22 18 282 763 %%HiResBoundingBox: 22.080001 18.240001 281.520011 762.960029 ubuntu@focalvm:~$ echo $? 0 ubuntu@focalvm:~$ ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. Test Plan 2 -- * Run ocrfeeder from a terminal * Click File -> Import PDF * Select a PDF file * Note that no pages are displayed, and ocrfeeder throws a "Permission denied" error in the
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
Test showing the failure with ocrfeeder before installing from -proposed ** Attachment added: "gs_test2_fail_case.png" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5542883/+files/gs_test2_fail_case.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. Test Plan 2 -- * Run ocrfeeder from a terminal * Click File -> Import PDF * Select a PDF file * Note that no pages are displayed, and ocrfeeder throws a "Permission denied" error in the terminal from which it was launched * Install ghostscript from -proposed * Run ocrfeeder from a terminal and attempt to import the PDF file again * Note that the pages of the PDF are displayed in ocrfeeder and no error is reported in the terminal - Test Plan 3 --- * Using the version of ghostscript in -proposed, run a variety of different commands to ensure there has been no regression. * gs * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH -- [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
Test showing ocrfeeder succeeding with the version of ghostscript in -proposed ** Attachment added: "gs_test2_success_casae.png" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5542884/+files/gs_test2_success_casae.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. Test Plan 2 -- * Run ocrfeeder from a terminal * Click File -> Import PDF * Select a PDF file * Note that no pages are displayed, and ocrfeeder throws a "Permission denied" error in the terminal from which it was launched * Install ghostscript from -proposed * Run ocrfeeder from a terminal and attempt to import the PDF file again * Note that the pages of the PDF are displayed in ocrfeeder and no error is reported in the terminal - Test Plan 3 --- * Using the version of ghostscript in -proposed, run a variety of different commands to ensure there has been no regression. * gs * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH * gs -r300x300 -sPAPERSIZE=letter \ -sOUTPUTFILE=waterfal.jpg \ -dNOPAUSE -dBATCH -- [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
The verification passed for focal. --- Test case 1 verification ubuntu@focalvm:~$ apt-cache policy ghostscript ghostscript: Installed: 9.50~dfsg-5ubuntu4.3 Candidate: 9.50~dfsg-5ubuntu4.4 Version table: 9.50~dfsg-5ubuntu4.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages *** 9.50~dfsg-5ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 9.50~dfsg-5ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@focalvm:~$ gs -- waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Error: /undefinedfilename in (waterfal.ps) Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push Dictionary stack: --dict:724/1123(ro)(G)-- --dict:0/20(G)-- --dict:76/200(L)-- Current allocation mode is local Last OS error: Permission denied GPL Ghostscript 9.50: Unrecoverable error, exit code 1 ubuntu@focalvm:~$ sudo apt install ghostscript -y Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgs9 libgs9-common Suggested packages: ghostscript-x The following packages will be upgraded: ghostscript libgs9 libgs9-common 3 upgraded, 0 newly installed, 0 to remove and 33 not upgraded. Need to get 2,906 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 ghostscript amd64 9.50~dfsg-5ubuntu4.4 [51.8 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libgs9 amd64 9.50~dfsg-5ubuntu4.4 [2,173 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libgs9-common all 9.50~dfsg-5ubuntu4.4 [682 kB] Fetched 2,906 kB in 1s (4,127 kB/s) (Reading database ... 214058 files and directories currently installed.) Preparing to unpack .../ghostscript_9.50~dfsg-5ubuntu4.4_amd64.deb ... Unpacking ghostscript (9.50~dfsg-5ubuntu4.4) over (9.50~dfsg-5ubuntu4.3) ... Preparing to unpack .../libgs9_9.50~dfsg-5ubuntu4.4_amd64.deb ... Unpacking libgs9:amd64 (9.50~dfsg-5ubuntu4.4) over (9.50~dfsg-5ubuntu4.3) ... Preparing to unpack .../libgs9-common_9.50~dfsg-5ubuntu4.4_all.deb ... Unpacking libgs9-common (9.50~dfsg-5ubuntu4.4) over (9.50~dfsg-5ubuntu4.3) ... Setting up libgs9-common (9.50~dfsg-5ubuntu4.4) ... Setting up libgs9:amd64 (9.50~dfsg-5ubuntu4.4) ... Setting up ghostscript (9.50~dfsg-5ubuntu4.4) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for man-db (2.9.1-1) ... ubuntu@focalvm:~$ gs -- waterfal.ps GPL Ghostscript 9.50 (2019-10-15) Copyright (C) 2019 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Creating waterfall printout at 4000 DPI. Loading NimbusMonoPS-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusMonoPS-Regular... 4308816 2842275 2772400 1477640 2 done. /Courier 6 7 8 9 10 11 12 14 16 /HelveticaLoading NimbusSans-Regular font from /usr/share/ghostscript/9.50/Resource/Font/NimbusSans-Regular... 4395128 3043690 2792600 1499460 3 done. 6 7 8 9 10 11 12 14 16 %%BoundingBox: 28 18 282 764 %%HiResBoundingBox: 28.547999 18.251999 281.375991 763.055977 >>showpage, press to continue<< ubuntu@focalvm:~$ ** Description changed: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. - In addition see
[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"
racb: In order to add the steps from comment #2 as a useful test case, another bug in ocrfeeder needed to be fixed with an SRU. See https://bugs.launchpad.net/ubuntu/+source/ocrfeeder/+bug/1890013 for more details. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: `gs [options] -- ` fails with "permission denied" Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: Fix Committed Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Plan] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. In addition see comment 6 and comment 2 for two more items in the test plan. -- ~racb [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
This bug appears to also exist in hirsute. Could you prepare a debdiff for hirsute as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Here I am, trying to use headless Chromium to render screenshots, and on Ubuntu 20.04, I find that Chromium is simply not writing to `/tmp`. So, let me add my voice to the chorus of those flummoxed and frustrated by this decision. The easiest way to get around this appears to be to install Chromium from an unofficial PPA. Ironic, given the intent of "improved security". As they say, security at the expense of usability comes at the expense of security. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Invalid Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Reupload to fix s/hplib/hplip/ typo in changelog ** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537488/+files/lp1938442_bionic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Reupload to fix s/hplib/hplip/ typo in changelog ** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537487/+files/lp1938442_impish.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537375/+files/lp1938442_impish.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537379/+files/lp1938442_bionic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Focal debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537378/+files/lp1938442_focal.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Hirsute debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537377/+files/lp1938442_hirsute.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537376/+files/lp1938442_impish.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Description changed: + [Impact] + * The directory ~/.hplip/.gnupg is readable by non-root users + * This directory contains only public keys, but should still + have the permissions changed to 700 for privacy reasons + + [Test Case] + * Install hplip and run `hp-plugin -i` + * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x + * rm -rf ~/.hplip and install hplip from -proposed + * run `hp-plugin -i` again + * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- + + [Regression Potential] + * Because of file permissions becoming more restrictive, + it is possible that some other hplip binaries would + fail to read the .gnupg directory + * To ensure this isn't the case, testing should be done + on different hplip use-cases to ensure they still + function properly + + [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. ** Patch added: "Jammy debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537374/+files/lp1938442_jammy.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: Fix for Ghostscript 9.50 upstream bug needs to be back-ported
** Patch added: "lp1913656.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+attachment/5532989/+files/lp1913656.debdiff ** Changed in: ghostscript (Ubuntu Focal) Assignee: Till Kamppeter (till-kamppeter) => William Wilson (jawn-smith) ** Changed in: ghostscript (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: Fix for Ghostscript 9.50 upstream bug needs to be back-ported Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: In Progress Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Case] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913656] Re: Fix for Ghostscript 9.50 upstream bug needs to be back-ported
** Tags added: verification-needed verification-needed-focal ** Description changed: - Ghostscript 9.50 exhibits - https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co - options) which causes (eg) ocrfeeder to fail to load PDF files: an input - file specified using the "... -- filename ..." command line syntax has - no read permission in the GS interpreter. + [Impact] + * The command line syntax `gs [options] -- ` fails +to load in the input file with a "permission denied" error. + * Per the ghostscript documentation, the `--` syntax is used as follows: + "-- filename arg1 ... +Takes the next argument as a file name as usual, +but takes all remaining arguments (even if they +have the syntactic form of switches) and defines +the name ARGUMENTS in userdict (not systemdict) +as an array of those strings, before running the +file. When Ghostscript finishes executing the file, +it exits back to the shell." + + [Test Case] + -- to be performed in a desktop environment -- + * Obtain a valid input file for ghostscript. The Source package +contains an `examples/` directory with plenty to choose from. + * `gs -- ` + * Observe that the test failed with a "permission denied" error. + * Install the version of ghostscript from focal-proposed. + * `gs -- ` + * Observe that the command succeeds and a ghostscript window. +appears with the output of the `gs` command. + + [Regression Potential] + * Since this patch affects command line processing, it is possible +that other arguments or command line syntaxes could be affected. + + [Original Description] + Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1913656 Title: Fix for Ghostscript 9.50 upstream bug needs to be back-ported Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Focal: In Progress Bug description: [Impact] * The command line syntax `gs [options] -- ` fails to load in the input file with a "permission denied" error. * Per the ghostscript documentation, the `--` syntax is used as follows: "-- filename arg1 ... Takes the next argument as a file name as usual, but takes all remaining arguments (even if they have the syntactic form of switches) and defines the name ARGUMENTS in userdict (not systemdict) as an array of those strings, before running the file. When Ghostscript finishes executing the file, it exits back to the shell." [Test Case] -- to be performed in a desktop environment -- * Obtain a valid input file for ghostscript. The Source package contains an `examples/` directory with plenty to choose from. * `gs -- ` * Observe that the test failed with a "permission denied" error. * Install the version of ghostscript from focal-proposed. * `gs -- ` * Observe that the command succeeds and a ghostscript window. appears with the output of the `gs` command. [Regression Potential] * Since this patch affects command line processing, it is possible that other arguments or command line syntaxes could be affected. [Original Description] Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894 (fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF files: an input file specified using the "... -- filename ..." command line syntax has no read permission in the GS interpreter. This commit fixes it: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410 GS 9.52 includes the commit. Either apply the fix from the linked commit in the Focal-Updates version, or upgrade it to 9.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1913656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
We've found that this bug is much easier to create on certain monitors. satmandu, dnoedelfan: what monitors are you using? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: HDMI does not display anything with Impish RPi desktop image Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Invalid Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-firmware-raspi2 source package in Impish: Confirmed Status in linux-raspi source package in Impish: Fix Committed Status in mutter source package in Impish: Invalid Bug description: [ Impact ] The desktop does not come up and the screen stays blank when using 'dtoverlay=vc4-kms-v3d' on a Pi 4 (as is the case in raspi desktop images). If the desktop does come up, playing video freezes the desktop and/or the system. The kernel log shows loads of WARNINGs and potentially firmware errors. [ Test Case ] Use a raspi desktop image, play video (youtube or VLC), move windows around, switch to and from fullscreen video playback. [ Where problems could occur ] The fixes are all local to the VC4 driver so (new) issues should only show up when that driver is in use. Potential problems are UI freezes, kernel stalls and crashes. [ Original Description ] Workaround -- With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt Original Description Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
linux-raspi/5.11.0-1021.22 does not fix this problem. I am still seeing the flip_done timed out error message. ** Tags removed: verification-needed-hirsute ** Tags added: verification-failed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: HDMI does not display anything with Impish RPi desktop image Status in linux-firmware-raspi2 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Invalid Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-firmware-raspi2 source package in Impish: Confirmed Status in linux-raspi source package in Impish: Fix Committed Status in mutter source package in Impish: Invalid Bug description: [ Impact ] The desktop does not come up and the screen stays blank when using 'dtoverlay=vc4-kms-v3d' on a Pi 4 (as is the case in raspi desktop images). If the desktop does come up, playing video freezes the desktop and/or the system. The kernel log shows loads of WARNINGs and potentially firmware errors. [ Test Case ] Use a raspi desktop image, play video (youtube or VLC), move windows around, switch to and from fullscreen video playback. [ Where problems could occur ] The fixes are all local to the VC4 driver so (new) issues should only show up when that driver is in use. Potential problems are UI freezes, kernel stalls and crashes. [ Original Description ] Workaround -- With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt Original Description Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
This was fixed previously in hirsute by an upstream merge that resulted in bluez 5.56-0ubuntu1 ** Changed in: bluez (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: bluez (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Groovy: Won't Fix Status in bluez source package in Hirsute: Fix Released Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
Seb, I have made a PR in the github repo. This PR also pulls in the
changes in version 1.6.3, which were previously not present.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
Confirmed
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
Attached is a patch to add the hwcap metric to ubuntu-report.
** Patch added: "lp1922712.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+attachment/5485728/+files/lp1922712.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
New
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
Status in ubuntu-report package in Ubuntu:
New
Bug description:
we want to collect information which most recent hwcap is supported by
a machine. The result should be a string like "x86-64-v2",
"x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
linux --help" output. The string should be empty for architectures
without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
string should be empty if no specific hwcaps is supported (e.g. on a
power8 machine). The string should be "N/A" (not available), when
trying to run ld-linux on a release with glibc (<< 2.33).
Note that lexical sorting won't work for "p9", "p10".
if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
fi
supported=
if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk
'/supported/ {print $1}')
fi
Here, $supported has listed all supported hwcaps, not just the best
supported one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922792] [NEW] Bluez should notify users when they need to reboot to apply changes
Public bug reported: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes Status in bluez package in Ubuntu: New Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915565] [NEW] screen fades for about 10 seconds glslideshowthen returns to normal
Public bug reported: The fading happens online at . But it also happens offline in games. Using Ubuntu 20.04 Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 12 13:14:56 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:820c] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820c] InstallationDate: Installed on 2017-04-14 (1400 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0eef:c04d D-WAV Scientific Co., Ltd eGalaxTouch EXC3000-0367-44.01.00 Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc. HP Wide version HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=07e929a4-0ebf-4ecc-bedd-3f5fbf79e6d8 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820C dmi.board.vendor: HP dmi.board.version: 82.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd09/21/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820C:rvr82.29:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: X0S49UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Oct 17 14:45:19 2020 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915565 Title: screen fades for about 10 seconds glslideshowthen returns to normal Status in xorg package in Ubuntu: New Bug description: The fading happens online at . But it also happens offline in games. Using Ubuntu 20.04 Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 12 13:14:56 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA
[Desktop-packages] [Bug 1909352] Re: (1) video hangs or (2) screen goes blank and case fan turns on
Another error state is monitors stay black with cooling fan(s) at normal slow speed. This has happened after the screens go dark from inactivity. Such as monitors in power saving mode. Press enter key, monitors stay dark. Again use reset switch on case to restart system. Do not recall this behavior before update to Ubuntu 20.04.1 LTS. Good thing Chrome is good at recovering open tabs and windows. :). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909352 Title: (1) video hangs or (2) screen goes blank and case fan turns on Status in xorg package in Ubuntu: New Bug description: Recover system by press and release reset switch. Log in again. Had these issues with Ubuntu 18.04. Updated to Nvidia drivers and issues resolved. Updated to 20.04.1 and issues have returned. Checked and see that Nvidia drivers newer than those packaged for use. Available at Nvidia / Newest package and in use: GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.45 - Release Date: Tue Nov 17, 2020 GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.38 - Release Date: Thu Oct 29, 2020 Hopefully the command ubuntu-bug xorg attached all the information you may need. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 09:54:40 2020 DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-56-generic, x86_64: installed nvidia, 455.38, 5.4.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2018-03-03 (1029 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago) dmi.bios.date: 08/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Desktop-packages] [Bug 1909352] [NEW] (1) video hangs or (2) screen goes blank and case fan turns on
Public bug reported: Recover system by press and release reset switch. Log in again. Had these issues with Ubuntu 18.04. Updated to Nvidia drivers and issues resolved. Updated to 20.04.1 and issues have returned. Checked and see that Nvidia drivers newer than those packaged for use. Available at Nvidia / Newest package and in use: GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.45 - Release Date: Tue Nov 17, 2020 GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.38 - Release Date: Thu Oct 29, 2020 Hopefully the command ubuntu-bug xorg attached all the information you may need. $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 09:54:40 2020 DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-56-generic, x86_64: installed nvidia, 455.38, 5.4.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2018-03-03 (1029 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago) dmi.bios.date: 08/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Dec 26 08:48:35 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909352 Title: (1) video hangs or (2) screen goes blank and case fan turns on Status in xorg package in Ubuntu: New Bug description: Recover system by press and release reset switch. Log in again. Had these issues with Ubuntu 18.04. Updated to Nvidia drivers and issues resolved. Updated to 20.04.1 and
[Desktop-packages] [Bug 1903723] [NEW] Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek AL
Public bug reported: Audio dropouts and general surround sound issues. Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info card: 1 device: 0 subdevice: 0 stream: CAPTURE id: ALC887-VD Analog name: ALC887-VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350 Gaming 3) Specifications. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: billy 9531 F pulseaudio /dev/snd/controlC2: billy 9531 F pulseaudio /dev/snd/controlC1: billy 9531 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 15:05:30 2020 InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Nov 10 14:37:41 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Nov 10 14:37:43 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.41' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Nov 10 14:57:06 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.341' (uid=1000 pid=9531 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-10T14:56:54.599621 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903723 Title: Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Audio dropouts and general surround sound issues. Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info card: 1 device: 0 subdevice: 0 stream: CAPTURE id: ALC887-VD Analog name: ALC887-VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350 Gaming 3) Specifications. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: billy 9531 F pulseaudio /dev/snd/controlC2: billy 9531 F pulseaudio /dev/snd/controlC1: billy 9531 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 15:05:30 2020 InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver
[Desktop-packages] [Bug 1901213] [NEW] I'm a novice
Public bug reported: Just following the popup pages Updates will not install hence why I am here on my journey Also trying to find out how to back up Thunderbird externally as want to reinstall Ubuntu after using for 6 years and cannot update because of This report: Software updater : The package is broken window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 23 11:22:12 2020 DistUpgraded: 2018-06-30 14:29:00,147 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2014-09-23 ( days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=0eaecf29-797f-4744-9015-4ef391a04f60 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-30 (845 days ago) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: 502420 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd02/24/2011:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 28 08:24:17 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1901213 Title: I'm a novice Status in xorg package in Ubuntu: New Bug description: Just following the popup pages Updates will not install hence why I am here on my journey Also trying to find out how to back up Thunderbird externally as want to reinstall Ubuntu after using for 6 years and cannot update because of This report: Software updater : The package is broken window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 23 11:22:12 2020 DistUpgraded: 2018-06-30 14:29:00,147 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2014-09-23 ( days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
[Desktop-packages] [Bug 1893311] Re: Add libcurl4-openssl-dev build-dep for lumix camlib
This is now fixed in Debian as of 2.5.26-1 https://salsa.debian.org /debian-phototools-team/libgphoto2/-/merge_requests/3 ** Changed in: libgphoto2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgphoto2 in Ubuntu. https://bugs.launchpad.net/bugs/1893311 Title: Add libcurl4-openssl-dev build-dep for lumix camlib Status in libgphoto2 package in Ubuntu: Fix Released Bug description: The lumix camlib is in a somewhat usable state (https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully using it for a few months. It would be good to add the libcurl4-openssl-dev to Build-Depends to enable building the lumix camlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1893311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898416] [NEW] Wine failed to install
Public bug reported: ubuntu 20.04 Tried to download wine from store, download failed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Oct 4 18:32:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libvdpau1:(not installed) Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-rmJMEd/144-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack): trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1462:7a40] MachineType: Micro-Star International Co., Ltd. MS-7A40 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=c257c1a8-59c6-4967-add4-929a999d1246 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libvdpau Title: package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.70:bd07/10/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libvdpau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1898416 Title: Wine failed to install Status in libvdpau package in Ubuntu: New Bug description: ubuntu 20.04 Tried to download wine from store, download failed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Oct 4 18:32:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libvdpau1:(not installed) Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-rmJMEd/144-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack): trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1462:7a40] MachineType: Micro-Star International Co., Ltd. MS-7A40 ProcKernelCmdLine:
[Desktop-packages] [Bug 1898072] Re: no sound
continue to ponder pavucontrol and now udev. my clean install ubuntu 20 lts did not find my built-in audio so i have posted to the bug site hoping you will have previously sorted this. i am guessing udev is not finding sound setup, did not correctly populate alsa and is currently not correctly populating pavucontrol setttings. i do not want to start editing conf files using pacmd. really wanted a strategy that would automatically repopulate the settings. i am just experienced enough to brick this install...a bad thing. i realize you are sorting out issues for the greater population. ubuntu 20 lts is almost completely functional. i can manually configure gui pavucontrol on each start and go on with life. i have a week's worth of data and config under my belt and do not intend to restore my clone or investigate other flavors linux. the previous 4 years of ubuntu 16 lts was not without its quirks...and the decades of windoze, mac and even in late 80's an ibm pc. i no longer have to deal with vertical market software for the architctural industry and have fully converted all my office apps to libreoffice. i don't want to be a weiner...i am a greyhair, retired and just tired of messing with confusers. hope my comments are useful as you continue to develop ubuntu 20lts. now for something completely different: national lampoon magazine from 1971 subscription ads "you may already be a weiner" and "buy this magazine or we will shoot the dog" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1898072 Title: no sound Status in alsa-driver package in Ubuntu: New Bug description: no sound issue 4 years using ubuntu 16.04. weekend 9.26.20 clean install ubuntu 20.04.01. planned 3 days install. day one clone and full ext hd backup all files. day two clean install, paste files and use clean system. all mostly works but no sound from prior working setup. day 3 troubleshoot sound, install new versions of apps from prior working system. seems no sound is a very common issue. ubuntu/settings/sound not showing my outup options, being locked to an hdmi ouput was baffling and i considered restoring my clone except for the 2 days of sucessfully transferring my files. i am satisfied the system is functional for my core uses so i will continue to try to work this sound issue. politely asking for advice from community. no shouting here and i do appreciate help. the following is my no sound experience on day 3 of clean install: ubuntu/settings/audio. only showed hdmi output device, everything else blank. online advice to search devices lspci: found my sound card 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) tried online advice: search pci devices kill alsa, reinstall kill pulseaudio, reinstall alsamixer: turned up/on everything, finally speaker feeback for alsamixer loopback setting so i knew sound was capable of something. pulseaudio, tried every random setting. finally the setting "analog surround 4.1 ouput + analog stereo input (unplugged) (unavailable)" setting worked normally thru my audio jacks. now pulseaudio does not save these settings thru shutdown. whaaa? relief! baffled. reluctant to touch anything else because it works...so far. went thru pulseaudio settings files, seems almost all options are commented out. i pasted these files at end this message. alsa mixer keeps settings. ubuntu/settings/audio still only shows hdmi output device, everything else blank. now i am considering online advice to kill and reset all pulseaudio. Reset PulseAudio If the system is not playing audio, first try reseting the pulseaudio daemon: systemctl --user restart pulseaudio Applications may need to be restarted. If this fails then try removing the user configuration files for PulseAudio: rm -r ~/.config/pulse Then, kill all instances of PulseAudio: pulseaudio -k When PulseAudio starts again (which it should do automatically), it will create new configuration files. https://support.system76.com/articles/audio/ sound output works if i manually reset pulseaudio after start. i am not confident to blast away or edit conf or daemon files. i would like working pulseaudio settings to survive restart and i would prefer ubuntu/settings/audio reflect actual settings. thanks in advance for suggestions/comments. following are existing pulseaudio files: ******** william@william-Studio-XPS-7100:/etc/pulse$ tree . ├── client.conf ├── client.conf.d │ └── 01-enable-autospawn.conf -> /run/pulseaudio-enable-autospawn ├── daemon.conf ├── default.pa └── system.pa This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify
[Desktop-packages] [Bug 1898072] [NEW] no sound
Public bug reported: no sound issue 4 years using ubuntu 16.04. weekend 9.26.20 clean install ubuntu 20.04.01. planned 3 days install. day one clone and full ext hd backup all files. day two clean install, paste files and use clean system. all mostly works but no sound from prior working setup. day 3 troubleshoot sound, install new versions of apps from prior working system. seems no sound is a very common issue. ubuntu/settings/sound not showing my outup options, being locked to an hdmi ouput was baffling and i considered restoring my clone except for the 2 days of sucessfully transferring my files. i am satisfied the system is functional for my core uses so i will continue to try to work this sound issue. politely asking for advice from community. no shouting here and i do appreciate help. the following is my no sound experience on day 3 of clean install: ubuntu/settings/audio. only showed hdmi output device, everything else blank. online advice to search devices lspci: found my sound card 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) tried online advice: search pci devices kill alsa, reinstall kill pulseaudio, reinstall alsamixer: turned up/on everything, finally speaker feeback for alsamixer loopback setting so i knew sound was capable of something. pulseaudio, tried every random setting. finally the setting "analog surround 4.1 ouput + analog stereo input (unplugged) (unavailable)" setting worked normally thru my audio jacks. now pulseaudio does not save these settings thru shutdown. whaaa? relief! baffled. reluctant to touch anything else because it works...so far. went thru pulseaudio settings files, seems almost all options are commented out. i pasted these files at end this message. alsa mixer keeps settings. ubuntu/settings/audio still only shows hdmi output device, everything else blank. now i am considering online advice to kill and reset all pulseaudio. Reset PulseAudio If the system is not playing audio, first try reseting the pulseaudio daemon: systemctl --user restart pulseaudio Applications may need to be restarted. If this fails then try removing the user configuration files for PulseAudio: rm -r ~/.config/pulse Then, kill all instances of PulseAudio: pulseaudio -k When PulseAudio starts again (which it should do automatically), it will create new configuration files. https://support.system76.com/articles/audio/ sound output works if i manually reset pulseaudio after start. i am not confident to blast away or edit conf or daemon files. i would like working pulseaudio settings to survive restart and i would prefer ubuntu/settings/audio reflect actual settings. thanks in advance for suggestions/comments. following are existing pulseaudio files: ******** william@william-Studio-XPS-7100:/etc/pulse$ tree . ├── client.conf ├── client.conf.d │ └── 01-enable-autospawn.conf -> /run/pulseaudio-enable-autospawn ├── daemon.conf ├── default.pa └── system.pa This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, see <http://www.gnu.org/licenses/>. ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; daemonize = no ; fail = yes ; allow-module-loading = yes ; allow-exit = yes ; use-pid-file = yes ; system-instance = no ; local-server-type = user ; enable-shm = yes ; enable-memfd = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; lock-memory = no ; cpu-limit = no ; high-priority = yes ; nice-level = -11 ; realtime-scheduling = yes ; realtime-priority = 5 ; exit-idle-time = 20 ; scache-idle-time = 20 ; dl-search-path = (depends on architecture) ; load-default-script-file = yes ; default-script-file = /etc/pulse/default.pa ; log-target = auto ; log-level = notice ; log-meta = no ; log-time = no ; log-backtrace = 0 ; resample-method = speex-float-1 ; avoid-resampling = false ; enable-remixing = yes ; remixing-use-all-sink-channels = yes ; remixing-produce-lfe = no ; remixing-consume-lfe = no ; lfe-crossover-freq = 0 ; flat-volumes = no ; rescue-streams = yes ; rlimit-fsize = -1 ; rlimit-data = -1 ; rlimit-stack = -1 ; rlimit-core = -1 ; rlimit-as = -1 ; rlimit-rss = -1 ; rlimit-nproc = -1 ; rlimit-nofile = 256 ; rlimit-me
[Desktop-packages] [Bug 1897856] [NEW] snap launch fails: symbol lookup error
Public bug reported: Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04: /snap/evince/532/usr/bin/evince: symbol lookup error: /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined symbol: gdk_pixbuf_init_modules ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897856 Title: snap launch fails: symbol lookup error Status in evince package in Ubuntu: New Bug description: Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04: /snap/evince/532/usr/bin/evince: symbol lookup error: /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined symbol: gdk_pixbuf_init_modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1897567] Re: webcam not initialized
issue fixed...i think. cheese: had to select a matching resolution to enable camera. webcam resolution was higher than default. still have to resolve my no sound issue...so common, there are very many possible alsa and alsa-pulseaudio related options. On 9/28/20 12:04 PM, Kai-Heng Feng wrote: > Nothing special from dmesg. Probably a bug in Cheese. > > ** Also affects: cheese (Ubuntu) > Importance: Undecided > Status: New > -- W.C. Backus, Architect Lexington, Ky backus.will...@gmail.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1897567 Title: webcam not initialized Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when usb camera was working. webcam not initialized in cheese from my generic usb anivia webcam webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:03:27 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 09:03:37.505: The udisks-daemon is running (name-owner :1.10). UpgradeSt
[Desktop-packages] [Bug 1897600] [NEW] PCI/internal sound card not detected
Public bug reported: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when sound was working. lspci lists all sources. internal intel ada card not intialized. only option in sound is hdmi. all worked before clean install. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] william@william-Studio-XPS-7100:~$ cat /proc/asound/cards 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe8f4000 irq 16 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfe9bc000 irq 26 william@william-Studio-XPS-7100:~$ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC887 same audio issue, settings and pavucontrol only see hdmi audio out and not intel hda audio older dell desktop with 4 years previous use ubuntu. audio worked on morning of my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and other dist same linux, but broke my base machine. base machine restart and messing with pavucontrol allowed my to select appropriate settings to restore audio after exit virutalbox session. all else works and i do not want to risk all my transfer/setup trying to fix this one issue, as important as it may be to me. just politely adding my experience to thread in case future update may address this issue. william@william-Studio-XPS-7100:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] 02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 Gigabit Ethernet PCIe (rev 01) 03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william1432 F pulseaudio /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:16:19 2020 InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card no
[Desktop-packages] [Bug 1897570] [NEW] PCI/internal sound card not detected
Public bug reported: ubuntu 20.04.01 clean install. thanks in advance for your attention. polite comment, no yelling here. going thru transfer and setup machine previous install ubuntu 16.04 when sound was working. lspci lists all sources. internal intel ada card not intialized. only option in sound is hdmi. all worked before clean install. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] same audio issue, settings and pavucontrol only see hdmi audio out and not intel hda audio older dell desktop with 4 years previous use ubuntu. audio worked on morning of my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and other dist same linux, but broke my base machine. base machine restart and messing with pavucontrol allowed my to select appropriate settings to restore audio after exit virutalbox session. all else works and i do not want to risk all my transfer/setup trying to fix this one issue, as important as it may be to me. just politely adding my experience to thread in case future update may address this issue. william@william-Studio-XPS-7100:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] 02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 Gigabit Ethernet PCIe (rev 01) 03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1432 F pulseaudio /dev/snd/pcmC0D1p: william1432 F...m pulseaudio /dev/snd/controlC1: william1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 09:17:53 2020 InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.
[Desktop-packages] [Bug 1897455] Re: Notifications don't say which VPN and network interface
Okay, filed https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #543 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1897455 Title: Notifications don't say which VPN and network interface Status in network-manager package in Ubuntu: New Bug description: In Ubuntu MATE 20.04: If I connect to or disconnect from a VPN, I get a notification that says something like "disconnected from Network". This is too generic. Every notification involving a VPN change should specify the VPN connection name, and the underlying network interface name too. Every notification involving a network interface change (such as enabling/disabling Wi-Fi or Ethernet) should specify the network interface name. Every notification involving Wi-Fi should specify the Wi-Fi network name. Always give as much information as possible and reasonable. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 15:04:15 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1897455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896349] Re: PCI/internal sound card not detected
add to previous comment: devices found but not intialized. discovered my webcam not initialized in clean install ubuntu 20.04.01 thanks in advance for any attention and possible response or future fixes. so far, no sound from my Azalia (Intel HDA) webcam not found in cheese from my generic usb anivia webcam william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera" [43532.227381] usb 1-6: Product: USB 2.0 Camera [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43532.671103] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27 [43931.982272] usb 1-6: Product: USB 2.0 Camera [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366) [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not initialized! [43932.011667] input: USB 2.0 Camera: USB Camera as /devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28 william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video* crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1 crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0 william@william-Studio-XPS-7100:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass Storage Device Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1896349 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 I can select my default audio hardware When I test it, doesn't work. When watching a Youtube video, for example, audio doesn't work as well. Thru the command lspci, this shows up: 00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03) 00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03) 00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30) 00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 30) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30) 00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 30) 00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30) 00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30) 00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30) 00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30) 00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller (rev 30) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03) 04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 App
[Desktop-packages] [Bug 1896349] Re: PCI/internal sound card not detected
new install ubuntu 20.04.01 same audio issue, settings and pavucontrol only see hdmi audio out and not intel hda audio older dell desktop with 4 years previous use ubuntu. audio worked on morning of my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and other dist same linux, but broke my base machine. base machine restart and messing with pavucontrol allowed my to select appropriate settings to restore audio after exit virutalbox session. all else works and i do not want to risk all my transfer/setup trying to fix this one issue, as important as it may be to me. just politely adding my experience to thread in case future update may address this issue. william@william-Studio-XPS-7100:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] 02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 Gigabit Ethernet PCIe (rev 01) 03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1896349 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 I can select my default audio hardware When I test it, doesn't work. When watching a Youtube video, for example, audio doesn't work as well. Thru the command lspci, this shows up: 00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03) 00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03) 00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30) 00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 30) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30) 00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 30) 00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30) 00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30) 00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30
[Desktop-packages] [Bug 1897455] [NEW] Notifications don't say which VPN and network interface
Public bug reported: In Ubuntu MATE 20.04: If I connect to or disconnect from a VPN, I get a notification that says something like "disconnected from Network". This is too generic. Every notification involving a VPN change should specify the VPN connection name, and the underlying network interface name too. Every notification involving a network interface change (such as enabling/disabling Wi-Fi or Ethernet) should specify the network interface name. Every notification involving Wi-Fi should specify the Wi-Fi network name. Always give as much information as possible and reasonable. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 15:04:15 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1897455 Title: Notifications don't say which VPN and network interface Status in network-manager package in Ubuntu: New Bug description: In Ubuntu MATE 20.04: If I connect to or disconnect from a VPN, I get a notification that says something like "disconnected from Network". This is too generic. Every notification involving a VPN change should specify the VPN connection name, and the underlying network interface name too. Every notification involving a network interface change (such as enabling/disabling Wi-Fi or Ethernet) should specify the network interface name. Every notification involving Wi-Fi should specify the Wi-Fi network name. Always give as much information as possible and reasonable. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 15:04:15 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1897455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895421] [NEW] package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was about to install):
Public bug reported: Hello, trying to install over outdated w7 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.445.1 Date: Sat Sep 12 22:21:20 2020 ErrorMessage: unable to stat './usr/share/libreoffice/help/es' (which I was about to install): Input/output error LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1895421 Title: package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was about to install): Input/output error Status in libreoffice package in Ubuntu: New Bug description: Hello, trying to install over outdated w7 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.445.1 Date: Sat Sep 12 22:21:20 2020 ErrorMessage: unable to stat './usr/share/libreoffice/help/es' (which I was about to install): Input/output error LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1895421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893311] [NEW] Add libcurl4-openssl-dev build-dep for lumix camlib
Public bug reported: The lumix camlib is in a somewhat usable state (https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully using it for a few months. It would be good to add the libcurl4-openssl-dev to Build-Depends to enable building the lumix camlib. ** Affects: libgphoto2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgphoto2 in Ubuntu. https://bugs.launchpad.net/bugs/1893311 Title: Add libcurl4-openssl-dev build-dep for lumix camlib Status in libgphoto2 package in Ubuntu: New Bug description: The lumix camlib is in a somewhat usable state (https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully using it for a few months. It would be good to add the libcurl4-openssl-dev to Build-Depends to enable building the lumix camlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1893311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893119] [NEW] Restart-required dialog gives no feedback
Public bug reported: I uninstall something that affects Nautilus, such as the MEGA sync package. I get a dialog that says "Nautilus Restart Required" (see attached screenshot). I click the "Restart Nautilus" button. I get no feedback that anything happened. I sit there wondering if it worked. I click the button a few more times. Eventually I go looking at other windows and find that yes, clicking that button makes any open Nautilus windows close, so I think a restart actually does happen. But the dialog gives me no feedback, no "restarted" message or anything. It should do so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Uname: Linux 5.4.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 20:17:34 2020 InstallationDate: Installed on 2020-04-29 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of dialog" https://bugs.launchpad.net/bugs/1893119/+attachment/5404892/+files/Screenshot%20from%202020-08-26%2020-16-17.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1893119 Title: Restart-required dialog gives no feedback Status in nautilus package in Ubuntu: New Bug description: I uninstall something that affects Nautilus, such as the MEGA sync package. I get a dialog that says "Nautilus Restart Required" (see attached screenshot). I click the "Restart Nautilus" button. I get no feedback that anything happened. I sit there wondering if it worked. I click the button a few more times. Eventually I go looking at other windows and find that yes, clicking that button makes any open Nautilus windows close, so I think a restart actually does happen. But the dialog gives me no feedback, no "restarted" message or anything. It should do so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Uname: Linux 5.4.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 20:17:34 2020 InstallationDate: Installed on 2020-04-29 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891132] [NEW] package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
.99.4+dfsg+really4.12.0-1build1) ... Setting up imagemagick (8:6.9.10.23+dfsg-2.1ubuntu11) ... Processing triggers for desktop-file-utils (0.24-1ubuntu3) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for libc-bin (2.31-0ubuntu9) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for shared-mime-info (1.15-1) ... Processing triggers for fontconfig (2.13.1-2ubuntu3) ... Errors were encountered while processing: zsys [master 4d8b0ba] committing changes in /etc made by "apt install calibre" Author: william 69 files changed, 3770 insertions(+) create mode 100644 ImageMagick-6/coder.xml create mode 100644 ImageMagick-6/colors.xml create mode 100644 ImageMagick-6/delegates.xml create mode 100644 ImageMagick-6/log.xml create mode 100644 ImageMagick-6/magic.xml create mode 100644 ImageMagick-6/mime.xml create mode 100644 ImageMagick-6/policy.xml create mode 100644 ImageMagick-6/quantization-table.xml create mode 100644 ImageMagick-6/thresholds.xml create mode 100644 ImageMagick-6/type-apple.xml create mode 100644 ImageMagick-6/type-dejavu.xml create mode 100644 ImageMagick-6/type-ghostscript.xml create mode 100644 ImageMagick-6/type-urw-base35.xml create mode 100644 ImageMagick-6/type-windows.xml create mode 100644 ImageMagick-6/type.xml create mode 12 alternatives/animate create mode 12 alternatives/animate-im6 create mode 12 alternatives/animate-im6.1.gz create mode 12 alternatives/animate.1.gz create mode 12 alternatives/compare create mode 12 alternatives/compare-im6 create mode 12 alternatives/compare-im6.1.gz create mode 12 alternatives/compare.1.gz create mode 12 alternatives/composite create mode 12 alternatives/composite-im6 create mode 12 alternatives/composite-im6.1.gz create mode 12 alternatives/composite.1.gz create mode 12 alternatives/conjure create mode 12 alternatives/conjure-im6 create mode 12 alternatives/conjure-im6.1.gz create mode 12 alternatives/conjure.1.gz create mode 12 alternatives/convert create mode 12 alternatives/convert-im6 create mode 12 alternatives/convert-im6.1.gz create mode 12 alternatives/convert.1.gz create mode 12 alternatives/csscapture create mode 12 alternatives/csscapture.1.gz create mode 12 alternatives/csscombine create mode 12 alternatives/csscombine.1.gz create mode 12 alternatives/cssparse create mode 12 alternatives/cssparse.1.gz create mode 12 alternatives/display create mode 12 alternatives/display-im6 create mode 12 alternatives/display-im6.1.gz create mode 12 alternatives/display.1.gz create mode 12 alternatives/html2markdown create mode 12 alternatives/html2markdown.1.gz create mode 12 alternatives/identify create mode 12 alternatives/identify-im6 create mode 12 alternatives/identify-im6.1.gz create mode 12 alternatives/identify.1.gz create mode 12 alternatives/import create mode 12 alternatives/import-im6 create mode 12 alternatives/import-im6.1.gz create mode 12 alternatives/import.1.gz create mode 12 alternatives/mogrify create mode 12 alternatives/mogrify-im6 create mode 12 alternatives/mogrify-im6.1.gz create mode 12 alternatives/mogrify.1.gz create mode 12 alternatives/montage create mode 12 alternatives/montage-im6 create mode 12 alternatives/montage-im6.1.gz create mode 12 alternatives/montage.1.gz create mode 12 alternatives/stream create mode 12 alternatives/stream-im6 create mode 12 alternatives/stream-im6.1.gz create mode 12 alternatives/stream.1.gz ZSys is adding automatic system snapshot to GRUB menu E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zsys 0.4.6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 11 08:07:51 2020 ErrorMessage: installed zsys package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-04-25 (107 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_61wq9x@/vmlinuz-5.4.0-28-generic root=ZFS=rpool/ROOT/ubuntu_61wq9x ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: zfs-initramfs 0.8.3-1ubuntu12.2 zfsutils-linux 0.8.3-1ubuntu12.2 SourcePackage: zsys Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 Upgrade
Re: [Desktop-packages] [Bug 1761216] Re: Backup fails if backup destination is not mounted
Yes, since 20.04, I have not had the problem, but I thought it was due to using a linux server and smb which solved the problem. The original problem was localized to my desktop machine and a local drive, which would fail after bootup because the dedicated backup drrive/partition was not mounted at bootup. Only after mounting the drive/partition would the backup run. This prevented the automated backup that should run shortly after the system booted up. To be clear, the backup partition and deja-dup were being run locally on a client machine. Since 20.04, I built a xigmanas server and moved the backup destination off the local machine to the server and started using smb to access the backup partition. This saved space on the local machine and further protected the backups as they are now stored on a remote server. Thanks for the reply, response and fix. On 8/2/20 4:13 PM, Michael Terry wrote: > OK, then yah, I suspect the change I recently made should fix this: > deja-dup now checks fstab and mounts the target location before a backup > starts. > > You should be able to test it by installing the latest edge snap: > snap install deja-dup --classic --edge > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1761216 Title: Backup fails if backup destination is not mounted Status in Déjà Dup: Incomplete Status in deja-dup package in Ubuntu: Triaged Bug description: I have set my backup destination to a separate drive in the machine, but not at the default location. When the backup runs, it fails stating permission denied, as the destination drive is not mounted. When I enter the proper destination in the backup at the "storage location", the drive then mounts and is present on the desktop. Then the backup will run successfully. I then "unmount" the drive using the menu on the drive icon, and the mounted drive disappears from the desktop. I don't need a bunch of drives listed or shown on my desktop, as it detracts from the beauty of the screen. If I mount the drive before running the backup, it will succeed. My point with this is that I am not going to mount the drive every time I run backup, and when mounted, I don't need it listed or shown on my desktop. In unity, the drives appeared in the launcher or dock, and there was an option to "remove from launcher", which still left the drive mounted, but off the desktop and launcher. This was a nice way to fix this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1761216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1761216] Re: Backup fails if backup destination is not mounted
Yes, it is listed in fstab and yes, I entered the path as a local storage device. All drives are SSD's connected to the computer's internal SSD ports and seen as local. The server is running XIGMANAS with SMB shares for each of the SSD's. I am not running SAMBA server. The local OS is Unbuntu 20.04 where the backup app is running and will not work if the backup drive partition is not mounted first. I can get to it by using a combination of IP address and share name, i.e. "smb:192.168.15.1/Backup Drive". Hope this helps. On 8/1/20 10:57 AM, Michael Terry wrote: > How is this other drive configured? Is it an entry in fstab? And you > were entering its path as a Local Folder storage location? > > If so, we didn't previously do anything special about mounting fstab > entries for you. But I just added some code to try that. > > Could you give a beta build a try and see if it works for you? > `snap install deja-dup --classic --edge` > > ** Changed in: deja-dup > Status: Triaged => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1761216 Title: Backup fails if backup destination is not mounted Status in Déjà Dup: Incomplete Status in deja-dup package in Ubuntu: Triaged Bug description: I have set my backup destination to a separate drive in the machine, but not at the default location. When the backup runs, it fails stating permission denied, as the destination drive is not mounted. When I enter the proper destination in the backup at the "storage location", the drive then mounts and is present on the desktop. Then the backup will run successfully. I then "unmount" the drive using the menu on the drive icon, and the mounted drive disappears from the desktop. I don't need a bunch of drives listed or shown on my desktop, as it detracts from the beauty of the screen. If I mount the drive before running the backup, it will succeed. My point with this is that I am not going to mount the drive every time I run backup, and when mounted, I don't need it listed or shown on my desktop. In unity, the drives appeared in the launcher or dock, and there was an option to "remove from launcher", which still left the drive mounted, but off the desktop and launcher. This was a nice way to fix this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1761216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889447] Re: Progress dialog looks frozen for multi-file 7z archives
Maybe use these steps to create the archives, then double-click on the first resulting archive file (tmp1.7z.001) and do an extract. mkdir tmp1 cd tmp1 for f in a b c d e f g h i j do for g in a b c d e f g h i j do for h in a b c d e f g h i j do dd if=/bin/ls of="$f$g$h" count=200 done done done cd .. 7za a -v10m -mx=0 tmp1.7z tmp1/* mv tmp1 tmp2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1889447 Title: Progress dialog looks frozen for multi-file 7z archives Status in file-roller package in Ubuntu: Incomplete Bug description: Suppose you have a four-file archive with files a.7z.001 a.7z.002 a.7z.003 a.7z.004 containing 500 files. While extracting from it, the progress dialog will show filename "a.7z.001" and "500 files remaining" and the progress-bar will stay near the left end, for the whole time, until extracting finishes. If it's not possible to display progress (maybe file-roller is launching 7zip in the background and there's no feedback mechanism ?), the dialog should say so. Give what information it has (total number of files that will be extracted, maybe), say progress can not be monitored, and don't give the appearance of a frozen extraction process. I don't know if the same happens for other file types. Same should apply to them. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:49:48 2020 InstallationDate: Installed on 2020-04-29 (91 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1889447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889447] [NEW] Progress dialog looks frozen for multi-file 7z archives
Public bug reported: Suppose you have a four-file archive with files a.7z.001 a.7z.002 a.7z.003 a.7z.004 containing 500 files. While extracting from it, the progress dialog will show filename "a.7z.001" and "500 files remaining" and the progress-bar will stay near the left end, for the whole time, until extracting finishes. If it's not possible to display progress (maybe file-roller is launching 7zip in the background and there's no feedback mechanism ?), the dialog should say so. Give what information it has (total number of files that will be extracted, maybe), say progress can not be monitored, and don't give the appearance of a frozen extraction process. I don't know if the same happens for other file types. Same should apply to them. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:49:48 2020 InstallationDate: Installed on 2020-04-29 (91 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1889447 Title: Progress dialog looks frozen for multi-file 7z archives Status in file-roller package in Ubuntu: New Bug description: Suppose you have a four-file archive with files a.7z.001 a.7z.002 a.7z.003 a.7z.004 containing 500 files. While extracting from it, the progress dialog will show filename "a.7z.001" and "500 files remaining" and the progress-bar will stay near the left end, for the whole time, until extracting finishes. If it's not possible to display progress (maybe file-roller is launching 7zip in the background and there's no feedback mechanism ?), the dialog should say so. Give what information it has (total number of files that will be extracted, maybe), say progress can not be monitored, and don't give the appearance of a frozen extraction process. I don't know if the same happens for other file types. Same should apply to them. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:49:48 2020 InstallationDate: Installed on 2020-04-29 (91 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1889447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885130] Re: Please add a way to show only open-source apps
Okay, filed https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021 Would be nice if ubuntu-bug sent me there directly. I'm getting tired of having to file a lot of bug reports twice. Sometimes downstream says go to upstream, sometimes upstream says go to downstream. The app displays as Ubuntu Software, but its CLI / package name is gnome- software. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1021 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps Status in gnome-software package in Ubuntu: New Bug description: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885130] [NEW] Please add a way to show only open-source apps
Public bug reported: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps Status in gnome-software package in Ubuntu: New Bug description: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879144] Re: Balance reset when sound reachs 0
** Summary changed: - Balance resetted when sound reachs 0 + Balance reset when sound reachs 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879144 Title: Balance reset when sound reachs 0 Status in pulseaudio package in Ubuntu: Triaged Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879144] Re: Custom volume output configuration reset
It seems that it is not a single problem that happens on analog surround 4.0 I tried using Bluetooth audio, then set custom balance. The same thing resets when the volume gradually turns down and reached 0 volume. Didn't reset when I manually mute it with a switch or through a button. ** Summary changed: - Volume output settings reset on analog surround 4.0 + Custom volume output configuration reset ** Summary changed: - Custom volume output configuration reset + Audio custom output settings reset ** Summary changed: - Audio custom output settings reset + Audio custom output settings unintendly reset -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879144 Title: Audio custom output settings unintendly reset Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879144] Re: Volume output settings reset on analog surround 4.0
There is one thing I am not sure: it is an issue of pulseaudio or an issue of the ubuntu settings. But I will upstream it though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879144] [NEW] Volume output settings reset on analog surround 4.0
Public bug reported: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Volume output reset settings reset on surround 4.0 + Volume output reset settings reset on pulseaudio surround 4.0 ** Summary changed: - Volume output reset settings reset on pulseaudio surround 4.0 + Volume output settings reset on pulseaudio surround 4.0 ** Summary changed: - Volume output settings reset on pulseaudio surround 4.0 + Volume output settings reset on analog surround 4.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
Still happening on 20.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1723117 Title: Desktop icons goes under the Dock, if the Dock is set to auto-hide. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: This bug is found in Artful. Desktop icons goes under the Dock, if the Dock is set to auto-hide. Either the Dock should auto-hide on the Desktop as well, or the Desktop Icons should leave a margin with the same size of the Dock. This happen both horizontal and vertical Dock positions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1723117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857941] Re: Ubuntu Studio audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled
Also, no I'm not using bluetooth. The sound issues happen whether I'm using an audio interface or the onboard sound. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1857941 Title: Ubuntu Studio audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled Status in jackd2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Turning off PulseAudio timer scheduling does not fix the problem. Shouldn't be a hardware issue because it was not present in Ubuntu 18.04. I am currently on the latest Ubuntu Studio release. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william2221 F jackdbus /dev/snd/pcmC2D0c: william2221 F...m jackdbus /dev/snd/pcmC2D0p: william2221 F...m jackdbus CurrentDesktop: MATE Date: Mon Dec 30 18:22:30 2019 InstallationDate: Installed on 2019-11-27 (33 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - USB Audio CODEC Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0TRW8H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1857941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857941] Re: Ubuntu Studio audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled
I think you're right that it's probably the kernel. I'm having trouble changing that, but when I get it done I'll update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1857941 Title: Ubuntu Studio audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled Status in jackd2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Turning off PulseAudio timer scheduling does not fix the problem. Shouldn't be a hardware issue because it was not present in Ubuntu 18.04. I am currently on the latest Ubuntu Studio release. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william2221 F jackdbus /dev/snd/pcmC2D0c: william2221 F...m jackdbus /dev/snd/pcmC2D0p: william2221 F...m jackdbus CurrentDesktop: MATE Date: Mon Dec 30 18:22:30 2019 InstallationDate: Installed on 2019-11-27 (33 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - USB Audio CODEC Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0TRW8H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1857941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857941] [NEW] [HDA-Intel - HDA Intel PCH, playback] Audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled
Public bug reported: Turning off PulseAudio timer scheduling does not fix the problem. Shouldn't be a hardware issue because it was not present in Ubuntu 18.04. I am currently on the latest Ubuntu Studio release. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william2221 F jackdbus /dev/snd/pcmC2D0c: william2221 F...m jackdbus /dev/snd/pcmC2D0p: william2221 F...m jackdbus CurrentDesktop: MATE Date: Mon Dec 30 18:22:30 2019 InstallationDate: Installed on 2019-11-27 (33 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - USB Audio CODEC Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0TRW8H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1857941 Title: [HDA-Intel - HDA Intel PCH, playback] Audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled Status in pulseaudio package in Ubuntu: New Bug description: Turning off PulseAudio timer scheduling does not fix the problem. Shouldn't be a hardware issue because it was not present in Ubuntu 18.04. I am currently on the latest Ubuntu Studio release. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: william2221 F jackdbus /dev/snd/pcmC2D0c: william2221 F...m jackdbus /dev/snd/pcmC2D0p: william2221 F...m jackdbus CurrentDesktop: MATE Date: Mon Dec 30 18:22:30 2019 InstallationDate: Installed on 2019-11-27 (33 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - USB Audio CODEC Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0TRW8H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
I also see this happen quite often. The User Manual link posted here will trigger it when you open the link with Document Viewer. https://www.star-cooperation.com/de/kompetenzen/elektronik/produkte/vernetzungstechnik/hardware/vernetzungszubehoer/flexmedia-100base-t1/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in evince package in Ubuntu: Expired Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1350527] Re: Custom keyboard shortcuts using Esc key do not work
Ubuntu 18.04 - Can use Escape for shortcuts! Using ctrl-shift-esc to open system monitor so I have the same(ish) command across my dual-boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1350527 Title: Custom keyboard shortcuts using Esc key do not work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 and found an issue with custom keyboard shortcuts. In 12.04 I used to have Shift + Ctrl + Esc as a custom shortcut to suspend my machine, upon upgrading I have found that any combination use Esc key will not run the command. It appears to be a regression from 13.10 as another user is reporting the same issue in askubuntu: http://askubuntu.com/q/489418/8570 Using any alternative such as Shift + Ctrl + F1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1350527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 577038] Re: [Upstream] Hard lock in opening files from a remote NFS volume
** Description changed: Binary package hint: openoffice.org I recently updated to Lucid, and noticed that Openoffice would lock with opening certain files. First I thought the problem was a corrupt file, now I can reproducibly hard lock OO.org when trying to open ANY file (.xls, .doc, .odt) that is present in a remote NFS volume (locally mounted). Any file on the local hard disk can be opened without problems. Any file on the mounted NFS directory causes a hard lock, requiring a force-quit. Other applications don't show this behaviour (e.g. gedit, command line programs). FilesystemSize Used Avail Use% Mounted on /dev/md0 70G 17G 50G 26% / 192.168.10.72:/home/fernan243G 182G 42G 82% /home/fernan/gama-remote - http://yourrxstore.com/product-category/buy-soma-online/ - http://yourrxstore.com/blog/order-tramadol-online-severe-and-acute-pain/ ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openoffice.org 1:3.2.0-7ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri May 7 11:48:21 2010 EcryptfsInUse: Yes ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/577038 Title: [Upstream] Hard lock in opening files from a remote NFS volume Status in LibreOffice: Invalid Status in LibreOffice: Confirmed Status in OpenOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org I recently updated to Lucid, and noticed that Openoffice would lock with opening certain files. First I thought the problem was a corrupt file, now I can reproducibly hard lock OO.org when trying to open ANY file (.xls, .doc, .odt) that is present in a remote NFS volume (locally mounted). Any file on the local hard disk can be opened without problems. Any file on the mounted NFS directory causes a hard lock, requiring a force-quit. Other applications don't show this behaviour (e.g. gedit, command line programs). FilesystemSize Used Avail Use% Mounted on /dev/md0 70G 17G 50G 26% / 192.168.10.72:/home/fernan243G 182G 42G 82% /home/fernan/gama-remote ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openoffice.org 1:3.2.0-7ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri May 7 11:48:21 2010 EcryptfsInUse: Yes ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/577038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833010] [NEW] PCI/internal sound card not detected
Public bug reported: Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1931 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 22:29:12 2019 InstallationDate: Installed on 2019-06-14 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: LINX1010B.R22.03.010 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: LINX1010B dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: LINX ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833010 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1931 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 22:29:12 2019 InstallationDate: Installed on 2019-06-14 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: LINX1010B.R22.03.010 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: LINX1010B dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: LINX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Wish I had the ability to edit a post... Scratch most of my last post. There is a problem with vdagent~, but I just refuted my previous post. I do have the error, but I am 99.9% certain that it does not cause the problems that I am experiencing which brought me to this bug report. Apologies if the previous post caused any inconvenience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
I am wondering if a JVM can be used to more reliably trigger the bug and thus help isolate it? Hopefully someone else reading this has an opinion... Below is my experience and the reason why I am considering this idea: I have had what I first believed were random black screens, restarts directly after login, occasional hangups, and also one two reproducible issues... 1.) I run Google Chrome in nearly every session. I like to listen to music using the Youtube website. As time passes and I open, close, and move forward through the playsists on the site Chrome will become less and less responsive. It will occassionally crash the application too. It will usually be fixed by completely closing the application and running it again. Maybe it is a due to an issue which can be triggered through Java or JScript? 2.) My reason for the Java/JScript angle is that I discovered I cannot use Open Office - certain features in it will freeze my entire desktop session completely. This leaves the mouse able to move but nothing else works at all. The same is true for several other select applications - all of which I have removed form the machine. But one thing all the applications have in common is heavy reliance on Java/JScript. So, perhaps the use of a JVM can help to trigger this issue reliable and thus find the actual source of the bug? Anybody else able to confirm or refute this idea? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797749] Re: Drag and drop from File Roller to Nautilus not working
I'm experiencing this on Ubuntu 19.04. Can this bug be re-opened or should I create a new one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797749 Title: Drag and drop from File Roller to Nautilus not working Status in nautilus package in Ubuntu: Expired Bug description: This started to appear after updating to 18.10. Steps to reproduce: * open any archive with File Roller * open any location in Nautilus * drag a file or directory from File Roller to Nautilus Expected: * selected files/directories are extracted to the drop location Actually happens: * nothing ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu6 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 14 10:26:22 2018 InstallationDate: Installed on 2017-12-20 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-20T17:55:23.166649 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819005] Re: Want To Pass JN0-220 Juniper Exam Immediately?
** Package changed: gvfs (Ubuntu) => null-and-void ** Information type changed from Public to Private -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1819005 Title: Want To Pass JN0-220 Juniper Exam Immediately? Status in NULL Project: Invalid Bug description: Buy Our Effective Juniper JN0-220 Exam Dumps Dumpsprovider.com provides Juniper JN0-220 dumps which are prepared beautifully in detail and whole course is included in it. The presentation is great. All technical details are explained in easy way with the help of demos. Clients feel like it’s a one to one session and not an online distant class because of high quality and well explained content. Juniper Networks Automation and DevOps Associate JN0-220 Braindumps are full of relevant information and guidance which is enough for success in first attempt. It is a very important factor, that one must pass the exam in first try. Juniper JN0-220 Exam Dumps will save your time and money and help you succeed in your career. Quick Tips To Pass - Juniper JN0-220 Exam Questions Juniper JN0-220 Question Answers are prepared by a very skillful and competent IT team at Dumpsprovider.com. A large no. of practice tests is provided for the sake of rehearsal and improvement. The right solution is also provided along with the tests so that clients can check their results and improve their skills before actual exam. Juniper JN0-220 Dumps PDF is an easily manageable document. It is a very user-friendly guide. The best thing is extra software installation is not needed in order to run this. It is compatible to mobiles, tablets and laptops. It can be used in printed form also. Download Full Exam In PDF https://www.dumpsprovider.com/Juniper/JN0-220-exam-dumps Pass Juniper JN0-220 Exam Easily With 100% Success Guaranteed The price of our product is also very reasonable. It is not at all heavy on pocket. Furthermore, we also provide money back guarantee. If due to any misfortune, a client fails in the Juniper Automation and DevOps Certification exam, he or she can claim money back from us. Please read our refund policy in detail before purchasing the study material in order to avoid any ambiguity or complexity. Free demo is also another perk by us. Have an overview of our product before buying the product. Once you purchase the product, updates will be provided absolutely free of cost up till three months. Try Our Best Juniper JN0-220 Exam Actual Questions Our customer support team is very courteous, proficient and well qualified. They never hesitate to help the customers. Feel free to contact them whenever you have any query related to content or any system related issue, you will be entertained immediately. Our team is available 24/7 and gives a prompt response. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1819005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818371] Re: Simple Scan images are too dark at resolutions > 75ppi.
Please disregard my first bug description in my post #1. Apologies for this confusion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1818371 Title: Simple Scan images are too dark at resolutions > 75ppi. Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1818371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818371] Re: Simple Scan images are too dark at resolutions > 75ppi.
Ubuntu 18.04.2 Canon Pixma TS6220 These issues are similar to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) The output always contains the images of what ever is on the platen on a "full size" white background; i.e., unlike scangearmp2, if there is a 4” x 6” photo on the platen, the output is a letter size white background with the 4” x 6” image scaled down. 2) Only images at resolutions of 75 ppi are acceptable. When cropped in Gimp, and size adjusted to 4” x 6”, this works out to 300 ppi. The scanned image of photos at all resolutions greater than 75 ppi are very dark/saturated – beyond my ability to correct. 3) The adjustments for Brightness and Contrast have little, if any, affect on the output for scans at resolutions > 75 ppi. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1818371 Title: Simple Scan images are too dark at resolutions > 75ppi. Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1818371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818371] Re: Simple Scan images are too dark at resolutions > 75ppi.
** Summary changed: - Simple Scan does not scan only the area which is framed after "preview" + Simple Scan images are too dark at resolutions > 75ppi. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1818371 Title: Simple Scan images are too dark at resolutions > 75ppi. Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 18.04.2 Canon Pixma TS6220 These issues are identical to an earlier bug (#1818186) that I reported regarding the operation of Xsane. 1) I am able to move the dashed lines to frame the print to be scanned, but the output always contains the images of what ever is on the platen on a "full size" white background. 2) I have selected “inches” as the unit of measurement, but the preview window has “px” in the upper left corner, and the dimensions in the windows at the bottom of the main menu are in pixels. These dimensions do not change as I adjust the frame of the photo to be scanned and always read 2480*3507*24 (24.9MB). 3) There are no length markings along the side or top of the preview window. 4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust the frame, but for a 4” x 6” photo in the upper left corner, the lower right corner is shown to be .00235x, .00154y. 5) The scanned image of the photos is very dark/saturated – beyond my ability to correct. 6) Max scan resolution in the main menu is only 300, whereas it is 1200 with the HP scanner. If I can be of any assistance in “testing”, please let me know. Kind regards, Bill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Mar 1 20:59:54 2019 InstallationDate: Installed on 2018-08-04 (210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire XC-603 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1818371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
