[Desktop-packages] [Bug 1551776] Re: Calendar: high cpu usage while open
This is still present for me in Ubuntu 20.04, so I do not think it is resolved. Moreover, through time memory usage of the app grows substantially. I suspect there is a memory leak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1551776 Title: Calendar: high cpu usage while open Status in GNOME Calendar: Fix Released Status in gnome-calendar package in Ubuntu: Triaged Bug description: STEPS: 1. Fresh flash of 16.04 daily 2. Open calendar 3. Open top 4. Note the 3 apps at the top of the hit list EXPECTED: I expect to see a small spike in cpu usage as a app open and then it to lower to a reasonable level ACTUAL: Calendar uses 22% X 41% Compiz 35% This cripples even a relatively performent machine See screenshots To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1551776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770886] Re: gnome-calendar runs in background and uses a lot of memory
This is still a problem in Ubuntu 20.04. I am also noticing high CPU usage and UI often triggers "this app is frozen, kill it?" message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1770886 Title: gnome-calendar runs in background and uses a lot of memory Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Some minutes after I logged in I realized that gnome-calendar runs in the background and uses more than 400MB memory. I don't launched it. Is it normal? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 12 20:39:27 2018 InstallationDate: Installed on 2017-10-20 (204 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to bionic on 2018-04-15 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1770886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
I can confirm this is not working on Bionic. vainfo output: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 error: failed to resolve wl_drm_interface(): /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823857] Re: Backport to bionic a patch for improved fractional scaling
** Tags removed: removal-candidate verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1823857 Title: Backport to bionic a patch for improved fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Bug description: * Impact In some cases after a configuration chang ethe "apply" button is not displayed * Test case On a multimonitor setup, go to settings -> display and change the monitors layout and zoom factor, following a change a "apply" button should be displayed * Regression potential The change is in the monitor configurations logic, just make sure that changing resolution/layouts work correctly and is restored are a logout/login cycle -- I have been debugging why I do not get "Apply" button in Displays view when my primary monitor is on the left of the external monitor, but it appears when it is on the right. I traced the problem down to this issue and patch: https://gitlab.gnome.org/GNOME/mutter/issues/412 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346 Reading this issue tracker I see that some issues people are reporting my be connected to this problem. I would suggest, if possible, that this patch is backported to Bionic and its version of gnome-control- center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823857] Re: Backport to bionic a patch for improved fractional scaling
Sorry for the delay. I have just now tested the package and can confirm that it works for me. I can resize/scale screens and move them around and I always get "apply" button I can use. -- 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/1823857 Title: Backport to bionic a patch for improved fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Bug description: * Impact In some cases after a configuration chang ethe "apply" button is not displayed * Test case On a multimonitor setup, go to settings -> display and change the monitors layout and zoom factor, following a change a "apply" button should be displayed * Regression potential The change is in the monitor configurations logic, just make sure that changing resolution/layouts work correctly and is restored are a logout/login cycle -- I have been debugging why I do not get "Apply" button in Displays view when my primary monitor is on the left of the external monitor, but it appears when it is on the right. I traced the problem down to this issue and patch: https://gitlab.gnome.org/GNOME/mutter/issues/412 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346 Reading this issue tracker I see that some issues people are reporting my be connected to this problem. I would suggest, if possible, that this patch is backported to Bionic and its version of gnome-control- center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823857] Re: Backport to bionic a patch for improved fractional scaling
I made this patch for myself and it solved the problem. ** Patch added: "scaling-displays.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+attachment/5254413/+files/scaling-displays.patch -- 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/1823857 Title: Backport to bionic a patch for improved fractional scaling Status in gnome-control-center package in Ubuntu: New Bug description: I have been debugging why I do not get "Apply" button in Displays view when my primary monitor is on the left of the external monitor, but it appears when it is on the right. I traced the problem down to this issue and patch: https://gitlab.gnome.org/GNOME/mutter/issues/412 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346 Reading this issue tracker I see that some issues people are reporting my be connected to this problem. I would suggest, if possible, that this patch is backported to Bionic and its version of gnome-control- center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823857] [NEW] Backport to bionic a patch for improved fractional scaling
Public bug reported: I have been debugging why I do not get "Apply" button in Displays view when my primary monitor is on the left of the external monitor, but it appears when it is on the right. I traced the problem down to this issue and patch: https://gitlab.gnome.org/GNOME/mutter/issues/412 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346 Reading this issue tracker I see that some issues people are reporting my be connected to this problem. I would suggest, if possible, that this patch is backported to Bionic and its version of gnome-control-center. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1823857 Title: Backport to bionic a patch for improved fractional scaling Status in gnome-control-center package in Ubuntu: New Bug description: I have been debugging why I do not get "Apply" button in Displays view when my primary monitor is on the left of the external monitor, but it appears when it is on the right. I traced the problem down to this issue and patch: https://gitlab.gnome.org/GNOME/mutter/issues/412 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346 Reading this issue tracker I see that some issues people are reporting my be connected to this problem. I would suggest, if possible, that this patch is backported to Bionic and its version of gnome-control- center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733727] Re: visual-bell-type frame-flash does not work
I can confirm that in 18.04 and Wayland this works as expected and only the frame flashes. -- 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/1733727 Title: visual-bell-type frame-flash does not work Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I tried to enable visual bell, frame-flash type, by doing: gsettings set org.gnome.desktop.wm.preferences visual-bell true gsetings set org.gnome.desktop.wm.preferences visual-bell-type 'frame-flash' The issue is that while visual bell gets enabled, it always flashes the whole screen. I am trying this by pressing backspace in the terminal app. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 16:08:47 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-20 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1733727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751545] [NEW] In Ubuntu artful, ther is no nopasswdlogin group anymore
Public bug reported: In Ubuntu artful, there is no nopasswdlogin group anymore. It seems also that the option to configure user to not have a password is missing. Moreover, in the login screen, "login" button is disabled if the password input box is empty, so even if I force set an empty password, it cannot be used. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1751545 Title: In Ubuntu artful, ther is no nopasswdlogin group anymore Status in accountsservice package in Ubuntu: New Bug description: In Ubuntu artful, there is no nopasswdlogin group anymore. It seems also that the option to configure user to not have a password is missing. Moreover, in the login screen, "login" button is disabled if the password input box is empty, so even if I force set an empty password, it cannot be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1751545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743736] Re: In overview, windows from all workspaces are shown for the second display
It seems this one is reporting the issue: https://bugzilla.gnome.org/show_bug.cgi?id=652580 There are few patches, but it does not like fixed. So I do not care so much about switcher than the behavior described: Observed behavior: Actvities overview (got by pressing the logo key), however, handles the two monitors differently: for the primary monitor, it exposes only windows on the current workspace, but for the external monitor, it always shows all windows on all workspaces. Expected behavior: when /desktop/gnome/shell/windows/workspaces_only_on_primary is false, both monitors should behave the same, and both should show only windows on the current workspace. ** Bug watch added: GNOME Bug Tracker #652580 https://bugzilla.gnome.org/show_bug.cgi?id=652580 -- 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/1743736 Title: In overview, windows from all workspaces are shown for the second display Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have disabled workspaces on primary display only, and I have enabled workspaces to span displays, in tweak tool. Now things mostly work how I expect. Windows are isolated to the workspace they are and I can move them between displays (monitors). The issue is if I go into an overview mode. Then, for the primary display, I see only windows from my current workspace. But for the secondary display, I see windows from all workspaces being shown in the overview mode. I would expect that only the windows from the current workspace are shown also on the secondary display in the overview mode. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 02:19:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-20 (57 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743736] [NEW] In overview, windows from all workspaces are shown for the second display
Public bug reported: I have disabled workspaces on primary display only, and I have enabled workspaces to span displays, in tweak tool. Now things mostly work how I expect. Windows are isolated to the workspace they are and I can move them between displays (monitors). The issue is if I go into an overview mode. Then, for the primary display, I see only windows from my current workspace. But for the secondary display, I see windows from all workspaces being shown in the overview mode. I would expect that only the windows from the current workspace are shown also on the secondary display in the overview mode. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 02:19:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-20 (57 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- 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/1743736 Title: In overview, windows from all workspaces are shown for the second display Status in gnome-shell package in Ubuntu: New Bug description: I have disabled workspaces on primary display only, and I have enabled workspaces to span displays, in tweak tool. Now things mostly work how I expect. Windows are isolated to the workspace they are and I can move them between displays (monitors). The issue is if I go into an overview mode. Then, for the primary display, I see only windows from my current workspace. But for the secondary display, I see windows from all workspaces being shown in the overview mode. I would expect that only the windows from the current workspace are shown also on the secondary display in the overview mode. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 02:19:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-20 (57 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733727] [NEW] visual-bell-type frame-flash does not work
Public bug reported: I tried to enable visual bell, frame-flash type, by doing: gsettings set org.gnome.desktop.wm.preferences visual-bell true gsetings set org.gnome.desktop.wm.preferences visual-bell-type 'frame-flash' The issue is that while visual bell gets enabled, it always flashes the whole screen. I am trying this by pressing backspace in the terminal app. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 16:08:47 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-20 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1733727 Title: visual-bell-type frame-flash does not work Status in gnome-shell package in Ubuntu: New Bug description: I tried to enable visual bell, frame-flash type, by doing: gsettings set org.gnome.desktop.wm.preferences visual-bell true gsetings set org.gnome.desktop.wm.preferences visual-bell-type 'frame-flash' The issue is that while visual bell gets enabled, it always flashes the whole screen. I am trying this by pressing backspace in the terminal app. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 16:08:47 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-20 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681129] [NEW] debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch
Public bug reported: Running debsums on my machine report that /usr/lib/x86_64-linux- gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix the problem. (BTW, I cannot report this against the libgbm1 package, because Launchpad is saying that '"libgbm1" does not exist in Ubuntu.') ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.6 [modified: usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0] ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 8 11:44:48 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: isgx, 0.10, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) isgx, 0.10, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06fd] InstallationDate: Installed on 2016-05-02 (340 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 13-7359 ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=bc09f41a-6b3d-47f9-b01d-9ac1dce625eb ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0110N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0110N8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 23 08:37:58 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 34381 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu ** Package changed: mesa (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1681129 Title: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch Status in Ubuntu: New Bug description: Running debsums on my machine report that /usr/lib/x86_64-linux- gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix the problem. (BTW, I cannot report this against the libgbm1 package, because Launchpad is saying that '"libgbm1" does not exist in Ubuntu.') ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.6 [modified: usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0] ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 8 11:44:48 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: isgx, 0.10, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) isgx, 0.10, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06fd] InstallationDate: Installed on 2016-05-02 (340 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 13-7359 ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
