[Desktop-packages] [Bug 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox
Lubuntu kinetic daily & issue today with install; I try and use `ubuntu- bug calamares` and get -- start paste (double \n\n trimmed to single \n) What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (21.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 99% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/2aec355c-3001-11ed-99a1-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/2aec355c-3001-11ed-99a1-40a8f0305cb4?' -- end paste Today's daily contains the following (from manifest or https://cdimage.ubuntu.com/lubuntu/daily-live/pending/kinetic-desktop- amd64.manifest) so it's ~same as the jammy daily of the original report (excluding version(s)) snap:core20 stable 1611 snap:snapd stable 16292 snap:firefoxstable/ubuntu-22.10 1810 snap:gnome-3-38-2004stable/ubuntu-22.10 115 snap:bare stable 5 snap:gtk-common-themes stable/ubuntu-22.10 1535 I'm using `firefox` from that daily for this entry; manually started so I can enter details here & my other failure to open using `ubuntu-bug` & firefox works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1969291 Title: apport-collect & ubuntu-bug failing to switch to firefox Status in xdg-utils package in Ubuntu: New Bug description: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION' --- On attempting to file using `ubuntu-bug apport` --- guiverc@dc7700-2re:~$ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.0 KB)
[Desktop-packages] [Bug 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox
** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1969291 Title: apport-collect & ubuntu-bug failing to switch to firefox Status in xdg-utils package in Ubuntu: New Bug description: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION' --- On attempting to file using `ubuntu-bug apport` --- guiverc@dc7700-2re:~$ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 96% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?' --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Apr 17 12:34:57 2022 InstallationDate: Installed on 2022-04-16 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1969291/+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 1988744] Autopkgtest regression report (libreoffice/1:7.3.6-0ubuntu0.22.04.1)
All autopkgtests for the newly accepted libreoffice (1:7.3.6-0ubuntu0.22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/1:7.3.6-0ubuntu0.22.04.1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#libreoffice [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1988744 Title: [SRU] libreoffice 7.3.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744/+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 1988906] Re: Night light and colour management has stopped working in 22.10
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed -- 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/1988906 Title: Night light and colour management has stopped working in 22.10 Status in mutter package in Ubuntu: Fix Committed Bug description: Night light and colour management has stopped working in 22.10, because it's transitioning from the gnome-settings-daemon project into mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1988906/+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 1989132] Re: gnome-shell crashed with SIGABRT
*** This bug is a duplicate of bug 1988315 *** https://bugs.launchpad.net/bugs/1988315 Comment #2 is wrong. This is a duplicate of bug 1988315. ** This bug is no longer a duplicate of bug 1959507 gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) ** This bug has been marked a duplicate of bug 1988315 gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 -- 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/1989132 Title: gnome-shell crashed with SIGABRT Status in gnome-shell package in Ubuntu: New Bug description: Gnome crashed when logging in after restarting after a package update. A second log in to Gnome succeeded. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 16:20:23 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LC_MESSAGES=en_GB.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 clutter_actor_destroy_all_children () at /usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989132/+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 1975745] Re: Cursor change in full screen application causes recursive loop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1975745 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: cursor -- 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/1975745 Title: Cursor change in full screen application causes recursive loop Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version: Ubuntu 22.04 LTS What happens: When my mouse cursor changes in a full screen application (while hovering over something) (like the root prompt or the search bar in the application menu) it repeats the action over and over til I crash my computer. (This problem does not seem to occur when I play a video in full screen.) Expected behavior: The cursor should change to the new one and stay like this until a new cursor change is required. I've attached a video for better understanding of the problem. (I can't record my screen when this happens because the file won't save, so I had to record it via my phone, sorry for that) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975745/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- 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/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+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 1986889] Re: Icons are blurry in nautilus 43 at display scale >= 200%
** Tags added: fixed-in-43.0 fixed-upstream ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- 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/1986889 Title: Icons are blurry in nautilus 43 at display scale >= 200% Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Committed Bug description: Icons are blurry in nautilus 43 at display scale >= 200%. Screenshot attached (compare the icons to their text). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 18 10:58:35 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2022-07-20 (28 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.1-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1986889/+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 1989102] Re: Dragging windows is very slow and choppy
*** This bug is a duplicate of bug 1799679 *** https://bugs.launchpad.net/bugs/1799679 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1799679, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** This bug has been marked a duplicate of bug 1799679 Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1989102 Title: Dragging windows is very slow and choppy Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: 1. UBUNTU VERSION Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy 2. PACKAGE VERSION gdm3: Installed: 42.0-1ubuntu7 Candidate: 42.0-1ubuntu7 Version table: *** 42.0-1ubuntu7 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. WHAT I EXPECTED TO HAPPEN When dragging a window, the window follows the mouse cursor smoothly. 4. WHAT ACTUALLY HAPPENS Dragging windows is extremely slow and choppy. You grab a window and start to drag it. For a very brief moment, around .5s, the window moves smoothly. Then it stops being re-drawn for around 3s. Then there's another brief .5s of smoothness, and the cycle repeats. This occurs with all windows. 5. ADDITIONAL INFORMATION - I was previously on Ubuntu 18.04 and have just upgraded to 22.04. - I am using the nVidia proprietary driver: NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 - I have three monitors. Two standard 60Hz monitors, and one Gigabyte G27Q Freesync compatible 144Hz monitor (I have tried all refresh settings for the monitor, and it makes no difference). - I am running X and do not have the option on login to switch to Wayland (no cog shown). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:41:49 2022 InstallationDate: Installed on 2021-01-05 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-05 (33 days ago) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2022-09-08T10:42:52.395463 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1989102/+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 1989141] Re: temporary hold for mutter
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1989141 Title: temporary hold for mutter Status in mutter package in Ubuntu: Fix Released Bug description: I think we should push gnome-shell to 43~rc to kinetic-proposed before letting mutter 43~rc migrate. I had a tooltip issue with the Ubuntu Dock when I was using mismatched versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989141/+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 1551171]
(In reply to Boris Zbarsky [:bzbarsky] from comment #6) > … xdg-mime … Bug 296443 … See also: bug 724461, bug 893799, bug 1304650, … -- 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/1551171 Title: /usr/share/applications/mimeinfo.cache is used for default applications in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=727422 With Firefox, default applications are selected by Firefox using /usr/share/applications/mimeinfo.cache, however, this list is a system generated list in random order and therefor does not reflect the user's preferences of which application should be used to open a file. When I click on a pdf (for example), I want to have the option to open it in my default application, in my case in okular, and not in something else. However, acroread is invariably presented is presented as default choice because it happens to be the first entry in /usr/share/applications/mimeinfo.cache for application/pdf. This happens in spite of the fact that the desktop provides correct defaults.list and mimeapps.list files The comments in the firefox bug seem to suggest that firefox developers are convinced that firefox calls the correct gtk libraries to determine the correct application. If this is the case, then it is necessarily the ubuntu (or possibly kubuntu) infrastructure to be failing. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 44.0.2+build1-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BuildID: 20160209234513 CurrentDesktop: KDE Date: Mon Feb 29 11:37:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (808 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: firefox UpgradeStatus: Upgraded to wily on 2015-10-23 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1551171/+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 119899]
*** Bug 1787394 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/119899 Title: After-the-fact Filters on custom header won't match for IMAP messages Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Message filtering appears to be broken on Thunderbird 2.0.0.4~rc1-0ubuntu1 in Gutsy with IMAP. I created a filter for the warthogs list and it would not move the messages from my inbox to the folder I had created. It also did not put anything into the filter log. I tried using the Thunderbird on Feisty with my laptop and it worked fine when using the same settings. Chris Jones mentioned he also noticed the same or perhaps a similar issue today. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/119899/+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 1989141] [NEW] temporary hold for mutter
Public bug reported: I think we should push gnome-shell to 43~rc to kinetic-proposed before letting mutter 43~rc migrate. I had a tooltip issue with the Ubuntu Dock when I was using mismatched versions. ** Affects: mutter (Ubuntu) Importance: Undecided Status: Triaged ** Tags: block-proposed kinetic ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1989141 Title: temporary hold for mutter Status in mutter package in Ubuntu: Triaged Bug description: I think we should push gnome-shell to 43~rc to kinetic-proposed before letting mutter 43~rc migrate. I had a tooltip issue with the Ubuntu Dock when I was using mismatched versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989141/+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 1284122] Re: unable to change check spelling language in an textarea without refreshing the page
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/1284122 Title: unable to change check spelling language in an textarea without refreshing the page Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Released Bug description: Hello, chromium browser is still unable to change check spelling language in an textarea (via right click) without refreshing the page (which results to losing the data input and is frustrating anyway)... Firefox, to the contrary, does not have problem to change it on-the- fly. But it seems FF uses some different mechanism, because it looks slightly different - see the attachments. There must be a bug somewhere :( ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 14:28:11 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2013-10-26 (121 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1284122/+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 1258812] Re: No prompt for webapps
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- 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/1258812 Title: No prompt for webapps Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrading to ubuntu 13.10 when I access a site that has a webapp (e.g. youtube) and I didn't access before I don't get the usual prompt asking me whether I want to enable the webapp. If I access the same site via firefox it does ask me and, once the webapp is enabled from firefox, it works also in chromium. I'm using chromium-browser 30.0.1599.114-0ubuntu0.13.10.2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 30.0.1599.114-0ubuntu0.13.10.2 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic i686 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CheckboxSubmission: b005b394090223fa15eccd0cb510e904 CheckboxSystem: e2a9e28435948e86843155dc45ba128e Date: Sat Dec 7 20:32:30 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda4 ext4 124G 106G 12G 91% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 979M 4.0K 979M 1% /dev\ntmpfs tmpfs 199M 1.3M 197M 1% /run\nnone tmpfs 5.0M 16K 5.0M 1% /run/lock\nnone tmpfs 991M 5.1M 986M 1% /run/shm\nnone tmpfs 100M 56K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda47.9M 786K 7.1M 10% /\nnone 216K 2 216K1% /sys/fs/cgroup\nudev 210K 554 209K1% /dev\ntmpfs 216K 603 215K1% /run\nnone 216K13 216K1% /run/lock\nnone 216K21 216K1% /run/shm\nnone 216K30 216K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2010-03-20 (1358 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: Upgraded to saucy on 2013-11-23 (14 days ago) chromium-default: gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %U\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %U\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser # Options to pass to chromium-browser #CHROMIUM_FLAGS="--password-store=detect" mtime.conffile..etc.chromium.browser.default: 2013-07-28T12:54:15.460397 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1258812/+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 1276270] Re: /usr/lib/chromium-browser/chromium-browser:11:content::PluginURLFetcher::OnReceivedRedirect:content::ResourceDispatcher::OnReceivedRedirect:DispatchToMethod:Dispat
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- 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/1276270 Title: /usr/lib/chromium-browser/chromium- browser:11:content::PluginURLFetcher::OnReceivedRedirect:content::ResourceDispatcher::OnReceivedRedirect:DispatchToMethod:Dispatch:content::ResourceDispatcher::DispatchMessage Status in chromium-browser package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with version 32.0.1700.102-0ubuntu0.13.10.1~20140128.970.1, the problem page at https://errors.ubuntu.com/problem/fa29d969eaeca7b9e5f33f8ccc3143bbb522d938 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1276270/+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 1243544] Re: create -dev bin package
** Changed in: chromium-browser (Ubuntu) Status: Triaged => Won't Fix -- 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/1243544 Title: create -dev bin package Status in chromium-browser package in Ubuntu: Won't Fix Bug description: You should create one (or multiple) -dev packages to have .h files. So tools using libraries for ex can be built without needing the complete source code (which is very big). Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1243544/+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 1224225] Re: Chromium codecs packages should use Enhances
** Changed in: chromium-browser (Ubuntu) Status: Triaged => Invalid -- 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/1224225 Title: Chromium codecs packages should use Enhances Status in chromium-browser package in Ubuntu: Invalid Bug description: In 29.0.1547.65-0ubuntu2, you removed the dependency from the codecs to chromium-browser. Instead, you should use Enhances: chromium- browser so that users can find one from the other in package managers that support Enhances (which should be almost all of them). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1224225/+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 1250550] Re: Java plugin crash
Please bump it if still reproducible. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- 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/1250550 Title: Java plugin crash Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Incomplete Bug description: 1) Ubuntu Release: Description: Ubuntu 12.04.3 LTS Release: 12.04 2) Package version: chromium-browser: Instalados: 30.0.1599.114-0ubuntu0.12.04.3 Candidato: 30.0.1599.114-0ubuntu0.12.04.3 Tabla de versión: *** 30.0.1599.114-0ubuntu0.12.04.3 0 500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages 100 /var/lib/dpkg/status 18.0.1025.151~r130497-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages Oracle / Sun Java: JDK 1.6.0_45 (also tested with 1.6.0_38) 3) What I expect: Java applets should load using Oracle/Sun 1.6.0.x / 1.7.0.x 4) What I get: erevilla@ub1204:/usr/lib/chromium-browser$ chromium-browser Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64/libnio.so: /usr/lib/chromium-browser/libs/libnet.so: version `SUNWprivate_1.1' not found (required by /usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64/libnio.so) at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724) at java.lang.Runtime.loadLibrary0(Runtime.java:823) at java.lang.System.loadLibrary(System.java:1028) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at sun.nio.ch.Util.load(Util.java:464) at sun.nio.ch.FileChannelImpl.(FileChannelImpl.java:1224) at java.io.FileInputStream.getChannel(FileInputStream.java:342) at com.sun.deploy.util.SyncFileAccess.openLockFileObject(SyncFileAccess.java:233) at com.sun.deploy.util.SyncFileAccess.openLockFileInputStream(SyncFileAccess.java:71) at com.sun.deploy.config.Config.loadPropertiesFile(Config.java:1740) at com.sun.deploy.config.Config.refreshProps(Config.java:1133) at com.sun.deploy.config.Config.initialize(Config.java:939) at com.sun.deploy.config.Config.(Config.java:886) at sun.plugin2.main.server.JVMManager.processJREInfo(JVMManager.java:578) at sun.plugin2.main.server.JVMManager.(JVMManager.java:48) at sun.plugin2.main.server.JVMManager.(JVMManager.java:26) at sun.plugin2.main.server.MozillaPlugin.(MozillaPlugin.java:111) when loading an applet. 5) Workarounds: - Install Chromium 29.x from ppa:chromium-daily/stable - Use Chrome 6) Probable cause: name clash in libnet.so: Chromium: /usr/lib/chromium-browser/libs/libnet.so Java: /usr/lib/jvm//jre/lib/amd64/libnet.so To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1250550/+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 1219800] Re: update apparmor profiles for chromium browser
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- 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/1219800 Title: update apparmor profiles for chromium browser Status in chromium-browser package in Ubuntu: Invalid Bug description: apparmor="ALLOWED" operation="open" parent=22477 profile="/usr/lib/chromium-browser/chromium- browser//chromium_browser_sandbox" name="/usr/lib/i386-linux- gnu/libstdc++.so.6.0.18" pid=14545 comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 apparmor="ALLOWED" operation="file_mmap" parent=22477 profile="/usr/lib/chromium-browser/chromium- browser//chromium_browser_sandbox" name="/usr/lib/i386-linux- gnu/libstdc++.so.6.0.18" pid=14545 comm="chromium-browse" requested_mask="mr" denied_mask="mr" fsuid=0 ouid=0 apparmor="ALLOWED" operation="open" parent=22477 profile="/usr/lib/chromium-browser/chromium- browser//chromium_browser_sandbox" name="/lib/i386-linux- gnu/libgcc_s.so.1" pid=14545 comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 apparmor="ALLOWED" operation="file_mmap" parent=22477 profile="/usr/lib/chromium-browser/chromium- browser//chromium_browser_sandbox" name="/lib/i386-linux- gnu/libgcc_s.so.1" pid=14545 comm="chromium-browse" requested_mask="mr" denied_mask="mr" fsuid=0 ouid=0 Less important: apparmor="ALLOWED" operation="exec" # profile="/usr/lib/chromium- browser/chromium-browser" name="/usr/bin/lsb_release" comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 target="/usr/lib/chromium-browser/chromium-browser//null-16" apparmor="ALLOWED" operation="getattr" # profile="/usr/lib/chromium-browser/chromium-browser//null-16" name="/etc/ld.so.cache" comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="getattr" # profile="/usr/lib/chromium-browser/chromium-browser//null-16" name="/usr/lib/chromium-browser/" comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="getattr" # profile="/usr/lib/chromium-browser/chromium-browser//null-16" name="/usr/lib/chromium-browser/libs/" comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="open" # profile="/usr/lib/chromium-browser/chromium-browser" name="/sys/devices/system/cpu/cpu0/topology/core_id" comm="GoogleTalkPlugi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="open" # profile="/usr/lib/chromium- browser/chromium-browser" name="/sys/devices/system/cpu/cpu1/topology/core_id" comm="GoogleTalkPlugi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="open" # profile="/usr/lib/chromium- browser/chromium-browser" name="/sys/devices/system/cpu/cpu2/topology/core_id" comm="GoogleTalkPlugi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="open" # profile="/usr/lib/chromium- browser/chromium-browser" name="/sys/devices/system/cpu/cpu3/topology/core_id" comm="GoogleTalkPlugi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="open" # profile="/usr/lib/chromium- browser/chromium-browser" name="/sys/devices/system/cpu/present" comm="GoogleTalkPlugi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="ALLOWED" operation="open" # profile="/usr/lib/chromium- browser/chromium-browser//null-16" name="/etc/ld.so.cache" comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1219800/+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 1195547] Re: Reconsider third-party-cookies-off-by-default.patch
** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- 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/1195547 Title: Reconsider third-party-cookies-off-by-default.patch Status in chromium-browser package in Ubuntu: Fix Released Bug description: The latest version of Chromium in Saucy turns off all third-party cookies. Last month, Firefox decided to postpone their more advanced third party cookie default block which would have only blocked third party cookies for sites the user hadn't visited yet. The feature just wasn't ready yet. http://arstechnica.com/information-technology/2013/05/mozilla-delays- turning-on-third-party-cookie-killer-in-firefox/ The third-party-cookies-off-by-default.patch breaks web functionality (such as social networking widgets). For instance it appears to make it impossible to post a comment on news sites that use Facebook comments. Disabling this new feature requires a user to open Settings, scroll to the bottom and click Show advanced settings, find the Content Settings button in Privacy and uncheck Block third-party cookies and site data. Before this is enabled by default, I'd like to see an easy way for users to whitelist websites that they use. Blocking needs to be smarter as third-party cookies aren't necessarily evil; it depends on what features the user wants. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 28.0.1500.52-0ubuntu2 [origin: unknown] ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 overlayfs nls_utf8 isofs pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv parport_pc ppdev rfcomm bnep dm_crypt intel_powerclamp coretemp kvm_intel kvm joydev crc32_pclmul ghash_clmulni_intel arc4 cryptd ath9k dm_multipath scsi_dh ath9k_common ath9k_hw uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core ath snd_hda_codec_hdmi snd_hda_codec_conexant mac80211 snd_hda_intel videodev ath3k btusb snd_hda_codec bluetooth cfg80211 snd_hwdep snd_pcm psmouse microcode toshiba_acpi toshiba_bluetooth serio_raw sparse_keymap snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei soundcore lpc_ich mac_hid lp parport btrfs xor zlib_deflate raid6_pq libcrc32c dm_mirror dm_region_hash dm_log ums_realtek usb_storage i915 i2c_algo_bit drm_kms_helper drm atl1c ahci libahci wmi video ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 CrashDB: ubuntu Date: Thu Jun 27 22:54:27 2013 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-06-14 (13 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1195547/+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 1989131] Re: [snap] What about PDF MimeType in .desktop file?
Fair enough :-) I think PDF is pretty major. -- 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/1989131 Title: [snap] What about PDF MimeType in .desktop file? Status in chromium-browser package in Ubuntu: Triaged Bug description: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1980143] Re: Permission denied when trying to load unpacked browser extension from folder with 755 permissions
*** This bug is a duplicate of bug 1987945 *** https://bugs.launchpad.net/bugs/1987945 ** This bug has been marked a duplicate of bug 1987945 [snap] chromium does not read root-owned files in $HOME -- 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/1980143 Title: Permission denied when trying to load unpacked browser extension from folder with 755 permissions Status in chromium-browser package in Ubuntu: New Bug description: 1) Ubuntu version Description:Ubuntu 20.04.4 LTS Release:20.04 2) chromium snap 103.0.5060.53 3) Expected result When trying to load an "unpacked" browser extension for development, I should be able to click the "Load unpacked" button on the chrome://extensions/ view (in Developer mode) and select any folder for which I have access rights. In particular, I'm trying to access a folder within my own home directory which has 755 permissions and root:root ownership. I have access to read this folder (and the files within it) as far as the operating system is concerned. This always worked fine with the apt/deb packaging of Chromium until I updated to Ubuntu 20.04.4 (and thus the snap packaging) a few days ago. The extension would load as expected. 4) Actual result When I try to load the extension from that folder in Chromium, I receive an error: Could not read the contents of app Error opening directory '/home/myuser/some/path/to/app': Permission denied Regardless of whether or not I should have this strange scenario, chromium should not be deciding for me which files/folders I can or cannot access. I expect this permissions issue extends beyond only the loading of unpacked extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1980143/+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 1989131] Re: [snap] What about PDF MimeType in .desktop file?
Thanks for your report, Alexander. > What about PDF Pretty much, and since web browsers are handle a wide range of file types nowadays, we will certainly still miss many of them :). ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/1989131 Title: [snap] What about PDF MimeType in .desktop file? Status in chromium-browser package in Ubuntu: Triaged Bug description: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1989132] Re: gnome-shell crashed with SIGABRT
*** This bug is a duplicate of bug 1959507 *** https://bugs.launchpad.net/bugs/1959507 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959507, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1989132/+attachment/5614703/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1989132/+attachment/5614705/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1989132/+attachment/5614709/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1989132/+attachment/5614710/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1989132/+attachment/5614711/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1989132/+attachment/5614713/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1989132/+attachment/5614714/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1959507 gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1989132 Title: gnome-shell crashed with SIGABRT Status in gnome-shell package in Ubuntu: New Bug description: Gnome crashed when logging in after restarting after a package update. A second log in to Gnome succeeded. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 16:20:23 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LC_MESSAGES=en_GB.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 clutter_actor_destroy_all_children () at /usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989132/+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 1989131] [NEW] [snap] What about PDF MimeType in .desktop file?
Public bug reported: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1989131 Title: [snap] What about PDF MimeType in .desktop file? Status in chromium-browser package in Ubuntu: New Bug description: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1989128] [NEW] ctrl shift printscreen not working
Public bug reported: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1989128 Title: ctrl shift printscreen not working Status in libfprint package in Ubuntu: New Bug description: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1989128/+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 1988744] Re: [SRU] libreoffice 7.3.6 for jammy
Hello Rico, or anyone else affected, Accepted libreoffice into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1988744 Title: [SRU] libreoffice 7.3.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1988744] Re: [SRU] libreoffice 7.3.6 for jammy
** Description changed: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release - * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of ?? bugs): + * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of ?? bug fixes always carries the + * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/1988744 Title: [SRU] libreoffice 7.3.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests
[Desktop-packages] [Bug 993656] Re: chromium isn't a drag target in the unity launcher
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/993656 Title: chromium isn't a drag target in the unity launcher Status in chromium-browser package in Ubuntu: Fix Released Bug description: When I drag a png file (and other files) from the dash to the launcher, many apps (including firefox) light up but chromium doesn't. As I understand it this is due to the .desktop file for chromium not mentioning png files. MimeType=text/html;text/xml;application/xhtml_xml;x-scheme- handler/http;x-scheme-handler/https; Whereas Firefox has:- MimeType=text/html;text/xml;application/xhtml+xml;application/xml;application/vnd.mozilla.xul+xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme- handler/http;x-scheme-handler/https;x-scheme-handler/ftp;x-scheme- handler/chrome;video/webm; ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 2 17:57:57 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120203) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/993656/+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 1968377] Re: [snap] New Chromium icon, not yet used by Snap
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1968377 Title: [snap] New Chromium icon, not yet used by Snap Status in chromium-browser package in Ubuntu: Fix Released Bug description: Google updated the Chrome/Chromium icons recently (see more at https://twitter.com/elvin_not_11/status/1489647032201465861), but I don't think the Snap icon has been updated. Here's the Chromium icons on the Chromium source GitHub mirror, which was easier for me to search: https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+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 1988744] Re: [SRU] libreoffice 7.3.6 for jammy
@sil2000: I will try to "break" or tweak an existing installation for verification of this specific issue. I haven't ran into this problem myself and didn't see a report in Ubuntu. Apparently there were users in Debian suffering from this problem. -- 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/1988744 Title: [SRU] libreoffice 7.3.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744/+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 1988744] Re: [SRU] libreoffice 7.3.6 for jammy
While reviewing, I see that a new `libreoffice-common.preinst.in` maintscript has been added. The script itself seems to be sane, but can we add a test case to the test plan that would test the scenario of the preinst? Making sure that it works and also that it doesn't actually remove anything invalidly. 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/1988744 Title: [SRU] libreoffice 7.3.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of ?? bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744/+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 1989117] [NEW] when booting up pc, asks for authentication twice and tries to automatically connect to an unknown wifi network
Public bug reported: This started happening after installing vmware ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 19:17:56 2022 InstallationDate: Installed on 2022-08-25 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1989117 Title: when booting up pc, asks for authentication twice and tries to automatically connect to an unknown wifi network Status in network-manager package in Ubuntu: New Bug description: This started happening after installing vmware ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 19:17:56 2022 InstallationDate: Installed on 2022-08-25 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1989117/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
Same problem on version 105.0.5195.102. Neither of the proposed solutions solved the problem. I tested Google Chrome beta, version 106.0.5249.30 and the problem is not present. -- 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child
vanvugt, Thanks! That resolved the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Fedora: Confirmed Bug description: After upgrading to kinetic gnome-shell is crashing on start when using wayland. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 10:28:31 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso InstallationDate: Installed on 2020-05-18 (834 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20200511-12:31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-05-11T08:18:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1989029] Re: volume-key build test failure
This bug was fixed in the package volume-key - 0.3.12-5 --- volume-key (0.3.12-5) unstable; urgency=medium * Use dh-sequence-python3 Build-Depends to enable the python3 addon * Avoid test suite failure due to overlong socket path. In compat 13, dh will reset HOME to a writable location managed by debhelper. The resulting socket path can exceed the 108 char limit of sockaddr_un.path, resulting in a test suite failure. Thus call "make check" directly to avoid HOME being overridden. -- Michael Biebl Thu, 08 Sep 2022 01:54:16 +0200 ** Changed in: volume-key (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1989029 Title: volume-key build test failure Status in volume-key package in Ubuntu: Fix Released Bug description: I'm just filing this bug for tracking. The debhelper compat bump to 13 ended up causing volume-key's build tests to fail because the path is too long for gpgme. The Debian maintainer for volume-key is working on figuring out an appropriate workaround for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1989029/+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 1311880] Re: screen locks after timeout even when configured not to
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1311880 Title: screen locks after timeout even when configured not to Status in xorg package in Ubuntu: Incomplete Bug description: in System Settings, "Brightness & Lock", "Turn screen off when inactive for:" is set to "Never", the screen is automatically turned off after 5 minutes of inactivity. HIGHLY annoying behavior when running in a VM, and in my workflow, extremely disruptive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 23 13:58:07 2014 DistUpgraded: 2014-04-21 13:11:34,486 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2012-10-19 (551 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ed2abf01-d9e4-43ff-8430-fc9580e8be4c ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-21 (2 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 23 13:24:21 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: No surface to present from. No surface to present from. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311880/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Attaching the logs when running chromium. The /usr/share/libreoffice is missing from chromium's mount namespace, and the logs show that an error occurred when creating it: change.go:446: DEBUG: remove "/tmp/.snap/usr/share" (error: ) change.go:320: DEBUG: mount name:"/var/lib/snapd/hostfs/usr/share/gtk-doc" dir:"/usr/share/gtk-doc" type:"none" opts:MS_BIND|MS_RDONLY unparsed:"" (error: ) update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied ** Attachment added: "SNAPD_DEBUG=1 chromium" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+attachment/5614653/+files/chromium.log -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.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/1951210/+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 1988660] Re: snap doesn't map joystick buttons correctly
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- 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/1988660 Title: snap doesn't map joystick buttons correctly Status in chromium-browser package in Ubuntu: New Bug description: I tested the deb version and works fine. Steps to reproduce the problem: 1.Connect the PS4 joystick by Bluetooth in Linux 2.Test mapping in a webpage like gamepad-tester.com 3.Almost all buttons are incorrectly mapped Problem Description: The buttons of the joystick are incorrectly mapped in the browser and this makes impossible to play Stadia, even the right axis remain always pressed when you press R2 once, you can see the error by yourself at this short video: https://www.youtube.com/watch?v=VLPQkXyVAsM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1988660/+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 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)
I can confirm this issue also exists with opening attached Libre Office documents from within Mozilla Thunderbird. What a pity this problem still exists in a LTS version. What can I do to help fixing this issue? -- 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/1790608 Title: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp) Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1790608/+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 1881603] Re: [snap] Cannot open attached file from e-mail
This bug is similar to the issue described in this older bug report https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1790608 I'm a bit disappointed that we've left a bug like this in a LTS release without a solution. It seems the snap approach is not yet on equal ux/ui footing with the previous approaches. Is there a way I can help with fixing this? -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1633852] Re: Blank screen on boot when using nvidia
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: New => Incomplete ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1633852 Title: Blank screen on boot when using nvidia Status in nvidia-graphics-drivers-361 package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: The problem always happens when I try to use the nvidia graphics card using the command prime-select nvidia. When using prime-select intel it works fine. The baffling part is that I dual boot 2 Ubuntu installs... And the other one works fine. I can help try and figure out what seems to be wrong, I just don't know which files to diff. - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 16 13:48:35 2016 DistUpgraded: 2016-05-13 01:31:31,411 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 540M] [17aa:397d] InstallationDate: Installed on 2014-12-31 (654 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic.efi.signed root=UUID=dddc1c5f-ac3e-48b9-90c3-cd0effbf6a55 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-05-13 (156 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Oct 16 13:45:12 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1682897] Re: Ubuntu is very Slowly HP Notebook 14
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1682897 Title: Ubuntu is very Slowly HP Notebook 14 Status in xorg package in Ubuntu: Incomplete Bug description: with de Graphics Controller VGA compatible controller : Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.11.0-041100rc5-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 CurrentDesktop: Unity Date: Fri Apr 14 13:12:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:226c] InstallationDate: Installed on 2017-03-31 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc5-generic root=UUID=334f5d0d-319f-4cf0-8f2c-ea99c43284d2 ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 226C dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.37:bd01/21/2015:svnHewlett-Packard:pnHP14NotebookPC:pvr097710405F0610180:rvnHewlett-Packard:rn226C:rvr74.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 14 Notebook PC dmi.product.version: 097710405F0610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 14 08:34:58 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682897/+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 1637882] Re: no funciona mi video intel
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1637882 Title: no funciona mi video intel Status in xorg package in Ubuntu: Incomplete Bug description: no funciona correctmene diver intel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started Accounts Service. 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 Oct 30 22:39:48 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems 3rd Gen Core processor Graphics Controller [1019:9991] InstallationDate: Installed on 2016-09-08 (51 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: VIT VIT P3400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=f67a0a94-0978-4494-8c4e-1c4e40ab830b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 2.00.01.IP_T4 dmi.board.asset.tag: NULL dmi.board.name: VIT P3400 dmi.board.vendor: VIT dmi.board.version: Not applicable dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: VIT dmi.chassis.version: Not applicable dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr2.00.01.IP_T4:bd03/25/2013:svnVIT:pnVITP3400:pvr1.0:rvnVIT:rnVITP3400:rvrNotapplicable:cvnVIT:ct9:cvrNotapplicable: dmi.product.name: VIT P3400 dmi.product.version: 1.0 dmi.sys.vendor: VIT version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Oct 30 22:29:25 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1401 vendor IVO xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637882/+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 1705884] Re: Black screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- 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/1705884 Title: Black screen Status in xorg package in Ubuntu: Incomplete Bug description: black screen when lock. Black screen not able to recover login info to re-enter gnome. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jul 23 11:29:32 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 420] [174b:1162] InstallationDate: Installed on 2017-06-04 (49 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Packard Bell imedia S3810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=61dd95f6-c8ec-48c9-82fd-87eee44dd781 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: imedia S3810 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd08/19/2010:svnPackardBell:pnimediaS3810:pvr:rvnPackardBell:rnimediaS3810:rvr:cvnPackardBell:ct3:cvr: dmi.product.name: imedia S3810 dmi.sys.vendor: Packard Bell version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705884/+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 1663886] Re: crash after power save timeout
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1663886 Title: crash after power save timeout Status in Ubuntu: Incomplete Bug description: after computer is going to powersave, it is not possible to wakeup the screen with any key or mouse moving ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Feb 11 15:09:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300/X550/X1050 Series] [1002:5b63] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV370 [Radeon X300/X550/X1050 Series] [174b:1490] Subsystem: PC Partner Limited / Sapphire Technology RV370 [Radeon X300/X550/X1050 Series] (Secondary) [174b:1491] InstallationDate: Installed on 2017-02-03 (7 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=209ef71d-7cb0-4e0f-8da4-af8f0c35cf4c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0509 dmi.board.name: P5PL2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0509:bd12/01/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5PL2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Feb 11 12:38:52 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1663886/+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 1668165] Re: Cannot control brightness
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1668165 Title: Cannot control brightness Status in xorg package in Ubuntu: Incomplete Bug description: Brightness is set to max automatically. ProblemType: Bug DistroRelease: elementary 0.4 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Pantheon Date: Mon Feb 27 12:01:55 2017 InstallationDate: Installed on 2017-02-26 (0 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668165/+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 1692213] Re: black screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1692213 Title: black screen Status in Ubuntu: Incomplete Bug description: my system went to black screen and became unresponsive ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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: Sat May 20 14:30:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 7310] [144d:c0db] InstallationDate: Installed on 2016-12-30 (140 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=c0b388a3-7664-45c6-a50e-24458bdf7bd5 ro splash quiet nopat SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ABG dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355E5C-A01GR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ABG:bd02/23/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP05ABG.008.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E5C-A01GR:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 355V4C/356V4C/3445VC/3545VC dmi.product.version: P05ABG.008.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat May 20 09:47:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1692213/+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 1988836] Re: Enable the open NVIDIA kernel modules
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- kernel-modules/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1665946] Re: Screen flickers turns off then on
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1665946 Title: Screen flickers turns off then on Status in xorg package in Ubuntu: Incomplete Bug description: The display is constantly flashing on and off it just started doing it a couple of days ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 CurrentDesktop: Unity Date: Sat Feb 18 18:37:48 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] InstallationDate: Installed on 2016-12-30 (50 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=97dd6a2c-686c-4698-a2ae-13a1c9d24137 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0G785M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0G785M:rvrA00:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Feb 18 09:52:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2702 vendor SAM xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1665946/+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 1665796] Re: multi-display layout corrupt after reboot or log out/in
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1665796 Title: multi-display layout corrupt after reboot or log out/in Status in xorg package in Ubuntu: Incomplete Bug description: Every time I reboot or log out and back in again, The layout of the displays is incorrect. Correcting the layout is a bit 'hit and miss' as the changed layout is not always applied correctly. There was a massive improvement after upgrading to 16.04 from 14.04. Previously, the upper display did not render pixels consistently. The upgrade corrected this. The upper display (29") is connected to the NVIDIA Corporation GK107 [GeForce GT 740] display card and the lower display (23") is connected to the on-board Intel Integrated Graphics Controller. I hope this information is useful. Thanks for your efforts... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,move,regex,resize,mousepoll,animation,wall,place,compiztoolbox,grid,gnomecompat,fade,workarounds,vpswitch,snap,imgpng,scale,session,expo,ezoom,switcher] CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Fri Feb 17 21:59:43 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [1458:d000] NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GK107 [GeForce GT 740] [1569:0fc8] InstallationDate: Installed on 2014-05-28 (995 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. Z68XP-UD3P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=71be335b-0f03-461d-b458-0b40a18be8ab ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: Z68XP-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68XP-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Feb 17 21:25:03 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD,
[Desktop-packages] [Bug 1704041] Re: Screen resolution
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1704041 Title: Screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: I having graphics problem with ubuntu 16.04not able to add screen resolution...everthing is too bigit gives option only to select one resolution in setting and display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39 Uname: Linux 3.13.0-108-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 12 20:24:26 2017 DistUpgraded: 2017-02-15 16:10:12,331 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: open-vm-tools, 10.0.7: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2017-02-15 (147 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-108-generic root=UUID=4f931ec7-b9ca-4a3b-82bc-5fc68306ba69 ro nomdmonddf nomdmonisw Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-02-16 (147 days ago) dmi.bios.date: 11/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0316 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0316:bd11/08/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 12 20:22:45 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1697918] Re: ubuntu resolution
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1697918 Title: ubuntu resolution Status in xorg package in Ubuntu: Incomplete Bug description: there is no resolution list available just 800*600 and my screen up tp 1920*1080 , and there was desktop login loop when i installed any nvidia drivers version . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.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 CurrentDesktop: Unity Date: Wed Jun 14 13:11:09 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2017-06-12 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed root=UUID=e53ad924-76e5-4007-b242-c39ae16ebcc7 ro quiet splash nomodeset vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.217:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL552VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jun 14 15:06:01 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1697918/+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 1711856] Re: Help! Mouse moves but none of the buttons work!
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1711856 Title: Help! Mouse moves but none of the buttons work! Status in xorg package in Ubuntu: Incomplete Bug description: I start it up and everything goes fine for maybe the first two minutes of whatever I'm doing. then all of a sudden I can't click anything. Also I want to close a window, move the cursor over the X, going backward and forward with my mouse buttons but I can't. I can push right click, try to kill the window but then I can't confirm because I can't click 'yes.' I can't even power down normally because I can't click 'yes' when the duologue appears. Very annoying. when I had windows 7 and 8 it happened and with so much searches that I did nothing worked so I did not use my gaming mouse for months and after a long time I did plug in my mouse and there was no problem. rightnow I have Ubuntu 14.04 for one year and this problem happened again. I have "MSI Gaming Mouse P/n s12-0400690-AA3" Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 19 23:49:25 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.4.0-89-generic, x86_64: installed nvidia-304, 304.135, 4.4.0-91-generic, x86_64: installed nvidia-304, 304.135, 4.4.0-92-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d] InstallationDate: Installed on 2016-12-06 (256 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic root=UUID=f01602a0-6076-4436-9a4b-e05e01b6cdc5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Card 0" BusID "PCI:0@0:2:0" EndSection dmi.bios.date: 05/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16G5IMS V1.0F dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16G5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: GE620/GE620DX/FX620DX dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Error querying enabled displays on GPU 0 (Missing Extension). ERROR: Error querying connected displays on GPU 0 (Missing Extension). version.compiz:
[Desktop-packages] [Bug 1732889] Re: graphic bootloader
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1732889 Title: graphic bootloader Status in xorg package in Ubuntu: Incomplete Bug description: i don't have graphical bootloader and i cant restart the PC. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 17 14:33:06 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3800] InstallationDate: Installed on 2017-11-13 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5664 IMC Networks Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=b72bf002-0c4a-44dc-a065-ecaa2bbb864c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K45914 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN39WW:bd10/11/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Nov 16 07:06:50 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732889/+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 1697185] Re: vce init error (-22)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) and give us some more information about the issue you are seeing otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1697185 Title: vce init error (-22) Status in xorg package in Ubuntu: Incomplete Bug description: gaphic display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0m[0;31m* [0m] A start job is running for Hold until boot process finishes up (22s / no limit) [K Starting WPA supplicant... [[0;32m OK [0m] Started WPA supplicant. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 10 21:35:59 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Carrizo [1043:13d0] InstallationDate: Installed on 2017-06-08 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555QG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=1c098302-9a84-4d05-b001-bcb26aff0602 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555QG.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555QG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555QG.304:bd10/18/2016:svnASUSTeKCOMPUTERINC.:pnX555QG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555QG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555QG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jun 10 19:37:12 2017 xserver.configfile: default xserver.errors: AMDGPU(G0): amdgpu_device_initialize failed RADEON(G1): [drm] failed to set drm interface version. RADEON(G1): Kernel modesetting setup failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1697185/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
I'm afraid that Olivier is right. In the commit he linked to, the two lines apparmor.GenWritableProfile(emit, "/usr/share/libreoffice/help", 3) apparmor.GenWritableProfile(emit, "/usr/share/xubuntu-docs", 3) were replaced with a single apparmor.GenWritableProfile(emit, "/usr/share/", 3) I need to investigate this, but my first guess is that this has the effect of making firefox and chrome see a different /usr/share/ tree than the one from the host. I'll be investigating this. ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.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/1951210/+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 1708924] Re: Monitor positions and resolution not saved
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1708924 Title: Monitor positions and resolution not saved Status in xorg package in Ubuntu: Incomplete Bug description: Upon boot, I always have right monitor ending up on the left and vice versa. I have to move them every single time after boot and after I turn off both then turn on both. It never saves my settings. Also, 1 of the monitors is 4k and other one is 2560x1440 max, I save them both to be 2560x1440 but after boot or turn off/turn on sequence 4k goes into max resolution of 3840x2160. I tried various options with xrandr but nothing helps. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Aug 6 00:58:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Hawaii PRO [Radeon R9 290] [1043:04dd] InstallationDate: Installed on 2016-04-02 (490 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=322e367a-ab42-4f50-9ddf-fc99d43a174c ro plymouth SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Rampage III Extreme dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd05/12/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIIExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Aug 6 00:51:37 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708924/+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 1987875] Re: Cmore streaming service not working well after recent updates
** Package changed: ubuntu => firefox (Ubuntu) ** Changed in: firefox (Ubuntu) Status: Incomplete => New ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987875 Title: Cmore streaming service not working well after recent updates Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: I have tried with several computers and version 18.04 20.04 and 22.04 after last update Cmore is not playing well. The picture and sound is interrupting, so the streaming is not good. I think it is the last version of widevine decryption is doing it, because youtube and dr.dk works fine. The laptop is also getting very very hot, and in the end it just stop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987875/+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 1600414] Re: Xorg freezes regularly on login, more likely immediately after boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1600414 Title: Xorg freezes regularly on login, more likely immediately after boot Status in xorg package in Ubuntu: Incomplete Bug description: I regularly get Xorg freezes if I log in immediately after booting, and only when when running dual 4k displays (internal and external). If I alt-ctrl-F1 to virtual console, login and enter a catchall $ sleep 20 && kill -9 -1 0 and then alt-ctrl-F7 to attempt an X login, the Xorg freezes seem to happen less often. When the freezes do happen, the kill statement returns the X login prompt. Typically (but not always) when repeating this process a second time, the X login succeeds. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Docker Application Container Engine. [[0;32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jul 8 21:33:28 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.45.18, 4.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Skylake Integrated Graphics [144d:c12b] Subsystem: Samsung Electronics Co Ltd GM107M [GeForce GTX 950M] [144d:c12b] InstallationDate: Installed on 2015-12-22 (199 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 940Z5L ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=24c27814-5135-4a80-9ce1-b932e2513949 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P07AFC.093.160516.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP940Z5L-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8554A1H-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP07AFC.093.160516.SH:bd05/16/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn940Z5L:pvrP07AFC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940Z5L-X01US:rvrSGL8554A1H-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 940Z5L dmi.product.version: P07AFC dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri
[Desktop-packages] [Bug 1620065] Re: intermittent black screen on bootup
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1620065 Title: intermittent black screen on bootup Status in xorg package in Ubuntu: Incomplete Bug description: sometimes when I boot up, the screen stays black. Only the mouse cursor works, and control-alt-f1 gives a useable screen. Rebooting from there usually gives me a clean bootup, but sometimes it takes several efforts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Sep 4 15:57:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-08-15 (19 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge Bus 002 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=2acc9848-1f7b-48e3-ad25-0d953ae79051 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.asset.tag: dmi.board.name: 939NF4G-SATA2 dmi.board.version: 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/15/2006:svn:pn939NF4G-SATA2:pvr1.00:rvn:rn939NF4G-SATA2:rvr1.00: dmi.product.name: 939NF4G-SATA2 dmi.product.version: 1.00 version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 4 15:56:01 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1620065/+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 1642600] Re: PC freeze when turning off screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1642600 Title: PC freeze when turning off screen Status in xorg package in Ubuntu: Incomplete Bug description: I have an ubuntu 16.04 PC which was recently upgraded from 10.something to 12.04 and then to 16.04 (I think that is how it went, it was a two day thing with me checking on it now and again to say yes. Now that it is running on 16.04 I have noticed that when I left the PC for a while it locked up. The display was off, the power light on the tower solidly on and the keyboard unresponsive. The Num Lock light was lit but would not respond to key presses, nor would the Caps Lock or Scroll Lock lights. No key presses or short press of a power light would change the system state. The only thing I could do while sat at the PC was hold the power button in to force a power off. When the PC was powered back on everything seemed to be OK. I thought it might be a problem with suspending the PC. I was able to do that manually though. The display went off, the tower fans went quiet and the power light started to blink. Pressing keyboard keys did nothing but a short press of the power button brought the system back online. The only problem being that the Wi-Fi was lost until I restarted the system, not ideal but better than frozen. I attempted to disable the automatic suspend option from the Settings menu but the system still ended up in the frozen state. Next to completely disable suspend by creating a /etc/polkit-1/localauthority/50-local.d/com.ubuntu.disable- suspend.pkla file as suggested at http://askubuntu.com/questions/452908/how-to-disable-suspend-in-14-04 but the system still ended up frozen. That leaves me to think it was the act of going into the Monitor Disabled state which caused the issue. So I started to report an ubuntu-bug and here I am typing out this description of what I remember doing. $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Memory 2.0 GiB Processor Intel Core 2 Duo CPU E4400 @ 2.00 GHz x 2 Graphics Gallium 0.4 on ATI RV515 OS type 64-bit Disk 96.6 GB If there are any further diagnostic steps I can take please let me know. This is a personal machine so I can do most things to it. I am a c/c++ software engineer by trade so although I am not great with the GNU Debugger I can do most things with a bit of instruction. I do not do much Ubuntu or Kernel work so links to getting started guides for how to do anything more specific that git clone or make would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Nov 17 13:29:59 2016 DistUpgraded: 2016-11-16 07:49:36,758 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7183] (prog-if 00 [VGA controller]) Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0d02] Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0d03] InstallationDate: Installed on 2014-02-03 (1017 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) LightdmGreeterLogOld: (lightdm-gtk-greeter:1176): GLib-CRITICAL **: g_shell_parse_argv: assertion 'command_line != NULL' failed ** (lightdm-gtk-greeter:1176): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/sessions': No such file or directory **
[Desktop-packages] [Bug 1987875] [NEW] Cmore streaming service not working well after recent updates
You have been subscribed to a public bug: I have tried with several computers and version 18.04 20.04 and 22.04 after last update Cmore is not playing well. The picture and sound is interrupting, so the streaming is not good. I think it is the last version of widevine decryption is doing it, because youtube and dr.dk works fine. The laptop is also getting very very hot, and in the end it just stop. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bot-comment focal jammy -- Cmore streaming service not working well after recent updates https://bugs.launchpad.net/bugs/1987875 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- 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 1654093] Re: boot loop
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1654093 Title: boot loop Status in Ubuntu: Incomplete Bug description: I have a dual boot system running with Windows7 and Ubuntu LTS 16.04. The first attempt to boot into ubuntu every time ends up with a boot loop with a colored magenta blank screen. After rebooting and then entering ubuntu as OS choice, an error about an "Intel pch overrun error" (error not mentioned exactly as displayed because I dont understand the error category or content) is shown but eventually after sometime ubuntu boots up normally. The next time when the system boots up, the above process have to be repeated. I am not very educated in Linux operations or grub operations but can understand and implement changes if guided. Also, Ubuntu taking unusually long time to boot up. Is it bcoz I have quite a few applications installed? But I don't have much startup applications set up? Please advice. This is the first time I am reporting a bug and pardon me for using xdiagnose for this (if I should not have used it). I don't know what bug or bugs is/are shown by xdiagnose either. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 5 03:41:24 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2016-12-17 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 003: ID 0ac8:3450 Z-Star Microelectronics Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=dc488953-1b39-46a7-b2b1-c8b099adee06 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1107 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1107:bd02/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
[Desktop-packages] [Bug 1575128] Re: unity dialogues split between 2 monitors
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1575128 Title: unity dialogues split between 2 monitors Status in gtk+3.0 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: Since upgrading from Ubuntu 15.10 to 16.04, Unity is now shown across both my monitors in a hard to use manner: unity dialogues, such as the log-out and shutdown popups, are displayed centered between both monitors, so the left half is on one monitor, and the right half on another. Also, the unity top panel indicators and clock used to be on both monitors, but are now only on the right monitor. More info since it is likely relevant: I have a Dell laptop with an NVidia Prime GPU and Intel built-in GPU. This laptop has always been trouble configuring for dual monitors. The nvidia-settings controls only shows one monitor, though it is supposed to show two. I have never been able to get a working xorg.conf for the two monitors, despited 2 days of trying (and I am a software developer well versed in reading docs). The instructions in the nvidia docs simply don't work as stated for this hardware (Dell XPS 17 L702X). Purging all graphics settings doesn't help. Upgrading to a newer nvidia driver didn't help (I've tried the latest official nvidia package as well as one newer). As a result, I've been using an xrandr command and compiz display settings since Ubuntu 15.10. This worked perfectly in 15.10. But, as stated, the unity top panel and dialogues are not working properly in 16.04. I tried Nvidia 361.42 and 364.19 from the PPA at http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu. The xrandr command in use is: xrandr --fb 3520x1080 --output HDMI-0 --preferred --primary --mode 1920x1080 --pos 0x0 --panning 3520x1080+0+0/3520x1080+0+0/0/0/-3520/0 --output LVDS-1 --mode 1600x900 --pos 1920x180 --panning 0x0 (I know the fb sets up a wide virtual screen, but as stated, in 15.10, that worked perfectly for unity) In compiz display settings I have the following "Outputs" set: 1920x1080+0+0 1600x900+1920+180 It would appear in 16.04, Unity ignores the compiz outputs whereas in 15.10 it does not. But that's just a guess. Sorry I cannot get a screenshot of the dialogues. They seem to block Ubuntu's screenshot program due to their modal nature. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 364.19 Tue Apr 19 14:44:55 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 26 07:01:26 2016 DistUpgraded: 2016-04-25 10:00:42,012 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.2.0-35-generic, x86_64: installed bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-364, 364.19, 4.4.0-21-generic, x86_64: installed vboxhost, 5.0.18, 4.2.0-35-generic, x86_64: installed vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0571] NVIDIA Corporation GF116M [GeForce GT 550M] [10de:1246] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell
[Desktop-packages] [Bug 1604382] Re: problem with sleep, suspend & hibernate (back light supected)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1604382 Title: problem with sleep, suspend & hibernate (back light supected) Status in Ubuntu: Incomplete Bug description: When laptop lid is closed, the power, hdd & wifi led remain blue. when the lid is re-opened, the screen remain blank (black no backlight at all) Note: this happens across windows (except the oem windows 8.0 home edition that came with the laptop), Debian, CentOS and now Ubuntu. The laptop is a Medion Akoya p7817 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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: Tue Jul 19 13:02:30 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Pegatron 3rd Gen Core processor Graphics Controller [1b0a:20e4] Subsystem: Pegatron GK107M [GeForce GT 730M] [1b0a:20e4] InstallationDate: Installed on 2016-07-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Medion Akoya P7817 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=2023bd09-71bf-4555-bc6b-dd88d2d9e0fa ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 509 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Akoya P7817 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr509:bd01/23/2013:svnMedion:pnAkoyaP7817:pvr1.0:rvnMedion:rnAkoyaP7817:rvr1.0:cvnMedion:ct10:cvr1.0: dmi.product.name: Akoya P7817 dmi.product.version: 1.0 dmi.sys.vendor: Medion version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 19 12:42:33 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1604382/+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 1914821] Re: Disks won't execute
Thank you for taking the time to report this bug and helping to make Ubuntu better. If this is till an issue then please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1914821 and then change the status of the bug report back to 'New'. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1914821 Title: Disks won't execute Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: a@a-desktop:~$ gnome-disks (gnome-disks:11342): GNOME-Disks-ERROR **: 14:09:11.170: Error getting udisks client: Timeout was reached Trace/breakpoint trap (core dumped) a@a-desktop:~$ a@a-desktop:~$ uname -a Linux a-desktop 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux a@a-desktop:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1914821/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
Fixed upstream in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1548259 and in the patch for mutter 42: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2487.patch ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-upstream -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1988625] Re: Left-over cursor visible on second screen
Also fixed in the patch for mutter 42: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2487.patch ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-upstream -- 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/1988625 Title: Left-over cursor visible on second screen Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: This sounds like (Fix Released) #1724977, but seems to happen on extra screens. When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+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 1975745] Re: Cursor change in full screen application causes recursive loop
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm moving this to gnome-shell so that this issue is brought to the attention of the Desktop Team. However, for me using Chrome and Firefox your .mp4 attachment doesn't illustrate the problem that you were or maybe are still seeing. ** Tags added: jammy ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1975745 Title: Cursor change in full screen application causes recursive loop Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version: Ubuntu 22.04 LTS What happens: When my mouse cursor changes in a full screen application (while hovering over something) (like the root prompt or the search bar in the application menu) it repeats the action over and over til I crash my computer. (This problem does not seem to occur when I play a video in full screen.) Expected behavior: The cursor should change to the new one and stay like this until a new cursor change is required. I've attached a video for better understanding of the problem. (I can't record my screen when this happens because the file won't save, so I had to record it via my phone, sorry for that) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975745/+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 1975745] [NEW] Cursor change in full screen application causes recursive loop
You have been subscribed to a public bug: Ubuntu version: Ubuntu 22.04 LTS What happens: When my mouse cursor changes in a full screen application (while hovering over something) (like the root prompt or the search bar in the application menu) it repeats the action over and over til I crash my computer. (This problem does not seem to occur when I play a video in full screen.) Expected behavior: The cursor should change to the new one and stay like this until a new cursor change is required. I've attached a video for better understanding of the problem. (I can't record my screen when this happens because the file won't save, so I had to record it via my phone, sorry for that) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment jammy -- Cursor change in full screen application causes recursive loop https://bugs.launchpad.net/bugs/1975745 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 1989102] [NEW] Dragging windows is very slow and choppy
Public bug reported: 1. UBUNTU VERSION Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy 2. PACKAGE VERSION gdm3: Installed: 42.0-1ubuntu7 Candidate: 42.0-1ubuntu7 Version table: *** 42.0-1ubuntu7 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. WHAT I EXPECTED TO HAPPEN When dragging a window, the window follows the mouse cursor smoothly. 4. WHAT ACTUALLY HAPPENS Dragging windows is extremely slow and choppy. You grab a window and start to drag it. For a very brief moment, around .5s, the window moves smoothly. Then it stops being re-drawn for around 3s. Then there's another brief .5s of smoothness, and the cycle repeats. This occurs with all windows. 5. ADDITIONAL INFORMATION - I was previously on Ubuntu 18.04 and have just upgraded to 22.04. - I am using the nVidia proprietary driver: NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 - I have three monitors. Two standard 60Hz monitors, and one Gigabyte G27Q Freesync compatible 144Hz monitor (I have tried all refresh settings for the monitor, and it makes no difference). - I am running X and do not have the option on login to switch to Wayland (no cog shown). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:41:49 2022 InstallationDate: Installed on 2021-01-05 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-05 (33 days ago) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2022-09-08T10:42:52.395463 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1989102 Title: Dragging windows is very slow and choppy Status in gdm3 package in Ubuntu: New Bug description: 1. UBUNTU VERSION Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy 2. PACKAGE VERSION gdm3: Installed: 42.0-1ubuntu7 Candidate: 42.0-1ubuntu7 Version table: *** 42.0-1ubuntu7 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. WHAT I EXPECTED TO HAPPEN When dragging a window, the window follows the mouse cursor smoothly. 4. WHAT ACTUALLY HAPPENS Dragging windows is extremely slow and choppy. You grab a window and start to drag it. For a very brief moment, around .5s, the window moves smoothly. Then it stops being re-drawn for around 3s. Then there's another brief .5s of smoothness, and the cycle repeats. This occurs with all windows. 5. ADDITIONAL INFORMATION - I was previously on Ubuntu 18.04 and have just upgraded to 22.04. - I am using the nVidia proprietary driver: NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 - I have three monitors. Two standard 60Hz monitors, and one Gigabyte G27Q Freesync compatible 144Hz monitor (I have tried all refresh settings for the monitor, and it makes no difference). - I am running X and do not have the option on login to switch to Wayland (no cog shown). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:41:49 2022 InstallationDate: Installed on 2021-01-05 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-05 (33 days ago) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2022-09-08T10:42:52.395463 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1989102/+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 1988315]
Just confirmed that updating gnome-shell-extension-appindicator to the code in the "ubuntu/jammy" branch makes the crash disappear -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Fedora: Confirmed Bug description: After upgrading to kinetic gnome-shell is crashing on start when using wayland. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 10:28:31 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso InstallationDate: Installed on 2020-05-18 (834 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20200511-12:31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-05-11T08:18:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1988625] Re: Left-over cursor visible on second screen
Fix proposed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2620 but I'll also include it in the next triple buffering update. -- 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/1988625 Title: Left-over cursor visible on second screen Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: This sounds like (Fix Released) #1724977, but seems to happen on extra screens. When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+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 1988667] Re: Quito isn't displayed as choice for time zone
Thank you for your bug report, the choice of the city to display for Ecuador is coming from tzdata, you can see an old similar report on https://bugzilla.redhat.com/show_bug.cgi?id=131320 for example ** Changed in: systemsettings (Ubuntu) Status: New => Invalid ** No longer affects: systemsettings (Ubuntu) ** Bug watch added: Red Hat Bugzilla #131320 https://bugzilla.redhat.com/show_bug.cgi?id=131320 ** Package changed: gnome-control-center (Ubuntu) => tzdata (Ubuntu) ** Changed in: tzdata (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1988667 Title: Quito isn't displayed as choice for time zone Status in tzdata package in Ubuntu: Opinion Bug description: On Ubuntu 22.04.1 (and 20.04.x) there is no option available for Quito. On GNOME Settings > Date & Time > (A map is displayed) Type Quito on the search field. There are no matches. On KDE == System Settings > Regional Settings > Date & Time > Time Zone When searching for the time zone I enter: Quito There are no matches. The entries for Ecuador are Galapagos Islands and Guayaquil. Quito is the capital city of Ecuador, whereas Guayaquil is the second biggest. It makes no sense for the capital not to be displayed in the city list, but to have the second. It is akin to have Marseille as the main choice for France instead of Paris. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1988667/+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 1989067] Re: gnome-control-center Segmentation fault (core dumped)
The output to `dpkg -l dbus-x11`: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= un dbus-x11 (no description available) The system log is included in the attachments. ** Attachment added: "journalctl -b 0 > systemlog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989067/+attachment/5614594/+files/systemlog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1989067 Title: gnome-control-center Segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When i try to open the settings, i see the loading cursor but noting opens, in the system monitor gnome control center appears briefly but quickly disappears. When i try to run it in the terminal using `gnome- control-center` it returns "Segmentation fault (core dumped)", same with `gnome-control-center display` or `gnome-control-center --version` which is why i could only specify the gnome-shell version. I have tried: `sudo apt update; sudo apt dist-upgrade`, `sudo apt install --reinstall gnome-control-center`, `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system restart (this worked temporarily like 3 times but is no longer effective), `gsettings reset org.gnome.ControlCenter last-panel` `dconf reset -f /org/gnome/control-center/` When i run `sudo gnome-control-center` i can briefly see the settings window and get this warning after it crashes almost immediately: (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Error creating rfkill proxy: (null) Segmentation fault ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 08:56:05 2022 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989067/+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 1989054] Re: Brightness bar not working properly on HP EliteBook 8460p
** Summary changed: - Brightness bar not working properly + Brightness bar not working properly on HP EliteBook 8460p ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989054 Title: Brightness bar not working properly on HP EliteBook 8460p Status in linux package in Ubuntu: New Bug description: My brightness doesn't change and stays at lowest brightness level till about 70% of the slider, after that the brightness starts increasing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:47:44 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.release: 15.8 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.08 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU147038F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.69 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SN119UC#ABA dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989054/+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 1989054] Re: Brightness bar not working properly
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989054 Title: Brightness bar not working properly on HP EliteBook 8460p Status in linux package in Ubuntu: New Bug description: My brightness doesn't change and stays at lowest brightness level till about 70% of the slider, after that the brightness starts increasing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:47:44 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.release: 15.8 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.08 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU147038F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.69 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SN119UC#ABA dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989054/+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 1989067] Re: gnome-control-center Segmentation fault (core dumped)
Thank you for your bug report. What's the output of $ dpkg -l dbus-x11 could you also include a 'journalctl -b 0' log from the system? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1989067 Title: gnome-control-center Segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When i try to open the settings, i see the loading cursor but noting opens, in the system monitor gnome control center appears briefly but quickly disappears. When i try to run it in the terminal using `gnome- control-center` it returns "Segmentation fault (core dumped)", same with `gnome-control-center display` or `gnome-control-center --version` which is why i could only specify the gnome-shell version. I have tried: `sudo apt update; sudo apt dist-upgrade`, `sudo apt install --reinstall gnome-control-center`, `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system restart (this worked temporarily like 3 times but is no longer effective), `gsettings reset org.gnome.ControlCenter last-panel` `dconf reset -f /org/gnome/control-center/` When i run `sudo gnome-control-center` i can briefly see the settings window and get this warning after it crashes almost immediately: (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Error creating rfkill proxy: (null) Segmentation fault ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 08:56:05 2022 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989067/+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 1989054] [NEW] Brightness bar not working properly
You have been subscribed to a public bug: My brightness doesn't change and stays at lowest brightness level till about 70% of the slider, after that the brightness starts increasing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:47:44 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.release: 15.8 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.08 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU147038F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.69 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SN119UC#ABA dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Brightness bar not working properly https://bugs.launchpad.net/bugs/1989054 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1875671] Re: wayland: desktop folder missing in Nautilus sidebar
** Tags added: kinetic -- 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/1875671 Title: wayland: desktop folder missing in Nautilus sidebar Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Using Wayland session nautilus home window does not show Desktop folder in sidebar while is dispayed using X11 session. see attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 Uname: Linux 5.7.0-050700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 17:24:45 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 852)' InstallationDate: Installed on 2020-04-23 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875671/+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 1185468] Re: [gsfonts] Fonts include copyrighted adobe fragment all right reserved
** Changed in: gsfonts (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsfonts in Ubuntu.
https://bugs.launchpad.net/bugs/1185468
Title:
[gsfonts] Fonts include copyrighted adobe fragment all right reserved
Status in gsfonts package in Ubuntu:
Confirmed
Status in gsfonts package in Debian:
Fix Released
Bug description:
Imported from Debian bug http://bugs.debian.org/694320:
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308
This package include copyrighted font hinting from adobe.
For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10 adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug 2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright: Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright: 2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments
--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[ {}
{}
{}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsfonts/+bug/1185468/+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 1875671] Re: wayland: desktop folder missing in Nautilus sidebar
still broken in 22.10 -- 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/1875671 Title: wayland: desktop folder missing in Nautilus sidebar Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Using Wayland session nautilus home window does not show Desktop folder in sidebar while is dispayed using X11 session. see attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 Uname: Linux 5.7.0-050700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 17:24:45 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 852)' InstallationDate: Installed on 2020-04-23 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875671/+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 1989067] [NEW] gnome-control-center Segmentation fault (core dumped)
Public bug reported: When i try to open the settings, i see the loading cursor but noting opens, in the system monitor gnome control center appears briefly but quickly disappears. When i try to run it in the terminal using `gnome- control-center` it returns "Segmentation fault (core dumped)", same with `gnome-control-center display` or `gnome-control-center --version` which is why i could only specify the gnome-shell version. I have tried: `sudo apt update; sudo apt dist-upgrade`, `sudo apt install --reinstall gnome-control-center`, `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system restart (this worked temporarily like 3 times but is no longer effective), `gsettings reset org.gnome.ControlCenter last-panel` `dconf reset -f /org/gnome/control-center/` When i run `sudo gnome-control-center` i can briefly see the settings window and get this warning after it crashes almost immediately: (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Error creating rfkill proxy: (null) Segmentation fault ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 08:56:05 2022 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Description changed: - I am using Ubuntu 22.04.1 LTS - with GNOME Shell version 42.4 - When i try to open the settings, i see the loading cursor but noting opens, in the system monitor gnome control center appears briefly but quickly disappears. When i try to run it in the terminal using `gnome- control-center` it returns "Segmentation fault (core dumped)", same with `gnome-control-center display` or `gnome-control-center --version` which is why i could only specify the gnome-shell version. I have tried: `sudo apt update; sudo apt dist-upgrade`, `sudo apt install --reinstall gnome-control-center`, `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system restart (this worked temporarily like 3 times but is no longer effective), `gsettings reset org.gnome.ControlCenter last-panel` `dconf reset -f /org/gnome/control-center/` When i run `sudo gnome-control-center` i can briefly see the settings window and get this warning after it crashes almost immediately: (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Error creating rfkill proxy: (null) Segmentation fault ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 08:56:05 2022 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1989067 Title: gnome-control-center Segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: New Bug description: When i try to open the settings, i see the loading cursor but noting opens, in the system monitor gnome control center appears briefly but quickly disappears. When i try to run it in the terminal using `gnome- control-center` it returns "Segmentation fault (core dumped)", same with `gnome-control-center display` or `gnome-control-center --version` which is why i could only specify the gnome-shell version. I have tried: `sudo apt update; sudo apt dist-upgrade`, `sudo apt install --reinstall gnome-control-center`, `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system restart (this worked temporarily like 3 times but is no longer effective), `gsettings reset org.gnome.ControlCenter last-panel` `dconf reset -f /org/gnome/control-center/` When i run `sudo gnome-control-center` i can briefly see the settings window and get this warning after it crashes almost immediately: (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
[Desktop-packages] [Bug 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
could you clean /var/crash, trigger the issue again and resubmit the crash? the bot failing to recover debug information on the current report -- 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/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1989064] Re: kde get blocked
Please describe the problem you would like to report in more detail. And if you have multiple problems to report then please ensure each is logged as a separate bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1989064 Title: kde get blocked Status in Ubuntu: Incomplete Bug description: problems with kde and kernels, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_113_127_generic_89 nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.226.00 Wed Sep 8 13:57:02 UTC 2021 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 8 08:40:53 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 7906, 5.4.0-113-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 418.226.00, 5.4.0-113-generic, x86_64: installed r8168, 8.045.08, 5.4.0-113-generic, x86_64: installed rts_pstor, 1.11: added virtualbox, 5.2.42, 5.4.0-113-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fa] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fa] InstallationDate: Installed on 2019-03-16 (1271 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-113-generic root=UUID=26bfb978-0c46-41b4-be00-6d89ad9ff16d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 038M0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn038M0M:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1989064/+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 1988625] Re: Left-over cursor visible on second screen
** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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/1988625 Title: Left-over cursor visible on second screen Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: This sounds like (Fix Released) #1724977, but seems to happen on extra screens. When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
I can finally reproduce this using a dual GPU dual monitor setup (Intel + AMD). -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1988625] Re: Left-over cursor visible on second screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1988625 Title: Left-over cursor visible on second screen Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: This sounds like (Fix Released) #1724977, but seems to happen on extra screens. When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+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 1989064] [NEW] kde get blocked
Public bug reported: problems with kde and kernels, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_113_127_generic_89 nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.226.00 Wed Sep 8 13:57:02 UTC 2021 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 8 08:40:53 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 7906, 5.4.0-113-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 418.226.00, 5.4.0-113-generic, x86_64: installed r8168, 8.045.08, 5.4.0-113-generic, x86_64: installed rts_pstor, 1.11: added virtualbox, 5.2.42, 5.4.0-113-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fa] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fa] InstallationDate: Installed on 2019-03-16 (1271 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-113-generic root=UUID=26bfb978-0c46-41b4-be00-6d89ad9ff16d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 038M0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn038M0M:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu possible-manual-nvidia-install resolution ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989064 Title: kde get blocked Status in xorg package in Ubuntu: New Bug description: problems with kde and kernels, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_113_127_generic_89 nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.226.00 Wed Sep 8 13:57:02 UTC 2021 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 8 08:40:53 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 7906, 5.4.0-113-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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
