[Desktop-packages] [Bug 1546634] Re: Is "Restart & Install" appropriate for Ubuntu
Sorry, I can not edit the comment, I paste the info on the package and version of ubuntu: Ubuntu 18.10 full update; ubuntu-software: cosmic,cosmic,now 3.30.0-0ubuntu1 all [installato]. -- 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/1546634 Title: Is "Restart & Install" appropriate for Ubuntu Status in gnome-software package in Ubuntu: Fix Released Bug description: On the updates tab there is a button "Restart & Install" button which performs an offline update of the system (i.e. restarts and installs updates outside of a session). Is this an appropriate option for Ubuntu? Does it work? Should there be an "Update All" button instead that updates everything inside the session? Or do we just leave this to update-manager and just allow users to update individual apps from GNOME Software? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1546634/+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 1546634] Re: Is "Restart & Install" appropriate for Ubuntu
When there are updates on the software center, I have the "restart and update" button, but when I click on it, I reboot the system but nothing is updated. I expect an update button, without restarting the system. ** Attachment added: "Schermata del 2018-10-08 11-45-09.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1546634/+attachment/5198565/+files/Schermata%20del%202018-10-08%2011-45-09.png -- 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/1546634 Title: Is "Restart & Install" appropriate for Ubuntu Status in gnome-software package in Ubuntu: Fix Released Bug description: On the updates tab there is a button "Restart & Install" button which performs an offline update of the system (i.e. restarts and installs updates outside of a session). Is this an appropriate option for Ubuntu? Does it work? Should there be an "Update All" button instead that updates everything inside the session? Or do we just leave this to update-manager and just allow users to update individual apps from GNOME Software? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1546634/+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 1806697] Re: Status of interface connections not properly updated in the UI
I have the same problem: GNOME software does not update the status of the interface. Ubuntu 19.04 Ubuntu software: ubuntu-software/disco,disco,now 3.30.5-0ubuntu2 all [installato] -- 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/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Confirmed Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell
I was able to retrieve other logs in the time the BUG happened:mar 05 13:40:01 > mar 05 13:43:01 approx ** Attachment added: "log1" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+attachment/5243808/+files/log1 -- 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/1817546 Title: Changing the volume (with the mouse wheel over icon) locks up gnome- shell Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: If I change the volume, the display freezes right after the volume display floating indictor appears in the middle of the screen. I have to either reboot or switch to virtual terminal and killall -3 gnome- shell to restart the session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 13:20:49 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-19 (615 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-31 (24 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-02-23T10:27:39.206420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+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 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell
I have the problem on Ubuntu 19.04, I attach the logs, I hope they are useful. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+attachment/5243805/+files/log -- 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/1817546 Title: Changing the volume (with the mouse wheel over icon) locks up gnome- shell Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: If I change the volume, the display freezes right after the volume display floating indictor appears in the middle of the screen. I have to either reboot or switch to virtual terminal and killall -3 gnome- shell to restart the session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 13:20:49 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-19 (615 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-31 (24 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-02-23T10:27:39.206420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+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 1818751] [NEW] Single display: I can not apply the changes
Public bug reported: Ubuntu 19.04 apt policy gnome-settings-daemon gnome-settings-daemon: Installato: 3.31.90-1ubuntu1 Candidato: 3.31.90-1ubuntu1 Tabella versione: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages When I change monitors in the single display and I want to go back to the previous monitor, it does not change me anymore, there's no button to apply the changes. I enclose a video to better demonstrate the problem ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "vokoscreen-2019-03-05_23-56-13.mkv" https://bugs.launchpad.net/bugs/1818751/+attachment/5243817/+files/vokoscreen-2019-03-05_23-56-13.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1818751 Title: Single display: I can not apply the changes Status in gnome-settings-daemon package in Ubuntu: New Bug description: Ubuntu 19.04 apt policy gnome-settings-daemon gnome-settings-daemon: Installato: 3.31.90-1ubuntu1 Candidato: 3.31.90-1ubuntu1 Tabella versione: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages When I change monitors in the single display and I want to go back to the previous monitor, it does not change me anymore, there's no button to apply the changes. I enclose a video to better demonstrate the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1818751/+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 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell
** Attachment removed: "log1" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+attachment/5243808/+files/log1 ** Attachment added: "log1" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+attachment/5243809/+files/log1 -- 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/1817546 Title: Changing the volume (with the mouse wheel over icon) locks up gnome- shell Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: If I change the volume, the display freezes right after the volume display floating indictor appears in the middle of the screen. I have to either reboot or switch to virtual terminal and killall -3 gnome- shell to restart the session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 13:20:49 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-19 (615 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-31 (24 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-02-23T10:27:39.206420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+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 1820104] [NEW] Ask what to do when moving files/folders
Public bug reported: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. I attach a screenshot to show what the Dolphin file manager does, and what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Schermata del 2019-03-14 19-12-43.png" https://bugs.launchpad.net/bugs/1820104/+attachment/5246224/+files/Schermata%20del%202019-03-14%2019-12-43.png ** Description changed: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. - Many times it happens that I have to copy files/folders and I find myself moving these files is not very friendly as a user experience. + Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. + + I attach a screenshot to show what the Dolphin file manager does, and + what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' - b'org.gnome.nautilus.preferences' b'show-create-link' b'true' - b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" - b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" + b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' + b'org.gnome.nautilus.preferences' b'show-create-link' b'true' + b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" + b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=it_IT.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- 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/1820104 Title: Ask what to do when moving files/folders Status in nautilus package in Ubuntu: New Bug description: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these
[Desktop-packages] [Bug 1820104] Re: Ask what to do when moving files/folders
Sorry, I'll correct myself: The different behavior is on the same partition: move. However the problem of usability remains, many inexperienced users accustomed to Windows, use the mouse to move, copy folders etc I must be able to decide at least whether to move or copy. -- 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/1820104 Title: Ask what to do when moving files/folders Status in nautilus package in Ubuntu: Opinion Bug description: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. I attach a screenshot to show what the Dolphin file manager does, and what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1820104/+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 1820104] Re: Ask what to do when moving files/folders
I recently installed the Chromium SNAP, so I wanted to copy the Chromium DEB configuration: I select the folder /home/user/.config/chromium and move it to /home/user/snap/Chromium/current/.config/chromium My intention is to copy, since I want to keep the ".deb" installation configuration, Nautilus has moved the folder, because it is in the same partition. Since on the chromium snap configuration there was already the configuration folder, I applied and overwritten the files/folders, in this case I lost the configurations, nothing serious, but it is annoying. -- 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/1820104 Title: Ask what to do when moving files/folders Status in nautilus package in Ubuntu: Opinion Bug description: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. I attach a screenshot to show what the Dolphin file manager does, and what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1820104/+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 1820104] Re: Ask what to do when moving files/folders
Thank you for responding so quickly. The problem is that it has two different behaviors: 1) The use case that operates in the same partition, in this case copy; 2) The use case that operates on different partitions, in this case moves, I expect at least the same "copy" behavior, because I can move files or folders from backup, and I want the folder to remain on the backup. My concern is when I install Ubuntu to a few experienced people, in this case if they want to copy some documents to the USB stick, they could only find the copy on USB, since in this case nautilus moves the folders. I reported the BUG because I often have to restore the other copy to the original place. -- 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/1820104 Title: Ask what to do when moving files/folders Status in nautilus package in Ubuntu: Opinion Bug description: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. I attach a screenshot to show what the Dolphin file manager does, and what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1820104/+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 1820104] Re: Ask what to do when moving files/folders
In fact, not even Windows shows a choice when moving a folder, even if it visually indicates that you are moving a folder. Unfortunately I don't use keyboard shortcuts very much, I use a lot of mouse. Same thing the users to whom I install an operating system, in 99% of the cases they are used to the click, and it is difficult to explain to them to memorize the keyboard shortcuts, they must already get used to the change of operating system between Windows 7/10 and Ubuntu / Kubuntu. Yesterday I installed Kubuntu (I removed Windows 7) to a user, so I made a temporary backup on a USB disk, at the end of the installation I made all the files move (not copy), with dolphin it was simple and intuitive because I was proposed a choice. ** Attachment added: "Cattura.PNG" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820104/+attachment/5246261/+files/Cattura.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/1820104 Title: Ask what to do when moving files/folders Status in nautilus package in Ubuntu: Opinion Bug description: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. I attach a screenshot to show what the Dolphin file manager does, and what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1820104/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Is there any news about this bug? To this day I still can't use plasma-browser-integration -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1820104] Re: Ask what to do when moving files/folders
The ideal is the behavior that Dolphin has, because sometimes I want to copy, sometimes I want to move, Dolphin in this case when you drag a folder asks you: copy, move, link, as seen in the screenshot I attached on post #1 -- 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/1820104 Title: Ask what to do when moving files/folders Status in nautilus package in Ubuntu: Opinion Bug description: When I move a document to a folder on the same disk, by default I move the folder/file, what I expect is that it asks me if: copy, move or create a connection, as does the Dolphin file manager. Many times it happens that I have to copy files/folders and I find myself moving these files, is not very friendly as a user experience. I attach a screenshot to show what the Dolphin file manager does, and what I expect Nautilus to do. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 14 19:06:41 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(889, 549)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-02-18 (23 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1820104/+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 1824657] [NEW] GNOME shell crash
Public bug reported: I was watching a video on youtube with the Chromium snap browser, suddenly the GNOME shell crashed, no possibility to click for Chromium or other closure, but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4. Using Ubuntu 19.04 from the beginning of development, first with KDE, after I install GNOME with the metapackage: sudo apt install ubuntu-desktop, eliminating any KDE package, until now I have had no problem. full update, proposed repository disabled. I attach the logs from the time I had the problem, about 10:50 pm, I started with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 22:40:00" ( if it is wrong, let him know) >From the logs I see many gnome-shell errors, but obviously I can't decipher them if it was the cause of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:07:59 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' InstallationDate: Installed on 2019-02-18 (53 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Attachment added: "log_freeze_desktop" https://bugs.launchpad.net/bugs/1824657/+attachment/5255491/+files/log_freeze_desktop -- 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/1824657 Title: GNOME shell crash Status in gnome-shell package in Ubuntu: New Bug description: I was watching a video on youtube with the Chromium snap browser, suddenly the GNOME shell crashed, no possibility to click for Chromium or other closure, but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4. Using Ubuntu 19.04 from the beginning of development, first with KDE, after I install GNOME with the metapackage: sudo apt install ubuntu-desktop, eliminating any KDE package, until now I have had no problem. full update, proposed repository disabled. I attach the logs from the time I had the problem, about 10:50 pm, I started with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 22:40:00" ( if it is wrong, let him know) From the logs I see many gnome-shell errors, but obviously I can't decipher them if it was the cause of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:07:59 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' InstallationDate: Installed on 2019-02-18 (53 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell 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/1824657/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1824657] Re: GNOME shell crash
I put the logs also on pastebin, maybe they are more readable. https://paste.ubuntu.com/p/TPMDVJZgqJ/ -- 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/1824657 Title: GNOME shell crash Status in gnome-shell package in Ubuntu: New Bug description: I was watching a video on youtube with the Chromium snap browser, suddenly the GNOME shell crashed, no possibility to click for Chromium or other closure, but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4. Using Ubuntu 19.04 from the beginning of development, first with KDE, after I install GNOME with the metapackage: sudo apt install ubuntu-desktop, eliminating any KDE package, until now I have had no problem. full update, proposed repository disabled. I attach the logs from the time I had the problem, about 10:50 pm, I started with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 22:40:00" ( if it is wrong, let him know) From the logs I see many gnome-shell errors, but obviously I can't decipher them if it was the cause of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:07:59 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' InstallationDate: Installed on 2019-02-18 (53 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell 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/1824657/+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 1841774] [NEW] Freeze gnome shell and dekstop
Public bug reported: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "I attach the logs" https://bugs.launchpad.net/bugs/1841774/+attachment/5285381/+files/logfreeze -- 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/1841774 Title: Freeze gnome shell and dekstop Status in gnome-shell package in Ubuntu: New Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell 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/1841774/+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 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
Strange, these two extensions('sensory-percept...@harlemsquirrel.github.io',
'temperature@xtranophilist', 'gnom...@panacier.gmail.com'
) I've already uninstalled from gnome-tweaks, for a long time.
If they are available and easy to install, I think there is some problem with
gnome shell extensions, it happens to many users that they can't start the
desktop with any extension that doesn't work well (I can fix it because I know
how to fix it, but many users, no).
The bug occurred only on one occasion, but I wanted to report it because I want
to help fix bugs, if there are any.
--
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/1841774
Title:
gnome-shell freezes and continuously logs "JS ERROR: TypeError: null
has no properties" in _addWindowEffect from vfunc_show (both in
closeDialog.js)
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I was closing the dialog of the "software and updates" tools (I was
checking the repositories and ppa), but the entire desktop went into
freeze, no mouse movement, at the click no action, I pressed the keys
"ctrl + alt + f3 "and I went into a tty session, from there I recorded
the logs via:" journalctl -f> log ", and I restarted.
This is one part of the log, but it seems to repeat itself, I have
attached a file with a longer log.
-- Logs begin at Tue 2019-02-19 00:29:40 CET. --
ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no
properties
_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13
vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no
properties
_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13
vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.33.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
Uname: Linux 5.2.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 28 14:51:01 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-02-18 (190 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
SourcePackage: gnome-shell
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/1841774/+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 1843572] [NEW] Unable to select icons on the Ubuntu dock
Public bug reported: Coincidentally dask to dock did not work anymore: by clicking on any software on the dock, I could no longer make the switch from one software to another, it seems that the dock has been blocked. I attach a file with logs. Ubuntu 19.10 gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico] gnome-shell-extension-dashtodock/eoan,eoan 66-1 all mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:40:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (204 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "crash" https://bugs.launchpad.net/bugs/1843572/+attachment/5288035/+files/crash -- 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/1843572 Title: Unable to select icons on the Ubuntu dock Status in gnome-shell package in Ubuntu: New Bug description: Coincidentally dask to dock did not work anymore: by clicking on any software on the dock, I could no longer make the switch from one software to another, it seems that the dock has been blocked. I attach a file with logs. Ubuntu 19.10 gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico] gnome-shell-extension-dashtodock/eoan,eoan 66-1 all mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:40:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (204 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell 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/1843572/+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 1844453] [NEW] Access to the Google remote account does not work
Public bug reported:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1844453
Title:
Access to the Google remote account does not work
Status in libreoffice package in Ubuntu:
New
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1844453/+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 1844453] Re: Access to the Google remote account does not work
I have LibreOffice in the snap version, but it doesn't matter, it
doesn't even work in the "deb" version.
snap-id: CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
tracking: stable
refresh-date: 4 days ago, at 20:25 CEST
channels:
stable:6.3.1.2 2019-09-13 (147) 440MB -
candidate: 6.3.1.2 2019-09-13 (147) 440MB -
beta: ↑
edge: ↑
installed: 6.3.1.2(147) 440MB -
--
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/1844453
Title:
Access to the Google remote account does not work
Status in libreoffice package in Ubuntu:
New
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1844453/+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 1843572] Re: Unable to select icons on the Ubuntu dock
This is what gnome-tweak shows ** Attachment added: "Schermata del 2019-09-16 14-13-47.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843572/+attachment/5289001/+files/Schermata%20del%202019-09-16%2014-13-47.png -- 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/1843572 Title: Unable to select icons on the Ubuntu dock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Coincidentally dask to dock did not work anymore: by clicking on any software on the dock, I could no longer make the switch from one software to another, it seems that the dock has been blocked. I attach a file with logs. Ubuntu 19.10 gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico] gnome-shell-extension-dashtodock/eoan,eoan 66-1 all mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:40:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (204 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell 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/1843572/+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 1843572] Re: Unable to select icons on the Ubuntu dock
Using ubuntu-dock, I installed dash to dock from ubuntu-software to do some small customizations (minimize on click). I install extensions from ubuntu-software, so in the folder where they are installed, as you can see I don't have these extensions: "gnom...@panacier.gmail.com ',' sensory-percept...@harlemsquirrel.github.io ',' temperature @ xtranophilist '" ** Attachment added: "Schermata del 2019-09-16 14-09-59.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843572/+attachment/5289000/+files/Schermata%20del%202019-09-16%2014-09-59.png -- 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/1843572 Title: Unable to select icons on the Ubuntu dock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Coincidentally dask to dock did not work anymore: by clicking on any software on the dock, I could no longer make the switch from one software to another, it seems that the dock has been blocked. I attach a file with logs. Ubuntu 19.10 gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico] gnome-shell-extension-dashtodock/eoan,eoan 66-1 all mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:40:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (204 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell 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/1843572/+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 1843572] Re: Unable to select icons on the Ubuntu dock
I've had other random freezes, the most common problem is when I right-click on the menu (ubuntu-dock), it stays in the menu above on the top left, and doesn't go away easily. When I right-click the dock icon, I have this log: set 16 14:18:51 emanuc gnome-shell[2402]: JS ERROR: TypeError: mutterWindow.get_texture(...).get_size is not a function _cloneTexture@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:382:62 _init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:371:9 _populateAllWindowMenu@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:982:32 update@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:943:15 _redisplay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:909:9 popup@resource:///org/gnome/shell/ui/appDisplay.js:2341:9 popupMenu@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:351:9 _onButtonPress@resource:///org/gnome/shell/ui/appDisplay.js:1947:13 113/5000 I hope I explained myself well, if there are other things I can do to identify the problem, tell me. Thanks ** Attachment added: "Schermata del 2019-09-16 14-10-28.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843572/+attachment/5289003/+files/Schermata%20del%202019-09-16%2014-10-28.png -- 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/1843572 Title: Unable to select icons on the Ubuntu dock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Coincidentally dask to dock did not work anymore: by clicking on any software on the dock, I could no longer make the switch from one software to another, it seems that the dock has been blocked. I attach a file with logs. Ubuntu 19.10 gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico] gnome-shell-extension-dashtodock/eoan,eoan 66-1 all mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:40:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (204 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell 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/1843572/+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 1843572] Re: Unable to select icons on the Ubuntu dock
*** This bug is a duplicate of bug 1843520 *** https://bugs.launchpad.net/bugs/1843520 I made a video to show the bug more clearly https://youtu.be/HbVaZTnssUQ I hope it's useful. -- 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/1843572 Title: Unable to select icons on the Ubuntu dock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Coincidentally dask to dock did not work anymore: by clicking on any software on the dock, I could no longer make the switch from one software to another, it seems that the dock has been blocked. I attach a file with logs. Ubuntu 19.10 gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico] gnome-shell-extension-dashtodock/eoan,eoan 66-1 all mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:40:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (204 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell 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/1843572/+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 1850995] Re: gnome-shell: freeze and high CPU usage
I also played it on VM: https://youtu.be/knTm-WYdT6Y -- 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/1850995 Title: gnome-shell: freeze and high CPU usage Status in gnome-shell package in Ubuntu: New Bug description: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell 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/1850995/+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 1850995] [NEW] gnome-shell: freeze and high CPU usage
Public bug reported: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "log crash" https://bugs.launchpad.net/bugs/1850995/+attachment/5302128/+files/logg -- 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/1850995 Title: gnome-shell: freeze and high CPU usage Status in gnome-shell package in Ubuntu: New Bug description: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell 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/1850995/+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 1850995] Re: gnome-shell: freeze and high CPU usage
I tried to start a session with "ubuntu wayland" on the VM and the problem is not there, the problem is only on the xorg session. I can't start "ubuntu wayland" on the host desktop with the NVIDIA GPU, of course I enable "nvidia-drm.modeset = 1", but that's another problem. -- 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/1850995 Title: gnome-shell: freeze and high CPU usage Status in gnome-shell package in Ubuntu: New Bug description: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell 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/1850995/+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 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
I have the same problem, I start CS: GO, after a while I see a warning window that the game is locked, so click "careful" or "force shut", but it is not clickable and nothing happens. I have to force the game to close. I attach the logs. GPU: NVIDIA GTX 750 ti Driver: nvidia-driver-435 / eoan, now 435.21-0ubuntu2 amd64 [installed] ** Attachment added: "Log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848852/+attachment/5301130/+files/logcsgo -- 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: After upgrade to ubuntu 19.10, when I launch counter strike global offensive from steam the game is frozen. I can alt-tab and close the game. Tried in fluxbox window manager where the game works, changed fullscreen to windowed fullscreen in the options and tried on gnome again, now the desktop isn't responding after launching the game and I had to ctrl-alt-f3 to reboot my machine. Using a Radeon RX 580 video card. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
I noticed right now that in the logs I keep spam: ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:33 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:33 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:33 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:33 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:33 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:33 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:33 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:33 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:34 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:34 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:34 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:34 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:34 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:34 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:35 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:35 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:35 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:35 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) ott 29 13:16:35 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ott 29 13:16:35 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 == ott 29 13:16:35 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15) ott 29 13:16:35 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392) -- 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: After upgrade to
[Desktop-packages] [Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
The bug has been reported upstream and looks like the same bug https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1607 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607 -- 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/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell 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/1841774/+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 1813441] Re: Can no longer drag and drop files between desktop and applications
Being able to move Applications from the Menu to the desktop or move documents from the file manager to the desktop is a function that is required by many users, it is a feature that any OS and Linux Desktop has, for years that I use my PC for the first time. it's such a limit, and only GNOME-Shell has it. Is there anyone working on it or is there a plan to get it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1847882] [NEW] Excessive use of gnome-shell memory
Public bug reported: After 9 hours of uptime, I have the gnome-shell process that uses 6GB of memory ... emanu@emanuc:~$ ps aux | grep gnome-shell gdm 2014 0.0 1.0 2857772 175052 ? Ssl 13:42 0:10 /usr/bin/gnome-shell emanu 2934 6.3 38.7 10087648 6350632 ?Ssl 13:43 36:18 /usr/bin/gnome-shell emanu 2963 0.0 0.1 520028 17796 ?Sl 13:43 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server emanu 3278 0.2 0.6 2608268 111668 ? Sl 13:43 1:33 gjs /home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da emon.js emanu13107 0.0 0.0 9056 924 pts/2S+ 23:18 0:00 grep gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 12 23:22:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (235 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1847882/+attachment/5296752/+files/Schermata%20del%202019-10-12%2023-16-33.png -- 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/1847882 Title: Excessive use of gnome-shell memory Status in gnome-shell package in Ubuntu: New Bug description: After 9 hours of uptime, I have the gnome-shell process that uses 6GB of memory ... emanu@emanuc:~$ ps aux | grep gnome-shell gdm 2014 0.0 1.0 2857772 175052 ? Ssl 13:42 0:10 /usr/bin/gnome-shell emanu 2934 6.3 38.7 10087648 6350632 ?Ssl 13:43 36:18 /usr/bin/gnome-shell emanu 2963 0.0 0.1 520028 17796 ?Sl 13:43 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server emanu 3278 0.2 0.6 2608268 111668 ? Sl 13:43 1:33 gjs /home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da emon.js emanu13107 0.0 0.0 9056 924 pts/2S+ 23:18 0:00 grep gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 12 23:22:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (235 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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/1847882/+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 1847882] Re: Excessive use of gnome-shell memory
** Attachment added: "Screenshot 2" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847882/+attachment/5296758/+files/Schermata%20del%202019-10-12%2023-29-44.png -- 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/1847882 Title: Excessive use of gnome-shell memory Status in gnome-shell package in Ubuntu: New Bug description: After 9 hours of uptime, I have the gnome-shell process that uses 6GB of memory ... emanu@emanuc:~$ ps aux | grep gnome-shell gdm 2014 0.0 1.0 2857772 175052 ? Ssl 13:42 0:10 /usr/bin/gnome-shell emanu 2934 6.3 38.7 10087648 6350632 ?Ssl 13:43 36:18 /usr/bin/gnome-shell emanu 2963 0.0 0.1 520028 17796 ?Sl 13:43 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server emanu 3278 0.2 0.6 2608268 111668 ? Sl 13:43 1:33 gjs /home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da emon.js emanu13107 0.0 0.0 9056 924 pts/2S+ 23:18 0:00 grep gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 12 23:22:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (235 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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/1847882/+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 1847882] Re: Excessive use of gnome-shell memory
I don't know if it is related to the bug, but at the start you notice a slowdown compared to before the latest updates, I paste the logs: https://paste.ubuntu.com/p/XCQky53Vz5/ -- 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/1847882 Title: Excessive use of gnome-shell memory Status in gnome-shell package in Ubuntu: New Bug description: After 9 hours of uptime, I have the gnome-shell process that uses 6GB of memory ... emanu@emanuc:~$ ps aux | grep gnome-shell gdm 2014 0.0 1.0 2857772 175052 ? Ssl 13:42 0:10 /usr/bin/gnome-shell emanu 2934 6.3 38.7 10087648 6350632 ?Ssl 13:43 36:18 /usr/bin/gnome-shell emanu 2963 0.0 0.1 520028 17796 ?Sl 13:43 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server emanu 3278 0.2 0.6 2608268 111668 ? Sl 13:43 1:33 gjs /home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da emon.js emanu13107 0.0 0.0 9056 924 pts/2S+ 23:18 0:00 grep gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 12 23:22:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (235 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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/1847882/+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 1847882] Re: Excessive use of gnome-shell memory
Update: The problem of excessive use of memory I have at every start, after a short time, about 1 hour of activity the memory in use of gnome- shell goes to more than 1Gb. I checked on the notebook with the same version of Ubuntu and the same configuration: package version, extension version, then a 99% replica, the gnome shell process is kept at about 234mb / 328mb of memory in use. Hardware difference: Notebook(no bug): CPU: Intel i3-6006, GPU: integrated Intel HD 520, session Wayland. Desktop(bug): CPU: Ryzen 2600x, GPU: NVIDIA gtx 750 ti (NVIDIA proprietary driver 435.21), Xorg session. ** Attachment added: "photo_2019-10-13_12-29-08.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847882/+attachment/5296801/+files/photo_2019-10-13_12-29-08.jpg -- 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/1847882 Title: Excessive use of gnome-shell memory Status in gnome-shell package in Ubuntu: New Bug description: After 9 hours of uptime, I have the gnome-shell process that uses 6GB of memory ... emanu@emanuc:~$ ps aux | grep gnome-shell gdm 2014 0.0 1.0 2857772 175052 ? Ssl 13:42 0:10 /usr/bin/gnome-shell emanu 2934 6.3 38.7 10087648 6350632 ?Ssl 13:43 36:18 /usr/bin/gnome-shell emanu 2963 0.0 0.1 520028 17796 ?Sl 13:43 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server emanu 3278 0.2 0.6 2608268 111668 ? Sl 13:43 1:33 gjs /home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da emon.js emanu13107 0.0 0.0 9056 924 pts/2S+ 23:18 0:00 grep gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 12 23:22:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (235 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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/1847882/+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 1847882] Re: Excessive use of gnome-shell memory
Update: I have disabled and removed all the additional extensions from: /home/user/.local/share/gnome-shell/extensions, after 3 hours of uptime, now the ram is stable on the 200mb/300mb. So I think the problem was caused by some extension. I wonder, given the instability that extensions can have, if it is not wrong to have them installed so easily to the user (gnome-software)? Maybe keep only some popular and well tested repository extensions? -- 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/1847882 Title: Excessive use of gnome-shell memory Status in gnome-shell package in Ubuntu: New Bug description: After 9 hours of uptime, I have the gnome-shell process that uses 6GB of memory ... emanu@emanuc:~$ ps aux | grep gnome-shell gdm 2014 0.0 1.0 2857772 175052 ? Ssl 13:42 0:10 /usr/bin/gnome-shell emanu 2934 6.3 38.7 10087648 6350632 ?Ssl 13:43 36:18 /usr/bin/gnome-shell emanu 2963 0.0 0.1 520028 17796 ?Sl 13:43 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server emanu 3278 0.2 0.6 2608268 111668 ? Sl 13:43 1:33 gjs /home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da emon.js emanu13107 0.0 0.0 9056 924 pts/2S+ 23:18 0:00 grep gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 12 23:22:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (235 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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/1847882/+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 1874049] [NEW] Gnome-shell block
Public bug reported: I have gnome-shell blocked, when I click on any part of the shell: dock, menu etc ... nothing happens. I can only switch between windows with alt + tab. This is not the first time it happens, it has done so by replicating these steps: Virtual manager with OS started, taken the GNOME screenshot tool on Ubuntu (host), I select the screenshot (select area to be captured) I select a part of the screen on Virtual Manager, at this point the whole shell freezes, becomes non-clickable. I hope the explanation is understandable and helpful to improve Ubuntu. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 12:53:28 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1874049 Title: Gnome-shell block Status in gnome-shell package in Ubuntu: New Bug description: I have gnome-shell blocked, when I click on any part of the shell: dock, menu etc ... nothing happens. I can only switch between windows with alt + tab. This is not the first time it happens, it has done so by replicating these steps: Virtual manager with OS started, taken the GNOME screenshot tool on Ubuntu (host), I select the screenshot (select area to be captured) I select a part of the screen on Virtual Manager, at this point the whole shell freezes, becomes non-clickable. I hope the explanation is understandable and helpful to improve Ubuntu. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 12:53:28 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell 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/1874049/+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 1874049] Re: Gnome-shell block
I reproduced it without extensions, the cause that triggers the bug seems to be the "gnome-screenshot" tool. It is easy to readjust. I created a video on how to reproduce the bug. Hope it helps. https://www.youtube.com/watch?v=gBQKVUiKbFs As you can see from the video, once the bug shows up, the mouse can be clicked on the windows, but not on the iGNOME shell: menu, dock etc ... -- 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/1874049 Title: Gnome-shell block Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have gnome-shell blocked, when I click on any part of the shell: dock, menu etc ... nothing happens. I can only switch between windows with alt + tab. This is not the first time it happens, it has done so by replicating these steps: Virtual manager with OS started, taken the GNOME screenshot tool on Ubuntu (host), I select the screenshot (select area to be captured) I select a part of the screen on Virtual Manager, at this point the whole shell freezes, becomes non-clickable. I hope the explanation is understandable and helpful to improve Ubuntu. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 12:53:28 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell 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/1874049/+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 1874049] Re: Gnome-shell block
Test 2: https://youtu.be/erRt5MIA81o -- 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/1874049 Title: Gnome-shell block Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have gnome-shell blocked, when I click on any part of the shell: dock, menu etc ... nothing happens. I can only switch between windows with alt + tab. This is not the first time it happens, it has done so by replicating these steps: Virtual manager with OS started, taken the GNOME screenshot tool on Ubuntu (host), I select the screenshot (select area to be captured) I select a part of the screen on Virtual Manager, at this point the whole shell freezes, becomes non-clickable. I hope the explanation is understandable and helpful to improve Ubuntu. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 12:53:28 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell 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/1874049/+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 1874049] Re: Gnome-shell block
Update: I tried installing the "gnome-session" session, without extensions pre-installed with Ubuntu. After many attempts, I was unable to reproduce the bug with "gnome-screenshot". Another test: I installed in VM through the Ubuntu 20.04 daily ISO of "2020-04-21 20:32", with the default extensions of Ubuntu, I managed to reproduce the bug. -- 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/1874049 Title: Gnome-shell block Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have gnome-shell blocked, when I click on any part of the shell: dock, menu etc ... nothing happens. I can only switch between windows with alt + tab. This is not the first time it happens, it has done so by replicating these steps: Virtual manager with OS started, taken the GNOME screenshot tool on Ubuntu (host), I select the screenshot (select area to be captured) I select a part of the screen on Virtual Manager, at this point the whole shell freezes, becomes non-clickable. I hope the explanation is understandable and helpful to improve Ubuntu. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 12:53:28 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell 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/1874049/+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 1868083] [NEW] gnome-shell process "estabilished"
Public bug reported: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: New Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell 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/1868083/+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 1868083] Re: gnome-shell process "estabilished"
Seems like they eventually want to add one on/off control over checking for these updates? I hope so and thank you for taking the time on this. -- 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/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: New Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell 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/1868083/+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 1995412] Re: Expandable folders option disappeared
Is it an upstream problem with the port to gtk4? It seems so from reading this post: https://blogs.gnome.org/antoniof/2022/06/15/the-tree- view-is-undead-long-live-the-column-view%E2%80%BD/ There is work in progress to restore it: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/817 -- 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/1995412 Title: Expandable folders option disappeared Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 nautilus: Installed: 1:43.0-1ubuntu1 Nautilus click on 'Preferences' Expandable folders option was present in Ubuntu 22.04 now disappeared in Ubuntu 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 Nov 1 18:54:22 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 879)' InstallationDate: Installed on 2022-10-25 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995412/+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 1028970] [NEW] Sync doesn't work
Public bug reported: In firefox version 15 sync doesn't work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0~b1+build1-0ubuntu0.12.04.1~mfn1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanuele 1525 F pulseaudio BuildID: 20120724174602 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xc800 irq 46' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1025160d,0012 HDA:14f12bfa,10250094,0009' Controls : 33 Simple ctrls : 17 Channel: Unavailable Date: Wed Jul 25 17:44:38 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.5 metric 2 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0/20120724174602 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.1 icedtea-6-plugin 1.2-2ubuntu1 totem-mozilla 3.0.1-0ubuntu21 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3239 dmi.board.name: Bodensee dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3239:bd01/12/07:svnAcer,inc.:pnAspire5670:pvrNotApplicable:rvnAcer,Inc.:rnBodensee:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5670 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- 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/1028970 Title: Sync doesn't work Status in “firefox” package in Ubuntu: New Bug description: In firefox version 15 sync doesn't work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0~b1+build1-0ubuntu0.12.04.1~mfn1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanuele 1525 F pulseaudio BuildID: 20120724174602 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xc800 irq 46' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1025160d,0012 HDA:14f12bfa,10250094,0009' Controls : 33 Simple ctrls : 17 Channel: Unavailable Date: Wed Jul 25 17:44:38 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.5 metric 2 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0/20120724174602 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.1 icedtea-6-plugin 1.2-2ubuntu1 totem-mozilla 3.0.1-0ubuntu21 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3239 dmi.board.name: Bodensee dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3239:bd01/12/07:svnAcer,inc.:pnAspire5670:pvrNotApplicable:rvnAcer,Inc.:rnBodensee:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5670 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1028970/+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 1028970] Re: Sync doesn't work
-- 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/1028970 Title: Sync doesn't work Status in “firefox” package in Ubuntu: New Bug description: In firefox version 15 sync doesn't work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0~b1+build1-0ubuntu0.12.04.1~mfn1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanuele 1525 F pulseaudio BuildID: 20120724174602 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xc800 irq 46' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1025160d,0012 HDA:14f12bfa,10250094,0009' Controls : 33 Simple ctrls : 17 Channel: Unavailable Date: Wed Jul 25 17:44:38 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.5 metric 2 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0/20120724174602 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.1 icedtea-6-plugin 1.2-2ubuntu1 totem-mozilla 3.0.1-0ubuntu21 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3239 dmi.board.name: Bodensee dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3239:bd01/12/07:svnAcer,inc.:pnAspire5670:pvrNotApplicable:rvnAcer,Inc.:rnBodensee:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5670 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1028970/+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 997630] Re: evince and eog broken on remote sessions (X, NX, x2go and VNC)
I can also confirm that the proposed update fixes this bug. To verify the fix I've started an EC2 instance with the official precise AMI, installed ubuntu-desktop and the relevant x2go packages. The bug was reproducible. After installing libgrip0 and its dependencies from precise-proposed the bug was not reproducible anymore. Thanks, Emanuele -- 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/997630 Title: evince and eog broken on remote sessions (X, NX, x2go and VNC) Status in Open Input Framework Geis C API: Fix Released Status in “evince” package in Ubuntu: Invalid Status in “geis” package in Ubuntu: Fix Released Status in “evince” source package in Precise: Invalid Status in “geis” source package in Precise: Fix Committed Bug description: libgrip has some troubles when accessing a Ubuntu 12.04 desktop via x2go, which uses libnx-x11. The applications (evince and eog) start up very slowly. It takes about 50 seconds to open a 900k pdf document. The following output makes me think that the problem is libgrip- related. A way to avoid the issue is running evince in preview mode (-w). $ evince (evince:15833): GRIP-WARNING **: failed to determine device types (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. (evince:15833): GRIP-WARNING **: Failed to initialize gesture manager. $ lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 $ apt-cache policy libgrip0 libgrip0: Installed: 0.3.4-0ubuntu1 $ apt-cache policy evince evince: Installed: 3.4.0-0ubuntu1 $ apt-cache policy eog eog: Installed: 3.4.1-0ubuntu1 $ apt-cache policy libnx-x11 libnx-x11: Installed: 2:3.5.0.12-0~234~oneiric1 Candidate: 2:3.5.0.12-0~234~oneiric1 Version table: *** 2:3.5.0.12-0~234~oneiric1 0 500 http://ppa.launchpad.net/x2go/stable/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/997630/+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 915443] [NEW] package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: During a partial upgrade the update manager has reported a problem with repository cache. At process end the package libre-office-core was not installed due missing dependencies ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 15:26:19 2012 DpkgTerminalLog: Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120104) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- 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/915443 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “libreoffice” package in Ubuntu: New Bug description: During a partial upgrade the update manager has reported a problem with repository cache. At process end the package libre-office-core was not installed due missing dependencies ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 15:26:19 2012 DpkgTerminalLog: Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120104) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915443/+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 915443] Re: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
-- 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/915443 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “libreoffice” package in Ubuntu: New Bug description: During a partial upgrade the update manager has reported a problem with repository cache. At process end the package libre-office-core was not installed due missing dependencies ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 15:26:19 2012 DpkgTerminalLog: Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120104) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915443/+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 915271] Re: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty
@zval: worked for me too. Thanks -- 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/915271 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty Status in LibreOffice Productivity Suite: New Status in “libreoffice” package in Ubuntu: Confirmed Bug description: running updates/upgrades on Precise machine and message popped up saying it needed to report this bug. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 11:44:43 2012 DuplicateSignature: Unpacking replacement libreoffice-math ... Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915271/+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 1250063] [NEW] nvidia-173 doesn't work on Ubuntu 13.10 Saucy Salamander
Public bug reported: My nvidia graphic card is GeForce 6150SE nForce 430. In past only nvidia 173 drivers worked correctly. Nor 304 or others (like nouveau). After a fresh new installation of Ubuntu 13.10 I open Software Sources (software-properties-gtk) and in tab Additional Drivers I select the only one driver called nvidia-173. Later the first reboot, everything seems working good, but after turning it off and on again 2 more times, everythings black! Only an underscore blinking in the upper left. I tried CTRL+ALT+F!, etc. combinations but nothing happens. I suspect this problem happens after some Nvidia drivers updates. Now I use gnome-session-fallback (no effects) and nouveau drivers that doesn't work properly (1280x1024) and everything appears crushed (5:4 or 4:3 in a 16:9 display) but it's the only way to see ubuntu in graphic mode. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-173 (not installed) ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,imgpng,place,move,compiztoolbox,mousepoll,mag,gnomecompat,grid,wall,vpswitch,regex,zoom,snap,session,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,dbus] CompositorRunning: None Date: Mon Nov 11 12:30:52 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:03d0] InstallationDate: Installed on 2013-11-10 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 001 Device 002: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58) Bus 002 Device 002: ID 04f9:0270 Brother Industries, Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=4632bb01-e975-4d15-a221-3242a155ddbf ro nomodeset quiet splash vt.handoff=7 SourcePackage: nvidia-graphics-drivers-173 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: ALiveNF6G-DVI 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.:bvrP2.20:bd08/08/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-DVI: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.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Nov 11 12:17:29 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 ** Affects: nvidia-graphics-drivers-173 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug nvidia-173 saucy ubuntu ** Summary changed: - nvidia-173 doesn't work on Ubuntu 13.10 + nvidia-173 doesn't work on Ubuntu 13.10 Saucy Salamander -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu. https://bugs.launchpad.net/bugs/1250063 Title: nvidia-173 doesn't work on Ubuntu 13.10 Saucy Salamander Status in “nvidia-graphics-drivers-173” package in Ubuntu: New Bug description: My nvidia graphic card is GeForce 6150SE nForce 430. In past only nvidia 173 drivers worked correctly. Nor 304 or others (like nouveau). After a fresh new installation of Ubuntu 13.10 I open Software Sources
[Desktop-packages] [Bug 1259530] [NEW] r8712u - RTL8191SU - WiFi USB pen causes freeze in Ubuntu 13.10
Public bug reported: WiFi USB pen causes freeze in Ubuntu 13.10 during LiveCD installation and during uses (after installation withouth RTL8191SU USB pen drive). I tried other WiFi USB pen and system doesen't freeze. This r8712u - RTL8191SU - WiFi USB pen worked up to Ubuntu 13.04 (and earlier versions). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Dec 10 13:42:04 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-10 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan1 proto static 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.116 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Connessione via cavo 16006573b-fbe3-40af-b8f4-10ec7a183fb0 802-3-ethernet1386678769 mar 10 dic 2013 13:32:49 CET yes no /org/freedesktop/NetworkManager/Settings/1 NemboKid 63c6680b-554e-40e9-a9d9-d68a6c941db5 802-11-wireless 1386678801 mar 10 dic 2013 13:33:21 CET yes no /org/freedesktop/NetworkManager/Settings/0 NemboKid 19ea78711-e024-4c18-a5d6-0fccbcfa872e 802-11-wireless 1386679069 mar 10 dic 2013 13:37:49 CET yes no /org/freedesktop/NetworkManager/Settings/4 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/4 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1259530 Title: r8712u - RTL8191SU - WiFi USB pen causes freeze in Ubuntu 13.10 Status in “network-manager” package in Ubuntu: New Bug description: WiFi USB pen causes freeze in Ubuntu 13.10 during LiveCD installation and during uses (after installation withouth RTL8191SU USB pen drive). I tried other WiFi USB pen and system doesen't freeze. This r8712u - RTL8191SU - WiFi USB pen worked up to Ubuntu 13.04 (and earlier versions). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Dec 10 13:42:04 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-10 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan1 proto static 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.116 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Connessione via cavo 16006573b-fbe3-40af-b8f4-10ec7a183fb0 802-3-ethernet1386678769 mar 10 dic 2013 13:32:49 CET yes no /org/freedesktop/NetworkManager/Settings/1 NemboKid 63c6680b-554e-40e9-a9d9-d68a6c941db5 802-11-wireless 1386678801 mar 10 dic 2013 13:33:21 CET yes no /org/freedesktop/NetworkManager/Settings/0 NemboKid 19ea78711-e024-4c18-a5d6-0fccbcfa872e 802-11-wireless 1386679069 mar 10 dic 2013 13:37:49 CET yes no
[Desktop-packages] [Bug 66566]
(In reply to :Gavin Sharp (email ga...@gavinsharp.com) from comment #56) Unfortunately fixing this at this point would be disastrous for muscle memory/user habits, so it's just not feasible. The problem with not fixing it is that the current behavior *is* atrocious for muscle memory/user habit, as (at least on Mac OS X, I can't speak for other OSes) currently, Firefox is the only browser that doesn't open a new tab when pressing Cmd+Return. This (and several other little things that are beyond the scope of this bug) makes it very hard for new users to switch to Firefox from e.g. Safari, where Cmd+Return means Open URL in a new tab (and, FWIW, Cmd+click means Open link in a new tab, Alt+Return means Download URL, and Alt+click means Download link.) I believe you should at the very least consider parity with other browsers / UX integration with the platform. This is a summary of the current behavior of the three main browsers on OS X: Browser | Cmd-Return | Alt-Return | Cmd-click| Alt-click Safari | Open in a new tab | [Download URL]| Open in a new tab | Download link Chrome(Chromium) | Open in a new tab | Open in a new tab | Open in a new tab | Download link Firefox | [Auto-completion] | Open in a new tab | Open in a new tab | [Nothing?] -- 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/66566 Title: Inconsistent shortcuts for new tab Status in The Mozilla Firefox Browser: Won't Fix Status in “firefox” package in Ubuntu: Won't Fix Status in “firefox-3.0” package in Ubuntu: Won't Fix Status in “firefox-3.5” package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: ALT + ENTER - GO button: CTRL + click - search bar: CTRL + ENTER - SEARCH button ALT + click - links: SHIFT + click - menu bar: CTRL + click - BACKWARD/FORWARD button: CTRL + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 291743] Re: Fatal signal 6
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782450 ** Bug watch added: Debian Bug tracker #782450 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782450 ** Also affects: ppp (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782450 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/291743 Title: Fatal signal 6 Status in ppp package in Ubuntu: Confirmed Status in ppp package in Debian: Unknown Bug description: Binary package hint: ppp After upgrading to Itrepid (ppp 2.4.4rel-9ubuntu2 - 2.4.4rel- 10ubuntu2) it became impossible to create pptp-tunnels. I changed nothing in configuration after upgrade. When I downgrade ppp to 2.4 .4rel-9ubuntu2 everything works fine. The error is Fatal signal 6. How to track that down? What can it be? The full debug log of session: Oct 31 09:09:59 server pppd[78791]: Plugin radius.so loaded. Oct 31 09:09:59 server pppd[78791]: RADIUS plugin initialized. Oct 31 09:09:59 server pppd[78791]: Plugin radattr.so loaded. Oct 31 09:09:59 server pppd[78791]: RADATTR plugin initialized. Oct 31 09:09:59 server pptp[78791]: Plugin pptp.so loaded. Oct 31 09:09:59 server pptp[78791]: PPTP plugin version 0.7.13 compiled for pppd-2.4.4, linux-2.6.27.2 Oct 31 09:09:59 server pptp[78791]: pppd 2.4.4 started by root, uid 0 Oct 31 09:09:59 server pptp[78791]: using channel 4579 Oct 31 09:09:59 server pptp[78791]: Using interface ppp1 Oct 31 09:09:59 server pptp[78791]: Connect: ppp1 -- pptp (XXX.XXX.XXX.XXX) Oct 31 09:09:59 server pptp[78791]: sent [LCP ConfReq id=0x1 asyncmap 0x0 auth chap MS-v2 magic 0x123d78e2 pcomp accomp] Oct 31 09:09:59 server pptp[78791]: rcvd [LCP ConfReq id=0x0 mru 1400 magic 0x2043406c pcomp accomp callback CBCP] Oct 31 09:09:59 server pptp[78791]: sent [LCP ConfRej id=0x0 callback CBCP] Oct 31 09:09:59 server pptp[78791]: rcvd [LCP ConfReq id=0x1 mru 1400 magic 0x2043406c pcomp accomp] Oct 31 09:09:59 server pptp[78791]: sent [LCP ConfAck id=0x1 mru 1400 magic 0x2043406c pcomp accomp] Oct 31 09:10:02 server pptp[78791]: sent [LCP ConfReq id=0x1 asyncmap 0x0 auth chap MS-v2 magic 0x123d78e2 pcomp accomp] Oct 31 09:10:02 server pptp[78791]: rcvd [LCP ConfAck id=0x1 asyncmap 0x0 auth chap MS-v2 magic 0x123d78e2 pcomp accomp] Oct 31 09:10:02 server pptp[78791]: sent [LCP EchoReq id=0x0 magic=0x123d78e2] Oct 31 09:10:02 server pptp[78791]: sent [CHAP Challenge id=0xb4 7c4cf5ceec08ea00c4f49155a5414e02, name = pptpd] Oct 31 09:10:02 server pptp[78791]: rcvd [LCP Ident id=0x2 magic=0x2043406c MSRASV5.10] Oct 31 09:10:02 server pptp[78791]: rcvd [LCP Ident id=0x3 magic=0x2043406c MSRAS-0-NAME] Oct 31 09:10:02 server pptp[78791]: rcvd [LCP EchoRep id=0x0 magic=0x2043406c] Oct 31 09:10:02 server pptp[78791]: rcvd [CHAP Response id=0xb4 d3753acb5ccddf79415040021e69b2f8fe276eb935df54fea7dd10479ae45346ac491945899a4fdb00, name = some-login] Oct 31 09:10:02 server pptp[78791]: RADATTR plugin wrote 3 line(s) to file /var/run/radattr.ppp1. Oct 31 09:10:02 server pptp[78791]: sent [CHAP Success id=0xb4 S=F4F46C682887F63B3EA1184EA72E32FAB155BA50] Oct 31 09:10:02 server pptp[78791]: sent [IPCP ConfReq id=0x1 addr XXX.XXX.XXX.XXX] Oct 31 09:10:02 server pptp[78791]: rcvd [CCP ConfReq id=0x4 mppe +H -M -S -L -D +C] Oct 31 09:10:02 server pptp[78791]: sent [CCP ConfReq id=0x1] Oct 31 09:10:02 server pptp[78791]: sent [CCP ConfRej id=0x4 mppe +H -M -S -L -D +C] Oct 31 09:10:02 server pptp[78791]: rcvd [IPCP ConfReq id=0x5 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-wins 0.0.0.0 ms-dns3 0.0.0.0 ms-wins 0.0.0.0] Oct 31 09:10:02 server pptp[78791]: sent [IPCP ConfRej id=0x5 ms-wins 0.0.0.0 ms-wins 0.0.0.0] Oct 31 09:10:02 server pptp[78791]: rcvd [IPCP ConfAck id=0x1 addr XXX.XXX.XXX.XXX] Oct 31 09:10:02 server pptp[78791]: rcvd [CCP ConfAck id=0x1] Oct 31 09:10:02 server pptp[78791]: rcvd [CCP TermReq id=0x6 C@l\000\315t\000\000\002\334] Oct 31 09:10:02 server pptp[78791]: sent [CCP TermAck id=0x6] Oct 31 09:10:02 server pptp[78791]: rcvd [IPCP ConfReq id=0x7 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-dns3 0.0.0.0] Oct 31 09:10:02 server pptp[78791]: sent [IPCP ConfNak id=0x7 addr XXX.XXX.XXX.XXX ms-dns1 XXX.XXX.XXX.XXX ms-dns3 XXX.XXX.XXX.XXX] Oct 31 09:10:02 server pptp[78791]: rcvd [IPCP ConfReq id=0x8 addr XXX.XXX.XXX.XXX ms-dns1 XXX.XXX.XXX.XXX ms-dns3 XXX.XXX.XXX.XXX] Oct 31 09:10:02 server pptp[78791]: sent [IPCP ConfAck id=0x8 addr XXX.XXX.XXX.XXX ms-dns1 XXX.XXX.XXX.XXX ms-dns3 XXX.XXX.XXX.XXX] Oct 31 09:10:02 server pptp[78791]: found interface eth1 for proxy arp Oct 31 09:10:02 server pptp[78791]: local IP address XXX.XXX.XXX.XXX Oct 31 09:10:02 server pptp[78791]: remote IP address XXX.XXX.XXX.XXX Oct 31 09:10:02 server pptp[78791]: Fatal signal 6
[Desktop-packages] [Bug 1507296] [NEW] Crash Kernel
Public bug reported: problem with Openoffice start crash kernel ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: fglrx wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.5 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: Sun Oct 18 14:28:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-15-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-30-generic, x86_64: installed fglrx-updates-core, 15.200, 3.19.0-30-generic, x86_64: installed vboxhost, 5.0.6, 3.19.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:f927] Subsystem: Toshiba America Info Systems Device [1179:f927] InstallationDate: Installed on 2015-10-16 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L50D-B ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=3df541b9-3346-46eb-b53d-40a3b5f48f9f ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Larne dmi.board.vendor: AMD dmi.board.version: Base 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:bd05/07/2014:svnTOSHIBA:pnSATELLITEL50D-B:pvrPSKUQE-00F00KIT:rvnAMD:rnLarne:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L50D-B dmi.product.version: PSKUQE-00F00KIT dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Oct 18 13:30:14 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: fglrx(0): XMM failed to initialize AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: 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.17.1-0ubuntu3.1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- 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/1507296 Title: Crash Kernel Status in xorg package in Ubuntu: New Bug description: problem with Openoffice start crash kernel ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: fglrx wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.5 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: Sun Oct 18 14:28:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus:
[Desktop-packages] [Bug 1534234] [NEW] The store does not load
Public bug reported: The store does not load pages, and after started is stored away on the white screen and no buttons and pushable. Using ubuntu 16.04 and USC 16.01 ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1534234 Title: The store does not load Status in software-center package in Ubuntu: New Bug description: The store does not load pages, and after started is stored away on the white screen and no buttons and pushable. Using ubuntu 16.04 and USC 16.01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1534234/+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 1540157] Re: Xenial: Mouse pointer disappears after release upgrade
I can confirm this is an actual bug as my system is affected too. My system: Xubuntu 16.04 LTS, x86-64. My system is an update to a 15.10 installation. My solution is to switch to a virtual terminal (CTRL+ALT+F) and then switch back to X session (CTRL+ALT+F7). -- 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/1540157 Title: Xenial: Mouse pointer disappears after release upgrade Status in unity package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: After release upgrade from Wily to Xenial, the mouse pointer is invisible. Reproduce: – Install Ubuntu Wily Werewolf desktop from the official Live CD. – Upgrade to Xenial Xerus with „do-release-upgrade -d”. Only had a chance to test it on KVM virtual machine, but it happened every time I upgraded a virtual machine to Xenial. Also, only tested via Wily -> Xenial upgrade, haven't tried Trusty -> Xenial. Nature Xenial install from the Xenial Live CD daily build right away doesn't have this issue, so I assume something goes wrong during the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20151218-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 BootLog: 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: Sun Jan 31 22:45:19 2016 DistUpgraded: 2016-01-31 21:18:14,758 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2016-01-31 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic root=/dev/mapper/wvg-root ro Renderer: Software SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-01-31 (0 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-vivid dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-vivid dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Sun Jan 31 22:44:03 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 9 inputspice vdagent tablet TOUCHSCREEN, id 10 xserver.errors: systemd-logind: failed to get session: PID 700 does not belong to any known session AIGLX: reverting to software rendering qxl(0): EXECBUFFER failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual-0 Virtual-1 Virtual-2 Virtual-3 xserver.version: 2:1.17.3-2ubuntu2 xserver.video_driver: qxl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1540157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1581569] Re: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial)
The bug still persist with Thunderbird 45.0.4 under Xubuntu Xenial. I tried to restart with all add-on off, but it still crashes. -- 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/1581569 Title: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial) Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Since I have been using Thunderbird version 1:38.7.2+build1-0ubuntu0.16.04.1 on Xenial, I can observe it crashing (seemingly) randomly while idle or while busy, resulting in the platform-independent Mozilla crash dialogue window. I don't know if this is related to Xenial or to internal changes at Mozilla. - lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 apt-cache policy thunderbird thunderbird: Installed: 1:38.7.2+build1-0ubuntu0.16.04.1 Candidate: 1:38.7.2+build1-0ubuntu0.16.04.1 Version table: *** 1:38.7.2+build1-0ubuntu0.16.04.1 500 500 http://mirror.lstn.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.lstn.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:38.6.0+build1-0ubuntu1 500 500 http://mirror.lstn.net/ubuntu xenial/main amd64 Packages 1:24.4.0+build1-0ubuntu1 500 500 http://cz.archive.ubuntu.com/ubuntu trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:38.7.2+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elkins 1436 F pulseaudio BuildID: 20160426220723 Channel: Unavailable CurrentDesktop: XFCE Date: Fri May 13 09:40:02 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-05-05 (8 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.219 metric 100 IwConfig: enp2s0no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-73d462c6-f824-4a34-819a-3c9d82160513 Plugins: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so (icedtea-8-plugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=38.7.2/20160426220723 (In use) RelatedPackageVersions: icedtea-8-plugin 1.6.2-3ubuntu1 RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-73d462c6-f824-4a34-819a-3c9d82160513 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: NM70I-1037U dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/05/2013:svnBIOSTARGroup:pnNM70I-1037U:pvr6.0:rvnBIOSTARGroup:rnNM70I-1037U:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.name: NM70I-1037U dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1581569/+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 1598300] Re: CUPS web interface stops responding after a while
Thank you Robie for pointing to the fix in comment 21 and for the comment that the final fix should be exactly as that one. Any estimate about when will we see the final fix in updates? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1952715] [NEW] package libreoffice-help-en-us 1:6.4.7-0ubuntu0.20.04.2 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_fra
Public bug reported: idk ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 25 16:20:25 2021 DuplicateSignature: package:libreoffice-help-en-us:1:6.4.7-0ubuntu0.20.04.2 Unpacking libreoffice-help-en-us (1:6.4.7-0ubuntu0.20.04.2) over (1:6.4.7-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-GESKDO/29-libreoffice-help-en-us_1%3a6.4.7-0ubuntu0.20.04.2_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-23 (67 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.7-0ubuntu0.20.04.2 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1952715 Title: package libreoffice-help-en-us 1:6.4.7-0ubuntu0.20.04.2 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 25 16:20:25 2021 DuplicateSignature: package:libreoffice-help-en-us:1:6.4.7-0ubuntu0.20.04.2 Unpacking libreoffice-help-en-us (1:6.4.7-0ubuntu0.20.04.2) over (1:6.4.7-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-GESKDO/29-libreoffice-help-en-us_1%3a6.4.7-0ubuntu0.20.04.2_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-23 (67 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.7-0ubuntu0.20.04.2 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/menu/insert_frame.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1952715/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)
news? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1118903 Title: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines) Status in Mir: Triaged Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Bug description: As always, it's a critical requirement for Ubuntu to be able to render the same thing on any machine (metal or virtual), regardless of the availability of hardware acceleration. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1118903/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
It is a good thing that you are able to find the problem? It is fixable? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
@Gerry Ok thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
this is the result of that unity 7 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
@Gerry hahaha -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) Pineview M (0xa011) Version: 11.2.1 Accelerated: yes Video memory: 384MB Unified memory: yes Preferred profile: compat (0x2) Max core profile version: 0.0 Max compat profile version: 1.4 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 2.0 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Pineview M OpenGL version string: 1.4 Mesa 11.2.1 OpenGL extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_clear_buffer_object, GL_ARB_compressed_texture_pixel_storage, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, GL_ARB_fragment_program, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_get_program_binary, GL_ARB_get_texture_sub_image, GL_ARB_half_float_pixel, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_program_interface_query, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_separate_shader_objects, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_ARB_texture_storage, GL_ARB_transpose_matrix, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, GL_ATI_separate_stencil, GL_ATI_texture_env_combine3, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
[Desktop-packages] [Bug 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
roughly how long should we wait? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
it works? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Thanks!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
@Gerry, have you tested it on pineview hardware? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
I've Tried it but is very very slow! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
and now that the fix is no longer present, when will solve this bug? Now you can not use more -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1471998] Re: [enhancement] Support copy-paste between X and Mir
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1471998 Title: [enhancement] Support copy-paste between X and Mir Status in Mir: Fix Committed Status in xorg-server package in Ubuntu: Confirmed Bug description: X applications should be able to paste from Mir applications and vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1471998/+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 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics
Ok -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8/Mir doesn't load on Intel Pineview graphics Status in Mir: Invalid Status in mesa package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.11+16.04.201602.16.1 Version of Mir : 0.20.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
now happens to me a black screen and nothing else, I upgraded to mir 0:21 and does not access its only black screen rhyme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.11+16.04.201602.16.1 Version of Mir : 0.20.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
** Description changed: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. - Version: unity8.11+16.04.201602.16.1 - Version of Mir : 0.20.1 + Version: unity8.12+16.04.201604.01.1 + Version of Mir : 0.21 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics
Then i don't have possibility for use unity8? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8/Mir doesn't load on Intel Pineview graphics Status in Mir: Invalid Status in mesa package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.11+16.04.201602.16.1 Version of Mir : 0.20.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Hi Gerry, I'm sorry if I'm not very experienced, but could you explain the full procedure to download it and run? I am interested in trying it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
I currently have a problem with the internet and the network is down, but if you say you have not had good results does not know what to do -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
** Branch linked: lp:~gerboland/qtubuntu/adopt-more-eglconvenience2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Today I tried again (with ubuntu 16.10) to reopen unity8, the session is very fast game more than usual (it was from 2 weeks since the felt) but still the applications do not work and remain in their infinite loading. the cursor was displayed very large and it was slow (although I think it is caused by failure of applications open) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Using mir 0.21 and unity8.12+16.10.201605.18 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Some news? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
but this bug is solved in a short time or not? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtdeclarative package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
if I try to open on unity(7) an application developed for unity (8) and mir (es.dekko or browser) it opens but it is very slow and the commands are received after 5 seconds. Please fix this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
Daniel, i have the same processor That hast thou,n450 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Invalid Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
I confirm that the atom N470 processor is affected by this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Diamondville and Pineview, but not Cherryview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1603610] Re: Snaps have no screenshots
+1 -- 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/1603610 Title: Snaps have no screenshots Status in Snappy: New Status in gnome-software package in Ubuntu: Confirmed Bug description: Snaps have no screenshots To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1603610/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
When? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
one day we will never use Unity 8 on Atom? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
With the last version of QtUbuntu mir and unity8 work on Atom, thanks Gerry! It is very slow ( but faster than the old EGL convenience version) but it works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Diamondville and Pineview, but not Cherryview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1619178] Re: the contents of windows often appears entirely after opening the window
https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1605062/+attachment/4704374/+files/screenshot20160721_082315580.png ** Summary changed: - the contents of gtk windows often appears entirely after opening the window + the contents of windows often appears entirely after opening the window ** Also affects: libsdl2 (Ubuntu) Importance: Undecided Status: New ** Description changed: the contents of windows often appears entirely after opening the box. In fact, sometimes the right side of the window does not appear, and to see - it is necessary to resize the window. + it is necessary to resize the window. Tested with gtk and sdl2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619178 Title: the contents of windows often appears entirely after opening the window Status in gtk+3.0 package in Ubuntu: New Status in libsdl2 package in Ubuntu: New Bug description: the contents of windows often appears entirely after opening the box. In fact, sometimes the right side of the window does not appear, and to see it is necessary to resize the window. Tested with gtk and sdl2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1619178/+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 1619178] [NEW] the contents of gtk windows often appears entirely after opening the window
Public bug reported: the contents of windows often appears entirely after opening the box. In fact, sometimes the right side of the window does not appear, and to see it is necessary to resize the window. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-mir ** Tags added: gtk-mir ** Summary changed: - the contents of windows often appears entirely after opening the window + the contents of gtk windows often appears entirely after opening the window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619178 Title: the contents of gtk windows often appears entirely after opening the window Status in gtk+3.0 package in Ubuntu: New Bug description: the contents of windows often appears entirely after opening the box. In fact, sometimes the right side of the window does not appear, and to see it is necessary to resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1619178/+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 1618492] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati
Public bug reported: crash ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 14:35:15 2016 ErrorMessage: problemi con le dipendenze - trigger non elaborati InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618492 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati Status in gconf package in Ubuntu: New Bug description: crash ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 14:35:15 2016 ErrorMessage: problemi con le dipendenze - trigger non elaborati InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618492/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)
News? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1118903 Title: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines) Status in Canonical System Image: New Status in Mir: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: As always, it's a critical requirement for Ubuntu to be able to render the same thing on any machine (metal or virtual), regardless of the availability of hardware acceleration. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+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
