[Desktop-packages] [Bug 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
Even though I'm not using anydesk, I experience the same problem. And I think its caused by "dropbox" > gnome-extensions disable ubuntu-appindicat...@ubuntu.com This workaround seems to work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2012388/+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 1971168] Re: [snap] Files on local network shares are not opened / written
Sergio any news about this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Won't Fix Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written
Ok Thks for all the work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written
Soo no fix to 22.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written
It don't work, you can select a file but it don´t upload ** Attachment added: "Captura de ecrã de 2024-01-05 12-32-13.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+attachment/5736847/+files/Captura%20de%20ecr%C3%A3%20de%202024-01-05%2012-32-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written
Hi, This bug going to be solved for 22.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 2037794] [NEW] [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all
Public bug reported: Not sound at all ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 15:00:02 2023 InstallationDate: Installed on 2023-08-28 (33 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) 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_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX482EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX482EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX482EA_UX482EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2037794 Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Not sound at all ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 15:00:02 2023 InstallationDate: Installed on 2023-08-28 (33 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) 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_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX482EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX482EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX482EA_UX482EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2037794/+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 1980271] Re: Snap doesn't refresh automatically immediately after snap is quit when update is pending
Implemented in the PRs listed in this comment: https://github.com/snapcore/snapd/pull/12495#issuecomment-1446110993 ** Changed in: snapd Status: In Progress => Fix Committed ** Changed in: snapd Assignee: Sergio Costas (rastersoft-gmail) => Miguel Pires (miguelpires1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1980271 Title: Snap doesn't refresh automatically immediately after snap is quit when update is pending Status in snapd: Fix Committed Status in firefox package in Ubuntu: Confirmed Bug description: Impact / What Currently Happens -- Many people open their chosen web browser (Firefox or Chromium) immediately after logging in and keep the app running continuously. Eventually, there will be a snap update available. The system notifies that there is a pending update and to "Close the app to avoid notifications." Most people will eventually close the app, but the pending update is not applied until the next snap refresh is attempted which could be hours away. This is a frustrating experience because it feels like the notification is not helpful. I think many users would prefer the snap to just update silently in the background with little or no notification. Test Case - From Ubuntu 22.04 LTS with the Firefox snap installed by default Keep Firefox running Wait for a new Firefox release (happens at least monthly) Receive a notification about a pending update for Firefox Close Firefox Wait a few minutes Open Firefox Workaround -- Close the app that needs to be updated Open a terminal and run this command: snap refresh Other Info -- This issue was mentioned in the original post and in the first comment at https://forum.snapcraft.io/t/refresh-app-awareness-call-for-testing/29123 Suggested Mitigation Would it help to run a `snap refresh` immediately after Ubuntu is booted? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1980271/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Any news about this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1994183] [NEW] Freezes randomly, weird behaviour when I right click with my mouse
Public bug reported: When using the Files navigator, it sometimes freezes. When I right click with my mouse anywhere the menu that pops up has a lot of lag. All of this happened after the update from 22.04 to 22.10 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 22:22:28 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.window-state' b'initial-size' b'(901, 550)' InstallationDate: Installed on 2022-06-13 (133 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-22 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- 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/1994183 Title: Freezes randomly, weird behaviour when I right click with my mouse Status in nautilus package in Ubuntu: New Bug description: When using the Files navigator, it sometimes freezes. When I right click with my mouse anywhere the menu that pops up has a lot of lag. All of this happened after the update from 22.04 to 22.10 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 22:22:28 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.window-state' b'initial-size' b'(901, 550)' InstallationDate: Installed on 2022-06-13 (133 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-22 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1994183/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Any news about this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Hi The output miguel@miguel-HP-Pavilion-Laptop-14-ec0xxx:~$ which firefox /snap/bin/firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: Incomplete Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Exactly, the fileselector is different in my opinion, like you see in the screenshots -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Hi Oliver, I reapload the screenshots. I hope its ok now Regards Miguel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura3.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+attachment/5624602/+files/Captura3.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura2.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+attachment/5624601/+files/Captura2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura1.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+attachment/5624600/+files/Captura1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Changed in: firefox (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Hi Sebastien, I'm install de deb from Google. The share is a smb share, something like : smb://server ip adress/folder I can tell you that in 20.04 this problem dont occur, so i really think this is something to do with, like you said, fileselector., because if you compare the 3 printscreens, in the Browsers they use the same, thunderbird don't use the same. Any more info necessary please tell me Regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: Incomplete Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura de ecrã de 2022-10-08 21-21-14.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+attachment/5622342/+files/Captura%20de%20ecr%C3%A3%20de%202022-10-08%2021-21-14.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/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in nautilus package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura de ecrã de 2022-10-08 21-21-25.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+attachment/5622341/+files/Captura%20de%20ecr%C3%A3%20de%202022-10-08%2021-21-25.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/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in nautilus package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura de ecrã de 2022-10-08 21-20-53.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+attachment/5622343/+files/Captura%20de%20ecr%C3%A3%20de%202022-10-08%2021-20-53.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/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in nautilus package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
** Attachment added: "Captura de ecrã de 2022-10-08 21-18-22.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+attachment/5622344/+files/Captura%20de%20ecr%C3%A3%20de%202022-10-08%2021-18-22.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/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in nautilus package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+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 1992255] [NEW] Cant upload files from remote folders : Firefox and Chrome
Public bug reported: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in nautilus package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992255/+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 1990444] Re: firefox snap took 20 minutes to update
Hi. Thank you for opening a bug report. I'm not sure that the store outage could prevent a snap from being used for 20 minutes since the snap remains available during the part of the update that fetches snaps and assertions from the store. The snap only becomes unavailable later when it's absolutely necessary. In order to help us understand what happened, could you run this script https://github.com/snapcore/snapd/blob/master/debug-tools/snap-debug- info.sh and share the output with us? Also if you could run `snap changes` to see the latest changes, identify the change corresponding to the slow firefox update and then run `snap change ` with that update's ID, that might give us an idea of what happened. Thank you for your help. ** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1990444 Title: firefox snap took 20 minutes to update Status in snapd: Incomplete Status in firefox package in Ubuntu: Invalid Bug description: I logged and firefox was unavailable, no indication of update, nothing. When I tried to launch firefox I was invited to install it BUT I klnow it's installed, so I tried to install it but it said to me I needed to 'snap refresh', I tried to snap refresh but it indicated that everything was up to date. I tried to uninstall/reinstall the firefox snap and at this moment, I got the indication that the update was in progress since 15 MINUTES ! Then I tried to remove the snap because I was sure it's bugged : in 20.04 firefox never took more than 2 mins to update and my machine BUT after 20 minutes firefox launched... wtf ? I'm an ubuntu user since circa 2005 and I believe firefox was already the default browser then, this is the worse user experience I've ever had. 1/ I never selected auto-update, let me update when I want : being blocked 15 MINUTES by the OS is not a good user experience, I know this is accepted by Windows users but I prefer to use Ubuntu 2/ If you want to update tell me you're updating not that the application is not installed : really not a good idea if you want your users to trust you I've waited 6 months after 22.04 release to migrate from 20.04 because I don't want to have this kind of bugs, I hope you do something really quick because this is not at the level of quality expected by your users. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990444/+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 1990384] [NEW] Super + L doesn't work
Public bug reported: Neither does changing the shortkey to the lockscreen. In the journalctl I get this: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBuscreen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service fError.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 12:04:17 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-08-16 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1990384 Title: Super + L doesn't work Status in gnome-screensaver package in Ubuntu: New Bug description: Neither does changing the shortkey to the lockscreen. In the journalctl I get this: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBuscreen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service fError.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 12:04:17 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-08-16 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1990384/+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 1990346] [NEW] gnome terminal window shrinks in size on every maximize/restore cicle
Public bug reported: every time I maximize a terminal window and return it to the restored size, it shrinks in size every just slightly. I would expect it to return to the previous size as it was before I maximized. lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.44.0-1ubuntu1 Candidate: 3.44.0-1ubuntu1 Version table: *** 3.44.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:22:50 2022 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1990346 Title: gnome terminal window shrinks in size on every maximize/restore cicle Status in gnome-terminal package in Ubuntu: New Bug description: every time I maximize a terminal window and return it to the restored size, it shrinks in size every just slightly. I would expect it to return to the previous size as it was before I maximized. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.44.0-1ubuntu1 Candidate: 3.44.0-1ubuntu1 Version table: *** 3.44.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:22:50 2022 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1990346/+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 1990345] [NEW] gnome shell keeps growing in size/ram
Public bug reported: every 2 or 3 days I have to alt+F2 and "r" to restart gnome-shell to release ram, because it grows and grows until it starts swapping. Restarting gives me another 2 or 3 days of breathing room :) and then rinse and repeat. lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 apt-cache policy gnome-shell gnome-shell: Installed: 42.4-0ubuntu0.22.04.1 Candidate: 42.4-0ubuntu0.22.04.1 Version table: *** 42.4-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages gnome-extensions list gsconn...@andyholmes.github.io ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:18:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1990345 Title: gnome shell keeps growing in size/ram Status in gnome-shell package in Ubuntu: New Bug description: every 2 or 3 days I have to alt+F2 and "r" to restart gnome-shell to release ram, because it grows and grows until it starts swapping. Restarting gives me another 2 or 3 days of breathing room :) and then rinse and repeat. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy gnome-shell gnome-shell: Installed: 42.4-0ubuntu0.22.04.1 Candidate: 42.4-0ubuntu0.22.04.1 Version table: *** 42.4-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages gnome-extensions list gsconn...@andyholmes.github.io ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:18:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990345/+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 1971608] Re: Firefox PDF font rendering is often messed up
I think the issue is that the firefox snap is not able to find substitutes for the default pdf fonts when they are not embedded in the document. PDF documents with embedded fonts render fine with the snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+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 1977917] [NEW] package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overw
Public bug reported: trying to install wine 7 version ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jun 8 00:52:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:0622] InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 3847 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c 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.8 SourcePackage: libxau Title: package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.release: 65.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/07/2019:br65.10:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr:sku0622: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.product.sku: 0622 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libxau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1977917 Title: package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 Status in libxau package in Ubuntu: New Bug description: trying to install wine 7 version ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jun 8 00:52:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:0622] InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 3847 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c 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.8 SourcePackage: libxau Title: package libxau6
[Desktop-packages] [Bug 1971516] Re: Entering fileselector subdir disables the save button until filename is edited
Can confirm the bug is fixed in gtk4 4.6.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1971516 Title: Entering fileselector subdir disables the save button until filename is edited Status in gtk4 package in Ubuntu: Fix Committed Bug description: Affecting Chrome, Chromium, Firefox, Brave, Vivaldi Files can not reliably be downloaded to any folder except ~/downloads and /tmp. Ubuntu 22.04 Chrome installed from .deb, Brave installed from repos. Firefox and Chromium are both sneaky-snaps, but the behaviour is the same. Other reports in the wild: https://forum.vivaldi.net/topic/74989/ubuntu-22-04-save-as-doesn-t-fully-work https://askubuntu.com/questions/1405148/browsers-unable-to-save-downloads-to-network-drive-after-upgrade-to-ubuntu-22-04 Similar Bug(s): https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1971516/+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 1970984] Re: Can't save files in a Folder in a Folder 22.04
*** This bug is a duplicate of bug 1971516 *** https://bugs.launchpad.net/bugs/1971516 Can confirm the bug is fixed in gtk4 4.6.3 -- 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/1970984 Title: Can't save files in a Folder in a Folder 22.04 Status in nautilus package in Ubuntu: New Bug description: I can't save files when I have let's say Downloads and inside there is a folder named Usenet and inside a folder named nzbs. When I try to download something, in Usenet or nzbs it disappears. Or the download doesn't even start. When I download it directly to the Downloads folder, there is no problem. Ubuntu 22.04 on Wayland, fully updated to 30.04.2022. On X11 same thing. And Files doesn't remember the last folder you saved something. It always defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
Pinning an app to the dock (or removing it), displaying its details, open it in a new window (for browsers, for example), and other functions normally available with the right click, are all tasks very hard to complete right now when the dock is set to auto-hide at the bottom (like trying to hit a target on a video game). They might be specific, but also very basic circumstances. I just experienced it right now. I was trying to open a new window of my browser via right click on the app in the dock, but the menu shifted, or moved down, when clicked, and I ended up exiting the browser. -- 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/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: Currently testing a fresh install of the beta for 22.04. All packages are up to date. When having the dock auto-hide option enabled, a glitch occurs when opening the windows selector (when multiple instances of the same program are opened). The selector does open, but the dock will hide itself immediately instead of waiting for a selection. Selecting a window will then cause a glitch where the selector will align with the hidden dock in a non natural way before disappearing. A proposed fix would be to prevent the dock from auto-hiding when the miniatures selector opens and wait for a second input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967121/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
Same problem here, with dock set to auto-hide and positioned centered at the bottom. -- 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/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Currently testing a fresh install of the beta for 22.04. All packages are up to date. When having the dock auto-hide option enabled, a glitch occurs when opening the windows selector (when multiple instances of the same program are opened). The selector does open, but the dock will hide itself immediately instead of waiting for a selection. Selecting a window will then cause a glitch where the selector will align with the hidden dock in a non natural way before disappearing. A proposed fix would be to prevent the dock from auto-hiding when the miniatures selector opens and wait for a second input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967121/+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 1970984] Re: Can't save files in a Folder in a Folder 22.04
Yes Trogdor, it seems to be the same bug as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971516 Can confirm that when selecting the file name box this issue does not happen. This explains every single behavior I've described. On a second thought, this issue doesn't seem to be related to "top level directories" whatsoever. The observed behavior of top-level directories emerges because when you click on any shortcut on the left the file name box is selected. Another thing I've noticed is that both Chrome, Firefox and Telegram have a full screen file save dialog. Software that have a resizable file save dialog (or a custom file save dialog) don't seem to suffer from this behavior. -- 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/1970984 Title: Can't save files in a Folder in a Folder 22.04 Status in nautilus package in Ubuntu: Incomplete Bug description: I can't save files when I have let's say Downloads and inside there is a folder named Usenet and inside a folder named nzbs. When I try to download something, in Usenet or nzbs it disappears. Or the download doesn't even start. When I download it directly to the Downloads folder, there is no problem. Ubuntu 22.04 on Wayland, fully updated to 30.04.2022. On X11 same thing. And Files doesn't remember the last folder you saved something. It always defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+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 1970984] Re: Can't save files in a Folder in a Folder 22.04
And I've found yet another weird behavior. Although I can't save to "~/1" normally, if I add "~/1" as a bookmark, I can save to it, but only if click on the bookmark. If I navigate to "~/1" trough the file explorer with any other path instead of clicking the bookmark, I can't save anymore. -- 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/1970984 Title: Can't save files in a Folder in a Folder 22.04 Status in nautilus package in Ubuntu: Incomplete Bug description: I can't save files when I have let's say Downloads and inside there is a folder named Usenet and inside a folder named nzbs. When I try to download something, in Usenet or nzbs it disappears. Or the download doesn't even start. When I download it directly to the Downloads folder, there is no problem. Ubuntu 22.04 on Wayland, fully updated to 30.04.2022. On X11 same thing. And Files doesn't remember the last folder you saved something. It always defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+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 1970984] Re: Can't save files in a Folder in a Folder 22.04
I've done some further testing and this is 100% reproducible with Chrome (deb), Firefox (apt) and Telegram Desktop (binary): I can save to any of the "first level" directories, but not to any of the child folders: File saving testing with those three software: ~/ -> OK ~/1 -> Error ~/Desktop -> OK ~/Desktop/1 -> Error ~/Documents -> OK ~/Documents/1 -> Error ~/Downloads -> OK ~/Downloads/1 -> Error ~/Music -> OK ~/Music/1 -> Error ~/Pictures -> OK ~/Pictures/1 -> Error ~/Videos -> OK ~/Videos/1 -> Error /media/DATA (a mounted partition) -> OK /media/DATA/1 -> Error -- 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/1970984 Title: Can't save files in a Folder in a Folder 22.04 Status in nautilus package in Ubuntu: Incomplete Bug description: I can't save files when I have let's say Downloads and inside there is a folder named Usenet and inside a folder named nzbs. When I try to download something, in Usenet or nzbs it disappears. Or the download doesn't even start. When I download it directly to the Downloads folder, there is no problem. Ubuntu 22.04 on Wayland, fully updated to 30.04.2022. On X11 same thing. And Files doesn't remember the last folder you saved something. It always defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+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 1970984] Re: Can't save files in a Folder in a Folder 22.04
This does not happen only with browsers. Telegram Desktop can save files to "~/" but not to "~/1/". I've tried gedit code and deluge, and I have no issues saving files with those. -- 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/1970984 Title: Can't save files in a Folder in a Folder 22.04 Status in nautilus package in Ubuntu: Incomplete Bug description: I can't save files when I have let's say Downloads and inside there is a folder named Usenet and inside a folder named nzbs. When I try to download something, in Usenet or nzbs it disappears. Or the download doesn't even start. When I download it directly to the Downloads folder, there is no problem. Ubuntu 22.04 on Wayland, fully updated to 30.04.2022. On X11 same thing. And Files doesn't remember the last folder you saved something. It always defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+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 1970984] Re: Can't save files in a Folder in a Folder 22.04
*** This bug is a duplicate of bug 1969622 *** https://bugs.launchpad.net/bugs/1969622 I can confirm this is not the same issue as bug #1969622. "gtk4 - 4.6.2+ds-1ubuntu3" fixes the issues with the save button on empty folders but does not fix this issue. -- 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/1970984 Title: Can't save files in a Folder in a Folder 22.04 Status in nautilus package in Ubuntu: Confirmed Bug description: I can't save files when I have let's say Downloads and inside there is a folder named Usenet and inside a folder named nzbs. When I try to download something, in Usenet or nzbs it disappears. Or the download doesn't even start. When I download it directly to the Downloads folder, there is no problem. Ubuntu 22.04 on Wayland, fully updated to 30.04.2022. On X11 same thing. And Files doesn't remember the last folder you saved something. It always defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+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 1958312] Re: Livepatch not working on Ubuntu 22.04 LTS
** Tags removed: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1958312 Title: Livepatch not working on Ubuntu 22.04 LTS Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: No such file or directory error when I'll try to use livepatch on a 22.04 device with dev updates enabled. It turns off automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1958312/+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 1958312] [NEW] Livepatch not working on Ubuntu 22.04 LTS
Public bug reported: No such file or directory error when I'll try to use livepatch on a 22.04 device with dev updates enabled. It turns off automatically ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade ** Patch added: "Error Screenshot" https://bugs.launchpad.net/bugs/1958312/+attachment/255/+files/Captura%20de%20pantalla%20de%202022-01-18%2019-12-42.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1958312 Title: Livepatch not working on Ubuntu 22.04 LTS Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: No such file or directory error when I'll try to use livepatch on a 22.04 device with dev updates enabled. It turns off automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1958312/+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 1875056] Re: locate-pointer (w/ ctrl key) not working
My bad: the feature is now working (with CTRL key and of course not "any" key). I was using sudo dconf-editor to set the key and of course I was actually setting therefore the root user's desktop feature. Setting true my user's key still wouldn't work but setting then "enable- animations" true made the trick. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1875056 Title: locate-pointer (w/ ctrl key) not working Status in gnome-shell package in Ubuntu: Confirmed Bug description: It was working for an hour and then stopped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 19:09:37 2020 InstallationDate: Installed on 2020-03-31 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875056/+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 1875056] Re: locate-pointer (w/ ctrl key) not working
AFAICT, my left CTRL key is working but I won't be able to enable this feature. Actually looking at Thomas's screenshot I've noticed that the dconf setting apparently has been moved from settings-daemon/mouse to desktop/interface, what explains that I wouldn't found the key definition in the schemas.xml file even in the deprecated-keys section. But setting the key true in the new config won't enable either. I can also notice that toggling the key value in dconf won't change the the value in the "official" Settings/mouseand keyboard section or even in the Tweak app. And BTW the new dconf description reads that the pointer location will be be triggered by pressing *any* key (?) - as can be seen in Thomas's screenshot. Seems like the gnome shell is still expecting for the old key activation. I've tried to add the "locate pointer" in the schemas.xml's settings-daemon/interface but it won't show up aon dconf and won't activate anything either (even after reboot). Would there be a way to redirect the key from desktop/interface to settings-daemon/mouse so that the shell could grab it ? I'm on 21.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1875056 Title: locate-pointer (w/ ctrl key) not working Status in gnome-shell package in Ubuntu: Confirmed Bug description: It was working for an hour and then stopped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 19:09:37 2020 InstallationDate: Installed on 2020-03-31 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875056/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I solved the problem with $ sudo killall -9 gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I have the updated mutter package (3.38.1-2ubuntu1) and chromium snap is
working fine again.
Open sockets:
u_str LISTEN 0 1 @/tmp/.X11-unix/X0
64514* 0 users:(("Xwayland",pid=4667,fd=4))
u_str LISTEN 0 1 @/tmp/.X11-unix/X1
64516* 0 users:(("Xwayland",pid=4667,fd=7))
u_str LISTEN 0 1 /tmp/.X11-unix/X0
64515* 0 users:(("Xwayland",pid=4667,fd=5))
--
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/1897224
Title:
Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
Status in Mutter:
Unknown
Status in snapd:
In Progress
Status in mutter package in Ubuntu:
In Progress
Status in snapd package in Ubuntu:
Won't Fix
Status in mutter source package in Groovy:
Fix Committed
Status in snapd source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users who select the Wayland session on Ubuntu 20.10 cannot run snap
confined X11 applications, due to gnome-shell no longer listening on an
abstract socket for connections.
* The fix, which has been accepted into upstream's gnome-3-38 branch
reverts the change removing the abstract socket, and fixes the bug that
prompted it's removal:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508
[Test Case]
* Start with a stock Ubuntu 20.10 desktop install.
* At the GDM login screen, after selecting your user account use the gear
icon to select the "Ubuntu on Wayland" session, and log in.
* Ensure Chromium is installed by running "sudo snap install
chromium".
* Try to run "chromium" from the terminal. Without the fix, it will fail
with the error "Unable to open X display". With the fix applied, it
will launch as normal.
[Regression Potential]
* The patch modifies the logic gnome-shell uses to launch Xwayland. So
there is a potential that the change could break X11 application
support on the Wayland session.
* The default configuration for gnome-shell is to launch Xwayland on
session start, so it should be immediately obvious if there are
problems.
* In addition to checking snapped X11 apps like Chromium, verify that a
few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).
[Other Info]
* Running "ss -xlp | grep Xwayland" should show that it is listening on
both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
"@/tmp/.X11-unix/X0" (the abstract socket).
---
I'm trying to run chromium installed via snap in Ubuntu 20.10 when running
Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
> chromium
[49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to
open X display.
I am able to run Firefox just fine (assuming that Firefox still runs
on xwayland) and also Intellij snap works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 25 09:45:16 2020
InstallationDate: Installed on 2016-09-05 (1480 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
Snap: chromium 85.0.4183.121 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I am using Ubuntu 20.04. Here is the output of snap info: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/candidate/vaapi refresh-date: 2020-05-09T15:52:01+02:00 channels: latest/stable:81.0.4044.138 2020-05-06T18:11:18Z (1143) 161MB - latest/candidate: 81.0.4044.138 2020-05-06T14:20:15Z (1143) 161MB - latest/beta: 83.0.4103.44 2020-05-08T01:02:43Z (1144) 163MB - latest/edge: 84.0.4128.3 2020-04-29T05:50:21Z (1136) 164MB - installed: 81.0.4044.113 (1117) 165MB - -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I have tried the 81.0.4044.113 vaap candidate, but it is showing this warning at startup: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) For reference, this is the output of vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile2: VAEntrypointVLD -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1875134] Re: Brightness and contrast not working on Canon Lide 60
*** This bug is a duplicate of bug 1868408 *** https://bugs.launchpad.net/bugs/1868408 @Bartosz: this happens both using simple-scan and scanimage executables, so this seems to be related to Sane backend. If you still think the debug output will be useful, you can ask this again in the related bug #1868408 and I will send it there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1875134 Title: Brightness and contrast not working on Canon Lide 60 Status in sane-backends package in Ubuntu: New Bug description: When using /usr/bin/scanimage (or /usr/bin/simple-scan) to scan an image using a Canon CanoScan Lide 60 scanner, it ignores whatever you put in the --brightness and --contrast parameters. This was working in Ubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 08:51:41 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1875134/+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 1868408] Re: scanimage doesn't respect options (brightness, contrast, ...) with Canon CanoScan LIDE 35
This bug also affects Canon CanoScan LIDE 60. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1868408 Title: scanimage doesn't respect options (brightness, contrast, ...) with Canon CanoScan LIDE 35 Status in sane-backends package in Ubuntu: Confirmed Bug description: Device: Canon CanoScan LIDE 35 Options (--brightness and --contrast) are not respected. Reproduce the bug: Scan the same document with scanimage --brightness=0 > 0.pnm and scanimage --brightness=100 > 100.pnm The result will be the same. Changing the output format doesn't change anything. Graphical programs (simple-scan 3.36.0, skanlite 2.1.0.1) have the same problem. But with xsane-0.999 it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 22:39:23 2020 InstallationDate: Installed on 2020-01-05 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1868408/+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 1875134] [NEW] Brightness and contrast not working on Canon Lide 60
Public bug reported: When using /usr/bin/scanimage (or /usr/bin/simple-scan) to scan an image using a Canon CanoScan Lide 60 scanner, it ignores whatever you put in the --brightness and --contrast parameters. This was working in Ubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 08:51:41 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (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 sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1875134 Title: Brightness and contrast not working on Canon Lide 60 Status in sane-backends package in Ubuntu: New Bug description: When using /usr/bin/scanimage (or /usr/bin/simple-scan) to scan an image using a Canon CanoScan Lide 60 scanner, it ignores whatever you put in the --brightness and --contrast parameters. This was working in Ubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 08:51:41 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1875134/+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 1868872] Re: Nautilus Cant open files in shared folders
Yes. It solves the problem. Thanks -- 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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: Incomplete Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 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/1868872/+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 1868872] Re: Nautilus Cant open files in shared folders
Sorry Sebastian for some reason i don't received an email with your questions. - I only see this in .doc files in shared folders. PDF opens ok - the access is smb:// - I will post try to post the journal later - The error says: no app cant open the file "nameof the file".doc the file is of an unknown type -- 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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: Incomplete Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 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/1868872/+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 1868886] [NEW] Open VPNs stop working after upgrade
Public bug reported: Openvpn stops working after some updates. last connections was 25 days ago the Mar 24 22:25:54 miguel-X453MA nm-openvpn[7358]: Cannot load certificate file /home/miguel/Nextcloud/pontecontaescritorioclientmiguel/82B6CE01665256B1.pem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-openvpn-gnome 1.8.12-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 22:20:40 2020 SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (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-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1868886 Title: Open VPNs stop working after upgrade Status in network-manager-openvpn package in Ubuntu: New Bug description: Openvpn stops working after some updates. last connections was 25 days ago the Mar 24 22:25:54 miguel-X453MA nm-openvpn[7358]: Cannot load certificate file /home/miguel/Nextcloud/pontecontaescritorioclientmiguel/82B6CE01665256B1.pem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-openvpn-gnome 1.8.12-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 22:20:40 2020 SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1868886/+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 1868872] Re: Nautilus Cant open files in shared folders
** Attachment added: "The error" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+attachment/5341080/+files/Captura%20de%20ecr%C3%A3%20de%202020-03-24%2020-38-24.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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: New Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 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/1868872/+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 1868872] [NEW] Nautilus Cant open files in shared folders
Public bug reported: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 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 -- 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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: New Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 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/1868872/+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 1868872] Re: Nautilus Cant open files in shared folders
** Attachment added: "in nemo no error" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+attachment/5341081/+files/Captura%20de%20ecr%C3%A3%20de%202020-03-24%2020-42-15.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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: New Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 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/1868872/+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 1860904] Re: I was updating my linux and an error appeared saying the update could not continue
I was able to fix it I rant this command: "sudo apt-get install -f" Then I attempted an update, and it was successful -- 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/1860904 Title: I was updating my linux and an error appeared saying the update could not continue Status in libreoffice package in Ubuntu: New Bug description: I was updating my linux and the update program said that if found a problem and could not complete the update ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libreoffice-common 1:6.3.3-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 15:10:18 2020 DuplicateSignature: package:libreoffice-common:1:6.3.3-0ubuntu0.19.10.1 Unpacking libreoffice-help-common (1:6.3.4-0ubuntu0.19.10.1) over (1:6.3.3-0ubuntu0.19.10.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-FzjllT/49-libreoffice-help-common_1%3a6.3.4-0ubuntu0.19.10.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/polyfills.js.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/lib/libreoffice/share/template/common/wizard/agenda/1simple.ott.dpkg-new': Operation not permitted InstallationDate: Installed on 2019-08-04 (174 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: libreoffice Title: package libreoffice-common 1:6.3.3-0ubuntu0.19.10.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/wizard/agenda/1simple.ott.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to eoan on 2019-12-26 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1860904/+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 1849987] Re: empty space when on list view and when back to icon view
Bingo! After "nautilus -q" it appeared some message about some python-extension. I've found out the issue was related to an old "nautilus-terminal" python extension. Since the extension wasn't installed with apt or pip, i ran the following commands: sudo rm -r /usr/local/lib/python2.7/dist-packages/nautilus_terminal* sudo rm -r /usr/local/share/nautilus-python/extensions/ (note that under "usr/local/share/nautilus-python/extensions/" there was only a nautilus-terminal file) The issue then ceased to exist. After that, I could go to dconf-edit and go to: "org > flozz > nautilus-terminal" and "erase the key" since no schema was available. -- 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/1849987 Title: empty space when on list view and when back to icon view Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1849987/+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 1849987] Re: empty space when on list view and when back to icon view
I've now noticed the Bug is not reproducible in Nautilus Flatpak nightly version. So it does seem like it could be Ubuntu related. -- 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/1849987 Title: empty space when on list view and when back to icon view Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1849987/+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 1849987] Re: empty space when on list view and when back to icon view
Bug reported at: https://gitlab.gnome.org/GNOME/nautilus/issues/1273 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1273 https://gitlab.gnome.org/GNOME/nautilus/issues/1273 -- 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/1849987 Title: empty space when on list view and when back to icon view Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849987/+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 1849987] [NEW] empty space when on list view and when back to icon view
Public bug reported: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bug on Icon View screenshot" https://bugs.launchpad.net/bugs/1849987/+attachment/5300440/+files/Screenshot%20from%202019-10-26%2017-23-21.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/1849987 Title: empty space when on list view and when back to icon view Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849987/+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 1841420] [NEW] Xorg freeze
Public bug reported: Constant video freeze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 10:17:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-55-generic, x86_64: installed anbox, 1, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d] InstallationDate: Installed on 2018-08-20 (370 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.213:bd06/26/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1841420 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Constant video freeze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 10:17:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-55-generic, x86_64: installed anbox, 1, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d] InstallationDate: Installed on 2018-08-20 (370 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1841421] [NEW] Xorg freeze
Public bug reported: Constant video freeze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 10:17:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-55-generic, x86_64: installed anbox, 1, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d] InstallationDate: Installed on 2018-08-20 (370 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.213:bd06/26/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1841421 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Constant video freeze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 10:17:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-55-generic, x86_64: installed anbox, 1, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d] InstallationDate: Installed on 2018-08-20 (370 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1074351] Re: Vertical scrollbar has no minimal height
No, I don't have this problem anymore. It was a long time ago! I now have evince 3.28.4, with Xfce 4.12.2 (gtk2), on Xubuntu 18.04 LTS 32 bit. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic uname -a Linux 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:26:32 UTC 2019 i686 i686 i686 GNU/Linux -- 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/1074351 Title: Vertical scrollbar has no minimal height Status in evince package in Ubuntu: Incomplete Bug description: Since the upgrade to Xubuntu 12.10 (packet evince 3.6.0-0ubuntu2), the vertical scrollbar has a height that is strictly proportional to the visible fraction of the document. This means that becomes vanishingly small when the document is very long. I did not have this behavior with Xubuntu 12.04. $ uname -a Linux asuslinux 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:27:31 UTC 2012 i686 i686 i686 GNU/Linux Window managers: tried with Compiz and with Metacity. See attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1074351/+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 1825060] Re: libreoffice
Hi, I have tested the beta of Ubuntu 19.04 and it seems that it is already fixed. I will wait to update. Thank you and sorry for the inconvenience. El mié, 17-04-2019 a las 09:19 +, Sebastien Bacher escribió: > Thank you for taking the time to report this bug and helping to > makeUbuntu better. Unfortunately, we cannot work on this bug because > yourdescription didn't include enough information. You may find it > helpfulto read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be > gratefulif you would then provide a more complete description of the > problem. > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > At a minimum, we need:1. The specific steps or actions you took that > caused you to encounter the problem.2. The behavior you expected.3. > The behavior you actually encountered (in as much detail as > possible).Thanks! > ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low > ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete > -- 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/1825060 Title: libreoffice Status in libreoffice package in Ubuntu: Incomplete Bug description: In Libreoffice you can not put mosaic window from version 6.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825060/+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 1825060] [NEW] libreoffice
Public bug reported: In Libreoffice you can not put mosaic window from version 6.0 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1825060 Title: libreoffice Status in libreoffice package in Ubuntu: New Bug description: In Libreoffice you can not put mosaic window from version 6.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825060/+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 1354213] Re: With 'dwell-click' enabled there is no scrolling with mousewheel in gtk3 windows
Sorry, adding this at the end of ~/.profile solves the problem for the mentioned reason: export GDK_CORE_DEVICE_EVENTS=1 I forgot to add "export". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mousetweaks in Ubuntu. https://bugs.launchpad.net/bugs/1354213 Title: With 'dwell-click' enabled there is no scrolling with mousewheel in gtk3 windows Status in mousetweaks package in Ubuntu: Confirmed Bug description: Test Case: enable dwell-click in System Settings > Universal access > Pointing & Clicking > Hover click or gsettings set org.gnome.desktop.a11y.mouse dwell-click-enabled true Try to scroll in a scroll-able gtk3 window with mouse wheel, nothing happens Scrolling is possible in gtk2 windows like Firefox ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mousetweaks 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 7 19:33:45 2014 InstallationDate: Installed on 2014-07-31 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140729) SourcePackage: mousetweaks UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousetweaks/+bug/1354213/+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 1354213] Re: With 'dwell-click' enabled there is no scrolling with mousewheel in gtk3 windows
A possible workaround is explained here: https://forums.linuxmint.com/viewtopic.php?t=242806 Adding this: GDK_CORE_DEVICE_EVENTS=1 at the end of ~/.profile solves this issue. GTK3 uses the X Input Device Extension Library by default. It seems that for some reason this extension is the source of the problem. Setting that environment variable, GKT3 only reacts to core X input events. It doesn't use that extension library. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mousetweaks in Ubuntu. https://bugs.launchpad.net/bugs/1354213 Title: With 'dwell-click' enabled there is no scrolling with mousewheel in gtk3 windows Status in mousetweaks package in Ubuntu: Confirmed Bug description: Test Case: enable dwell-click in System Settings > Universal access > Pointing & Clicking > Hover click or gsettings set org.gnome.desktop.a11y.mouse dwell-click-enabled true Try to scroll in a scroll-able gtk3 window with mouse wheel, nothing happens Scrolling is possible in gtk2 windows like Firefox ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mousetweaks 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 7 19:33:45 2014 InstallationDate: Installed on 2014-07-31 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140729) SourcePackage: mousetweaks UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousetweaks/+bug/1354213/+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 1803059] Re: Nullpointer dereference
Thank you, the bug is fixed for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1803059 Title: Nullpointer dereference Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Bionic: Fix Released Status in poppler source package in Cosmic: Fix Released Bug description: * Impact Evince segfaults on some pdf documents * Test case Download and try to open https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't segfault * Regression potential Nothing special to test, make sure evince still opens pdfs without issue - System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Evince version: GNOME Document Viewer 3.28.4 While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04 LTS), a null-pointer dereference was observed, initially this was reported to evince but the evince team advised that the issue is in poppler, the library used by evince to render PDF, poppler version: 0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the issue is already fixed in poppler 0.70, but this will still crash your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70. Fuzzing result showing a very important vulnerability in a package currently shipped by a major Linux distribution is still of interest, even if that Linux distribution does not package the latest released upstream version. I think Ubuntu is still using, Source: poppler Version: 0.62.0-2ubuntu2.2 So, most of the systems will be affected to this issue. Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1803059] Re: Nullpointer dereference
Problem seems to be still present, possibly due to previous change. Crashes when opening PDF files since last update in Ubuntu ** Changed in: poppler (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1803059 Title: Nullpointer dereference Status in poppler package in Ubuntu: Confirmed Status in poppler source package in Bionic: Fix Released Status in poppler source package in Cosmic: Fix Released Bug description: * Impact Evince segfaults on some pdf documents * Test case Download and try to open https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't segfault * Regression potential Nothing special to test, make sure evince still opens pdfs without issue - System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Evince version: GNOME Document Viewer 3.28.4 While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04 LTS), a null-pointer dereference was observed, initially this was reported to evince but the evince team advised that the issue is in poppler, the library used by evince to render PDF, poppler version: 0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the issue is already fixed in poppler 0.70, but this will still crash your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70. Fuzzing result showing a very important vulnerability in a package currently shipped by a major Linux distribution is still of interest, even if that Linux distribution does not package the latest released upstream version. I think Ubuntu is still using, Source: poppler Version: 0.62.0-2ubuntu2.2 So, most of the systems will be affected to this issue. Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1803059] Re: Nullpointer dereference
I am getting reproducible crashes after update from poppler 0.62.0-2ubuntu2.2 to poppler 0.62.0-2ubuntu2.4 Test PDF file attached. Crashed experiences since following upgrades: libpoppler-cpp-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 libpoppler-cpp0v5 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 libpoppler-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 libpoppler-glib8 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 libpoppler-private-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 libpoppler-qt5-1 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 libpoppler73 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 poppler-utils (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4 Reverting to previous versions fixes the crashes. System: 18.04.1 LTS bionic (32 bit) Linux 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:10 UTC 2018 i686 i686 i686 GNU/Linux PC gdb trace: Starting program: /usr/bin/evince Bureau/evince/test_CGV_FORFAIT_hors_opt_20170308.pdf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [New Thread 0xb5b82b40 (LWP 6602)] [New Thread 0xb51ffb40 (LWP 6603)] [New Thread 0xb47ffb40 (LWP 6604)] warning: Error reading shared library list entry at 0x6840 warning: Error reading shared library list entry at 0x5a60 [New Thread 0xb3c77b40 (LWP 6608)] warning: Error reading shared library list entry at 0x75e0 [New Thread 0xb1356b40 (LWP 6609)] warning: Error reading shared library list entry at 0x5130 warning: Error reading shared library list entry at 0x97b0 Thread 6 "EvJobScheduler" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb1356b40 (LWP 6609)] 0xb096a379 in Parser::makeStream(Object&&, unsigned char*, CryptAlgorithm, int, int, int, int, bool) () from /usr/lib/i386-linux-gnu/libpoppler.so.73 ** Attachment added: "With poppler 0.62.0-2ubuntu2.4, evince and other PDF readers will immediately crash on my system" https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+attachment/5220277/+files/test_CGV_FORFAIT_hors_opt_20170308.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1803059 Title: Nullpointer dereference Status in poppler package in Ubuntu: Fix Committed Status in poppler source package in Bionic: Fix Released Status in poppler source package in Cosmic: Fix Released Bug description: * Impact Evince segfaults on some pdf documents * Test case Download and try to open https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't segfault * Regression potential Nothing special to test, make sure evince still opens pdfs without issue - System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Evince version: GNOME Document Viewer 3.28.4 While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04 LTS), a null-pointer dereference was observed, initially this was reported to evince but the evince team advised that the issue is in poppler, the library used by evince to render PDF, poppler version: 0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the issue is already fixed in poppler 0.70, but this will still crash your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70. Fuzzing result showing a very important vulnerability in a package currently shipped by a major Linux distribution is still of interest, even if that Linux distribution does not package the latest released upstream version. I think Ubuntu is still using, Source: poppler Version: 0.62.0-2ubuntu2.2 So, most of the systems will be affected to this issue. Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Coming back from Pop!_OS 18.10 (Based on Ubuntu 18.10, 4.18.0-10-generic) Still haven't tried with Audacity, but gnome-sound-recorded and Telegram Desktop have been fixed in my case. All I did this time was setting default-sample-rate = 48000 on /etc/pulse/daemon.conf and restarting (Probably restarting pulseaudio is enough). before this, trying to send an audio recording through Telegram would end in an "muted" audio. Now it's working perfectly. You can try with arecord arecord -f cd -d 10 test.wav -> For recording aplay test.wav -> For playing (Probably gonna end up in noise) arecord -f cd -d 10 -r 48000 test-mic.wav -> recording with the 48000 sample rate should provide good results PD: Remember to increase a bit the mic volume from the sound settings -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1764965/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Hi! Asus Crosshair VI Hero here with Linux 4.15.0-33-generic on Pop!_OS 18.04 (Ubuntu based). This problem is also affecting me, but I could fix it more or less. I'm using alsa for this specific device, so the audio control center for gnome is still usable and the DisplayPort audio (AMDGPU) is still working. In my case all I needed to do was loading the module this way: pacmd load-module module-alsa-source device=hw:1,2 I found the corresponding device using the instructions from this web- page: https://frdmtoplay.com/gigabyte-front-panel-audio-with-linux/ It will make a duplicate entry on the audio input list of Gnome audio settings, but now recording is working for me. Once you try the command above and you verify it works, you can add it to the default.pa file of pulse settings (/etc/pulse/default.pa or ~/.config/pulse/default.pa) and add it after the hardware detection (In my case, line 58) ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif load-module module-alsa-source device=hw:1,2 < Add this line Now with pulseaudio -k or restarting everything should be working without needing to do anything -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to:
[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
Hi, I'm having the same problem with 18.04. The command "sudo kbd_mode -s" (scancode (RAW) mode) works fine as well as the "-k" argument (key code mode (MEDIUMRAW)) as well. As opposed, "-u" (UTF-8 (UNICODE) mode) and "-a" (ASCII mode (XLATE)) arguments bring the bug back. -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1689927] Re: Rhythmbox crashes after starting it (Ubuntu MATE 17.04)
Thanks for the suggestion, but it doesn't works for me. I've removed the packet and it still crashes when trying to extract music to MP3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1689927 Title: Rhythmbox crashes after starting it (Ubuntu MATE 17.04) Status in rhythmbox package in Ubuntu: Invalid Bug description: After starting Rhythmbox the first time after fresh installing Ubuntu MATE 17.04, Rhythmbox searches for new files. The next time i start it, Rhythmbox crashes after less than 5 seconds. Rhythmbox is not usable anymore. You can see the attached screenshot for more details. EDIT 13.05.2017: When i start Rhythmbox i a terminal, this is the result: ** (rhythmbox:5566): Gtk-CRITICAL **: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed (rhythmbox:5566): Gtk-WARNING **: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:5566): Gtk-WARNING **: actionhelper: action app.play- shuffle can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:5566): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (rhythmbox:5566): Gtk-WARNING **: Allocating size to GtkButton 0x5620febf7c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (rhythmbox:5566): Gtk-WARNING **: Allocating size to GtkButton 0x5620fec6f880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (rhythmbox:5566): Gtk-CRITICAL **: gtk_tree_view_update_button_position: assertion 'column_el != NULL' failed Speicherzugriffsfehler (Speicherabzug geschrieben) ** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1689927/+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 1689927] Re: Rhythmbox crashes after starting it (Ubuntu MATE 17.04)
When I start it from console, the result is: (rhythmbox:29465): Rhythmbox-WARNING **: 21:09:26.010: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.MediaKeys was not provided by any .service files (rhythmbox:29465): Gtk-WARNING **: 21:09:26.170: Theme parsing error: :2:36: The style property GtkCheckButton:indicator-spacing is deprecated and shouldn't be used anymore. It will be removed in a future version Violación de segmento (`core' generado) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1689927 Title: Rhythmbox crashes after starting it (Ubuntu MATE 17.04) Status in rhythmbox package in Ubuntu: Invalid Bug description: After starting Rhythmbox the first time after fresh installing Ubuntu MATE 17.04, Rhythmbox searches for new files. The next time i start it, Rhythmbox crashes after less than 5 seconds. Rhythmbox is not usable anymore. You can see the attached screenshot for more details. EDIT 13.05.2017: When i start Rhythmbox i a terminal, this is the result: ** (rhythmbox:5566): Gtk-CRITICAL **: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed (rhythmbox:5566): Gtk-WARNING **: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:5566): Gtk-WARNING **: actionhelper: action app.play- shuffle can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:5566): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (rhythmbox:5566): Gtk-WARNING **: Allocating size to GtkButton 0x5620febf7c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (rhythmbox:5566): Gtk-WARNING **: Allocating size to GtkButton 0x5620fec6f880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (rhythmbox:5566): Gtk-CRITICAL **: gtk_tree_view_update_button_position: assertion 'column_el != NULL' failed Speicherzugriffsfehler (Speicherabzug geschrieben) ** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1689927/+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 1779592] Re: I have video lagging errors
Hi, In that laptop I use a double boot with W10 and there is not problems with video there, in Ubuntu I have a skipping frame problem, like 2 or 3 seconds of skipping frames in chrome and also in VLC. On Sun, Jul 1, 2018, 22:45 Daniel van Vugt wrote: > It appears your screen is 1366x768 and the CPU/GPU is an i5-4200U. I > would not expect any performance problems with those. > > Can you please elaborate as to what you mean by "lagging"? Do you mean > everything is smooth but delayed? Or do you mean it is stuttering > (skipping frames)? > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) > > ** Tags added: performance > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1779592 > > Title: > I have video lagging errors > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > In browser (Chrome) and VLC. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7 > ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 > Uname: Linux 4.15.0-23-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Jul 1 20:03:55 2018 > DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: bionic > DistroVariant: ubuntu > DpkgLog: > > GraphicsCard: >Intel Corporation Haswell-ULT Integrated Graphics Controller > [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f3] > InstallationDate: Installed on 2018-04-21 (71 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > MachineType: Dell Inc. Inspiron 5437 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic > root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago) > dmi.bios.date: 09/06/2013 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A04 > dmi.board.name: 0DM6M9 > dmi.board.vendor: Dell Inc. > dmi.board.version: A04 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: Not Specified > dmi.modalias: > dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: > dmi.product.name: Inspiron 5437 > dmi.product.version: Not Specified > 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 > 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 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779592/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1779592 Title: I have video lagging errors Status in gnome-shell package in Ubuntu: Incomplete Bug description: In browser (Chrome) and VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 1 20:03:55 2018 DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f3] InstallationDate: Installed on 2018-04-21 (71 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Inspiron 5437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
[Desktop-packages] [Bug 1779592] [NEW] I have video lagging errors
Public bug reported: In browser (Chrome) and VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 1 20:03:55 2018 DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f3] InstallationDate: Installed on 2018-04-21 (71 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Inspiron 5437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0DM6M9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified 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 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1779592 Title: I have video lagging errors Status in xorg package in Ubuntu: New Bug description: In browser (Chrome) and VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 1 20:03:55 2018 DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f3] InstallationDate: Installed on 2018-04-21 (71 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Inspiron 5437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0DM6M9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified 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 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
[Desktop-packages] [Bug 1775377] [NEW] package transmission-gtk 2.92-2ubuntu3.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: hjfjf ProblemType: Package DistroRelease: Ubuntu 17.10 Package: transmission-gtk 2.92-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu3.9 AptOrdering: transmission-gtk:amd64: Install google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 10:21:45 2018 ErrorMessage: problemas de dependencias - se deja sin configurar Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: transmission Title: package transmission-gtk 2.92-2ubuntu3.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: transmission (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1775377 Title: package transmission-gtk 2.92-2ubuntu3.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in transmission package in Ubuntu: New Bug description: hjfjf ProblemType: Package DistroRelease: Ubuntu 17.10 Package: transmission-gtk 2.92-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu3.9 AptOrdering: transmission-gtk:amd64: Install google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 10:21:45 2018 ErrorMessage: problemas de dependencias - se deja sin configurar Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: transmission Title: package transmission-gtk 2.92-2ubuntu3.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1775377/+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 1771839] [NEW] keyboard
Public bug reported: The keyboard is desconfigurated for spanish. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 17 10:03:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06fb] InstallationDate: Installed on 2017-04-21 (390 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3250 ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.5.2 dmi.board.name: 0J4NFV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: Vostro dmi.product.name: Vostro 3250 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 17 08:46:00 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 HDMI-1 xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1771839 Title: keyboard Status in xorg package in Ubuntu: New Bug description: The keyboard is desconfigurated for spanish. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 17 10:03:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06fb] InstallationDate: Installed on 2017-04-21 (390 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3250 ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.5.2 dmi.board.name: 0J4NFV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: Vostro dmi.product.name: Vostro 3250 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. version.compiz: compiz
[Desktop-packages] [Bug 1745793] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distin
Public bug reported: thanks ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 28 01:31:59 2018 ErrorMessage: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del paquetes libsane1:i386 InstallationDate: Installed on 2018-01-27 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del paquetes libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1745793 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del paquetes libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: thanks ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 28 01:31:59 2018 ErrorMessage: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del paquetes libsane1:i386 InstallationDate: Installed on 2018-01-27 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del paquetes libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1745793/+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 1741632] Re: FW update error: could not find thunderbolt device
Reproducible via the CLI too ``` fwupdmgr update Downloading 21.00 for XPS13 9360 Thunderbolt Controller... Fetching firmware https://fwupd.org/downloads/eac3961ba9bd466f6e34d9276c27d524395d7c3c-NN1TN_NVM21.00.cab Downloading… [] Updating 21.00 on XPS13 9360 Thunderbolt Controller... Decompressing… [- ] could not find thunderbolt device at /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0 ``` -- 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/1741632 Title: FW update error: could not find thunderbolt device Status in gnome-software package in Ubuntu: Confirmed Bug description: When trying to install a firmware update, I get this error: Failed to update "Thunderbolt NVM from Xps Notebook 9360" could not find the thunderbolt device at /sys/devices/pci:00/:00:1c.0/:01:00/:02:00/:03:00/domain0/0-0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 14:29:27 2018 InstallationDate: Installed on 2018-01-05 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash 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/1741632/+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 1742459] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: No actualiza ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Tue Jan 9 23:37:29 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-11-01 (1896 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-01-10 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1742459 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: No actualiza ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Tue Jan 9 23:37:29 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-11-01 (1896 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-01-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1742459/+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 1273682] Re: Xorg crashed with SIGABRT in swlDrmFreeSurfaces()
** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) => wax miguel (waxmigs2902) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1273682 Title: Xorg crashed with SIGABRT in swlDrmFreeSurfaces() Status in fglrx-installer package in Ubuntu: Confirmed Bug description: Upgraded to Ubuntu 14.04 via "do-release-upgrade -d" now OS complains about "Xorg crashed with SIGABRT in swlDrmFreeSurfaces()". ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.14.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.11.0-15-generic i686 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 27 05:45:06 2014 DistUpgraded: 2014-01-27 04:45:37,303 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.125, 3.11.0-15-generic, i686: installed fglrx-updates, 13.125, 3.13.0-5-generic, i686: installed virtualbox, 4.3.2, 3.11.0-15-generic, i686: installed virtualbox, 4.3.2, 3.13.0-5-generic, i686: installed ExecutablePath: /usr/bin/Xorg GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84c8] InstallationDate: Installed on 2011-11-02 (817 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) JockeyStatus: kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/X :1 -background none -verbose -auth /var/run/gdm/auth-for-gdm-CjhhKY/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=en_US.UTF-8 TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=826274e2-edc0-4e61-bfa4-b863df6ffd00 ro nomodeset Signal: 6 SourcePackage: fglrx-installer StacktraceTop: swlDrmFreeSurfaces () from /usr/lib/i386-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so xdl_xs114_atiddxDriCloseScreen () from /usr/lib/i386-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so xdl_xs114_atiddxDriScreenInit () from /usr/lib/i386-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so xdl_xs114_atiddxScreenInit () from /usr/lib/i386-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so AddScreen () Title: Xorg crashed with SIGABRT in swlDrmFreeSurfaces() UpgradeStatus: Upgraded to trusty on 2014-01-27 (0 days ago) UserGroups: openerp dmi.bios.date: 06/13/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F1A75-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd06/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu11 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Mon Jan 27 10:10:48 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubun
[Desktop-packages] [Bug 1735875] [NEW] package jackd1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-ja
Public bug reported: no pude instalar linuxsampler ProblemType: Package DistroRelease: Ubuntu 17.10 Package: jackd1 (not installed) Uname: Linux 4.14.3-041403-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 2 00:10:27 2017 DpkgTerminalLog: Preparing to unpack .../jackd1_1%3a0.125.0-2_amd64.deb ... Unpacking jackd1 (1:0.125.0-2) ... dpkg: error processing archive /var/cache/apt/archives/jackd1_1%3a0.125.0-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 DuplicateSignature: package:jackd1:(not installed) Unpacking jackd1 (1:0.125.0-2) ... dpkg: error processing archive /var/cache/apt/archives/jackd1_1%3a0.125.0-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 InstallationDate: Installed on 2017-10-22 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: jack-audio-connection-kit Title: package jackd1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jack-audio-connection-kit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jack-audio-connection-kit in Ubuntu. https://bugs.launchpad.net/bugs/1735875 Title: package jackd1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92 ~dfsg-5ubuntu1 Status in jack-audio-connection-kit package in Ubuntu: New Bug description: no pude instalar linuxsampler ProblemType: Package DistroRelease: Ubuntu 17.10 Package: jackd1 (not installed) Uname: Linux 4.14.3-041403-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 2 00:10:27 2017 DpkgTerminalLog: Preparing to unpack .../jackd1_1%3a0.125.0-2_amd64.deb ... Unpacking jackd1 (1:0.125.0-2) ... dpkg: error processing archive /var/cache/apt/archives/jackd1_1%3a0.125.0-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 DuplicateSignature: package:jackd1:(not installed) Unpacking jackd1 (1:0.125.0-2) ... dpkg: error processing archive /var/cache/apt/archives/jackd1_1%3a0.125.0-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 InstallationDate: Installed on 2017-10-22 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: jack-audio-connection-kit Title: package jackd1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjackserver.so.0', which is also in package libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-5ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jack-audio-connection-kit/+bug/1735875/+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 1726738] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1726739 *** https://bugs.launchpad.net/bugs/1726739 Public bug reported: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726738 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726738/+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 1726739] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726739 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726739/+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 1708500] [NEW] [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all. Rebooting does not fix & unmuting via alsamixer addresses the issue but audio play
Public bug reported: Rebooting does not fix & unmuting via alsamixer addresses the issue but audio plays from internal speakers AND headphones ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmendoza 2636 F pulseaudio /dev/snd/controlC1: mmendoza 2636 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 3 10:28:03 2017 InstallationDate: Installed on 2015-09-29 (674 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmendoza 2636 F pulseaudio /dev/snd/pcmC1D0p: mmendoza 2636 F...m pulseaudio /dev/snd/controlC1: mmendoza 2636 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago) dmi.bios.date: 05/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1708500 Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all. Rebooting does not fix & unmuting via alsamixer addresses the issue but audio plays from internal speakers AND headphones Status in alsa-driver package in Ubuntu: New Bug description: Rebooting does not fix & unmuting via alsamixer addresses the issue but audio plays from internal speakers AND headphones ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmendoza 2636 F pulseaudio /dev/snd/controlC1: mmendoza 2636 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 3 10:28:03 2017 InstallationDate: Installed on 2015-09-29 (674 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmendoza 2636 F pulseaudio /dev/snd/pcmC1D0p: mmendoza 2636 F...m pulseaudio /dev/snd/controlC1: mmendoza 2636 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago) dmi.bios.date: 05/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1708500/+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 1312756] Re: Monitor settings displays only one video resolution in Xubuntu 14.04
I'm using the Xenial. With an openchrome 1:0.3.3+git20160310-1 version the problem persists. In addition to activating an I2CDevices ativa option in xorg.conf (section device) to fix the system hang / freeze problem, black screen, monitor seems to shut down, when trying to start the GUI. However, I just upgraded to a version of PPA https://launchpad.net/~dylan.a/+archive/ubuntu/xxv-openchrome The problem of resolution persists. But solved another problem of freeze / black screen, no longer having to configure xorg.conf. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1312756 Title: Monitor settings displays only one video resolution in Xubuntu 14.04 Status in xserver-xorg-video-openchrome package in Ubuntu: Confirmed Bug description: A tool to monitor configuration displays only 1280x800 resolution. I tried setting the xorg.conf to display other resolutions, but did not succeed. My system: Xubuntu 14.04 (via LiveUSB) My hardware: lspci | grep -i vga 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1312756/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1658921 *** https://bugs.launchpad.net/bugs/1658921 Same problem after an upgrade from 16.04 to 16.10 via "do-release-upgrade". Ethernet and WiFi not managed. Solved it creating blank file at /etc/NetworkManager/conf.d/10-globally-managed-devices.conf as per comment #6 -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1674163] [NEW] imposibilidad de instalar una impresora
Public bug reported: Cada vez que intento instalarla marca error del sistema. No admite otra forma de instalarla ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;1;31mFAILED[0m] Failed to start Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb1-1\x2d2). See 'systemctl status "udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' for details. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 19 17:40:15 2017 DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics Controller [1849:2e32] InstallationDate: Installed on 2016-11-12 (127 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic root=UUID=8bc8c59a-fb09-421e-99b0-9f139eff2ea1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-27 (81 days ago) dmi.bios.date: 07/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: G41M-GS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/13/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 19 09:35:30 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 739 vendor SAM xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1674163 Title: imposibilidad de instalar una impresora Status in xorg package in Ubuntu: New Bug description: Cada vez que intento instalarla marca error del sistema. No admite otra forma de instalarla ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;1;31mFAILED[0m] Failed to start Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb1-1\x2d2). See 'systemctl status "udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' for details. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 19 17:40:15 2017 DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics Controller [1849:2e32] InstallationDate:
Re: [Desktop-packages] [Bug 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it as
sorry, I gave up and I gave the laptop to a family member who is going to reinstall an OS. Miguel On 3 January 2017 at 11:42, Michael Mess <1603...@bugs.launchpad.net> wrote: > Can you check the password in network-manager view and edit it there? > > I think that the "wrong password - enter new"-dialog does not save the > entered password and thus a reconnect with the old wrong password always > fails. > See also Bug #1542733 which I have experienced together with this one. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1603815 > > Title: > after updating to ubuntu 16.04 the network manager is unable to > connect me to the wifi network. I can see the network, but once I > introduce the password, it asks me for the password after a few > seconds and never connects. > > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > after updating to ubuntu 16.04 the network manager is unable to > connect me to the wifi network. I can see the network, but once I > introduce the password, it asks me for the password after a few > seconds and never connects. I use different devices connected to the > same wifi so it is not a problem of writting the wrong password. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: network-manager 1.1.93-0ubuntu4 > ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 > Uname: Linux 4.4.0-31-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sun Jul 17 16:58:17 2016 > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > InstallationDate: Installed on 2016-07-16 (1 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > IpRoute: >default via 192.168.2.1 dev enp2s0 proto static metric 100 >169.254.0.0/16 dev enp2s0 scope link metric 1000 >192.168.2.0/24 dev enp2s0 proto kernel scope link src > 192.168.2.242 metric 100 > NetworkManager.state: >[main] >NetworkingEnabled=true >WirelessEnabled=true >WWANEnabled=true > SourcePackage: network-manager > UpgradeStatus: No upgrade log present (probably fresh install) > nmcli-con: >NAME UUID TYPE > TIMESTAMP TIMESTAMP-REALAUTOCONNECT > AUTOCONNECT-PRIORITY READONLY DBUS-PATH > ACTIVE DEVICE STATE ACTIVE-PATH >Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 > 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes > 4294966297no/org/freedesktop/NetworkManager/Settings/2 > yes enp2s0 activated /org/freedesktop/NetworkManager/ > ActiveConnection/1 >BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 > 802-11-wireless 0 never yes 0 >no/org/freedesktop/NetworkManager/Settings/1 > no -- -- -- > nmcli-dev: >DEVICETYPE STATE DBUS-PATH > CONNECTION CON-UUID CON-PATH >enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 > Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 > /org/freedesktop/NetworkManager/ActiveConnection/1 >wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 > -- ---- >loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 > -- ---- > nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit > code 2: Error: Object 'nm' is unknown, try 'nmcli help'. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+ > subscriptions > -- 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/1603815 Title: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. Status in network-manager package in Ubuntu: Confirmed Bug description: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I u
[Desktop-packages] [Bug 1651698] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: The pc freezes sometimes ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Dec 21 01:09:25 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 FontConfigLog: /usr/share/fonts: caching, new cache contents: 0 fonts, 5 dirs /usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs /usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs /usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs /usr/share/fonts/X11/encodings/large: Bus error (core dumped) InstallationDate: Installed on 2016-12-08 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1651698 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in fontconfig package in Ubuntu: New Bug description: The pc freezes sometimes ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Dec 21 01:09:25 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 FontConfigLog: /usr/share/fonts: caching, new cache contents: 0 fonts, 5 dirs /usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs /usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs /usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs /usr/share/fonts/X11/encodings/large: Bus error (core dumped) InstallationDate: Installed on 2016-12-08 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1651698/+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 1644986] Re: Screen flickering since 16.10 upgrade
This affects me too. Wasn't an issue in Xubuntu 16.04 with three monitors plugged in to my desktop machine. However, after upgrading to 16.10 I am now getting occasional screen flickering that worsens in frequency over time. This seems to occur when the mouse pointer travels across monitors, with the worse flickering occurring on the primary monitor. Strangely, suspending to RAM and resuming the machine seems to *reset* the issue but not fix it. There are several other visual glitches affecting Libreoffice too. Let me know if you need me to gather any information about my machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1644986 Title: Screen flickering since 16.10 upgrade Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I'm noticing some random screen flickering since 16.10 upgrade. Something like every 10 minutes, mainly on the secondary monitor (hdmi connected), but sometimes on the laptop display too. Not sure if it's related, but when using LibreOffice Impress to display presentations on the secondary display the problem worsens, but it's only flickering in parts of the display, not all. HTH Fernando ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 26 12:17:18 2016 DistUpgraded: 2016-10-29 20:59:03,871 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2016-05-16 (193 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 003: ID 13d3:5652 IMC Networks Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE P50-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=244d0104-69e0-4b0e-98a5-f56d42d63020 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to yakkety on 2016-10-29 (27 days ago) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE P50-C dmi.product.version: PSPUEE-00C008EP dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Nov 26 09:36:23 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1644986/+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 1606238] Re: gnome-software won't open
** Also affects: gnome-software Importance: Undecided Status: New -- 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/1606238 Title: gnome-software won't open Status in GNOME Software: New Status in gnome-software package in Ubuntu: Triaged Bug description: Hello, I upgrade the system from Ubuntu 14.04 to 16.04 some time ago. At beginning, gnome-software refused to open and I had to remove old ubuntu software and "--reinstall" the gnome-software. Everything was fine, except for many sorts of packages it can't install so I installed synaptic. Some days ago, gnome software went on a strike but claimed nothing ! I can open a terminal and call gnome-software : nothing The launcher turns around in the dock. Any Idea ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 25 15:28:05 2016 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1606238/+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 1639483] [NEW] cgange resolution
Public bug reported: After the last update sotware Submitted by ubuntu screen resolution of 800x600 and Change Every Time I boot ubuntu manually Fix 1024x768. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDmesg: [ 34.778187] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 826.163504] audit: type=1400 audit(1478367307.183:18): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2751 comm="apparmor_parser" [ 826.163517] audit: type=1400 audit(1478367307.183:19): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2751 comm="apparmor_parser" [ 826.164164] audit: type=1400 audit(1478367307.183:20): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2751 comm="apparmor_parser" Date: Sat Nov 5 14:59:50 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:83a2] InstallationDate: Installed on 2015-11-14 (357 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=7bf112e5-6b74-44d0-8c32-7610a6b032b1 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-V EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Nov 5 14:21:57 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPS/2+USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty 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/1639483 Title: cgange resolution Status in xorg package in Ubuntu: New Bug description: After the last update sotware Submitted by ubuntu screen resolution of 800x600 and Change Every Time I boot ubuntu manually Fix 1024x768. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDmesg: [ 34.778187] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 826.163504] audit: type=1400 audit(1478367307.183:18): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2751 comm="apparmor_parser" [ 826.163517] audit: type=1400 audit(1478367307.183:19): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2751 comm="apparmor_parser" [ 826.164164]
[Desktop-packages] [Bug 1638343] [NEW] package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: s'està intentant sobreescriure «/lib/udev/ru
Public bug reported: It appeared while I was installing wine ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 13:04:08 2016 ErrorMessage: s'està intentant sobreescriure «/lib/udev/rules.d/40-libsane.rules» compartit, que és diferent d'altres instàncies del paquet libsane:i386 InstallationDate: Installed on 2016-09-07 (55 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: s'està intentant sobreescriure «/lib/udev/rules.d/40-libsane.rules» compartit, que és diferent d'altres instàncies del paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1638343 Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: s'està intentant sobreescriure «/lib/udev/rules.d/40-libsane.rules» compartit, que és diferent d'altres instàncies del paquet libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: It appeared while I was installing wine ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 13:04:08 2016 ErrorMessage: s'està intentant sobreescriure «/lib/udev/rules.d/40-libsane.rules» compartit, que és diferent d'altres instàncies del paquet libsane:i386 InstallationDate: Installed on 2016-09-07 (55 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: s'està intentant sobreescriure «/lib/udev/rules.d/40-libsane.rules» compartit, que és diferent d'altres instàncies del paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1638343/+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 1616943] Re: Can't auth against U1 in g-s
I have the same problem on Xubuntu 16.04 installing krita 3.0.1.1. Finally I installed correctly from terminal, but the issue exists in the Software Center. -- 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/1616943 Title: Can't auth against U1 in g-s Status in gnome-software package in Ubuntu: In Progress Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Yakkety: In Progress Bug description: [Impact] Authentication using Ubuntu One credentials to install/remove snaps always fails. This is due to a behaviour change in snapd (no longer accepts login requests from non-root users). Existing credentials continue to work. [Test Case] 1. Delete any existing credentials by deleting passwords marked "com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse. 2. Start GNOME Software 3. Search for a snap (e.g. "moon-buggy") 4. Install Snap 5. Enter Ubuntu One credentials when prompted Observed result: Dialog says "Incorrect email or password". Expected result: Authentication completes and the snap is installed. [Regression Potential] The solution is to use a new D-Bus service (snapd-login-service) and new library (snapd-glib) to get the Macaroon from snapd. This has some risk of introducing new bugs. The change is minimised (other snapd code paths unchanged) and the alternative is login to be impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+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 1021375] Re: Nautilus says the USB stick is read only when it is not
I had this problem with Ubuntu 16.04.1. So annoying! killall nautilus solves the problem -- 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/1021375 Title: Nautilus says the USB stick is read only when it is not Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: First time I use an USB drive since I updated to 12.04 and I found a really annoying bug on Nautilus. Nautilus claims that the destination drive is read-only when in fact it is not. How to reproduce: 1. Connect a USB stick drive to your competer. 2. The USB will appear in the desktop. 3. Open two Nautilus windows one in your home folder, other in the USB stick drive. 4. Select any file from your home folder (small enough to fit the free space in the USB drive) 5. Drag the file and drop it in the USB drive window. -- Nautilus will say that it cannot copy the file because the destination is read ony -- If you try the copy the same file with the terminal you will see that the file is copied without problem, other programs like gedit or LibreOffice can write in the usb stick drive just fine. It is not a problem with the USB stick, as shown here: [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd [ 6232.426378] scsi8 : usb-storage 2-1:1.0 [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP PQ: 0 ANSI: 0 CCS [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 GB/1.86 GiB) [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.210138] sdb: sdb1 [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk The permisions on the removable drive are set correctly: sergio@shana:/media$ ls -lah total 12K drwxr-xr-x 3 root root 4,0K jul 5 10:20 . drwxr-xr-x 23 root root 4,0K jul 3 11:01 .. drwx-- 5 sergio sergio 4,0K dic 31 1969 DESIGNPLUS There is enough free space in the drive: sergio@shana:/media/DESIGNPLUS$ df -h S.ficheros Tamaño Usado Disp Uso% Montado en /dev/sda2 50G 5,5G 42G 12% / udev 1,5G 4,0K 1,5G 1% /dev tmpfs579M 872K 579M 1% /run none 5,0M 0 5,0M 0% /run/lock none 1,5G 1,1M 1,5G 1% /run/shm /dev/sda1497M 113M 360M 24% /boot /dev/sda5245G 111G 122G 48% /home /dev/sdb11,9G 681M 1,2G 36% /media/DESIGNPLUS A file can be copied to the USB stick using the cp command for example. sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS sergio@shana:~/Trash$ cd /media/DESIGNPLUS sergio@shana:/media/DESIGNPLUS$ ls -lah total 204K drwx-- 5 sergio sergio 4,0K jul 5 10:38 . drwxr-xr-x 3 root root 4,0K jul 5 10:20 .. -rw-r--r-- 1 sergio sergio 117K jul 5 10:14 ._Screen Shot 2012-06-30 at 8.50.37 AM.png -rw-r--r-- 1 sergio sergio 55K jun 30 08:51 Screen Shot 2012-06-30 at 8.50.37 AM.png drwx-- 4 sergio sergio 4,0K jul 5 10:05 .Spotlight-V100 drwx-- 2 sergio sergio 4,0K jul 5 10:05 .Trashes -rw-r--r-- 1 sergio sergio 4,0K jul 5 10:05 ._.Trashes -rw-r--r-- 1 sergio sergio 73 jul 5 10:38 wireless.txt But nautilus just dennies to copy the file claming that the destination is read only, when it is not. I tested it with two different USB sticks in two different computers running Ubuntu 12.04 and the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+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 1607991] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: there are a lot of times with problems when I start my computer ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sat Jul 30 02:11:54 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-12-05 (1332 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-07-30 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1607991 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: there are a lot of times with problems when I start my computer ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sat Jul 30 02:11:54 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-12-05 (1332 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-07-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1607991/+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
